Service 07

Steady improvement, without a rebuild.

Replacing a functioning website is an expensive way to solve a handful of problems. We agree what to fix first, work in short cycles, and check afterwards whether each change did anything. If a cycle stops being worth the money, we stop.

How long
Cycles of 4 to 8 weeks
Who runs it
Reviewed by Dave Curtin, delivered by a small team
What you get

What the engagement includes.

  1. 01A review of the site and its analytics
  2. 02An ordered list of what to fix
  3. 03A first round of changes, fixed in scope
  4. 04Usability and content fixes
  5. 05Speed and accessibility fixes
  6. 06A review every quarter
Common questions

The things people ask before they call.

Why improve rather than rebuild?

Replacing a working site is an expensive way to fix a small number of problems. Where the foundation is sound, steady improvement achieves more for less. Where it is not, I will say so.

How does it work month to month?

We agree priorities, work in short cycles, and review afterwards whether each change made a measurable difference. You can stop at the end of any cycle.

What kind of things get fixed?

Whatever the evidence points to. Commonly: navigation people cannot follow, pages that do not answer the question that brought someone there, slow loading, and forms with high abandonment.

Do we need analytics set up first?

It helps considerably. If nothing useful is running, setting up measurement properly becomes the first cycle of work.

Not sure this is the right service?

Describe the situation and I will tell you whether this is the right piece of work, whether something smaller would do, or whether it is too early.

Start a projectSee everything we do