For many product managers, design can feel like a black box: provide the designer with information about the customer’s problem, wait a while and—voilà!—creative work issues forth. Sometimes the output is amazing, elegant in its intuitiveness. But sometimes the output doesn’t even approach the product manager’s expectations, creating a sense of frustration and wasted time. How did the design go off the rails, and how can both teams work together to get it back on track? Without mutual understanding and a focus on collaboration, it’s harder to reach successful outcomes.
Similarly, the role of product manager can mystify designers. How do product managers prioritize their decisions and balance different factors to home in on a product direction? What methods do they employ to gather user insight, and how does empathy play into that process? Inconsistent experiences with different product managers can contribute to designers’ confusion around roles and frustration around collaboration. This “black box” understanding of each other’s functions can create real problems, like poor communication and lack of trust, and result in inferior product outcomes.
Moving from the Black Box to the Sandbox: A Space to Build New Things Together
How did we get here? For one, we’ve reached this crossroads from different paths, bringing along varied skills, vocabulary, and perspectives that muddy the waters of understanding. Plus, organizations often oversimplify the separation of roles and responsibilities. This lack of nuance and an emphasis on ownership can contribute to an us-vs.-them mentality.
In their ideal states, both design and product management take an outside-in approach to problem solving.”
By breaking down walls and learning about our partners’ processes, we’ll find the key collaboration points that increase productivity and successful outcomes.
Designers and Product Managers Have a Lot in Common
In their ideal states, both design and product management take an outside-in approach to problem-solving. Over the years, both practices have evolved to better understand buyers and users, concentrating on research and problem-framing before building solutions. However, these practices evolved in parallel, resulting in somewhat different approaches to identifying, articulating, and solving market problems.
Both practices have also found greater influence within the industry. Neither wants to give up their focus on understanding user problems—and they shouldn’t have to! There’s strength in multiple perspectives. Each group has superpowers that, when combined, act as a force multiplier for the products they work on. But first, they must understand each other better, applying the same curiosity that serves them in research to their cross-functional relationships. For product managers, let’s start by peering into the black box of design.
What Designers Care About
(Spoiler Alert: You Care About These Things Too!)
Understanding People and Their Problems
To do their best work, designers crave a deep understanding of their target users. As Shannon likes to say, “Good designers often begin their work with a deep knowledge of design patterns and best practices, coupled with an intuitive sense of empathy. Over time, good designers become great by developing a rigorous curiosity about people.”
Designers apply empathy to step into the user’s shoes when imagining potential solutions. To activate their empathic powers, designers need deep user context: where the user is situated, what goals the user wants to achieve, who the user must collaborate with, what the user currently understands, and what decisions and actions the user needs to take with the information at hand. This desire for context frequently shows up as a request to be “brought in earlier in the process.” Translation: Designers want to be included in discovery or given rich context on the user.
Create collaboration points as mechanisms for deeper communication and idea sharing.”
Framing Problems Before Jumping to Solutions
To explore problems that have been identified and prioritized, designers employ problem-framing techniques. These techniques inspire the generation of innovative solutions and offer criteria for evaluating those solutions. A well-framed problem helps designers activate their creative talents. So, designers may want to collaborate with product managers on reframing the market problems they have been given.
Exploring Multiple Potential Solutions
Experimenters at heart, designers pinpoint the best ideas by generating a multitude. Knowing that the first solution is rarely the ideal one, they try out a variety of ideas and permutations before selecting the right one for the job.
There are specific methods for exploring alternatives individually as well as techniques for groups to generate and evaluate multiple ideas before settling on one. You can take advantage of this skill by dedicating time in the schedule for this approach.
Narrative and Storytelling
It’s common for both designers and product managers to use narrative and storytelling during product development. When it comes to designers, they craft stories in their heads to help them think through how the user might approach a product or a feature. These narratives are the easiest, cheapest form of prototyping: A designer can write a story that explains how the product helps the user solve a problem, stitch together multiple features into a coherent whole and use it to get others’ feedback—all before committing to build it.
Stories are also a compelling way to present work in progress, communicating the user’s perspective and ensuring the product experience is optimized for their goals.
Feedback and Refinement
Designers need feedback from colleagues and users on their designs in order to continually refine the solution to achieve the best possible fit. While they try to approach the problem from the user’s perspective, they may overlook some aspects of the problem in their solution. By giving productive feedback—grounded in the user’s context and problem—you help refine the solution.
What Designers Wonder About Product Managers
Designers are used to adopting the user’s perspective, but only a select few have deep grounding in business strategy. How can you provide a deeper context on the business goals you want to achieve to ensure the alignment of user and business needs?
How do you decide what problems to solve and solutions to employ? In what ways do you balance market data, business objectives, user needs, and technical considerations when choosing a path forward? Describing how you weigh these factors and, if possible, including them in the process (so they can see firsthand your rigor in understanding and prioritizing market problems) will help designers understand and buy into your decisions.
Product designers and researchers are steeped in user research practices. Consider partnering with designers on NIHITO user research: You’ll reap solid insights, and your designers will be fortified with the deep user context that inspires great work. Designers are less likely to be experienced in buyer research, so share your buyer insights with them, especially in cases where the buyer’s objectives might seem to conflict with the target user’s needs.
How You Like to Collaborate
This is the real black box for designers. Some product managers hand off interface sketches with a request to make them real. Others define the problem and simply hand it to the designer to generate the solution. Some are looking for a happy medium: product frames the problem, collaborates with the designer to find a solution direction, and then leaves it to the designer to perfect the details, with conversations along the way. Start a dialog with your designer about how you both prefer to collaborate, and select a model that makes sense for your working styles, business environment, personalities, and project priorities.
How You’ll Negotiate Conflict Together
Conflict is inevitable, especially when you’re approaching the same problem through different lenses. Making a plan for overcoming conflict ahead of time will minimize the potential stress in your relationship. What happens when the best solution for the user doesn’t address your business objectives? How will the two roles bring this up and work toward a resolution that satisfies all needs? What’s your plan for identifying conflict early, leaving you both enough time to resolve it?
An Expanded View of Collaboration
The only way to understand each other is to work together more intentionally. Partner to set up consistent spaces to play in the sandbox together throughout the process—with the necessary tools to achieve alignment.
Create collaboration points as mechanisms for deeper communication and idea-sharing. The key is meaningful collaboration. Everyone is busy, so you’ll all want to be intentional about crafting the right cadence for partnership. Avoid getting sucked into the “quicksand” of over-collaboration.
Finally, it’s good to remember that conflict can have its benefits. You can mine diamonds from the pressure of divergent perspectives. (See “Building Product Strategy with Design Thinking” on page 12 to learn how one product leader set up his team to create this very phenomenon.)
Moving from the black box to the sandbox will require transparency, communication, and effective collaboration. While a focus on relationship-building may require a small time investment upfront, it will pay dividends in the quality of the products you deliver and your team’s efficiency in achieving those market-winning, delightful solutions.