Part 3 of 3 of the series “How to use Post-it Notes”
In Part 2, we took a particularly traumatising shower and built ourselves a means of finding our audience.
We’ve drawn the map, agonised over where exactly we can help and who we’re designing for.
The issue is: Having One Map doesn’t necessarily mean we have One Who. Yet.
Let’s get into it.
…I’m not kidding.
Let that sink in.
Building the Map had been an exercise in defining our challenge.
In half a day, we had:
In the second half of that day, our task would be to develop solutions for that audience.
It’s called a Sprint for a Reason. Right?
We thought we’d already narrowed down our audience. But remember?
We can’t help everyone.
…But we can help someone. So now, we must narrow down more. Narrow down to one Who. That’s our aim. So, which Who do we aim for?
First, we must consider the fact that:
The Who is a user, but the user isn’t the only target.
We identify our users, but our role is to design their experience. So, our target must be the combination of both the user and a moment in that user’s journey.
Our user’s experience is essentially a combination of many of these moments. And each of these moments is an opportunity.
At this point, the team and I had become aware that each of us would be building and prototyping our own solution.
The assumption was that we must create a product manageable for us to:
Inside of our Design Sprint, while the team sketched solutions- we would work alone, but together. This was powerful.
Everyone has something valuable to contribute. But rather than battle for attention- each of us committed our contributions to paper in silence, working in the same room.
We separated, to generate ideas and define them without distraction. Only then would we re-join together, to present and share solutions.
Using this structure felt incredibly effective to me.
The first step was a round of Lightning Demos:
The Lightning Demo reminds us that there is no one correct solution for any struggle. There are many.
Everything’s been done- so we may as well learn from all of the things. We looked at the solutions that already exist around us- and presented the reasons why they’re great with everyone for 3 minutes each.
I look at The four-step sketch as a means of focusing myself and my team creatively. The combination of time constraint and variation in exercise brought a certain atmosphere of (sometimes, nervous) energy to the process.
The first three steps are introspective, quiet- while you gather your notes and resources, push through the first round of ideation and rush your way through a series of 8 fast-paced concept sketches- you have the comfort in knowing that these are just for you.
But the fourth takes your final concept and turns it outward. This final titled concept, your Solution Sketch, is for everybody’s eyes. Made to be shared.
Complete with a catchy titles and some short descriptions of the process- this final step closes out our day.
At the end, we each take the Solution Sketch we’ve drawn and place it up on the wall. Here, it can be seen by the whole team- in preparation for tomorrow.
(I’ll cover the final few steps of our sprint in the case study of Magneet- my product of this process).
Thank you so much for reading!
I’m Eli Hughes, an Illustrator and UX Designer living in Amsterdam.
Iterate's just a buzzword for F*ck it up, Fix it, Repeat.
I love stories and I love people. I spend a bunch of my time thinking about what people do and why people do it.
Follow me to hear about the next article on my experience in the Codaisseur Design Academy Next Week!