Founder focus starts by naming the constraint that can change the week
A longer task list will not settle a build-versus-sell decision. Find the constraint that makes other work secondary, define one seven-day bet, protect a calendar block, and review evidence before adding another initiative.
Good fit for
- Product work keeps displacing customer conversations
- Several urgent tasks compete without a decision rule
- Reactive meetings consume the block needed for the main bet
- The founder ends each week busy but cannot name new evidence
Not the right fit for
- A project plan whose priority and owner are already settled
- A team conflict that first requires a direct founder conversation
- A cash emergency that needs an immediate runway response
What changes the answer
Match the next move to the real bottleneck
The bottleneck decides the week
Demand, retention, distribution, runway, and team constraints require different actions; treating them as one productivity problem wastes time.
The calendar proves the priority
A stated priority without protected time remains a preference that reactive work can replace.
Evidence closes the loop
A weekly review should show observed behavior, a changed metric, a written decision, or a falsified assumption.
Produce the first result
Open the path that creates the needed output
Founder Weekly Office Hours
Diagnose the constraint, choose a seven-day bet, define evidence, and save the review date.
Founder Weekly Priority
Connect one startup priority to a customer-learning move and a protected maker block.
Startup Prioritization Matrix
Compare competing tasks by evidence, impact, urgency, reversibility, and cost of delay.
Separate the adjacent questions
Related problems need different answers
Get the first 10 customers
Make customer evidence the week's main bet.
Founder burnout
Separate an attention problem from an unsustainable workload.
Manage startup runway
Turn cash and burn into an operating response.
Questions people ask before choosing a path
How should a startup founder prioritize tasks?
Identify the current company constraint, then rank tasks by how directly they test or relieve it. Work that does not affect the constraint should wait, shrink, or stop.
Should a founder focus on product or sales?
The answer depends on the evidence gap. Weak demand calls for customer and sales work; strong demand with failed delivery may justify product or operations work.
How many priorities should a founder have each week?
Several responsibilities can continue, but one result should determine whether the week worked. The calendar and review should make that result visible.
What should go into a founder weekly review?
Record the bet, the action completed, observed customer or operating evidence, the assumption that changed, and the next decision.
Tell us which problem should get the next Program cycle.
Choose up to three topics. The results guide product work, Program releases, and coach recruitment.
Choose my topics Coach this topic