Workforce Architecture Is Not a Framework. It Is a Confession.

There was a file I found in a shared drive of a company I had been working with for eighteen months. It was called comp_philosophy_v3_FINAL_updated.xlsx. It had been created in 2014 by a compensation consultant who had not worked for the company in four years. It was the authoritative reference document for pay decisions across thirteen business units and two countries.

Nobody had opened it in fourteen months.

I found it by accident. I was looking for something else, a historical record of a band adjustment I had been trying to reconstruct, and the spreadsheet surfaced because someone had once linked to it from a slide deck that was itself four years old. I opened it. The tabs were color-coded. The formulas mostly still worked. The logic, which had been thoughtful when it was written, was elegant in the way that compensation philosophies are elegant when they have been built with real care.

It was also completely disconnected from how the organization actually made pay decisions.

That gap is the subject of this essay. Because what I have learned, after two decades inside large organizations, is that most people infrastructures are not strategies. They are artifacts. Nobody designed them. They just happened, one reaction at a time, one leader at a time, one forgotten spreadsheet at a time, until the accumulation became the architecture.

The accumulation

Most organizations do not have a people infrastructure.

They have an accumulation.

A policy written in 2014 that nobody updated. A job family structure designed for a company half the current size. A compensation philosophy that exists as a slide in an old board deck and nowhere else. A leadership competency model that was borrowed from a consulting firm the current CEO has never heard of.

Nobody designed it. It just happened. One decision at a time. One year at a time. One new leader at a time. Each one adding a layer without removing what came before.

I have spent two decades inside organizations like this. Large, complex, regulated. Public sector. Crown corporations. Multi-country operations. Retail. Financial services. And in every single one, the people infrastructure was the thing that nobody wanted to look at directly.

Because looking at it means admitting something uncomfortable.

It means admitting that the org chart is a political document, not an operational one. That the job descriptions bear almost no resemblance to what people actually do. That the performance management process exists to protect the organization legally, not to develop anyone. That the reason promotions feel arbitrary is because the underlying architecture of levels and scope and decision rights was never actually built.

It means admitting that you have been running a function on accumulated debt.

What architecture actually means

Workforce Architecture is what I started calling the work of actually designing these systems intentionally. Not copying what worked somewhere else. Not bolting new tools onto broken foundations. Not hiring a consulting firm to give you a report you already knew the contents of. Designing.

The word architecture matters. A building has structural logic before it has a façade. A system has flows before it has a dashboard. A people function has architecture before it has programs.

Most organizations invert this. They start with programs. They pick a performance management tool. They buy an engagement survey platform. They introduce a leadership framework. And they wonder why none of it holds together.

It does not hold together because there is nothing underneath it holding.

The five questions architecture has to answer

Before the programs, the architecture has to answer five questions.

The role question. What does this job exist to do. Not the title. Not the grade. The actual purpose. What decisions does it own. What does success look like in terms the person in the role and their manager would both recognize without being prompted.

The adjacency question. How does work flow between this role and the ones next to it. Where does accountability sit. Where does it disappear. What does the handoff look like. Who picks up the dropped ball.

The scale question. What happens to this architecture when the organization doubles. When it halves. When it acquires. When it divests. When it moves a function to a new geography. Is the design robust to those shocks, or does it assume the current shape is permanent.

The decision question. What can happen without a meeting. What requires a meeting. What requires a board. Most people infrastructures are silent on this, which is why organizations drown in meetings and call it collaboration.

The visibility question. What does this function look like to the outside. Can a candidate understand it. Can a regulator audit it. Can a new CEO inherit it without starting over. If the answer to any of these is no, the architecture is load-bearing in a way nobody has documented.

Most organizations answer zero of these questions. They answer the program questions instead. They have a new goal-setting process. They have a new manager training curriculum. They have a new recognition platform. And they measure the output of a system they never built.

That is not a technology problem. That is not a training problem. That is not even a change management problem.

That is an architecture problem.

The confession

The reason I call it a confession is that the work requires someone senior to say out loud that the current system is not designed. That it was built by people who had neither the time nor the mandate to design it. That every layer was a reaction to the last crisis, the last regulator, the last departed executive, the last all-hands where someone asked a question nobody wanted to answer.

Confession in the religious sense means two things. You admit the thing. Then you decide to do something about it.

Most organizations do neither. They perform both.

They commission an assessment, get a glossy deck back, nod at the findings, and then quietly put the deck in a SharePoint folder labelled People Transformation 2024. Nothing is confessed. Nothing is decided. The accumulation continues.

The organizations that actually rebuild are the ones where someone senior is willing to say, in a room with other senior people, that the current people infrastructure is not a strategy. It is a compromise that has been running the company for longer than anyone realizes. And that compromise is not free. It is expensive in ways that do not appear on any scorecard.

It costs you your best people, who leave because the career architecture makes no sense.

It costs you your time, because every decision requires a meeting to decode the system.

It costs you trust, because employees can tell the difference between a company that has a structure and a company that has a narrative about structure.

It costs you optionality, because when the moment comes to move fast, the architecture underneath cannot take the weight.

If this essay named something you have been sitting with, subscribe. Beyond the Title sends one essay a week on the architecture of work.

What the rebuild actually looks like

The organizations I have seen actually rebuild this, and there are fewer than I would like, share a small number of characteristics.

They start by making the accumulation visible. Not dramatically. Not as a transformation announcement. Quietly. An honest audit of what exists, who owns it, when it was last reviewed, and whether anyone inside the organization could defend its design if asked.

That audit almost always surfaces the same finding. The majority of the infrastructure was not designed. It was inherited. The current owners, many of them thoughtful and capable, have been operating it without ever having been asked whether it was the right design in the first place.

They separate maintenance from redesign. Most people functions are structured to maintain the current state. That is a reasonable posture when the current state works. It is a catastrophe when the current state was never designed. Maintenance, applied to accumulation, just extends the lifespan of systems that should have been rebuilt years ago. The rebuild requires someone empowered to question the design itself, not just the execution of it.

They sequence the work. Architecture is not a project. It is a multi-year reconstruction of systems that are carrying real weight while the reconstruction happens. You cannot rebuild the job architecture and the performance management system and the compensation philosophy and the career pathways all at the same time. You have to sequence. You have to protect the parts of the current state that are load-bearing. You have to accept that the rebuild will take longer than the political cycle that authorized it, and you have to design the governance so that the work continues even when the leader who started it moves on.

They protect the people doing the work. The hardest part of a rebuild is that it requires people to say, out loud, that the thing they have been running for five years was not built well. That admission is professional risk. In organizations that reward activity over architecture, the leader who confesses the accumulation is often the leader who gets pushed out. The rebuild requires a sponsor willing to shield that leader long enough for the redesign to take root.

What I have learned

In twenty years of doing this work, I have learned one thing with certainty.

The organizations that build intentional workforce architecture do not do it because they are well-funded or well-led or well-advised. They do it because one person, usually in a senior role, looks at the accumulation and names it for what it is.

Once it is named, the rebuild becomes possible.

Until it is named, the rebuild is impossible.

That is the confession. Not that you built something broken. That you inherited it, you kept it, and you have been charging the next generation of employees the interest.

The spreadsheet is still on that shared drive, as far as I know. Nobody deleted it. Nobody updated it. It sits there like a monument to a version of the organization that no longer exists, maintained by a person who no longer works there, containing decisions that nobody remembers making.

It is not the spreadsheet's fault.

It is the natural consequence of an organization that never asked whether its people infrastructure was built or whether it just happened.

That question is where the work begins.

When was the last time someone in your organization looked at the people infrastructure and asked whether it was designed, or whether it just accumulated?

Roy Tran Beyond the Title

If something here landed, or something snagged, the comments are open. I read every one.

The person who comes to mind right now is who this was written for.

Send it to them.