An iOS engineer at Merpay shares a workflow called 'Build First, Discuss Later,' where a working prototype is built before the kickoff meeting rather than after spec finalization. The approach uses three stages: building the best possible prototype beforehand, using it as a shared reference during the meeting to resolve open questions, and immediately reflecting decisions afterward. Results include finishing most discussions in a single meeting, faster and clearer communication, and reduced workload for product managers. The author also notes a mindset shift — engineers become active contributors to product direction rather than passive implementers of requirements, aided by generative AI making rapid prototyping more accessible.
Table of contents
A common development flow—and where it slows downThe "Build First, Discuss Later" approachThree steps for bringing a prototype into a meetingThree things that changed with "Build First, Discuss Later"How building first changed my mindsetConclusion54 Impressions