Does The Truth Travel

There is a moment in a company’s growth when leadership decides it is time to get serious about developing people. The organization has outgrown informal management. Managers are managing managers. Founders can no longer see everything themselves. Performance discussions happen inconsistently. Succession exists mostly as assumptions.

The response is almost always the same: a list.

Leadership development. Performance management. Succession planning. Manager training. Learning systems. Competencies. Career paths.

These are all things leadership should be doing, but the existence of a list itself doesn’t solve the problem.

Programs are visible. They have names, schedules, and owners. They produce decks, completion rates, and satisfaction scores. They signal that the organization takes development seriously. What they do not automatically produce is the thing the organization actually needs: a reliable way for information about people to travel to the decisions that affect those people.

That is a systems problem.

The distinction matters because programs and systems fail differently. A program that underperforms gets redesigned or replaced. A system that doesn’t work causes decisions to be made on bad information, or no information, for years. Succession pipelines built on social capital rather than assessed readiness. Performance conversations that produce ratings but not insight. Manager capability initiatives that train to a standard nobody modeled or enforced. Development plans that get written in January and opened again in December.

I once had a leader, in the very same meeting, state that she didn’t want the process at hand to be a “check the box exercise,” and also that it’s so simple “all you have to do is check a box.” It was an unintentional but accurate description of how many organizations approach people systems.

They understand that meaningful conversations matter. They also measure the easiest thing to see: completion. Over time, the box becomes the objective and the conversation becomes optional.

The program succeeds. The system fails.

The organizations that get this right at the mid-size moment do something the list doesn’t capture. Before they build, they ask where information about people currently goes and what happens when it gets there.

Who knows that a high-potential manager is burning out?

• Does that knowledge reach the person with authority to act, and in time to matter?
• Who knows that the most critical role in a business unit has no credible internal successor?
• Does that reality surface in a resource allocation conversation, or only at the moment of departure?

These are not questions about programs. They are questions about whether the organization has built the infrastructure for truth to travel.

The four layers of that infrastructure are the same in a two-hundred-person company as in a twenty-thousand-person company, even if the architecture looks different.

• Leadership practices determine whether managers are having the real conversations or the comfortable ones.
• Core systems determine whether the information from those conversations gets captured and used.
• Culture and norms determine whether candor is safe or whether the organization has learned to produce polished assessments that tell senior leaders what they want to hear.
• Governance determines whether any of it connects to a decision.

A mid-size company building people infrastructure for the first time has an advantage it rarely uses. It is small enough to see clearly. The signals are not buried under decades of accumulated process and political noise. The organization can actually know who its best people are, where the capability gaps live, and which leaders are developing others and which are hoarding talent. That clarity is an asset. The question is whether the infrastructure being built is designed to capture it and move it to action, or designed to demonstrate that the company now has programs.

Systems for organizational people information never reaches the decisions that matter: The manager knows. The HR partner knows. The team knows.

And yet the system doesn’t know.

And if the system doesn’t know, the organization acts as if the problem doesn’t exist.

That is why the first question is never what program to build.

The first question is whether the organization has created a reliable way for truth to travel.

Everything else is implementation.