The previous post in this series worked through Governance, the domain that determines who holds authority when the founder is not in the room. This post turns to the domain right behind it: People, which asks whether the organization has anyone besides the founder capable of using that authority well, and whether the people it depends on are likely to still be there next year.
Many owners think of the People domain as a hiring problem: find good people, pay them fairly, and the domain takes care of itself. That framing misses much of what actually determines whether a GovCon business can function without its founder. The People domain is where founder dependency is most visible and most expensive, because unlike a governance gap, which can sit quietly for years, a people gap shows up the moment someone leaves and takes capability with them.
If the business loses capability every time you leave the room, the People domain isn’t built yet.
What the People Domain Actually Includes
Hiring and retention get most of the attention when owners think about their people, but the domain is considerably wider than that, and it is worth working through each piece individually rather than treating people as a single line item on the org chart.
Hiring and Recruiting Practices
Some founder-led GovCon businesses hire reactively. Someone departs, and the company scrambles to backfill the role under time pressure, which is a difficult way to hire well under any circumstances and a particularly difficult one in an industry where security clearance timelines can stretch the search out for months. A repeatable recruiting process, one that sources and evaluates talent continuously rather than only when a seat is empty, is the difference between hiring from a position of pressure and hiring from a position of choice.
Onboarding
The first weeks in a new role largely determine how quickly someone becomes productive and how long they stay. Without a defined onboarding process, a new hire’s ramp depends entirely on whoever happens to have time to explain things that week, which means the quality of onboarding varies by accident rather than by design. Structured onboarding is also one of the more efficient ways to start transferring institutional knowledge from individual heads into a process the organization actually owns.
Compensation, Merit Increases, and Bonus Structure
Pay bands, how merit increases are actually decided, and bonus practices all belong in this domain. In a GovCon context, the bonus piece poses a specific risk that many owners do not consider until an audit surfaces it. DCAA reviewers scrutinize bonus payments closely, and a bonus structure that is discretionary, inconsistent, or undocumented can create cost allowability findings that a clearly defined and consistently applied compensation policy would have avoided. Getting this right protects the company in an audit and gives employees a compensation system they can actually trust rather than one that appears to depend on who asked.
Performance Management
A performance management system is only meaningful if it operates on a consistent cycle with clear criteria attached. In some founder-led businesses, performance only comes up when something has already gone wrong, meaning the majority of employees never receive structured feedback on what they are doing well or where they need to grow. This is also where the Accountability discipline from the broader Enterprise Readiness Operating Model™ shows up most directly within the People domain: performance management makes ownership of outcomes visible and reviewable rather than assumed.
Training and Professional Development
Building capability intentionally, rather than relying on people to arrive already fully skilled, matters in every industry, but it carries particular weight in GovCon, given the certifications, clearances, and compliance training that many roles require. A company that treats development as an ongoing investment rather than an occasional expense tends to retain people longer, for the straightforward reason that employees who are growing have less reason to look elsewhere.
Management Quality and the Manager Relationship
People more often leave a manager than they leave a company, and many GovCon businesses have no reliable way to know that a management problem exists until an exit interview reveals it, by which point the information arrives too late to be useful. Regular mechanisms for surfacing how people actually feel about their manager, whether through stay interviews, skip-level conversations, or simply a leadership team willing to ask directly, give the business a chance to address a management issue before it costs a valuable employee.
Organizational Structure and Role Clarity
An org chart and a set of job descriptions are often treated as the same piece of paperwork, but they answer different questions. An org chart is a map of reporting lines: who reports to whom, and how the departments connect to one another. Job descriptions are something deeper. A real job description defines what a role is actually expected to own: the decisions it makes, the outcomes it is responsible for, and how it connects to the authority levels established in the Governance domain. The org chart tells you the shape of the company. The job descriptions tell you what the company actually expects from the people inside that shape.
Some companies keep their org chart reasonably current as the business grows, while the job descriptions beneath it were written once, near the company’s founding, and have never been revisited since. That gap widens every year. Responsibilities shift and get absorbed informally by whoever has capacity, and the written description of a role drifts further from what the person actually does. A new manager trying to understand what their team is accountable for, a new hire trying to understand their own role, and, eventually, a buyer’s due diligence team trying to understand how decisions are made all depend on defined roles and responsibilities far more than on a reporting-line diagram. An accurate chart is a start. Accurate job descriptions are the deeper and more valuable work.
Institutional Knowledge and Key Person Risk
Some GovCon businesses have a handful of people, often including the founder, whose departure would take real capability out the door. That knowledge might be the specific history of a client relationship, the informal workaround for a recurring operational problem, or simply the accumulated judgment of someone who has been solving the same category of problem for a decade. Key person risk is rarely eliminated entirely, but it can be substantially reduced through documentation, cross-training, and a deliberate effort to ensure that more than one person understands how the business’s most important relationships and processes actually work.
Leadership Bench and Succession Depth
This connects directly to the succession planning discussed in the Governance post, but the two domains own different pieces of it. Governance owns the succession plan itself: the decision about who is authorized to step into an authority role, under what conditions, and with what approval. People owns the slower, harder work behind that plan, making sure a qualified successor actually exists by the time the plan calls for one, through hiring, training, coaching, and deliberate development of the individuals who might eventually fill that role. A governance succession plan naming a successor who was never developed for the role is a plan that only works on paper. The two domains have to work together: Governance decides who is authorized, and People builds the person capable of using that authority well.
Employee Welfare and Overall Employee Experience
The least tangible piece of the domain is also one of the more predictive ones. How people genuinely feel about working at the company, whether they feel supported, fairly treated, and connected to something larger than their individual task list, shows up in retention and in whether current employees refer people they respect. That signal tends to appear well before it shows up in any formal survey or exit interview, which means it rewards owners who pay attention to it early rather than only after turnover becomes a visible problem.
What Weak People Systems Cost
A cleared program manager who leaves mid-contract can put an entire task order at risk, particularly when that person held relationships and institutional context nobody else in the company had access to. A bonus structure that looks generous on paper can become a DCAA finding the moment an auditor asks for the documented criteria behind it and discovers there isn’t any. And during a due diligence process, elevated turnover or an obviously thin leadership bench reads to a buyer’s advisors as exactly the kind of founder dependency this entire series is about: a business that performs well today because of who is currently there, with no clear evidence it would perform the same way under someone else.
This series will continue working through the remaining domains one at a time, examining how structure, discipline, and decision flow show up in each. The next post moves to the domain where the capability built here is actually converted into day-to-day results: Operations.
This post is part of Building the Transferable Enterprise, a 13-part series working through the Enterprise Readiness Operating Model domain by domain.
