How do you write a good user story? Can you give us an example from your experience?

Situation

While working on a healthcare claims processing system, the product owner handed me a vague requirement: 'Make the claim status update faster.' There was no clarity on which user role, what 'faster' meant, or what specific problem needed solving.

Task

I needed to break down the high-level request into clear, actionable, and testable user stories that the development team could estimate and implement.

Action

I conducted a follow-up session with the product owner and two end-users (claims processors) to uncover the exact pain point: they were waiting too long after clicking 'Submit' to see a confirmation. I then crafted the user story: 'As a claims processor, I want to receive a visual confirmation within 2 seconds of clicking Submit, so that I can proceed to the next claim without uncertainty.' I added acceptance criteria: the system must display a success toast notification within 2 seconds under normal load, and if processing takes longer, a spinner must appear. I aligned the story to the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable).

Result

The story was estimated at 3 story points and completed in one sprint. Post-deployment, the average processing cycle time per claim dropped by 18 seconds, and user satisfaction with the interface improved notably in the next survey.