Build a useful investigation brief
Map outcome dependencies
Draw a small graph of outcomes, evidence, implementation paths, decisions, and approvals. Identify shared prerequisites and false coupling created by a common request, title, or milestone. Map the shared prerequisite separately from the outcomes that only share a parent record.
Test independent progress
Attempt the smallest meaningful action for each outcome and record whether it requires another scope. Compare data, release, ownership, and acceptance boundaries, noting where a split would create a new risk.
Write the boundary brief
Recommend a single item, linked split, or staged sequence with reasons, preserved context, owners, and acceptance conditions. State residual coupling and how future status should reflect each outcome. State the status signal that should represent each outcome after the boundary changes.
What to carry forward
A useful brief proves which outcomes are coupled and which can move independently, with evidence for the boundary. Stop when the work shape supports honest status and acceptance; retain links where a split would otherwise erase shared rationale.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow