--- title: The Two-Task Rule date: 2026-05-16 slug: startup-lessons-the-two-task-rule summary: At any moment, a startup should work on exactly two things. Not three. Not one. Two. One for the present. One for the future. Everything else is noise. This is the hardest lesson and the most important. tags: startup, prioritization, focus, two-task-rule --- At any moment, a startup should work on exactly two things. Not three. Not one. Two. One task for the present — the thing that keeps the company alive or moves the needle this week. One task for the future — the thing that prevents the company from being dead six months from now. Everything else is noise. This is the Two-Task Rule. It comes from Y Combinator's "The Hardest Lessons for Startups to Learn." It is the simplest rule in startups. It is also the most violated. ## Why two Two is not arbitrary. One is fragile — if your only task hits a wall, the company stalls with nothing else moving. Three is diluted — three tasks means three contexts, three sets of dependencies, three things competing for the founder's attention. Founders are not good at parallel processing. Nobody is. Three tasks means each gets a third of the attention. A third of the attention produces a tenth of the output. Two is the number where focus is real. Each task gets half the founder's attention. Half is enough to make progress. Two tasks can be held in one person's head simultaneously. Three cannot. Two tasks can be communicated to a team in one sentence each. Three becomes a list. Lists are not strategies. Lists are evidence that nobody decided what matters. The two tasks are not fixed. They change as the company changes. The task for the present might be "close three enterprise deals" this month and "reduce churn to under 5%" next month. The task for the future might be "build the API that enables the enterprise deals" this quarter and "hire the engineering lead" next quarter. The specific tasks change. The number stays the same. Always two. ## What the rule forces The rule forces saying no. Saying no is the hardest thing a founder does. Every opportunity feels urgent. Every customer request feels reasonable. Every feature idea from the team feels worth exploring. The Two-Task Rule gives you a reason to say no that is not personal, not political, and not debatable. "That's a good idea. It's not one of the two things we're doing right now. Put it on the list for next cycle." The list exists. The idea is not lost. It is deferred. Deferral is not rejection. Deferral is how focus survives. Brooks identified the same dynamic in design. The essential skill of the designer is saying no — repeatedly, to smart people with good arguments — and having the authority to make it stick. The founder is the designer of the company. The Two-Task Rule is the authority that makes the no stick. Without the rule, every no is a negotiation. With the rule, every no is a reference to a principle everyone agreed on. The principle is the authority. The founder enforces the principle. The principle does the work. ## What happens without it Startups die from indigestion, not starvation. The problem is never too few opportunities. The problem is too many, pursued simultaneously, none receiving enough attention to succeed. Without the rule, the company works on everything. The engineering team builds features for three different customer segments because each segment asked for something and the founder couldn't say no. The sales team pursues four different verticals because each vertical has a deal in the pipeline and nobody wants to drop a deal. The product roadmap has seventeen items in the "current sprint" and zero items in "done." The company is busy. The company is effective at nothing. The team feels it. They work hard. Nothing ships. Morale decays. The best people leave — not because the company is failing, but because they can't see progress. Progress is the fuel of startup morale. Without visible progress, the best people question whether their effort matters. They are right to question. Effort without focus is wasted. Focus without a rule is unsustainable. The rule provides the structure that makes focus durable. ## The connection to Lehman Lehman's First Law: an E-type system must be continually adapted or it becomes progressively less useful. A startup is an E-type system. It must change. The Two-Task Rule does not prevent change. It channels it. The tasks change as the company learns. Last month's "task for the future" becomes this month's "task for the present." The rule ensures that when the company adapts, it adapts to exactly two things, not to everything at once. Adaptation without focus is thrashing. The rule prevents thrashing. Lehman's Second Law: complexity increases unless work is done to reduce it. The Two-Task Rule is the work. Every cycle, the company re-evaluates what matters. Things that were important are demoted. Things that were urgent are recognized as noise. The rule forces the reduction of complexity by limiting the surface area of attention. The company's complexity grows naturally — new customers, new features, new people. The rule is the counterforce. Without it, complexity grows unchecked. With it, complexity is managed by the simple mechanism of only caring about two things. ## The connection to Unix McIlroy's Unix philosophy: make each program do one thing well. The Two-Task Rule applies this to the company. The company does two things well. Not because two is a magic number for companies the way one is for programs. Because two is the number that balances present and future, survival and growth, focus and resilience. A Unix program that tries to do three things is a program that does three things poorly. A startup that tries to do seven things is a startup that does seven things poorly. The principle is identical. The scale is different. McIlroy: "Instead of adding an option, think about what was forcing you to add that option." The startup equivalent: instead of adding a third priority, ask what deficiency made the third priority seem necessary. Fix the deficiency within the two existing priorities. Don't add the third. ## How to apply it Make a list of everything the company could work on. Everything. The features, the deals, the hires, the infrastructure improvements, the marketing experiments, the partnership discussions. The list will be long. Good. The length is the evidence that prioritization is necessary. Cut the list to two. The criterion: one task must move the company forward this week or this month. One task must prevent the company from dying in six months. If the first task succeeds and the second fails, the company survives the present but has no future. If the second succeeds and the first fails, the company has a plan but no present. Both must move. Everything else waits. Communicate the two tasks to the team. Everyone should know them. Everyone should be able to answer "what are we working on?" in one sentence. If someone can't answer, the communication failed. Fix it. Review the two tasks at a fixed cadence. Weekly or monthly. Not daily — daily is too fast for strategic re-evaluation. Not quarterly — quarterly is too slow for a startup. The cadence should match the speed at which the company learns. When the company learns something that changes what matters, the tasks change. When nothing has been learned, the tasks stay. The discipline is in the review, not in the change. Resist the temptation to add a third. The third will always seem urgent. It will always come from a customer who might leave, an investor who made a suggestion, a competitor who launched a feature. The third is urgent. It is not important. Important things move the company forward or prevent it from dying. Urgent things feel like they must be done now. Most urgent things can be deferred. Most deferred urgent things turn out to have been noise. The Two-Task Rule protects you from urgency by making importance the only criterion. --- **References:** - Y Combinator, "The Hardest Lessons for Startups to Learn." [YC Library](https://www.ycombinator.com/library/8w-the-hardest-lessons-for-startups-to-learn) - Related posts: [Brooks on Software Design: conceptual integrity](https://blog.hackspree.com/#brooks-design-conceptual-integrity), [Lehman's Software Evolution](https://blog.hackspree.com/#lehmans-laws), [The Unix philosophy](https://blog.hackspree.com/#unix-philosophy) Engineering is the application of knowledge to solve problems within constraints. The constraint here is the central fact. Understanding the constraint is understanding the problem. The solution follows from the constraint. This is the engineering method: name the constraint, design within it, verify the design works. > Focus is not about doing fewer things. It is about doing the right things. The two-task rule is not a productivity hack. It is a structural constraint that forces the question: what matters most right now?