Updated 20 October 2026.
A useful weekly priority describes a result you can finish and explains why it deserves the next available block of attention. Start with the outcome that matters, identify the work most likely to move it forward, and make the tradeoff visible to anyone affected.
The One Thing by Gary Keller and Jay Papasan centers on focused priorities and cutting through competing demands. The official book resource supports that broad theme. The weekly planning method here is an original ReadSprint exercise, not the authors' complete system or a promise of extraordinary results.
Begin with the decision behind the task list
A list containing “website,” “customers,” and “planning” mixes projects with activities. None tells you what would be different on Friday. Rewrite the candidates as outcomes: publish the revised delivery policy, learn why three customers abandoned onboarding, or agree on the next release's scope.
Next ask which outcome removes a real obstacle. Something that feels urgent may still leave the main project blocked. A polished presentation has limited value if the underlying decision has not been made.
Include required maintenance and existing commitments. Selecting a priority does not remove your responsibilities to customers or colleagues.
Compare the candidates on the same basis
For each possible outcome, record:
- The goal it supports.
- What is currently preventing progress.
- Who needs to contribute or approve it.
- The smallest useful result achievable this week.
Choose the candidate with a clear connection to the goal and a workable next step. If two tasks genuinely depend on each other, describe the sequence rather than pretending you can finish both simultaneously.
“Most important” is a judgment that can change with new evidence. Write the reason for your choice so you can review it later without relying on hindsight.
A worked example: remove an onboarding obstacle
Imagine a small software team considering three jobs: redesigning its dashboard, writing five announcements, and simplifying a confusing setup step. Support conversations suggest that customers are getting stuck during setup.
The team chooses: “By Friday, make the setup instructions clear enough for a new colleague to complete them without verbal help.” That is a proposed result, not a reported outcome.
They schedule a drafting block, arrange a walkthrough, and leave time to revise. The dashboard redesign moves to a later planning discussion. One person tells the announcements' owner what changed and checks whether there is a consequence they missed.
The priority now has a deliverable, a reason, and an explicit cost. It is still a hypothesis: clearer instructions may not resolve the actual customer problem.
Protect the work without making a brittle calendar
Reserve a realistic block for the next concrete action. Name it “rewrite setup step two,” rather than “focus.” Check that you have the information and access needed before the block begins.
Decide what will happen if an urgent incident interrupts it. You might move the block once, reduce its scope, or ask someone else to cover a routine duty. A priority that requires every other obligation to disappear is unlikely to be usable.
For broader reading on attention, use the focus reading list. This article stays with the narrower problem of choosing and finishing one weekly result.
Review the choice, not just your effort
At the end of the week, compare the result with your definition of done. Did the work remove the obstacle you named? Did you choose too large a deliverable? Did an unrecorded dependency consume the time?
Before reopening your notes, explain why you chose this outcome over the alternatives. If the reason no longer holds, revise the next week's choice. Keep the completed work, the remaining uncertainty, and the next action in separate sentences.
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 One Thing official 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.
