Wireframing Is a Team Sport
summary
Argues that wireframes function as transient artifacts for teams not deliverables that lock decisions and shows how PMs, designers, and developers actually use them: PMs get ideas down and generate variants, designers iterate and bridge feasibility and usability, developers sketch backend flows and map to design system components for implementation. Recommends limited-purpose tools (Balsamiq-style) to avoid premature polish, explicit handoffs with annotations and conversations, and that wireframes stay comfortable with divergence and convergence so ideas can be explored and refined.
AI-written summary · about
chapters (8)
- 0:00Introduction and welcome
- 2:58Why wireframing matters in 2023
- 6:27Teams and silos in software design
- 9:17Wireframes as team tools
- 13:29Wireframing for different roles
- 16:53Ten principles of effective wireframes
- 19:40Getting buy-in for wireframing
- 22:26Q&A session
related talks
52mQuestioning the "why"
23mThink Outside the Wireframe – How Design Becomes a Team Player
01h 03mUX Design for Product Managers
26mIdeation and Prototyping: Think Bigger, Fail Quicker
45mArtistic Drawing Applied to the Web Layout Designer
55mFrom Squiggles to Straight Lines: Sketch To Make Decisions & Get On With It
48mResponsive Design Workflow
48mGet your screen together: Design skills for frontend people