Keep the lesson for the next incident
Write the field contract
Document required, optional, format, default, and role-specific rules, plus save, skip, and resume states. State which values appear after refresh and how errors identify the field. Keep authority or identity changes outside this presentation contract.
Keep form fixtures
Save synthetic cases for valid, missing, invalid, partial, interrupted, resumed, keyboard, and narrow-screen use. Assert errors, persisted values, focus, and next action. Do not retain personal profile content; use fixtures that prove behavior without real identities.
Define recurrence signals
Reopen review when markers disagree with validation, a save disappears after refresh, optional fields block unexpectedly, or a mobile control clips the continuation. Record role and assistive-technology limits and assign an owner for each unresolved branch.
What to carry forward
Close learning with field semantics, persistence and resume rules, accessibility fixtures, and recurrence triggers. A completed form is only a durable success when the next onboarding state and the saved values agree after interruption after refresh.
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