The Ghost in the Steinway

Alex E.S. is a man who understands that some things cannot be captured by a lens, no matter how high the resolution. He is a piano tuner by trade, a man who carries a leather roll of levers and mutes into the quiet living rooms of people who haven’t touched their Steinways since the last administration.

When Alex works, he isn’t just tightening wires; he is listening for the “bloom” of a note, a specific acoustic resonance that depends entirely on the humidity of the room, the thickness of the carpet, and the age of the felt on the hammers.

If you were to set up a tripod and record him for ninety minutes, you would see his hands move with practiced precision. You would see him strike the middle C and turn the wrench. But when he leaves, and the piano eventually slips out of tune again six months later, that recording will be utterly useless to you.

You can watch his hands a thousand times, but you will not have his ears. You have the record of an event, but you do not have the capability of the master.

The Fallacy of the “Home Movie” Handover

In the world of high-stakes web development, we have fallen into the trap of believing that the recording is the training. We treat the handover of a complex, million-dollar digital ecosystem like a home movie.

There is a CMO in the room who is thinking about the quarterly board deck; there is an intern who is terrified of breaking a font style; and there is a project manager who is already mentally transitioning to a different account.

The developer’s cursor flies across the screen at three hundred miles per hour; the observers nod with the rhythmic hollowness of a wooden metronome; the recording light glows red to signal that the responsibility has officially shifted from the maker to the owner; we mistake the capture of a timestamp for the planting of a seed.

The Silent Failure of the Digital Archive

Let us examine the folder where this recording eventually resides. It is usually a sub-directory of a sub-directory, labeled “Training_Final_v1_DO_NOT_DELETE.” It sits there, a 1.2-gigabyte file of static and screen-glare, gathering digital dust.

The contractual milestone has been met. The agency has “onboarded” the client. The invoice is cleared. But the knowledge hasn’t actually moved; it has only been archived.

I am particularly sensitive to the failures of communication right now. Last week, while delivering a highly technical presentation on database architecture to a room of skeptical stakeholders, I developed a case of the hiccups.

Not the polite, quiet kind, but the violent, chest-racking variety that makes you sound like a malfunctioning bellows. Every fourteen seconds, my point about data integrity was punctuated by a sharp, involuntary “hic.”

It was a humbling reminder that the medium of the message is often more fragile than we care to admit. When we record a CMS training, we are recording the hiccups of the process-the “ums,” the “wait, let me refresh that,” the “can everyone see my screen?”-rather than the foundational logic of why the site was built the way it was.

The “August Hire” Crisis

The real crisis doesn’t happen during launch week. The crisis happens in August, five months after the site has gone live.

The original intern has returned to university. The project manager has moved on to a boutique agency in London. The CMO has been replaced by someone who “doesn’t really like the hero section.” Into this vacuum steps a new content lead.

They are talented, ambitious, and have absolutely no idea how the custom schema for the blog’s “related articles” section was designed to function. They ask where the training is. Someone finds the link.

“The content lead has the file, but they still have no vocabulary for the system.”

What they find is ninety minutes of a stranger’s screen, half of which is spent discussing a bug that was fixed in April, and the other half spent on a specific CSS naming convention that the developer never actually explained.

They end up opening a support ticket to ask how to add a simple blog post, which is the digital equivalent of hiring a piano tuner to hit a single key. This disconnect happens because organizations mistake the transfer of files for the transfer of capability.

Sites That Are “Enabled,” Not Just “Delivered”

In the rush to reach the “finish line” of a project, the handover is treated as a ceremony rather than an education. A true handover is not an event; it is the construction of a bridge.

When we talk about CMS flexibility, we aren’t just talking about having a lot of buttons to click. We are talking about an architecture that makes sense to a human who wasn’t in the room when the code was written.

This is why the “engineering first” approach matters. If a site is built by a team that understands how marketing directors actually think-people like the team at

Coherent Agency,

who refuse to pass off work to subcontractors mid-stream-the resulting CMS isn’t a labyrinth of confusion. It’s a tool with a clear logic.

The Logic Baked Into the Bones

The way a system actually works is rarely found in the “How-To” video. It is found in the technical SEO, the AEO strategy, and the schema markup that is baked into the very bones of the site.

A developer might show you where the “Publish” button is, but that is the easy part. The hard part is understanding why the schema was written to prioritize certain data points for AI-driven search engines, or how the motion work in GSAP is tied to the scroll position to prevent layout shift.

That logic isn’t a “step” you can record; it is a philosophy you have to inherit. We often see agencies deliver a beautiful design that loads with the speed of a glacier and converts with the efficiency of a screen door.

The client is happy on day one because the “recording” looks great. But three months later, the site is a mess because the marketing team didn’t understand the constraints. They didn’t understand that the “pixel-perfect” build required a specific image aspect ratio, or that the custom app development wasn’t just a “plugin” they could toggle on and off.

Liability Shift Disguised as Value

Let us be honest about the incentives at play. For most vendors, the goal is to get the recording done so they can move the project to the “Support & Maintenance” phase. It is a defensive maneuver.

If the client breaks something, the agency can point to the video and say, “We showed you how to do that at the 42-minute mark.” It is a liability shift disguised as a value-add.

But for the marketing director who is personally accountable for the pipeline, that “proof” of training doesn’t help when the lead-gen form stops working ten minutes before a major campaign launch. The failure of the recorded training is a failure of empathy.

It assumes that the person watching the video has the same mental model as the person making it. It ignores the reality of organizational churn, the “August Hire” problem, and the fact that most people learn by doing, not by watching a recording of someone else doing.

The Touch of the Instrument

If you want a website that actually functions as a growth engine, you have to stop valuing the recording and start valuing the architecture. You need a system that is intuitive enough that the “training” is almost redundant.

This requires an agency that doesn’t just hand over a “v1” and vanish. It requires a partner that builds with the end-user’s vocabulary in mind from the very first wireframe.

When Alex E.S. finishes tuning a piano, he doesn’t give the owner a video of his work. Instead, he plays a few chords-simple, resonant, and clear. He invites the owner to sit down and play something.

He listens to them play, and if he hears a slight buzzing in the upper register, he adjusts it right then and there, while the owner’s hands are still on the keys. He ensures they feel the weight of the action. He leaves them with an instrument that they understand through their own touch, not through a screen.

We should expect the same from our digital instruments. The next time an agency offers you a “recorded training session” as their primary method of handover, ask yourself if you are buying a capability or just a file.

Ask if the person who will be running the site in six months will find a bridge in that folder, or just the fading echo of a conversation they were never part of. We have to stop treating the CMS as a mystery that needs a secret decoder ring, and start treating it as the foundational infrastructure of the business.

Anything less is just a recording of a song that no one knows how to play.