Present designs in meetings

I need to present the new onboarding flows at Wednesday’s product review to the head of product, two engineering leads, and Maya from growth. Walk through screens in order, call out the two places we changed user text and the performance assumptions behind them, pause for questions after each flow, and close by asking for a go/no-go decision and any blocking technical concerns.

Before I present to the group, make these slides easy for non-designers to follow: put the conversion lift estimate on the first slide, mark which screens require backend changes, highlight two usability trade-offs we considered, and list the single ask for engineering and the single ask for growth so reviewers can approve quickly.

We just finished the walkthrough and the engineering lead looked confused about the payment step. I am the designer, the lead is Sam, and we have a Friday build deadline. I don’t know whether Sam is worried about technical feasibility, scope, or risk to stability. What’s the most likely diagnosis and the best next move to get a clear go/no-go?

Every demo turns into a long feature debate and we leave without concrete decisions. I run product demos for the PM, two eng leads, and growth. Which habit should I change to keep meetings focused and how should I enforce it so reviewers leave with clear actions?