Updated 20 October 2026.
Use short-term targets to coordinate work, then examine what the pursuit of those targets does to the team's ability to keep serving its purpose. A good result this month should be assessed alongside the capabilities, relationships, and obligations it leaves behind.
The Infinite Game by Simon Sinek contrasts games with fixed endpoints and ongoing activities whose players and rules can change. His official book overview applies that distinction to areas including business. The planning exercise here is our own application, not a claim that long-term language alone makes a strategy sound.
Identify the target and the larger purpose
Write the target in ordinary terms: finish a release, improve onboarding completion, or reduce a backlog. Next write what the work is meant to support beyond the reporting period.
If the second sentence is only “grow the metric,” ask what customers or colleagues receive when the number improves. This may reveal that the target is a useful proxy, an incomplete proxy, or a distraction.
Keep real constraints visible. Payroll, contractual commitments, and immediate customer needs do not disappear because the team values a longer horizon.
Add the cost of reaching the number
Before choosing an action, ask what it uses up. Does it consume maintenance time, make future support harder, or depend on promises the product cannot keep?
Also ask what it builds. A clear onboarding explanation may help this week's customers and become reusable knowledge. A rushed manual workaround may be appropriate for an incident but expensive as a permanent operating model.
The answer is contextual. A short-term intervention is not automatically wrong, and a project described as strategic is not automatically worthwhile.
Work through a sales-and-support tradeoff
Imagine a small business trying to meet a monthly sales target. One option is to promise custom reporting to every new customer. Another is to offer the existing report clearly, while investigating which additional need recurs most often.
For this fictional decision, the team lists the immediate benefit, delivery effort, support burden, and future options of each approach. They also identify what they do not know: whether the custom promises will lead to retained customers or just additional work.
They might choose a limited custom pilot with a named owner and review date. They might decline the requests. The example does not assume one answer is correct; it makes the future consequences part of the current decision.
Use two views of progress
Keep a short list of immediate measures and a separate list of conditions that support continuing work. Examples of the second list could include unresolved support problems, maintainability, or whether the team can deliver what it sells.
Avoid combining everything into one score. Different measures can conflict, and the disagreement may be exactly what the team needs to discuss.
Document the tradeoff when you decide. A record stating what you accepted and what you will revisit is more useful than a claim that the choice served the long term.
Revisit the decision when evidence changes
At the review point, compare the expected benefit and cost with what actually happened. Check whether a temporary compromise became permanent without discussion. Ask whether the original target still represents the purpose it was meant to serve.
The long-term leadership learning path provides a broader reading sequence. This article focuses on one planning conversation that makes ongoing capacity visible.
For recall, describe a case where meeting a target could weaken the work it was intended to support. Then name a near-term obligation that a long-term strategy still has to respect. Holding both questions together is the practice.
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: Simon Sinek’s Infinite Game 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.
