This guide focuses on choosing what proceeds and what waits within available capacity. The worked example follows three units: “customer question”, “tutorial script” and “journey test”.
Reference input: frequent questions and verified product behaviour. Expected output: a tutorial series with tested steps. Before assigning work, confirm the current input version and who will review the result.
Separate urgency from a genuine blockage
To prioritize the customer tutorial series production, start with the consequence of inaction. A task described as urgent by preference may matter less than another that enables committed work. Compare customer question, tutorial script and journey test using impact, dependency, useful date and effort. Avoid invented scoring weights that make an unresolved discussion appear objective. Evidence should explain why one unit should start and what is at risk if another waits. Priority is a decision about available capacity, rather than an adjective attached to every task. The decision needs to remain understandable to the people whose requests are deferred.
Calculate the capacity actually available
Before ordering requests, confirm who can work and how much time remains after other commitments and review. Theoretical availability differs from usable hours for this assignment. In this illustrative example, the team has 6 hours and three requests require 3, 2 and 4 hours. The total is 9 hours, so the complete set does not fit. That calculation requires a scope reduction, different sequence or renegotiated delivery. Assigning all three as urgent merely transfers the unresolved gap to the executor. Capacity planning becomes useful when the plan names the work that will wait.
Worked example
The fictional series answers three recurring questions through checkable journeys. Its author uses an account with specific permissions. Review asks another user to repeat the steps and identify context differences before marking each tutorial reproducible.
The example involves Diego, Alex and Mateo. Names, situations and numbers are illustrative and do not represent customer results. The three units let you test the proposed approach before extending it to other work.
| Unit | Illustrative effort | Decision with 6 h capacity | Reason |
|---|---|---|---|
| customer question | 3 h | Include in this cycle | Enables the next commitment |
| tutorial script | 2 h | Include if inputs are ready | Leaves 1 h unassigned |
| journey test | 4 h | Defer and review | The set requires 9 h and does not fit |
Choose what proceeds and what is deferred
Prioritize the unit that enables the next commitment and has sufficient inputs to proceed. If another task depends on it, respect that relationship before reserving capacity. An optional improvement can wait with an explicit reason and review point. Retain the pending request so its owner understands the condition for reconsideration. In this process, control the risk of publishing steps that only work in the author's account. The proposed check is to ask another user to repeat the steps in their context. The order should support explaining a difficult decision through observable facts, including the value that will remain unrealized because another delivery was selected first.
Revisit the order when evidence changes
The initial order becomes less useful when a dependency, date or availability changes. Define the signal that triggers reconsideration and who can decide. Keep the goal of producing a tutorial series with tested steps, using frequent questions and verified product behaviour as the reference. When a new urgent request appears, show which work it would displace before accepting it. Record the previous commitment, new decision and affected recipients. This allows adaptation without turning every message into an informal reassignment that nobody reflects in the plan, leaving several apparently prioritized tasks without the capacity needed to complete them.
What to check before closure
The risk to control in this case is publishing steps that only work in the author's account. A completed label needs a supporting observation. Keep the following beside the decision so the receiver can establish what was checked:
- Input and version used: frequent questions and verified product behaviour.
- Case check: ask another user to repeat the steps in their context.
- Outcome under review: a tutorial series with tested steps.
