Sitting between client requirements and technical delivery

A web development agency where the recurring failure was not technical capability. It was translation: what the client believed they had asked for, and what reached the person building it, drifting apart somewhere between the two.

That gap is administrative, not technical. It is caused by requirements living in a call nobody wrote down.

The useful intervention was boring: every requirement written down where both sides could see it, and every change to a requirement written down as a change rather than absorbed silently.

Doing design and build alongside the coordination is what made the coordination credible. It is difficult to mediate between a client and a developer about feasibility if you have never built the thing.

The agency’s own marketing got scheduled rather than improvised, which is the standard agency failure and an easy one to fix once somebody owns it.