Saying 'no' to product ideas is often contentious. At GitHub, the process is simplified by first 'seeking the truth'—rigorously assessing if an initiative aligns with the team's definition of success. If it doesn't, the 'no' becomes an objective, logical conclusion rather than a subjective or political decision.

When launching a new strategy, define the specific go/no-go decision criteria on paper from day one. This prevents "revisionist history" where success metrics are redefined later based on new fact patterns or biases. This practice forces discipline and creates clear accountability for future reviews.

The Navy's practice of rigorously defining 'world-class alignment metrics' (WHAMs) before a pilot begins is key. While startups might find it tedious, this process forces deep alignment on what winning looks like, ensuring the project delivers measurable, valuable outcomes for both sides.

To avoid "innovation theater," front-load the financial viability assessment to the very first stage gate. By asking about margins and P&L impact upfront, companies can kill 80% of unworkable, buzzword-driven projects before investing significant time and emotional energy.

Treat government programs as experiments. Define success metrics upfront and set a firm deadline. If the program fails to achieve its stated goals by that date, it should be automatically disbanded rather than being given more funding. This enforces accountability.

In biotech, early data is often ambiguous. Instead of judging programs on potential, leaders must prioritize based on the time and capital required to reach a clear 'yes' or 'no' outcome. Indefinite 'gray zone' projects drain resources that could fund a winner.

Instead of relying on serendipity, PureTech uses a structured process: 1) Identify unmet need, 2) Find a promising but flawed drug with human data, 3) Define the problem that held it back, 4) Design a solution to overcome it, and 5) Test the solution. This institutionalizes the innovation cycle for value creation.

To prevent engineers from going down a rabbit hole of endless improvements, teams must pre-define success criteria. When there's a clear, shared definition of the goal, it becomes easy to recognize when the objective is met and it's time to move on.

By centralizing resources (hub), PureTech can dispassionately kill failing programs and reallocate talent. This structural design counters the powerful emotional and financial pressure to continue that exists when a company's survival is tied to a single drug, as people's livelihoods aren't dependent on one program's success.