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
"The coalition of the willing has organically developed into a community for change."
Laura Smith Tom GaylerEmbedding Service Design and Agile Practice within UK Planning Teams to Create Services that Last
December 3, 2024
"Even though we’ve got a single dropdown field, it maps to a far richer set of instructions in the prompt."
Trisha Causley[Demo] Complexity in disguise: Crafting experiences for generative AI features
June 5, 2024
"Not every recommendation from ChatGPT was feasible for the Nigerian context, so human collaboration was essential."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"Developing team flow is a lot like dating—you have to nurture it, build instinct, and practice."
Ruzanna RozmanGetting in Flow with Your Team
January 8, 2024
"Natural language processing is basically about figuring out how to math words."
Karen McGrane Jeff EatonAI for Information Architects: Are the robots coming for our jobs?
November 21, 2024
"There are four trigger types: random, fixed, contextual, and self-initiated, each serving a unique purpose."
Amelia ColeData-Prompted Interviews
December 17, 2021
"Give non-researchers some applause when they run a test even if it's not perfect, then help them do it differently next time."
Trisha TerharEmpathizing with the Empowered: Non-Researcher Responses to Democratization
March 10, 2022
"We cannot just sit around and map systems. We can design where performance arrangements are made."
Jen van der MeerService design performs value
November 19, 2025
"Cross-training helps teams feel more capable and less afraid of losing their jobs during transitions, creating less resistance to change."
Steve Baty Richard Dalton Maria Giudice Harry MaxDiscussion
June 9, 2016
