Why we built Proxeum.

In 2012 I was running a project management office, and I spent more of my week managing spreadsheets than managing execution.

That is not a complaint about spreadsheets. The tracker had simply become the job. I rebuilt it every Monday. By Thursday somebody would email me a version of it that no longer matched mine, and I would spend an evening reconciling two documents that were both, in their own way, correct.

If you have worked anywhere that runs on spreadsheets, you already know how the folder looked.

Master Tracker.xlsxMon 8:14 AM

Master Tracker FINAL.xlsxMon 4:02 PM

Master Tracker FINAL_v7.xlsxWed 11:47 AM

Master Tracker FINAL_v7_REVISED.xlsxThu 6:31 PM

Master Tracker FINAL_v7_REVISED (Dennis edits).xlsxFri 9:58 PM

I did what most people do. I got better at the tracker. I color-coded it, locked cells, wrote instructions, and asked people, politely and then less politely, to use the version in the shared folder. It worked for about a month at a time.

Eventually I stopped trying to fix the file and started paying attention to why it kept happening. And what I found was not a spreadsheet problem at all.

A priority would be agreed in one forum, planned in another, tracked in a third, and reported in a fourth. Every handoff cost a little context. By the time work reached the people doing it, the original intent had thinned. By the time status reached leadership, it had been summarized into a confidence the underlying data did not support. That is how you end up with a status report that is green while the whole organization feels behind. Nobody is lying. The information simply degrades on its way up.

For a long time I assumed this was a discipline problem, and that better people or better meetings would fix it. They did not. I would arrive, install structure, and results would improve. I would leave, and within two quarters the organization drifted back. Nobody was failing. The organization simply had no shared way to execute.

Once I stopped looking for the person responsible and started looking at the spread of outcomes, the same picture appeared in every organization I walked into.

• One leader consistently delivers.Another struggles.
• One team finishes early.Another misses every date.
• One initiative creates measurable value.Another quietly fades away.
• One facility executes the plan.Another rewrites it.

Same organization. Same strategy. Often the same budget and the same calibre of people. What separates those columns is not effort and it is not talent. It is that execution happens differently for every leader, every department, every project, and every facility. That spread has a name in every other discipline that got serious about quality. It is variability, and variability can be engineered out of a system.

Before there was a platform, there was a method. It lived on flip charts, in templates, in a decision log, and in a weekly cadence that refused to move.

By 2013 I was consulting inside hospitals, and the room below is where a lot of it got worked out. No company. No product. No investors. A borrowed conference room, a folding table, and a sheet of paper with the whole engagement written on it in marker.

I built the method because I needed it. Every initiative started from the same charter. Every decision was written down with an owner and a date. Every week, the same review asked the same questions in the same order: what moved, what did not, what decision is waiting, and who owns the next step.

It worked. Initiatives that had been drifting for months started closing. Leaders stopped asking for updates because the updates were already there. The method was not clever. It was consistent, and consistency turned out to be the whole point.

Then I watched it fail for a reason I had not anticipated. It only worked where I was standing. The method lived on paper and in my head, so it travelled exactly as far as my attention did. Hand it to another leader and it degraded. Move to another facility and it had to be rebuilt from scratch. Change the person running it and it quietly stopped.

I had built a methodology. What these organizations needed was a system. A methodology depends on the person carrying it. A system holds without them.

I did not set out to start a company. I set out to stop watching the same failure repeat.

The idea followed me for years. I would sketch it between engagements, put it down when the work got heavy, and pick it up again the next time an initiative stalled for a reason that was entirely preventable. A decision nobody recorded. An owner nobody named. A risk that was visible to three people and invisible to everyone who could have acted on it.

What kept the idea alive was the cost of not having it. Capital committed to initiatives that quietly stopped. Board questions that could not be answered with confidence. Good clinical and operational leaders spending their evenings assembling slides that would be out of date before the meeting started.

Every engagement added another line to the specification. Not features: structure. Governance had to come before execution. Decisions had to be objects, not minutes. Status had to be read from the work rather than reported about it. Visibility had to be observed, not requested.

By the time I was ready to build, I was not designing a product. I was writing down something I had already run, dozens of times, in real organizations, under real pressure.

Every generation of organizations inherits a capability the one before it had to improvise. We think execution is next.

Manufacturing worked this out a long time ago. It did not get better by asking people to care more. It got better by treating variation as the enemy, and by engineering it out of the process until the same input reliably produced the same output. Finance, quality, and safety each made the same journey: from something good leaders did instinctively to something an organization could teach, measure, audit, and rely on.

Execution has not made that transition. It is still treated as a personal skill, distributed unevenly, and rebuilt from nothing every time a leader changes. It is the last major function in most organizations that nobody has engineered.

That is the work. Predictable execution as an organizational capability rather than an individual talent, built into the organizations that carry the most consequence when it fails. A rural hospital that keeps its service line because the initiative actually landed. A health system that can answer a board question with evidence instead of an impression. A transformation leader who inherits a portfolio and finds it intact.

Predictable execution is not created by working harder. It is created by reducing variability. That is not a slogan. It is the only method anyone has ever found that works at scale.