code for america
In pink are annotations made after the initial 20 minutes to give context to research, problem framing, and wireframing.
Please name the 5 favorite tools or methods in your design toolkit, and what you use them for.
When used well, brainstorms can be incredibly powerful tools for uncovering a group's desires, empowering people, and for generating ideas without judgement.
While we may share similarities with our users, we are never completely them. Having personas that are well-made and based on real people (rather than stereotypes) help to ground our product decisions, as well as help align the team and stakeholders.
Dividing features into "must have" "should have" "could have" and "would have" to better identify and discuss which features are to be built for the MVP. I've paired this with personas to better ground these decisions.
For testing and sharing flows in their native device, and being able to share quickly via SMS. Useful for understanding how intuitive (or non intuitive) your experiences are.
quartz composer / ORIGAMI STUDIO
For micro-interactions that may not exist in a prototyping program.
Given more time, what would be your next step on the interface you sketched?
I'd love to use it to advance our interviews with bike theft victims and police officers. The design currently operates under a few assumptions, such as photographs being a useful resource, or the user immediately using their phone to file. How might the design change once we speak with others about our ideas?
I'm interested in learning what goes through people's minds when their bikes are stolen, what their experience was like filing a report (if they did), and how the experience might still affect them today. I'm equally interested in understanding how police departments use data from reports, and identify their pain points as well.
Following these interviews, the team would have a better understanding of users' needs, allowing us to generate more fruitful ideas.