← Notes from the studio
Operations

8 posts tagged Operations.

Everything we’ve written about Operations — sorted newest first.

Operations

Getting off spreadsheets: the operations data guide.

A complete guide to moving an organisation off spreadsheets — why the estate fails, what it really costs, how to fix the reporting, and how to migrate without the team reverting.

HCOMS06 / 26
Operations

Rolling out a new system without the team reverting.

The technical migration is the easy half. The harder half is what happens to the people. A practical guide to the rollout, in the order it tends to bite, with the three signs it has actually landed.

HCOMS05 / 26
Operations

That's the way it has always been: the most expensive sentence in operations.

Every internal process has at least one step that survives only by habit. The audit that finds them, and the discipline that turns customisation into ongoing efficiency rather than ongoing drag.

HCOMS05 / 26
Operations

Re-keying: the most expensive habit in operations.

Typing the same fact into three systems is the clearest sign that you do not have a central record. The four costs, where the habit comes from, and how to retire it in priority order.

HCOMS05 / 26
Operations

The shadow spreadsheet problem.

Every team that has invested in a proper system also has a shadow spreadsheet. The four reasons they appear, what each one is telling you, and how to absorb them without insulting the team.

HCOMS05 / 26
Operations

One record, one place: what single source of truth actually means in practice.

Single source of truth is easy to agree with and hard to implement. A practical guide to the ownership map, the conversation it forces, and what changes when it is in place.

HCOMS05 / 26
Operations

When five SaaS tools cost more than one custom system.

The hidden integration tax, the data-fragmentation cost, and the point where the SaaS stack genuinely becomes more expensive than building.

HCOMS03 / 26
Operations

Documentation as a feature, not a deliverable.

Software documentation rots because nobody owns it after sign-off. Treating it as a deliverable guarantees decay; treating it as a feature is the only thing that does not.

HCOMS02 / 26