The Challenge

I ran three projects at once. Each had a master schedule. On paper that was the single record of every milestone and every date. In practice the same dates had to be kept alive in several places at the same time:

  • the master schedule itself
  • a separate tracker for each of two layers of senior review, each watching its own set of milestones
  • a timeline view rebuilt by hand, milestone by milestone, for every review slide deck

None of these talked to each other. Each layer of senior review ran on its own cycle: a call to confirm the dates, then its own tracker updated by hand, then its timeline view dragged back into shape for the slide deck. The same information, entered again and again, slightly different every time.

Dates often move on a live project. When one moved, I had to find every copy and change it by hand. Every week. I was not the only one. Around twenty other projects in the same programme ran on the exact same manual routine, each maintained by someone doing the same repetitive work.

"Ask three trackers for the same date and you can get three answers — which then burns more time reconciling them in the very review meetings the trackers were meant to support."

Half of a senior review could go on working out whose version was right before anyone discussed the actual project. The real cost was not only the hours. Duplicated records drift. The trackers were creating the problem they were meant to solve.

The Approach

The instinct in most teams faced with this is to work harder or buy another tool. Neither fixes it. The problem was not a missing feature. It was the shape of the workflow.

So I mapped it first. Every place a milestone date lived, who needed it and where it flowed next. That map made the fix obvious: there should be one place a date is ever entered or changed. Everything else should read from it rather than hold its own copy.

I made the master schedule that single source of truth. Then I connected the downstream views to it, so the senior-review trackers and the timeline slides pulled from the master automatically instead of being copied across by hand.

"One date change now flows everywhere on its own. The manual chase disappears, because there is nothing left to chase."

The Result

9

hrs/week saved

20+

projects fixed

0

competing versions

On my own three projects the change gave me back nine hours a week. That was time previously spent copying dates between systems, dragging milestones into slides and sitting through reviews to walk the same datasets line by line, often when nothing on my projects had changed since the last one. Once everything ran off one source, a lot of that review time was no longer necessary.

The bigger outcome was at programme scale. I built the same fix for the whole programme, so the twenty-plus projects that had each run the manual routine now operated from one source. The separate trackers were not swapped for tidier ones. They were no longer needed at all.

The data itself got better too. With one source there were no competing versions of the same date to reconcile. Everyone, at every level of review, was working from the same number.

Why This Matters Now

That last point — one clean version of the truth — is the foundation everything else is built on.

For AI to work, it needs a single source of truth. That is what lets it connect your workflows and tools together in a reliable, repeatable way. Point an AI tool at information that lives three different ways across three systems and it will hand you confident, wrong answers — because it has no way of knowing which version is true. Give it one clean source and it can finally do something useful.

"Fixing the workflow is the 90 percent of the job that everyone skips. AI is the last 10 percent. We build in that order on purpose."

Map how the work actually flows, consolidate to a single source, automate the handoffs, then add AI only once there is one clean version of the truth for it to work from. A single source of truth is not just a tidier way to work today — it already saved nine hours a week here. It is also the groundwork that makes any automation or AI you add later actually reliable.

This is a project from my own career, before QTAI. It is exactly what we now do for the businesses we work with. We find where the same information is entered in more than one place and turn that sprawl into a single source the whole team can trust. Any AI added later trusts it too.

Where to Start

If your team enters the same data into more than one place, that is usually the first thing worth fixing.

It is rarely the most exciting problem in the building. It is almost always the one quietly costing the most. Book a discovery call and we will map where your time is going.

Book a Free Discovery Call