Skip to content

Oliver ReedSystems Lead

A quick start looks good in a proposal. In practice, the weeks saved at the beginning are usually paid back later, with interest, when decisions made in a hurry have to be unpicked after launch.

The Case for Starting Slower

Chrome rabbit figurine standing on a white surface

Fast Starts Hide Slow Finishes

Every client wants to see progress early, and every studio is tempted to give it to them: a moodboard in week one, screens in week two. It feels efficient. But progress you can see is not the same as progress that lasts.

When the thinking is skipped, the questions do not go away. They come back as rounds of revisions, as features that do not fit the system, and as a launch date that slips while everyone wonders why the design keeps changing.

Where the Time Actually Goes

Starting slower does not mean doing less. It means doing the hard part first, while it is still cheap to change course:

  • Agreeing what problem we are solving, in one sentence everyone can repeat
  • Talking to the people who will use the work, not just the people who commission it
  • Writing down the rules before drawing the pictures

By the time we open a design file, most of the arguments have already happened. What follows is quicker, calmer and far less likely to be thrown away.

The Payoff Comes Later

A project that starts slowly tends to finish on time, because there are fewer surprises in the middle. More importantly, it keeps paying back after launch. A brand or product built on agreed foundations can take on new pages, new markets and new people without starting again.

We would rather spend three extra weeks at the beginning than three extra months at the end.

Slowness Is a Choice

We can work quickly, and sometimes a project needs exactly that. But speed is most useful once you know where you are going.

So we start slower on purpose.
It is the fastest way we know to finish well.

Made with Modulify