From software problem to a clear next step.
Choose a topic and what you need to do next. Add a search phrase to find a specific problem.
Browse 20 topics
Explore the playbooks
1500 guides · Page 44 of 60
-
Triage a work dependency cycle before more delay
Triage a work dependency cycle by confirming blocked conditions, owners, and the safest break point before more work stalls.
-
Prioritize work trapped in a dependency cycle
Prioritize work trapped in a dependency cycle by comparing outcome impact, leverage, reversibility, waiting cost, and authority.
-
Investigate the root cause of a work dependency cycle
Investigate a work dependency cycle by testing prerequisite assumptions, sequencing constraints, interface contracts, and authority gaps.
-
Verify that a work dependency cycle has been broken
Verify a broken work dependency cycle by checking released work, preserved contracts, clear next actions, and residual risk.
-
Learn why teams fall into recurring dependency cycles
Learn why teams fall into dependency cycles by improving sequencing assumptions, contracts, shared ownership, authority, and scope design.
-
Triage duplicated work items without losing findings
Triage duplicated work items by comparing outcomes, scope, evidence, and owners before merging, coordinating, splitting, or preserving parallel work.
-
Prioritize duplicated work before it consumes capacity
Prioritize duplicated work by comparing shared outcome value, sunk effort, independent confidence, delay cost, and lost coverage.
-
Investigate whether teams are duplicating work
Investigate duplicated work by comparing outcomes, methods, conditions, artifacts, and evidence until safe consolidation boundaries are clear.
-
Verify that duplicated work was consolidated correctly
Verify duplicated work consolidation by checking one coherent outcome, preserved evidence, clear ownership, and independent coverage.
-
Learn why teams repeatedly duplicate the same work
Learn why teams duplicate work by improving discovery, ownership, search, scope review, and shared decision context across teams.
-
Triage work when project decision context is missing
Triage work when decision context is missing by separating documented evidence, inferred rationale, alternatives, and unresolved assumptions.
-
Prioritize recovery of lost decision context before making changes
Prioritize recovery of lost decision context by comparing blocked outcome, reversal cost, dependency reach, uncertainty, and repeat risk.
-
Investigate a work item with missing decision rationale
Investigate missing decision rationale by tracing durable evidence, comparing alternatives, and testing assumptions until the boundary is clear.
-
Verify recovered decision context before proceeding
Verify recovered decision context by checking traceability, current understanding, scope consistency, and unconfirmed assumptions.
-
Learn how decision context gets lost from work items
Learn how decision context gets lost by improving durable links, handoffs, status detail, ownership, and decision records.
-
Triage a mixed-scope work item before splitting
Triage a mixed-scope work item by separating outcomes, owners, dependencies, and acceptance conditions before choosing its work shape.
-
Prioritize mixed-scope work without hiding independent outcomes
Prioritize mixed-scope work by comparing outcome value, urgency, dependencies, effort, and the risk of keeping unrelated work bundled.
-
Investigate whether a mixed-scope work item should be split
Investigate a mixed-scope work item by tracing outcome coupling, dependencies, ownership, evidence, and acceptance boundaries.
-
Verify a mixed-scope work item after splitting or sequencing
Verify a mixed-scope work item after splitting by checking shared context, ownership, dependencies, acceptance, and truthful progress.
-
Learn why work items accumulate mixed scope repeatedly
Learn why work items accumulate mixed scope by improving intake habits, deadline bundling, ownership, dependency review, and scope changes.
-
Triage work with unclear acceptance criteria safely
Triage work with unclear acceptance criteria by clarifying outcomes, actors, failure states, evidence, and decision ownership.
-
Prioritize work with unclear acceptance criteria
Prioritize work with unclear acceptance criteria by comparing outcome risk, customer impact, reversal cost, dependencies, and clarification effort.
-
Investigate why acceptance criteria remain unclear
Investigate unclear acceptance criteria by tracing outcome language, stakeholder assumptions, edge states, and evidence until testable.
-
Verify work against clear acceptance criteria and edge states
Verify work against clear acceptance criteria by testing representative success, failure, permission, empty, and recovery states.
-
Learn why teams repeatedly write unclear acceptance criteria
Learn why teams write unclear acceptance criteria by improving outcome language, examples, scope boundaries, and review ownership.