Build a useful investigation brief
Map both workflows
Document each segment's starting state, decisions, system responses, workarounds, and desired endpoint. Include timing and handoff points. Look for a shared step where the current design forces a choice, rather than assuming the named feature is the true source of conflict.
Test the constraint
Use controlled examples to vary role, data volume, permissions, and default settings one at a time. Record when the requested outcomes become incompatible and when they can coexist. Treat an untested explanation as a hypothesis, not an investigation result.
Frame the design brief
Summarize the verified constraint, affected segments, viable seams for separation, and unresolved assumptions. Include a small experiment or prototype question that would distinguish competing solutions without committing the whole product to either preference.
What to carry forward
The investigation is useful when each conflicting request is tied to a reproducible constraint and the team knows whether the conflict is inherent or introduced by the current workflow. Stop with an explicit uncertainty list and a bounded next experiment when reproduction is incomplete.
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