The week-eleven problem

You ordered a new appointment system for your garage in June. It is now week eleven. Every fortnight an email arrives: on schedule, working on the back end, nearly there. You have seen a design, a list of features and a plan with coloured bars. You have never clicked on anything.

Nothing has gone wrong yet. That is exactly the problem: you have no way of knowing whether something has.

Projects that end badly almost never end badly in one moment. They drift, through small misunderstandings that only become visible at handover. The habit that catches this in time is dull and costs you half an hour a week: every week, you look at something that runs.

Why a week is the right rhythm

A week is short enough that a wrong turn costs a week instead of a quarter. It is long enough to finish something real, so it does not become theatre.

More importantly, it changes the conversation. "How's it going?" always produces "fine". "Here's the link, have a go" produces, within two minutes, the discovery that your mechanics cannot select an MOT for a van, or that the confirmation email only goes out in English. In week two those are notes. In week eleven they are rebuilds.

In our experience a team also works differently when it knows someone will look on Friday. Not out of pressure — it simply pushes you to finish one thing rather than leave ten things half open.

What counts as "working"

This is where it slips. A status update is not a working version. Nor is a screenshot. A demo where someone shares their screen while you watch barely counts either.

  • A link you open yourself, on your own phone, with nobody watching over your shoulder.
  • One task you can complete end to end — book an appointment and receive the confirmation, say. One thing that genuinely works beats five screens that lead nowhere.
  • Test data that resembles your business, not "Customer 1" and "Service A". With real service names you spot the gap in ten seconds.
  • One sentence about what next week will show, in plain words. If that sentence cannot be written, the next step is not clear yet.

It is allowed to be ugly. Unstyled, half filled in, with a button that does nothing yet. That is fine. You are not inspecting the finish, you are checking the direction.

Agree it, don't hope for it

Put it in the quote before you sign, not in an email afterwards. Three lines will do: the first working version in week one or two, even if it does only one thing; a new one every week after that; and a fixed thirty-minute slot in both diaries.

Name one person on your side who decides. Not a committee. Someone who genuinely has that half hour and is allowed to say "yes, carry on" or "no, this is wrong". On a fixed-price project you can tie the payment moments to those versions rather than to dates on a plan.

While you are at it, agree in one sentence that you have access to the code and can export your data. Settled now, it saves an awkward conversation later.

What if a week is empty?

It happens. Holidays, a stubborn problem, a third party you are waiting on. One empty week is information, not an alarm. Ask something specific: what is blocking it, and what is the smallest visible thing that can be ready next week?

Two empty weeks in a row is a signal. Not to get angry about, but to make the job smaller. Almost always it turns out too much is open at once.

What to do this week

  • Have a project running? Ask today for a link to something that works, by Friday. Not a report — a link.
  • About to sign? Ask for "a working version every week, the first in week two" to be written into the quote.
  • Name one person who decides and keeps thirty minutes free each week.

At ITSysPro we work this way because it helps us as much as the client: we hear early when we have misunderstood something. If a project of yours feels stalled right now, we are happy to think it through with you, with no obligation.