Updated 20 October 2026.
Reduce project scope by naming the smallest result that still serves the intended user, then removing work that does not support that result. Keep essential quality requirements visible. A smaller project should have a clearer purpose, not simply fewer tasks on the same unrealistic deadline.
Rework by Jason Fried and David Heinemeier Hansson challenges conventional advice about running and building a business. The authors' Basecamp book overview supports that broad theme. The scope exercise below is an original ReadSprint method; it is not a claim that every kind of planning or process should be removed.
Name the result before cutting features
A project described as “launch the customer portal” can contain many different ambitions: access to invoices, support requests, account changes, analytics, and announcements. Without a primary use, every feature can appear essential.
Write the job the first version needs to do and who needs it. For example, a customer might need to find a reviewed invoice without contacting support. That is specific enough to evaluate proposed work.
Also record the quality conditions that must remain. Correct access control and accurate invoices are part of the result, not optional polish to be cut for speed.
Sort the work by its contribution
Create three lists for this exercise:
- Work required for the intended task to function safely and correctly.
- Work that makes the first experience more convenient.
- Work serving a different task or a later ambition.
Challenge the placement of each item with a concrete user situation. If you cannot explain the situation, the item may need more investigation before it consumes the current project's time.
Do not use the categories to hide costs. A feature deferred from the first version may still be a real obligation that needs an owner and a later decision.
A worked example: an invoice portal
Imagine a team considering invoice access, custom charts, profile editing, and a redesigned help center in one release. The immediate customer problem is locating invoices already issued.
For a fictional scope review, the team keeps secure access, a clear invoice list, correct document links, and the checks needed to avoid showing the wrong customer's information. It defers charts and profile editing because they serve different tasks.
The team also checks whether a simpler existing channel could solve the immediate problem. If the current system can provide reliable invoice access with a clearer link, a new portal might not yet be warranted.
This is a decision example, not a technical implementation recipe or a claim that fewer features always improve a product.
Make the tradeoff visible to the people affected
Explain what the smaller result includes, what it leaves out, and why the boundary exists. Ask whether an omitted item prevents the intended user from completing the task.
When someone requests more scope, discuss which current item would move or which date and resource assumptions must change. Silent additions make the original plan less useful even when each addition seems reasonable alone.
Review what the smaller version taught you
After the first version is used, examine whether the intended task became possible and where users still need help. Keep feedback about the core task separate from requests for entirely new capabilities.
The high-leverage-work learning path provides broader prioritization context. Here, the practical deliverable is a project boundary that everyone can describe consistently.
For recall, explain the difference between removing an unrelated feature and removing a requirement needed for the task to work correctly. Then take one current project and write its smallest useful result in a single sentence, followed by the quality conditions that still have to hold.
Continue with ReadSprint
Open the related book summary to revisit the book's broader ideas. Use the free Book-to-Action Plan to organize your own takeaways into practice and review phases; the tool arranges the entries you supply rather than validating the method or predicting results.
Source checked 20 October 2026: The authors’ Basecamp book overview. The source supports the attributed book concept. The scenarios, questions, and practice steps in this article are original ReadSprint suggestions; example outcomes are hypothetical.
