We scan new podcasts and send you the top 5 insights daily.
Borrowing from design's critique ritual, product teams can present works-in-progress to peers, stating the problem stage, solutions tried, and specific feedback needed. This fosters knowledge sharing and cross-pollination of ideas with low overhead.
Creating a product vision is only half the battle; its impact comes from relentless distribution. Proactively schedule presentations at all-hands, design reviews, and team meetings. If you don't actively share the work, it's as if it never happened.
To move beyond static playbooks, treat your team's ways of working (e.g., meetings, frameworks) as a product. Define the problem they solve, for whom, and what success looks like. This approach allows for public reflection and iterative improvement based on whether the process is achieving its goal.
Scheduled critiques create bottlenecks and encourage performative feedback. A better model is to empower designers with ownership, letting them decide when to seek input. This "organic grit" model values velocity and makes feedback a tool, not a ritual.
To accelerate design skill, seek out blunt feedback from practitioners you respect. Go beyond high-level user feedback and ask for a "roast" on the visual details. The goal is to get concrete, actionable advice—even down to specific CSS classes—to refine your taste and execution.
The common product development process is a sequential handoff model. A better approach is a "jazz band" model where cross-functional teams collaborate harmoniously from the start. This fosters creativity and reduces rework by including engineers in early ideation, rather than treating them as a final step.
The most effective product reviews eliminate all abstractions. Forbid presentations, pre-reads, and storytelling. Instead, force the entire review to occur within the actual prototype or live code. This removes narrative bias and forces an assessment of the work as the customer will actually experience it.
Teams can cultivate a shared sense of taste by encouraging constant and rigorous critique of both internal and external work. This process allows the team to self-regulate, learn from each other, and elevate their collective craft without top-down mandates.
Formal slide decks for sprint readouts invite a "judgment culture." Instead, use an "open house" format with work-in-progress on whiteboards. This frames the session as a collaborative build, inviting stakeholders to contribute rather than just critique.
Netflix holds a weekly product review where PMs present work via a pre-circulated memo. Unlike typical meetings, all attendees, from the CPO down, are expected to have read and engaged with the memo beforehand. This transforms the meeting into a highly collaborative problem-solving session.
Product reviews are conducted using live demos that the entire meeting can interact with. Team members can fork the prototype in real-time to build on ideas collaboratively, making reviews a dynamic, creative session rather than a passive presentation.