Decide where the work belongs
Classify the harm
Elevate a submission that drops required values, loops without an error, or blocks workspace access above an optional field with weak explanation. Treat a field that accepts but stores the wrong value as a data-integrity issue, not merely a copy issue.
Bound the journey
Record role, device, field branch, validation variant, and redirect where the friction appears. Use synthetic attempts or identified reports only. If completion rates or field reach are unknown, state the evidence gap rather than guessing at onboarding impact.
Choose a safe continuation
Prefer clear required markers, a truthful save result, and an explicit skip or return-later action when the existing workflow allows it. Do not coerce optional data to unlock setup. Assign one owner for form behavior and another for any authority boundary.
What to carry forward
Queue blocked access, lost profile values, and ambiguous required fields before optional copy refinement. Include the exact field branch, role and device scope, safe continuation, owner, and evidence that would demonstrate recovery before closing the issue.
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