Implementation phase

The direction is set. The concept is signed off. Now we build. The implementation phase is the part where Discover becomes results: drafts, structures, texts, designs, code. Concentrated work. And a rhythm that takes the team with it.

In the team, not in a tunnel.

Going deep into the material belongs to it. The so-called "flow state" is even welcome. Still, the project runs together. A short update in Basecamp is often enough: what is done? Where is it stuck? What still needs a decision? If the direction changes, get feedback early. Not because you have to, but because good work rarely happens alone. And if you are blocked: say so. The team is there to think along, not to judge.

Rhythm instead of guesswork.

We work best when something visible appears regularly: a draft, a structure, a mockup, an interim status. Every three to five working days is, in our experience, a good pulse. Not as deadline pressure, but as a shared beat that holds momentum and makes problems visible early. If an interim status comes later than thought, that is not a failure. Just communicate it, with a reason and a new time. Honesty builds trust. Silence eats time.

The scope as a protected space.

The agreed scope is our shared frame. It helps stay focused. For us and for the client. Not every piece of feedback has to be implemented one to one. If something contradicts the strategy, explain why and show alternatives. If something sits outside the scope, name it kindly and clearly. That way the project stays manageable, without every small request becoming a large detour.

Done. Perfect. Perfectly done.

Perfection is not a state, but our drive. When 80 to 90 percent of the quality is reached and the direction is right, we may ship. Sometimes even before that. Endless polishing without added value helps no one, neither the project nor the team. Ship it when it holds.

The shoulder check closes the phase.

At the end of the implementation phase we look at the status together: is the scope fulfilled? If not, what is still missing for finalisation? Depending on the size of the project there were already further alignment points before: the shared kick-off, one or more shoulder checks along the way. Now it is about the final feedback before handover. The meeting is not an exam, but a moment in which we make sure together that nothing important is lost. What follows from it we document again in Basecamp.

Once the status is aligned, we move into finalisation and handover. There, a shared working status becomes something that also works without us.