From b6da801b59dad642bd8f04d9c73d08e291824415 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Pinho?= Date: Fri, 31 Jan 2025 10:27:23 +0000 Subject: [PATCH 1/3] feat: new principle "Complete the Mission" A new principle about ownership --- README.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/README.md b/README.md index 85b2d63..bd2829e 100644 --- a/README.md +++ b/README.md @@ -9,6 +9,7 @@ The following is a list of core principles [epilot](https://epilot.cloud/) produ - [Freedom and Responsibility](#freedom-and-responsibility) - [Continuous Delivery](#continuous-delivery) - [Ownership: You build it, you run it](#ownership-you-build-it-you-run-it) +- [Complete the Mission](#complete-the-mission) - [Show, don’t tell: Deliver working software early and frequently.](#show-dont-tell-deliver-working-software-early-and-frequently) - [Every Week is Quality Week](#every-week-is-quality-week) - [Solutions over Problems](#solutions-over-problems) @@ -45,6 +46,22 @@ We organize and develop our software as small decoupled services, with named eng - **Speed** Continuous delivery with automated testing allows us to ship with confidence and deliver features our customers want, faster. - **Modular architecture** Keeping services small and decoupled helps keep our software easier to reason about and maintain while allowing diversity in tech choices. +## Complete the Mission + +With Freedom and Responsibility comes trust, and it's almost certain you will end up leading a squad or initiative at some point, with individuals around you to support. + +As a leader, people look up to you as an example, and you look up to them. It’s your job to set them up for success and ensure they have the focus and clarity to execute. + +At the same time, a leader must complete the mission—delivering results while balancing the long-term health of our codebase, user experience, and sustainability. This means making trade-offs between speed, quality, technical debt, and customer value, ensuring we don’t optimize for short-term wins at the cost of long-term failure. + +### Why? + +- **Ownership**: In the end, it’s your job to set the team up for success—not just today but in the long run. +- **Risk management**: You deeply care about the team, and sometimes you will have to make difficult decisions. Risks are necessary sometimes—but they should be taken deliberately, not recklessly. +- **Balance**: Fast execution matters, but so does avoiding technical debt, maintaining quality, and delivering a great user experience. Completing the mission means balancing all of these. +- **Accountability**: Risk is inherent in decision-making. When things go south, leaders don’t deflect blame—they step up and own the outcome. +- **Transparency**: A strong leader makes the mission clear, aligns the team around priorities, and ensures urgency without chaos. + ## Ownership: You build it, you run it We subscribe to this core principle of the DevOps movement. From fe69a40bee05483d8f5c8de8a9916351cc081198 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Pinho?= Date: Wed, 12 Mar 2025 13:02:38 +0000 Subject: [PATCH 2/3] Update README.md --- README.md | 15 ++------------- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index bd2829e..cf08bbe 100644 --- a/README.md +++ b/README.md @@ -48,19 +48,8 @@ We organize and develop our software as small decoupled services, with named eng ## Complete the Mission -With Freedom and Responsibility comes trust, and it's almost certain you will end up leading a squad or initiative at some point, with individuals around you to support. - -As a leader, people look up to you as an example, and you look up to them. It’s your job to set them up for success and ensure they have the focus and clarity to execute. - -At the same time, a leader must complete the mission—delivering results while balancing the long-term health of our codebase, user experience, and sustainability. This means making trade-offs between speed, quality, technical debt, and customer value, ensuring we don’t optimize for short-term wins at the cost of long-term failure. - -### Why? - -- **Ownership**: In the end, it’s your job to set the team up for success—not just today but in the long run. -- **Risk management**: You deeply care about the team, and sometimes you will have to make difficult decisions. Risks are necessary sometimes—but they should be taken deliberately, not recklessly. -- **Balance**: Fast execution matters, but so does avoiding technical debt, maintaining quality, and delivering a great user experience. Completing the mission means balancing all of these. -- **Accountability**: Risk is inherent in decision-making. When things go south, leaders don’t deflect blame—they step up and own the outcome. -- **Transparency**: A strong leader makes the mission clear, aligns the team around priorities, and ensures urgency without chaos. +Execution matters more than details. If you don’t deliver, nothing else counts. +There’s no credit for style, no excuses for setbacks, and no rewards for stopping short. This principle is about relentless focus—setting a clear mission and doing whatever it takes to achieve it. Perfection isn’t the goal; results are. ## Ownership: You build it, you run it From fb31e672d91942d053bfe05d2fac11f5b5e87dcc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Pinho?= Date: Fri, 14 Mar 2025 12:07:05 +0000 Subject: [PATCH 3/3] Keeping Complete the Mission but making it clearer to avoid overlap with Progress over Perfection --- README.md | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cf08bbe..ddca6a4 100644 --- a/README.md +++ b/README.md @@ -48,8 +48,19 @@ We organize and develop our software as small decoupled services, with named eng ## Complete the Mission -Execution matters more than details. If you don’t deliver, nothing else counts. -There’s no credit for style, no excuses for setbacks, and no rewards for stopping short. This principle is about relentless focus—setting a clear mission and doing whatever it takes to achieve it. Perfection isn’t the goal; results are. +Execution matters more than the details. If you don’t deliver, nothing else counts. + +Ownership is key—if something is your responsibility, it gets done. There’s no credit for effort alone, no excuses for setbacks, and no rewards for stopping short. This principle is about relentless focus on the outcome—setting a clear mission and ensuring it is achieved. + • We take **full responsibility** for what we own and see it through to the end. + • We **solve problems, not just highlight them**—delays and obstacles don’t excuse failure. + • We don’t celebrate “almost done”—**real impact comes from delivery, not effort.** + +When faced with challenges, we find a way forward, take responsibility, and make it happen. Delivering results is what matters, whether in engineering, operations, product, or leadership. + +### Why? +- **Ownership drives impact**: If no one owns a problem, it doesn’t get solved. Taking ownership means stepping up and ensuring real progress happens. +- **Accountability creates trust**: Teams that take responsibility—both for successes and failures—are the ones people rely on. +- **Delivery is the only measure of execution**: Ideas, discussions, and partial work mean nothing if they don’t translate into **real results**. ## Ownership: You build it, you run it