Choosing And Executing

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Choosing and Executing

The cost of searching for the perfect decision almost always exceeds the cost of making a "good enough" one and iterating. Scott McNealy, cofounder of Sun Microsystems, captured this asymmetry in a single observation: he spent far less energy worrying about making the right decision and far more ensuring that any decision he made turned out right. The distinction is not semantic. It relocates agency from the moment of choice -- where the entrepreneur has minimal control over future variables -- to the months of execution that follow, where nearly everything is within reach. Founders who internalise this shift stop treating decisions as bets to be perfected and start treating them as hypotheses to be tested, adapted, and driven to outcomes through disciplined follow-through.

The Toolkit

Technique 1: The Reversibility Test

Not all decisions deserve equal deliberation. Jeff Bezos famously divided choices into "one-way doors" (irreversible, high-stakes) and "two-way doors" (reversible, correctable). Most entrepreneurial decisions fall through the second door -- yet founders routinely treat them as though they are signing a blood oath.

The diagnostic question: If this decision proves wrong in six months, can the company course-correct without catastrophic loss? If yes, the decision is a two-way door. Make it quickly, monitor outcomes, and adjust.

Why founders over-deliberate on two-way doors:

• Identity attachment. The choice feels like it defines the founder, not just the venture.
• Anxiety amplification. Research by Francesca Gino demonstrates that anxiety makes people simultaneously more receptive to advice and less capable of distinguishing good advice from bad -- a dangerous combination that extends deliberation without improving quality.
• Perfectionism as procrastination. Waiting for the "objectively correct" answer is often a socially acceptable form of avoidance.

Reserve deep analysis for one-way doors: market exits, large capital commitments, equity dilution events. Everything else deserves the 70% rule.

Technique 2: The 70% Rule

If a decision has been analysed to the point where approximately 70% of the relevant information is in hand, make the call. The remaining 30% is unlikely to arrive before the cost of delay exceeds the value of marginal certainty.

When to apply the rule:

• The team has debated the same options across multiple meetings with no new data surfacing.
• The competitive landscape is shifting while internal deliberation continues.
• The decision maker's gut has already settled, but the rational mind insists on "one more data point."

When to override the rule:

• The decision is genuinely irreversible (shutting down a product line, terminating a co-founder relationship).
• The 70% of information gathered points in contradictory directions -- not ambiguous, but actively conflicting.
• Regulatory or legal constraints demand a higher evidentiary threshold.

Thomas Davenport suggests a meta-decision framework: decide how to decide. Assess importance, frequency, and urgency before allocating deliberation time. Rare, strategic, high-stakes choices merit extended analysis. Recurring, operational, reversible choices merit a clock -- and when the clock runs out, the decision is made.

Technique 3: Buying an Option

When neither committing nor abandoning is palatable, consider a third move: buy an option. Rather than acquiring a company, form a partnership. Rather than launching nationally, pilot in one city. Rather than hiring a full-time executive, engage a fractional one for ninety days. Options convert large, irreversible decisions into small, reversible experiments -- providing real-world data that no amount of spreadsheet modelling can replicate.

The discipline here is to treat the option as a learning vehicle, not as a permanent hedge against commitment. Every option must have an expiration date and explicit criteria for converting to a full commitment or walking away.

Technique 4: Post-Decision Implementation Protocol

A decision without an implementation plan is a wish. The moment a choice is finalised, the following elements must be articulated:

Communicate the decision before rumour fills the vacuum. Include the reasoning process, not merely the conclusion. Research consistently shows that perceived fairness of process predicts acceptance of outcome -- even among those who preferred a different option.

Technique 5: Transparency as Trust Architecture

Being transparent about how a decision was made is not a courtesy; it is a structural investment in trust. Liane Davey's work on organisational fairness identifies two dimensions that teams evaluate simultaneously: outcome fairness (did the result distribute burdens and benefits reasonably?) and process fairness (was the method of arriving at the result legitimate?).

The order-of-disclosure effect: Studies show that when people learn about the process before the outcome, process fairness dominates their satisfaction. When they learn the outcome first, outcome fairness dominates. The practical implication is clear: lead with process. Explain the criteria, the alternatives considered, and the trade-offs weighed before announcing the decision itself.

Transparency is especially critical when:

• A decision overrides the preference of a vocal stakeholder.
• Resources are being reallocated from one team or project to another.
• The founder is making a judgment call that cannot be fully supported by data.
• The decision involves equity, compensation, or role changes.

Technique 6: Handling Challenges to Decisions

Three patterns account for the majority of post-decision pushback:

1. "You didn't ask me." A stakeholder feels excluded from the process. The fix is proactive: define decision roles at the outset using frameworks such as RACI or RAPID. If someone was intentionally excluded, be prepared to explain why.

2. "I didn't say anything then, but I disagree now." Late-breaking dissent from someone who was present but silent. Establish the norm: silence denotes agreement. Those who wish to dissent must do so during the decision window, not after.

3. "I agreed, but I'm implementing something different." The most corrosive pattern. The person nominally endorsed the decision but quietly modifies execution to suit their own preference. Counter this with explicit milestones, a single accountable owner, and periodic checkpoints that compare actual implementation against the decision as made.

The one legitimate reason to reopen: new facts have emerged that materially alter the calculus. Changed opinions, second thoughts, or political manoeuvring do not qualify.

Technique 7: Defeating Second-Guessing

Second-guessing is not rigorous reassessment; it is anxiety wearing a rational costume. Sydney Finkelstein's research identifies its cost: a founder who second-guesses a hire actively undermines that hire's probability of success, creating a self-fulfilling prophecy that validates the original doubt.

The antidotes:

• Perspective calibration. Ask: what are the actual stakes of this decision? Many choices that consume disproportionate mental energy have surprisingly low consequence. Redirect attention to decisions that genuinely matter.
• Gut journalling. Maintain a log of past decisions and their outcomes. Over time, this record builds calibrated self-trust and reveals whether intuition is a reliable signal or a noisy one.
• Advisory polling. When doubt persists, consult two or three trusted advisers -- not for validation, but for perspective. The act of articulating the decision to another person often resolves the uncertainty before the adviser even responds.
• Scheduled review. Set a specific date to formally revisit the decision. Between now and that date, execute with full commitment. This converts open-ended rumination into bounded, productive monitoring.
• Process-outcome separation. Judge decisions by the quality of the process that produced them, not by the outcome that followed. A sound process that yields a bad outcome is not a bad decision -- it is a reminder that the world contains irreducible uncertainty. Confusing process quality with outcome quality is the hallmark of hindsight bias.

Prompts

Prompt 1 -- Paralysis Diagnostic:

I have been deliberating on [describe decision] for [time period]. List the information I already have versus the information I am still seeking. For each missing piece of information, estimate: (a) how long it will take to obtain, (b) how much it would change the decision if obtained, and (c) the cost of waiting. Then recommend whether to decide now or continue gathering data.

Prompt 2 -- Implementation Blueprint:

I have decided to [describe decision]. Draft an implementation plan that includes: a one-sentence decision statement, stakeholder notification list, milestone timeline, success criteria, escalation triggers, and the single accountable owner. Tailor it to a [stage] startup in [sector].

Prompt 3 -- Decision Communication Script:

I need to communicate [describe decision] to my team. Some members preferred a different option. Draft a communication that leads with the process used, explains the criteria and trade-offs, acknowledges the alternative viewpoints, and outlines next steps. Tone: direct, respectful, no hedging.

Prompt 4 -- Second-Guessing Audit:

I am second-guessing [describe past decision]. Walk me through: (1) the process I used to make it, (2) whether new facts have emerged that warrant revisiting, (3) whether my doubt is evidence-based or anxiety-driven, and (4) a recommended next action -- either recommit or reopen with specific new criteria.

Use Cases

The Feature Pivot That Stalled

A validation-stage SaaS founder has spent three months debating whether to pivot the core feature set based on user feedback. Metrics are mixed -- some cohorts respond well, others do not. The team has held four strategy sessions without resolution. Applying the 70% rule, the founder recognises that additional user interviews are unlikely to resolve the ambiguity. She buys an option instead: a 30-day A/B test running both feature sets simultaneously. The test provides real conversion data, and the team makes a definitive call within five weeks of the original deadlock. The cost of the test was trivial compared to the cost of three months of organisational drift.

The Hire Everyone Questioned

A growth-stage fintech founder hires a CTO from outside the industry, overriding the preference of several board members who favoured a candidate with sector-specific experience. Rather than letting the disagreement fester, he communicates the decision using the transparency protocol: he shares the evaluation criteria, the performance data from reference checks, and the strategic rationale for prioritising technical architecture skills over domain familiarity. He sets a 90-day review checkpoint. Two months in, early infrastructure improvements validate the choice, and the board members who initially objected acknowledge that the process was fair, even though their preferred outcome was not selected.

The Founder Who Could Not Stop Revisiting

An early-traction e-commerce founder finds herself re-examining every pricing decision within days of making it. She implements a gut journal: each decision is logged with the reasoning, the alternatives considered, and the expected outcome. After three months, she reviews the journal and discovers that 80% of her initial pricing calls were within 5% of what she later considered optimal. The journal transforms vague self-doubt into calibrated confidence, and her decision velocity doubles.

Anti-Patterns

The Consensus Trap. Waiting for unanimous agreement before acting is not thoroughness; it is abdication disguised as democracy. Consensus is a luxury of low-stakes decisions. For high-stakes choices, one person must own the call. Seeking input is wise; requiring permission from everyone is paralysing.

Transparency Theatre. Sharing the decision without sharing the reasoning. Announcing "we have decided to restructure the team" without explaining the criteria, alternatives, and trade-offs does not build trust -- it invites conspiracy theories. Transparency means process visibility, not just outcome notification.

The Perpetual Pilot. Using options and experiments as a permanent substitute for commitment. Buying an option is a tool for reducing uncertainty before a decision, not a strategy for avoiding decisions indefinitely. Every option must have an expiration date.

Outcome-Based Self-Flagellation. Judging a past decision harshly because the outcome was poor, without examining whether the process was sound. A founder who carefully evaluated three vendors, selected the best-qualified one, and still experienced a service failure did not make a bad decision. Punishing yourself for outcomes beyond your control trains you to avoid decisions, not to improve them.

The Silent Veto. Allowing a senior stakeholder to remain silent during deliberation and then reopen the decision after the fact. This pattern is organisational poison. It teaches the team that formal decision processes are performative and that real power operates through back channels.

By Stage

Output Template

markdownCopy code
# Decision Record: [Decision Title]

**Date:** [YYYY-MM-DD]
**Decision Owner:** [Name and role]
**Stage:** [idea / validation / early-traction / growth / scale]

## Decision Statement
[One sentence: what was decided and the primary rationale.]

## Context and Alternatives Considered
| Alternative | Key Advantage | Key Risk | Reason Not Selected |
|-------------|---------------|----------|---------------------|
| [Option A] | | | |
| [Option B] | | | |
| [Option C -- selected] | | | [N/A -- this was selected because...] |

## Process Used
- **Who was consulted:** [Names and roles]
- **Data reviewed:** [Key data sources]
- **Decision method:** [Founder call / team vote / advisory input / other]
- **Reversibility assessment:** [One-way door / two-way door]

## Implementation Plan
| Milestone | Owner | Deadline | Status |
|-----------|-------|----------|--------|
| [Stakeholder communication] | | | |
| [First execution step] | | | |
| [Checkpoint review] | | | |

## Success Criteria
- [Metric 1: target and measurement method]
- [Metric 2: target and measurement method]

## Escalation Triggers
- [Condition under which this decision should be revisited]

## Review Date
[Scheduled date for formal reassessment]

Related Skills

• Evaluating and Deciding -- The Clear Thinking framework's unified decision system covers criteria weighting, margin of safety, and the irreversibility test; this toolkit provides the complementary post-decision disciplines.
• Tough Decision Situations -- When the problem is not paralysis but genuinely bad options, failed consensus, wrong calls, or time pressure, this companion skill provides targeted techniques.
• Decision-Making Under Pressure -- Addresses the specific cognitive and emotional dynamics of high-stakes, time-compressed leadership decisions.
• Learning from Failure -- Extends the "extract the lesson" principle into a full organisational learning practice.
• Trust Equation -- The transparency techniques in this skill feed directly into the credibility and intimacy components of trust.
• Stoic Pragmatism -- The Stoic emphasis on decisive action and practical execution aligns with the commitment discipline that prevents decision paralysis and second-guessing.