Principles of Team Wireframing
Summary
Wireframing is not just making sketches; it's about team communication. Make handoffs clear, know why you're wireframing, and annotate your work. Roles like Product Managers, Designers, and Developers all benefit from wireframing for different reasons. PMs can clarify requirements and sketch ideas, designers can generate multiple options, and developers can understand what's easy or hard to code. So yeah, wireframing is great for teams, not just designers.
Key Insights
-
•
Wireframes are best seen as low-fidelity communication tools, not final deliverables or prototypes.
-
•
The real value of wireframes lies in the collaborative process of creating and iterating them.
-
•
Many teams lose the thread of wireframing as a communication tool when wireframes become overly detailed and siloed.
-
•
Billy’s five principles of team wireframing are articulate, generate, iterate, communicate, and validate.
-
•
Staying in low fidelity throughout most of the design process encourages rapid idea exploration and easier feedback.
-
•
Tools like Balsamiq intentionally limit high-fidelity design to keep users focused on idea communication rather than polished visuals.
-
•
Including content and content design in wireframes helps prepare for high-fidelity visual design and improves usability discussions.
-
•
Wireframes should enable alignment on user goals and flows before moving to detailed design or development.
-
•
Collaboration between UX designers, UI designers, product managers, and developers is crucial to successful wireframing.
-
•
Organizing multiple iterations with a hub-and-spoke file structure helps manage complexity in wireframing projects.
Notable Quotes
"Wireframes don’t add value to the product, customers don’t buy and install wireframes. The true value is the wireframing process."
"Wireframes are like an idea in time you can use for conversation."
"If you had to visualize what you thought you agreed to in a meeting, a lot of times there’s misalignment."
"Wireframes should not really be considered prototypes or high polished scale models of the thing."
"Low fidelity design lets you try things quickly and learn so much before you get too detailed."
"The more detailed, the more you start siloing and confusing the whole project."
"I like adding content to wireframes because they’re the best place for content design."
"Balsamiq is more a communication tool, intentionally limiting high polish so you focus on sharing ideas and getting feedback."
"If you show something that looks ready to ship too early, you may miss exploring 30 other concepts quickly."
"Collaboration is key; wireframes shouldn’t be thrown over the fence from UX to design without discussion."
Or choose a question:
More Videos
"We’re still at a nebula moment where defining what DesignOps truly is remains difficult."
Dave Malouf Patrizia Bertini Jon FukudaThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 2)
April 28, 2022
"The path of the eagle is technological growth without wisdom, while the condor represents spiritual respect for life."
Jayne Engle Tanya Chung-Tiam-FookCivic Design for the Next Seven Generations—A Discussion on Sacred Civics
August 25, 2022
"The fear is often from a perception of some locked-in future that we might not be caught up to understand yet."
Frances Yllana Jorge Arango Maria Taylor Briana ThomasThe Big Question about Impact: A Panel Discussion
September 24, 2024
"Diversity at the bottom without diversity at the top means narrowing perspective from the top down."
Joi FreemanA New Vantage Point: Building a Pipeline for Multifaceted Research(ers)
March 30, 2020
"The alternate to engaging with conflict is suffering quietly or accumulating conflict debt."
Laura WeissTurn Down the Heat: 3 Ways to Handle Conflict in the Moment
November 20, 2024
"Moving fast into prototyping helps keep momentum going beyond the fun ideation phase to actual implementation."
Stephanie WadeBuilding and Sustaining Design in Government
December 8, 2021
"Educating design leaders on setting expectations for Design Ops roles is critical to avoid 'teams of one' who are expected to do everything."
Dave Malouf Meredith Black Farid SabitovThe Past, Present, and Future of DesignOps: a 2-part DesignOps Community Call (Part 1)
February 17, 2022
"A producer is probably in JIRA day-to-day, running tasks, creating tickets and epics, while a program manager tracks board-level timelines."
Panel Discussion: Communicating the Value of DesignOps
November 7, 2018
"The legacy of folders and nested structures causes real problems in finding research and scaling repositories."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
