Build a useful investigation brief
Trace the work path
Review the item history, related changes, evidence, handoffs, and current queue. Identify where responsibility became ambiguous and which outcome still lacks an accountable decision. Treat historical comments as context to verify, not authority by themselves.
Map control points
For each proposed owner, identify the system, release, policy, or customer outcome they can change and the inputs they need from others. Record dependencies and approvals explicitly, including any boundary that prevents direct action.
Write the ownership brief
State the recommended owner, reason, first action, required collaborators, and unresolved decision. Include alternatives considered and evidence for the boundary. If ownership is genuinely shared, split outcomes or name one accountable coordinator.
What to carry forward
A useful brief proves why the selected role controls the next outcome and what collaborators provide. Stop when the ownership boundary is clear enough to route; if authority remains disputed, escalate that decision as the investigation result instead of hiding it in assignment metadata.
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