NEWSLETTER · ISSUE 15
Make dependencies visible before preparation stalls
Work can have an agreed priority and still be unable to move. A necessary approval is pending. A fact needs confirmation. A participant is unavailable. An earlier action has not reached the condition the next activity requires. Saying that the work is blocked names a position; it leaves the next person needing more context.
A useful dependency conversation makes that context available. What is waiting? What does it depend on? Who has accepted responsibility for resolving the dependency? What would establish that the next step may proceed? How will the question return while it remains open?
In our fictional supplier-integration example, the team wants colleagues to trial clearer status wording using a placeholder handoff. Before that authorized trial, participants need a dependable route to the current approved guidance. The proposed wording and the existing guidance must remain distinguishable. The live integration decision is still pending.
Making guidance findable can support preparation for the trial. It does not authorize the trial, approve the proposed wording, or settle the integration decision. Each relevant condition needs its own confirmation through the established route.
Describe the dependency precisely
A missing fact, a required approval, and someone's availability are different conditions. Each may need a different person or process. Identify the condition that actually prevents the specified next activity. If its effect is uncertain, record the question instead of treating an assumption as a confirmed blocker.
For the fictional trial, an appropriate owner might need to confirm that authorized participants can locate the applicable guidance. A separate owner may need to confirm permission to run the trial. Completing the first action does not establish the second. Preserve those distinctions where people coordinate the work.
Keep applicable obligations, deadlines, known-issue handling, and escalation needs visible. A dependency label does not waive required work, extend a deadline, or permit a shortcut around approval. If a waiting condition threatens an applicable commitment, use the relevant escalation process promptly.
Leave a dependency note people can use
Use five prompts to connect waiting work with a supported route forward:
Waiting work: Identify the specific activity that cannot yet proceed and the scope of that statement. Describe what remains possible only where the normal process permits it. Avoid marking an entire program blocked when the confirmed dependency concerns one activity.
Dependency: Name the prerequisite, missing fact, approval, or availability condition. Identify the approved reference and relevant uncertainty. Keep evidence in its authorized location rather than copying it into a general coordination note.
Resolving owner: Confirm who has accepted responsibility for the resolving action and has the appropriate authority. Preserve decisions that belong to other roles. If acceptance is unknown, leave the owner proposed and route the question through the normal process.
Unblock condition: Describe the confirmation needed before the specified activity can move. Keep completed actions distinct from permission to proceed. In the example, a findable guidance reference does not establish trial approval or integration authorization.
Return point: Record the agreed opportunity or relevant condition for returning to the dependency. Preserve required intervals and escalation routes. If new information changes the position, bring it back through the appropriate owner rather than waiting silently for an informal reminder.
The note supports coordination. It does not replace a formal approval, operating record, incident response, corrective-action process, or assessment decision. Keep unknown acceptance and unresolved conditions explicit.
Confirm what has actually changed
Suppose the fictional guidance owner provides the current approved reference. Record what that action establishes: the reference is available through the agreed location, within the confirmed scope. Then check whether the trial's other prerequisites have been satisfied through the proper route.
Do not change the work to unblocked simply because someone completed a related task. Equally, revisit a dependency that may no longer apply. An outdated blocked label can obscure a decision that is now available. The appropriate owner confirms the supported position and any remaining conditions.
Try a small dependency conversation
Use a placeholder trial and invented role names. Write a dependency note with the five prompts. Add one missing fact and one required approval. Ask a partner to identify what resolving either condition would establish and what it would leave unanswered.
Revise any wording that implies assumed acceptance, a bypassed approval, or authorization beyond the supported scope. Keep the live integration decision pending. This optional practice uses no real evidence, sets no PCI activity interval, and promises no assessment outcome.
A visible dependency gives waiting work a defined condition, an accepted resolving route, and a way back into the conversation.
Explore the free Program Maintenance guide (opens in a new tab)