How do sprints start?
Sprints start with a written challenge statement agreed between the agency and the client before any calendar is booked. One sentence names the problem, the user affected, and the decision the week must produce.
A statement like improve our checkout fails this test, while first time buyers abandon payment at the address step passes it, because the second version tells the team exactly where to look. Preparation then moves to people and materials. Agencies request one client decision maker who attends every session with the authority to choose, since sprints stall the moment choices wait on absent approvers. Past research, failed attempts, and known engineering limits get compressed into a briefing pack under ten pages, and recruitment for the final test day begins immediately because finding five matching users takes longer than any other task. Published schedules from top UX agencies show preparation running one to two weeks, nearly the length of the sprint itself, and skipped preparation remains the leading cause of weeks that end without a usable answer.
What fills sprint days?
Each of the five days carries one fixed purpose, moving from problem mapping on Monday through user testing on Friday. The sequence never reorders because every day feeds the next one.
- Monday – Client experts get interviewed one by one, the team draws the full user journey, and one moment on that map gets circled as the week’s target.
- Tuesday – Each person sketches complete solutions alone, since silent parallel work produces more usable ideas than any group session.
- Wednesday – Sketches hang anonymously on a wall, votes mark promising details, and the decision maker picks one direction for the storyboard.
- Thursday – A prototype covering only the storyboard gets built, convincing enough to test yet disposable by design.
- Friday – Five users work through the prototype in recorded sessions while the whole team watches from another room.
Reshaping sprint formats
Format changes cover remote delivery, shorter versions for narrow problems, and extended testing for complex ones, all decided during planning rather than mid-week. Facilitators lock every adjustment before day one because format surprises drain group energy.
Remote sprints stretch across shorter daily blocks with quiet work between, since screen sessions tire people faster than room sessions, and shared whiteboard tools replace paper without touching the underlying sequence. Narrow questions fit a four-day version that merges mapping and sketching, while enterprise challenges covering several user roles sometimes spread testing across two days. Attendance stays between five and seven people, whatever else changes, since larger rooms slow each exercise and smaller ones lose the range of viewpoints the method depends on.
Converting sprint findings
Findings convert into direction through a same-day review, a written answer against the challenge statement, and a report pairing each observation with a recommended next step. Patterns across three or more users count as signals, while single complaints get recorded without driving anything.
Within days, the agency delivers that report, covering paths from full production design through a second sprint on a revised question. Prototypes and session recordings are passed to the client for internal sharing, and a follow-up call two weeks later checks which recommendations have moved. A clear no carries the same value as a clear yes, since a weak idea abandoned after five days consumes nothing further.
Planning quality decides sprint value before the week begins. A precise challenge, a present decision maker, and finished preparation turn five working days into a direction that months of unfocused meetings never reach.
