Principles of Team Wireframing
Summary
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
"Design ops has the opportunity to set a new default future, not follow the path set by the past."
Dr. Karl JeffriesThe Science of Creativity for DesignOps
January 8, 2024
"You have to understand how the business actually makes money to align UX with it."
Amy MarquezINVEST: Discussion
June 15, 2018
"Trust is built by showing you’re there to help make them succeed, not just push your agenda."
Steve Portigal Chris Chapo Kelly Goto Christian RohrerDiscussion
May 13, 2015
"It took a lot of relationship building and conversations to break down the perception that designers' time was owned by particular teams."
Alicia MootyDesign Staffing Models
September 30, 2021
"UX should be a critical dependency, not an afterthought or checkbox on the to-do list."
Ana Maria Montero Barrantes Aditi Dhar Michelle Kaplan Nate Osborne Matt LaurenceThe Authentic UX Talent Show
January 8, 2024
"Operations tends to be something companies only think about when they are scaling rapidly, but investing early is essential."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"I didn’t want to be part of that as a founder, hacking attention just to fulfill engagement metrics."
Sofia QuinteroThe Product Philosophy Behind EnjoyHQ
March 10, 2021
"When things start to go bad, we’re going to pull the plug on it immediately—that helps build trust."
Laura KleinUnique challenges of innovation in enterprises
April 23, 2020
"You’ve got to take control of the backlog and position your team as value-driven, not just servicing individual teams."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
