"We aren't exactly sure what we want yet, so let's just start building and iterate on the fly."
In the era of agile methodology, this sounds like smart, fast-moving advice. In reality, it is a recipe for scope creep and burnt-out teams.
There is a massive difference between iterating on a solid foundation and throwing code or design at the wall to see what sticks. A recent study on project workflows revealed a massive red flag: 60% of stakeholders admit to using the execution process to clarify their strategy.
They don't know what they want until you build it.
Using highly-paid developers, designers, and creatives to "figure out the strategy" is the most expensive way to brainstorm.
How to kill the "Build to Think" habit
Because modern tools allow us to build things incredibly fast, people assume planning is obsolete. But fast execution on a bad strategy just means you reach a dead end faster. You have to separate Discovery from Delivery.
- Draw a hard line: Strategy is cheap to change; execution is expensive. Make it clear to stakeholders that iterating on a brief costs nothing, but iterating on a deployed staging environment costs thousands of dollars.
- Force visual alignment early: If a stakeholder needs to "see it to understand it," use wireframes, mood boards, or written user journeys during the briefing phase. Do not use high-fidelity execution to achieve strategic alignment.
- Lock the foundation: Treat the brief like the foundation of a house. Once the concrete is poured, you cannot move the walls without massive expense.
If you don't lock the architecture before you build, you will pay for it in endless revisions.
If you want a system that physically enforces this boundary, I built Brieflodge. It secures mutual sign-off on the strategy and locks the brief on record so you never have to build just to brainstorm again.