01
Describe the task before the feature list
Start with the intended user and the problem the app should solve. Describe a complete journey: how someone starts, what information they need, and what a useful outcome looks like. Concrete examples help the team agree on the product more effectively than a long list of disconnected features.
02
Make platform decisions in context
Consider target devices, existing systems, integration needs, and release constraints. Native and cross-platform approaches involve different tradeoffs. A product discussion should connect the technical choice to the experience and the work the first release actually needs.
03
Review the experience early
Use journeys, interface designs, and a focused prototype to discuss the important states. Include empty states, errors, access permissions, and the path back when something goes wrong. Early review can expose questions that are harder to resolve after the implementation is complete.
04
Agree on acceptance and handover
Define representative examples that show whether the agreed scope works. Include accessibility, device behavior, integration boundaries, and release preparation in the discussion. Before handover, clarify access, documentation, ownership, and how future maintenance or improvements will be scoped.