To give effective feedback, structure reviews at two key moments. At 20% completion, you can correct the overall direction before significant investment. At 80%, you can refine the nearly-finished product while there is still time for meaningful changes. Feedback at 0% is too early, and at 100% it's too late.
Related Insights
Menlo's weekly "show and tell" meetings involve the client directly in the development process. By having clients demo the work and plan the next week's tasks, the team ensures continuous alignment and avoids the common pitfall of delivering a finished product that misses the mark after months of isolated work.
Premortems are not just for project kickoffs. They are a powerful diagnostic tool when a project feels 'off track' or when teams are 'speaking from different sheets of music.' This can surface misalignments and communication breakdowns that sprint retrospectives might not catch.
Create dedicated time for two distinct processes. First, an 'idea development' phase for brainstorming without judgment of budget or feasibility. Only after this phase is complete should you move to a 'refining' phase to assess practicality.
To save a struggling product launch, you cannot wait for quarterly reviews. Implement a rapid, monthly feedback loop to assess messaging perception and performance. This allows the entire cross-functional team to adjust the strategy and execution plan in real-time before negative market perception solidifies.
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.
Early demos shouldn't be used to ask, "Did we build the right thing?" Instead, present them to customers to test your core assumptions and ask, "Did we understand your problem correctly?" This reframes feedback, focusing on the root cause before investing heavily in a specific solution.
Out of ten principles, the most crucial are solving real user needs, releasing value in slices for quick feedback, and simplifying to avoid dependencies. These directly address the greatest wastes of development capacity: building unwanted features and getting stalled by others.
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.
Methodologies like Agile are just tools. The fundamental principle is creating a feedback mechanism for error correction. Instead of dogmatically following a framework, leaders should choose a system that provides the right frequency of feedback and adjustment for their specific project.
The misconception that discovery slows down delivery is dangerous. Like stretching before a race prevents injury, proper, time-boxed discovery prevents building the wrong thing. This avoids costly code rewrites and iterative launches that miss the mark, ultimately speeding up the delivery of a successful product.
