How to Structure a 45-Minute App Critique (Even If You Can Barely Talk for 10)
- Tianyu Koenig
- 17 hours ago
- 5 min read
Most candidates struggle with the same problem during product or design interviews. They start an app critique and run out of things to say within ten minutes. Then they wonder, how is anyone supposed to talk about an app for forty five minutes?
The truth is, the actual critique only takes about twenty minutes.
What fills the rest of the time is your thinking, your perspective, your storytelling, and your ability to connect product decisions to user needs and business outcomes.
If you only describe features, you will finish quickly. If you connect user flows to user needs, business goals, design decisions, and tradeoffs, the conversation naturally expands. That is what turns ten minutes into forty five. Once you understand this, a forty five minute critique no longer feels long.
A strong critique is not about listing features. It is about structuring your thinking.
Let's get started.
Start with Context, Not Opinions (5 Min)
The first mistake most people make is jumping straight into critique. Instead, begin by grounding your audience.
In some cases, the interviewer may provide a few app options, and you will need to choose one. After that, share any relevant context, such as why you selected this particular app and what you aim to demonstrate through your critique.
It is also important to briefly confirm that your setup is working properly, including screen sharing or recording if required.
You can structure it like this:
“Hi! I’m xx, interviewing for PD, I’m excited to do this fun exercise with you. Today, I’ll be critiquing the XYZ app. I chose this app because… My critique will focus on … I will dive into two key flows, going through what works well, where it creates friction, and suggest opportunities for refinement.”
This opening only takes a few minutes, but it sets the tone for everything that follows.
Build a Clear Product and Business Understanding (10 min)
Before critiquing anything, you need to show that you understand the product.
Start with a one sentence description of the app, clearly explaining who it is for and what it does. Then expand into the company level by outlining its mission and current business goals. You should also touch on how the product makes money, including its monetization model and revenue streams, as well as the primary success metrics or product KPIs it likely tracks.
It is also important to ground your perspective by briefly explaining how you personally use the product. This helps frame your critique and shows where your insights are coming from.
Finally, include a short comparison of the competitive landscape to highlight how this product differs from others in the same space.
This is how you can structure everything:
“[App Name] is a [type of tool] for [target audience] that helps them [core job-to-be-done].
The company’s mission is to…, and their current business goals likely focus on…
From a monetization perspective, they likely use a freemium model with paid tiers, and may be exploring additional revenue streams such as…
In terms of success metrics, they are probably tracking user retention, activation, conversion to paid, and overall engagement.
Personally, I use the product for…, which gives me a particular lens into the experience. I’ll also balance that with a first-time user perspective.
In terms of competitors, products like A are strong in…, but weaker in…, while B does … better but lacks…. Compared to them, [Target App] differentiates itself by…”
You are setting up the foundation for your later critique.
Go Deep on One or Two Key User Flows (2x10 min)
Focus on one or two key user flows that are central to the app’s value.
For each flow, walk through the experience step by step and evaluate both what works well and what does not. Use UX principles to support your reasoning, but more importantly, explain your thinking clearly.
As you analyze the flow, connect your observations back to primary user needs and business goals. A strong critique is not just about identifying friction, but about understanding how that friction impacts outcomes like onboarding, engagement, or retention.
You should also incorporate both visual design and interaction design into your analysis. Look at elements such as layout, hierarchy, clarity, feedback, and usability, as well as how users move through the experience. If possible, briefly consider the designer’s perspective and what constraints may have influenced certain decisions, such as technical limitations or business priorities.
This is how you can structure everything:
“[Flow Name, such as ‘Creating a new project’] is a core flow because it directly supports the app’s primary value.
What works well is…, such as a clean interface, clear hierarchy, and alignment with usability principles like visibility of system status.
Where it falls short is…, where [specific pain point] creates friction, especially for [user type], and may violate principles like recognition over recall.
This flow directly impacts key goals such as [onboarding, engagement, or collaboration], and influences important metrics like…
From a visual and interaction design perspective, the experience is generally [cohesive, intuitive], but areas like [contrast, tap targets, motion, or platform-specific behavior] could be improved.”
At this stage, you are not just describing the experience. You are envisioning yourself as the designer and building a structured, insight-driven analysis that connects user behavior, design decisions, and business impact.
Propose Improvements and Think in Tradeoffs (10 min)
A critique without solutions feels incomplete. After identifying problems, suggest what you would change.
Be specific. Tie your ideas back to user needs and business impact. Explain how your proposal could improve metrics such as activation, retention, or monetization.
A strong answer does not stop at proposing ideas. It also evaluates them. You should actively critique your own suggestions by considering potential risks or tradeoffs. This shows that you understand product decisions are rarely straightforward and often involve balancing competing priorities.
This is how you can put everything together:
“I would improve [feature, design pattern, or process] to better support [specific user need or pain point].
This change would help users achieve goals such as [faster onboarding, easier discovery, or better collaboration], making the overall experience more efficient and intuitive.
From a business perspective, it could also improve key metrics such as retention, conversion, or monetization by [how the impact happens].
However, this approach comes with tradeoffs. It may introduce additional complexity to the interface, require backend changes, or create friction for certain user segments.
To address these risks, I would consider starting with a lightweight MVP, validating the impact through A/B testing on core KPIs, and potentially rolling out the feature gradually to specific user groups.”
How to Practice Effectively
The best way to improve is to practice with familiar apps. Pick products you use often. This allows you to go deeper and speak more naturally.
Well known consumer apps like Spotify, Notion, Google Maps, Slack, Airbnb, or Robinhood are great starting points because you already understand their context and competitors.
Try structuring your critique using the framework above. Over time, you will notice a shift. You will stop worrying about filling time and start focusing on telling a strong, structured story.
Final Thought
A great app critique is not about being right. It is about being structured, thoughtful, and grounded in real user and business impact.
Once you approach it this way, forty five minutes is no longer a challenge but an opportunity.
-
Want to practice together? I’d love to help. Feel free to book a free 15-minute consultation with me below.
Comments