This is part of a series on Techniques based on my experiences.
A dear Product Manager I work with, let’s call her June, gets stuck. She does so many things right! When defining a new, even big feature, she considers front-end users — yes! She knows how to think in terms of user flow for both Front-End and Back-End — yes! She appreciates the value of wireframing — yes! She knows how to use Axure and other design tools— yes! She is eager to move forward, and fast. S/he has spoken to customers. She has experience with older versions of similar features.
SO she jumps right into wireframing. She starts with the first screen in the user flow; the ‘create’ screen. She puts some boxes together, an interactive button or two… then chokes. She burns some time trying to crack this nut, but eventually, when the frustration builds, she brings me in.
Who area the users? What are their goals? I have to ask her. What’s the end-to-end user task flow necessary to achieve that goal?
At the end of the day, we have to start with the end. I have to steer her away from the ‘create’ flow, toward the end static state. Why? Create flows are tricky. Even trickier if we haven’t yet defined what we have to create, and why ;) Once we understand the end state of the new feature, we work backwards and define a create flow to get there.
Things fall into place. June is in the zone again, unstuck. She doesn’t need my ‘help’ any more, for now. This is a win for me, as a designer. It is empowerment, and feels spectacular.
Thanks for reading.
About this Series
This is part of a series on Design Techniques based on my experiences.
About The Author
I’m a UX Designer turned Product Manager, with experience in startups, freelance, and international B2B companies. Writing helps me reflect & continuously learn. Connect with me on Twitter.
