The Case for PMs Wireframing: Unlocking Greater Value and Diversity

The idea that PMs shouldn’t build wireframes should be retired now.

Yes, there’s no major need for a PM to always wireframe features. In fact, that’s an anti-pattern. But, for big features, it can be worthwhile.

In other words:

A great wireframe can:

• Convey your entire feature idea in a picture
• Uncover edge user segments you would otherwise discover down the line
• Act as a great tool to use in customer interviews to de-risk your next feature

But you probably already know and agree with that! You don’t wireframe because you believe design should be.

Here’s why PMs should also wireframe:

1. It yields a greater diversity of ideas
2. It increases exec involvement
3. It is a great way for the PM to add value

Find out more about the topic in this deep dive.

1. It brings a greater diversity of ideas to the table

Because of their respective areas of expertise:

→ PMs create basic, business-driving wireframes
→ Designers create beautiful, user-friendly wireframes

The result leads to more diverse ideas overall for the team to evaluate.

2. It increases exec involvement in the solutioning process

A quick wireframe doesn’t have to be a commitment:

• It can be a good way to demonstrate continued progress
• And, it uses the exec’s product sense to arrive on a better solution

3. It is a great way for the PM to add value to the team

If the designer is out that week, or busy with something else, or new to the team… these are all good reasons for the PM to wireframe instead of just waiting.

It’s also a great way for a PM to summarize a bunch of exec discussions in a PRD.