Twelve months - what compounded

Sled Island is winding down at the Palomino. School is ending across Calgary. The Stampede grounds are getting set up for the third week of the show. Summer has finally arrived in the way that only happens in late June, where the patio at Hayden Block makes business sense again. This is also twelve months into the Operator's Brief, which means it is a reasonable time to look at what compounded across the year and what didn't.

Year-over-year retrospective on the operational habits that actually compound at the mid-market - and the ones that look productive but don't.

A year of operating is roughly 250 working days. Most of those days are unremarkable in the moment. Looking back at twelve months of them, what's striking is how few of the day-by-day decisions actually mattered, and how the ones that did mostly weren't the ones that felt important at the time.

(Vencer Group, the Calgary firm publishing this column, has been operating mid-market energy IT for 19 years. The pattern recognition in this column comes from that - not from cleverness, just from having watched the same things happen enough times.)

The retrospective question worth asking at the end of a year is not "what did we accomplish" but "what compounded." Most things didn't. Some things did. The pattern of which is which is more consistent than people expect.

What compounded for mid-market operators in the past twelve months

Documentation discipline on critical systems. The operators who used the year to actually document - in a way that someone else could pick up - the systems that run their business are in a meaningfully different position than the ones who didn't. Not because the documentation gets used routinely (it mostly doesn't). Because the act of producing it forced clarity on dependencies that nobody had named. When the senior engineer left in October, the operators with documentation lost three weeks. The ones without lost three months.

Vendor relationship hygiene. A small number of operators used the year to actually map their vendor relationships, renegotiate the ones that were drifting, and consolidate where the consolidation made sense. This is unglamorous work that nobody asked for. By the end of twelve months, the operators who did it were paying 8 to 15 percent less for the same coverage and had clearer accountability when things went wrong. The savings continue indefinitely.

Backup restoration testing. The operators who set a quarterly cadence for actually restoring from backup - not testing that backups ran, but testing that systems could be rebuilt from them - are the only ones who actually know what their recovery posture is. The rest are guessing. When the incident comes, the difference between the two groups is everything.

What didn't compound, despite feeling like it should have

Tool adoption sprints. The new platform launched with executive sponsorship, three months of focused adoption work, and a clear set of success metrics. Six months later, usage is half what it was at the launch peak, and the workflows the platform was supposed to replace are still in place. The sprint didn't compound because the structural reasons the old workflows existed didn't get addressed. Most tools fail this way; it isn't the tool's fault.

One-off security improvements without an owner. The control got implemented. The configuration was correct on day one. Nobody owned maintaining it. Twelve months later, the configuration has drifted, the exceptions have multiplied, and the control is functionally not present in the way the auditor assumed it was. This is the most common failure mode at the mid-market and it has nothing to do with tooling sophistication.

Strategic plans without operational anchoring. The strategy decks were good. The leadership team was aligned. Twelve months later, the operational decisions don't trace back to the strategy because no one operationalized the connection. The strategy compounds when the day-to-day decisions reference it; otherwise it's an artifact of an offsite that becomes harder to defend each quarter.

The reading

The habits that compound have a shape. They are unglamorous. They require sustained attention rather than burst attention. They produce small, observable improvements quarter by quarter that look unimpressive in any individual report. They benefit from owners more than from sponsors.

The habits that don't compound also have a shape. They are launched. They have champions. They produce dramatic short-term metrics. They run out of attention before the structural change is locked in.

Both kinds of work get budgeted. Only one of them shows up twenty-four months later as part of the operating fabric. The choice is mostly about which work the leadership team commits to defending past the launch.

Twelve months from now, what would you want to look back on and say compounded.

This issue of the Operator's Brief is operator pattern recognition from Vencer Group's work with mid-market businesses across industries and geographies. Not industry-specific advice. Read accordingly.