User-centric Design: A Worked Example
Posted on October 21st, 2021
Part of Notes on Software Design
Looking at how we create scenarios, storyboards, and wireframes from a persona.
Observations
Discusses the role of an average bin collector in a city
The current system is inefficient
- Information on bin capacity is non-existant so all bins must be checked for litter
- Time is wasted on empty bins meaning routes may not be completed
The council wants to add sensors to bins
- Only bins that require collection will be scheduled, optimising the collection process
- Workload is reduced for bin men
- General public will shut the fuck up
- Local council save money on wages for scheduling roles and complaints-handling
Persona
(I couldn't be bothered to make one 🤷♂️)
Scenario
- James, a 28-year-old bin man, has gotten ready for work
- He carries everyday items, such as his phone, and his keys for his work van
- He checks which bins need collecting and starts his route
Goals
- Functionality
- Remotely accessible: it's a job on the move
- Available without internet connection: may not always have a connection
- Context factors
- Events around the city: can additional bin-usage be expected/predicted?
- Usability goals
- Easy to read on the move
- UX goals
- Reliable
Storyboard
Wireframe
(I couldn't be bothered to make this either)
Component | Functionalities | Used by |
---|---|---|
Text box | Entering text Censoring letters | Login fields |
Button | Navigation | Login button |
Text | Rendering text Rendering emojis | Scheduled bin component |
Scheduled bin | Displaying bin name Displaying bin status | Route preview |