Research before wireframes
Watching people do the task today, including the workarounds nobody writes down. This is where assumptions get killed cheaply. It routinely changes the scope, because the thing everybody agreed to build turns out to solve a problem users do not have, or to miss the step that actually costs them time.
- Stakeholder and user interviews
- Observation of the real task
- Journey mapping
- Assumptions written down and tested