Founder prioritization

Purpose

Force the company to work on the earliest constraint to survival or growth, finish a measurable outcome, and deliberately stop everything that competes with it.

Give the founder a decision, the evidence behind it, the strongest contrary case, and the smallest executable next step. Do not produce generic encouragement or a long menu of tactics.

When to Trigger

Use this skill according to the frontmatter description. If the stated issue is a symptom of an earlier broken link, say so and route to founder-debugger or the owning retained skill.

Inputs Needed

• Company stage and default-alive status
• Current target user and PMF evidence
• Full funnel and largest drop-off
• Weekly goals and actual completed outcomes
• Founder calendar and uninterrupted maker time
• Active projects, owners, deadlines, and dependencies
• Customer, reliability, personnel, legal, and cash emergencies
• Decisions awaiting founders
• Work that can be delegated, automated, deferred, or stopped

Ask only for missing inputs capable of changing the decision. For reversible actions, make assumptions explicit and propose a bounded test instead of blocking on perfect data.

Questions to Ask

• What single constraint most limits survival, learning, or retained growth?
• What evidence names it?
• What changes by Friday if the work succeeds?
• Which task is urgent but not important?
• Which important work keeps being displaced?
• What requires founder judgment or craft?
• What can be delegated as an outcome with decision rights?
• What must stop to create capacity?
• Is the work a reversible test or irreversible commitment?
• How will we know to continue, change, or kill it?
• Does the calendar match the stated priority?

Mental Models

• Bottleneck before backlog.
• One primary weekly outcome.
• Survival, PMF, then scale.
• Maker versus manager time.
• Reversible versus one-way-door decisions.
• Opportunity cost must be named.
• Work in progress is inventory.
• Delegation transfers outcomes and authority.
• Urgency cannot automatically outrank importance.

Use these models as competing lenses. Select the one that best explains the observed behavior, state what evidence would falsify it, and convert it into a decision rather than repeating it as a slogan.

YC Principles

• Before PMF, product and user contact dominate most other work.
• Distraction often looks respectable: conferences, press, networking, premature fundraising, and micromanagement.
• Ship early and often; launch delays often reveal diffuse work, fear, or perfectionism.
• Use a small number of meaningful weekly goals.
• The founder's job changes with stage; priorities must change with it.
• Do not add headcount as a substitute for deciding what matters.

Paul Graham Principles

• Protect maker schedules because a meeting can split an entire creative day.
• Keep the top priority visible so urgent requests do not erase it.
• Launch fast, talk to users, spend little, and preserve morale.
• Resourcefulness means changing the path when blocked, not preserving the plan.

Garry Tan Principles

• High agency means owning the outcome and removing obstacles, not accumulating tasks.
• Use AI to compress research and production while keeping founder judgment on company-defining work.
• Craftsmanship applies to the primary outcome; perfectionism on secondary work is waste.

Decision Frameworks

Priority order

1. Immediate safety, legal, payroll, security, or existential incident.
2. Default-alive risk and runway trigger.
3. Pre-PMF: problem truth, MVP value, activation, and retention.
4. Early PMF: reliability, delivery, and repeatable distribution.
5. Growth: constraint across acquisition, activation, retention, revenue, team, or infrastructure.
6. Everything else competes only after the earlier layer is sound.

Priority scorecard

1. Constraint impact: does it move the limiting factor?
2. Evidence: how certain is the mechanism?
3. Time to learning or value
4. Reversibility
5. Founder advantage
6. Opportunity cost
7. Downside and trust risk
8. Required coordination
9. Score only after applying the stage order; arithmetic cannot make a downstream project strategically correct.

Weekly outcome contract

1. Outcome, not activity
2. Single owner
3. Friday finish line
4. User or company evidence
5. Maximum scope
6. Dependencies
7. Explicit not-doing list
8. Stop or escalation rule
9. Scheduled review

Step-by-Step Process

1. Write company stage, runway state, and one current constraint.
2. List evidence and strongest contrary case.
3. Define one weekly outcome that moves the constraint.
4. Collapse recommendations from multiple skills into one company-level experiment aimed at the earliest unresolved constraint; downstream pricing, product, retention, and distribution work become guardrails or are deferred.
5. Cut scope to a finishable vertical slice.
6. Name one owner and their decision rights.
7. List projects and meetings to stop, defer, delegate, or batch.
8. Protect founder maker blocks and batch managerial work.
9. Resolve blocking reversible decisions immediately.
10. Track outcome progress, not busyness.
11. Review on a fixed cadence: result, evidence, learning, and next constraint.
12. Kill or change work that repeatedly misses the mechanism.

Checklists

Weekly planning

• Stage and constraint are explicit.
• One primary outcome has a measurable finish line.
• Owner and decision rights are clear.
• Scope fits the week.
• Not-doing list and maker blocks exist.

Weekly review

• Judge completed outcome, not effort.
• Inspect user or operating evidence.
• Name what was learned.
• Close or escalate unresolved decisions.
• Choose whether the constraint moved before selecting next work.

Red Flags

• More than one 'number one priority.'
• The roadmap is a list of stakeholder requests.
• The calendar contains no uninterrupted work on the priority.
• Founders fix small bugs to avoid hard customer, personnel, or cash decisions.
• Meetings exist without a decision or owner.
• Work begins without stating what will stop.
• A downstream growth project outranks broken retention.
• Delegation gives tasks but keeps every decision with the founder.
• The team repeatedly carries unfinished work into the next week.

Common Mistakes

• Scoring tasks without applying stage order.
• Confusing urgent inbound with strategic importance.
• Choosing projects too large to finish or learn from.
• Keeping optionality by running many weak bets.
• Protecting sunk cost after evidence changes.
• Delegating only grunt work.
• Using productivity tools to avoid saying no.
• Sacrificing sleep and judgment as the default operating model.

Metrics

• Primary weekly outcome hit rate
• Movement in the named constraint
• Work in progress
• Cycle time from decision to user evidence
• Unfinished work age
• Founder maker hours
• Meeting hours and decisions produced
• Decision latency
• Share of work tied to current constraint
• Projects stopped or deferred
• Delegated outcomes returned for founder approval
• Runway consumed per learning cycle

For every metric, define the unit, numerator, denominator, cohort, segment, cadence, source event, and owner. Prefer decision thresholds and cohort movement over universal benchmarks.

Example Scenarios

Scenario 1

Pre-PMF team debates brand, SOC 2, and referrals while activation is 8%: prioritize observing and fixing first value; defer downstream work unless a named customer requires it for the test.

Scenario 2

Founder calendar is full of sales, hiring, and product: choose the company constraint, reserve maker or customer blocks, delegate outcomes with authority, and batch remaining management.

Scenario 3

Three strategic bets seem equally promising: run the cheapest discriminating test for the weakest critical assumption rather than staffing all three.

AI Prompt Templates

Template 1

Prioritize this backlog using stage order and bottleneck evidence. Produce one weekly outcome, maximum scope, owner, decision rights, not-doing list, calendar blocks, and stop rule.
End with a decision, owner, deadline, metric, threshold, stop rule, and strongest contrary case.

Template 2

Audit this founder calendar against the stated company priority. Identify displacement, fragmentation, avoidant work, and the exact blocks to change.
End with a decision, owner, deadline, metric, threshold, stop rule, and strongest contrary case.

Template 3

Turn this large project into the smallest vertical slice that can produce user or operating evidence this week.
End with a decision, owner, deadline, metric, threshold, stop rule, and strongest contrary case.

Related Skills

• founder-debugger
• founder-default-alive
• founder-talking-to-users
• founder-mvp
• founder-retention
• founder-distribution
• founder-pricing

Further Reading

1. YC's Essential Startup Advice — The early-stage order of operations: launch, talk to users, iterate, and delay scaling until people want the product.
2. Startup Playbook — A broad operating reference for product, growth, focus, hiring, competition, and execution.
3. Advice for First-Time Founders — Firsthand warnings about distraction, decision avoidance, overwork, focus, and stage-inappropriate advice.
4. Office Hours with Ali Rowghani — How the founder's highest-leverage job changes from building PMF to building the company.
5. The Scientific Method for Startups — A disciplined hypothesize-test-conclude-repeat loop supported by instrumentation.
6. The Art of Shipping Early and Often — Diagnoses launch delay caused by fear, perfectionism, diffuse work, and weak problem understanding.

Source Links

• YC's Essential Startup Advice — Y Combinator. The early-stage order of operations: launch, talk to users, iterate, and delay scaling until people want the product.
• Startup Playbook — Sam Altman. A broad operating reference for product, growth, focus, hiring, competition, and execution.
• Advice for First-Time Founders — Y Combinator founders. Firsthand warnings about distraction, decision avoidance, overwork, focus, and stage-inappropriate advice.
• Office Hours with Ali Rowghani — Ali Rowghani. How the founder's highest-leverage job changes from building PMF to building the company.
• The Scientific Method for Startups — Michael Seibel. A disciplined hypothesize-test-conclude-repeat loop supported by instrumentation.
• The Art of Shipping Early and Often — Y Combinator. Diagnoses launch delay caused by fear, perfectionism, diffuse work, and weak problem understanding.
• Maker's Schedule, Manager's Schedule — Paul Graham. Why fragmented calendars destroy maker output and how to batch managerial interruption.
• The Top of My Todo List — Paul Graham. Keep the most important work salient because urgent demands otherwise displace it.
• Startups in 13 Sentences — Paul Graham. Compact rules on cofounders, launch speed, users, morale, spending, and focus.
• Relentlessly Resourceful — Paul Graham. Resourcefulness as the ability to find another path rather than remain attached to one method.