Principal Resolution

Tracy Keogh was the CHRO at HP when someone told her they were glad HR had a seat at the table. She said: HR is the table. This is a manifesto about what that actually means — and what organizations that have figured it out look like versus the ones that have not.

HR Is the Table

Tracy Keogh was the Chief Human Resources Officer at HP when someone walked up to her and said, "I'm glad HR has a seat at the table."

She said, "HR is the table."

Wendi Safstrom, President of the SHRM Foundation, shared that exchange on The Talent War Podcast. She said she has loved it ever since. So have the people she has told it to. The quote travels because it names something that most organizations understand intellectually but have not yet built into how they actually operate.

This is an attempt to say what that means in practice — not as a declaration about the importance of HR, but as a manifesto about what organizations that have figured this out actually look like, and what the ones that have not are quietly paying for not knowing.

The Table Metaphor and Why It Has Mattered

The "seat at the table" framing became shorthand for a legitimate problem. For a long time, human resources functions were structurally positioned as support infrastructure — the department that handled compliance, processed paperwork, and was called when something went wrong with a person. Not a strategic function. Not a decision-making function. A processing function.

The seat at the table argument was a response to that positioning. It said: the people decisions are strategic decisions. The hiring, development, culture, and organizational design choices that HR owns are not administrative outputs. They are the inputs to everything else the organization produces. If HR is not in the room when strategy is being set, then strategy is being set by people who are ignoring the most important variable in whether it succeeds.

This argument was correct. It was also, in most organizations, a losing argument — not because it was wrong, but because it was structured as a request for permission. It positioned HR as an outsider seeking entry into a room where decisions were already being made. It accepted, implicitly, that the table belonged to someone else.

Tracy Keogh's retort changed the terms. HR is not asking for a seat. HR is the architecture that makes the table possible. The question is not whether HR deserves to be there. The question is why we built the table the way we did, and what it says about what we actually believe.

What It Means for HR to Be the Table

An organization is, at its most fundamental level, a set of agreements between people about how they will work together toward a common purpose. The quality of those agreements — how clear they are, how honestly they are maintained, how well they match the actual capabilities and motivations of the people involved — determines almost everything else.

This is HR's domain. Not as an administrative category, but as an organizational function. The people who recruit, develop, structure, evaluate, and retain the humans who do the work are not supporting the strategy. They are executing the most consequential dimension of it.

Every strategic plan eventually encounters a person. It encounters the person who has to change their behavior for the plan to work, and whether they will. It encounters the team that has to coordinate in a new way, and whether they can. It encounters the leader whose style is either an accelerant or a drag on everything the plan requires, and which of those it is. It encounters the culture that either makes the required behaviors natural or treats them as foreign objects.

HR does not sit alongside strategy. HR is the medium through which strategy either succeeds or reveals itself as a fantasy.

The organizations that have internalized this do not describe it as "HR having a seat at the table." They describe it as: every major organizational decision is also a people decision, and we treat it accordingly. The decision to enter a new market is a decision about the capabilities the organization currently has and the ones it needs to acquire. The decision to restructure is a decision about the relationships, communication patterns, and informal power structures that will either survive the change or be destroyed by it. The decision to pursue a new technology is a decision about whether the organization has the learning culture and the leadership behaviors that will allow the technology to be adopted.

These are not HR questions that happen to intersect with strategy. They are the strategy questions. The organizations that understand this do not have HR at the table. They have HR as the organizing logic that determines who is at the table, what they are capable of, and whether the conversation they are having is connected to reality.

What the Alternative Looks Like

Most organizations have not gotten here. Most organizations have HR that is genuinely skilled, genuinely committed, and genuinely constrained by a structural position that limits what it can do.

The symptoms are recognizable.

The organization launches a transformation initiative. A consulting firm produces the strategy deck. The C-suite approves it. HR is brought in to "manage the change" — which in practice means: communicate the change to people who had no input into it, manage the reactions of people who are threatened by it, and hold together a culture that is being asked to absorb a shock it was not prepared for. The initiative produces less than promised. The diagnosis is that "people were resistant to change." The actual diagnosis — that the change was designed without accounting for what it would require of the people who had to implement it — is never written.

The organization wants to improve performance. A performance management system is designed. Competencies are identified. Rating scales are calibrated. Training is delivered. A year later, the performance distribution looks almost identical to what it did before, because the system was built to measure performance that already exists, not to produce performance that does not. The actual levers — how leaders give feedback, how teams are structured, what behaviors are rewarded in practice rather than on paper, whether the organization actually believes that people can develop — were never touched.

The organization is losing talent. Exit interviews are conducted. Themes are identified. A retention initiative is launched. It includes competitive compensation benchmarking and a new recognition program and a manager training curriculum. The actual reason people are leaving — that the leadership in a specific part of the organization has created an environment where the best people eventually decide they have better options — is known by everyone in HR and named by no one in a meeting that the relevant leader attends.

In each of these cases, HR is doing the work it is positioned to do. The positioning is the problem. HR has been structured as a response function rather than a design function. It processes the consequences of decisions that were made without its input. It manages the symptoms of organizational conditions that it did not help design.

This is what it looks like when HR has a seat at the table rather than being the table. It is not a failure of HR capability. It is a failure of organizational architecture.

The Belief System Under the Structure

Every organizational structure is an expression of a belief about how work happens. When HR is positioned as support infrastructure, the implicit belief is that the real work is done by the functions whose outputs are measurable in conventional terms — revenue, product, market share — and that HR supports those functions the way facilities management does: necessary, but not strategic.

This belief is not irrational given a narrow time horizon. In any given quarter, the revenue is more visible than the organizational health that produced it. The product is more visible than the culture that made it possible. The market share is more visible than the talent decisions that will determine whether it holds.

Over longer time horizons, the belief breaks down consistently. The organizations that have sustained high performance across leadership transitions, market disruptions, and competitive pressure are almost always the ones that figured out how to build organizational health as a deliberate practice rather than a lucky accident. The ones that perform well in good conditions and collapse in challenging ones are almost always the ones whose performance was produced by external tailwinds rather than internal capability.

HR being the table is not a positioning argument. It is a claim about where durable organizational performance comes from. It comes from the quality of the people, the quality of the leadership, the quality of the culture, and the quality of the organizational design. These are HR's domains, or they should be. The organizations that have made them HR's domains — not rhetorically, but structurally, with real authority and real accountability — consistently outperform the ones that have not.

This is not an observation about what HR professionals deserve. It is an observation about what works.

What Has to Change

The structural change is straightforward to describe and difficult to execute: HR has to be involved in strategic decisions at the point where they are being made, not after they have been made and need to be implemented. The CHRO has to have the standing to say "this strategy assumes an organizational capability we do not currently have, and here is what it would take to build it" — and have that statement treated as a strategic input rather than a logistical concern.

This requires something from HR and something from the rest of the organization.

From HR: the willingness to be accountable for organizational performance, not just organizational process. Not "we ran the program" but "the program produced this outcome, and here is how we know." The transition from process ownership to outcome ownership is the transition from support function to strategic function. It requires different skills, different metrics, and a different relationship with uncertainty — because outcomes are messier and harder to attribute than processes, and the organizations that want HR to be accountable for outcomes also have to be willing to give HR the authority that accountability requires.

From the rest of the organization: the willingness to treat people decisions as strategic decisions, consistently, including the ones that are uncomfortable. The decision to keep a high-performing leader whose behavior is destroying the team beneath them is a strategic decision with a measurable cost. The decision to promote someone based on technical performance when their leadership capability is undeveloped is a strategic decision with a predictable consequence. The decision to design an incentive structure that rewards individual performance at the expense of collaboration is a strategic decision that will produce exactly the culture it was designed to produce.

These decisions are made every day in organizations that say they believe in HR as a strategic partner. Making them explicitly, with HR at the table for the conversation rather than brought in to manage the fallout, is the operational expression of that belief.

The People Who Build the Table

Tracy Keogh's line works because it reframes the question. The question is not whether HR deserves to be in the room. The question is: who builds the room?

The organization is not a building that houses people. It is a structure made of people — of their agreements, their relationships, their capabilities, their motivations, and their willingness to work toward a shared purpose. The function that shapes all of that is not support infrastructure. It is the architecture of the thing itself.

The seat at the table argument was always asking for the wrong thing. It was asking to be included in a conversation about a structure that HR was already building, whether or not it was in the room.

The organizations that have figured this out are not having a conversation about whether HR belongs at the table. They are asking a different question entirely: what are we building, and are the people who understand how to build it with people actually involved in the design?

That is the question that produces the performance. Everything else is logistics.