Nepotism: The Two-Sided Gate

Nobody defends nepotism out loud. It sits alongside corruption and cronyism in the list of things everyone agrees are bad, a symbol of systems that reward who you know over what you can do.

And sometimes that’s exactly what it is.

But the honest version of this conversation is more complicated. Because nepotism, like gatekeeping, like the political oxymorons we recognize in movements that become what they hate — isn’t one thing. It’s a mechanism. And like every mechanism, what it produces depends entirely on who’s operating it and why.

The word deserves a closer look than it usually gets.

What Nepotism Actually Means

Nepotism, at its root, is the practice of favoring relatives or close associates when distributing opportunity; jobs, contracts, access, authority. The word comes from the Italian nipote, meaning nephew, a reference to the medieval Catholic Church’s habit of popes appointing their nephews to positions of power.

It has always existed. It exists in every culture, every sector, every era. The reason isn’t that people are uniquely corrupt, it’s that trust is scarce, and personal relationships are one of the oldest and most efficient ways to establish it. Hiring someone you know, or someone vouched for by someone you trust, reduces uncertainty. That’s not cynical. That’s human.

The problem isn’t the relationship. The problem is what the relationship substitutes for.

When Nepotism Rots Institutions

Bad nepotism is easy to identify in hindsight and surprisingly easy to rationalize in the moment.

It happens when a job goes to someone not because they can do it but because of who they’re connected to, and the organization absorbs the cost of that misalignment. The underqualified hire who coasts. The promoted loyalist who blocks better candidates below them. The contractor whose bid wins not because it’s competitive but because the relationship is comfortable.

The damage is rarely dramatic. It accumulates. Each individual act of bad nepotism seems manageable; one bad hire, one missed candidate, one mediocre vendor. But over time the institution fills up with people selected for loyalty over competence, and the selection pressure inverts. The best candidates stop applying because they’ve learned the game is rigged. The people who do advance are the ones who figured out how to navigate the network, not how to do the work.

This is where bad nepotism connects directly to bad gatekeeping: both redirect the filter from quality to relationship. Both produce the same result; an institution that has reorganized itself around protecting its insiders rather than serving its mission.

And both contain the same oxymoron. A leader who practices nepotism to protect institutional stability often produces the instability they feared, because an organization built on loyalty rather than competence is fragile in exactly the ways a meritocratic one isn’t. The nepotist, trying to control outcomes, loses control of them.

When Nepotism Strengthens Institutions

Here’s the part that rarely gets said: not all of it is bad. And refusing to acknowledge that produces its own blind spot.

When a job goes to someone through a personal connection and that person is genuinely qualified, genuinely motivated, and acutely aware that their performance reflects on the person who vouched for them, the dynamic can actually strengthen accountability rather than weaken it.

A referred candidate often works harder, not less. The relationship that got them in the door is the same relationship that makes underperforming costly. They aren’t just an employee, they’re a reflection. That’s a different kind of pressure than an anonymous hire faces, and it can produce better outcomes.

There’s also an information argument. A trusted referral often comes with better information than a résumé provides. A hiring manager who has seen someone perform under pressure, handle adversity, or demonstrate values over time has more signal than a structured interview typically generates. Personal networks, used honestly, can be a legitimate screening mechanism.

The difference between good and bad nepotism isn’t the relationship. It’s what the relationship is being used to accomplish. Is it routing in someone genuinely suited for the role, with the accountability that comes from a personal voucher? Or is it bypassing evaluation entirely and hoping the relationship is enough?

One is a shortcut to trust. The other is a shortcut away from it.

Nepotism in Facility Operations

Facility operations runs on relationships, and that cuts both ways.

On the vendor side, long-term relationships with trusted contractors, suppliers, and service providers are genuinely valuable. A vendor who knows your systems, has proven their reliability, and understands your building’s quirks is worth something a competitive bid can’t always capture. Preferring them isn’t nepotism in the toxic sense. It’s institutional knowledge expressed through a relationship.

But those same relationships curdle when they stop being evaluated. The vendor who wins the next contract not because they performed well on the last one but because the relationship is comfortable. The service provider whose pricing has drifted above market because nobody has compared it in three years. The contractor whose work has declined but whose calls still get returned first. That’s when relationship-based preference crosses into the territory that costs the building, and the budget, more than it should.

On the hiring and team side, the trades have their own version of this. Apprentices vouched for by a journeyman. Helpers hired because a senior tech knows the family. In a field where character, reliability, and willingness to learn matter as much as technical knowledge at the entry level, a personal voucher can be legitimate signal, if the person who gave the voucher holds themselves accountable for the outcome.

The problem is when the voucher becomes the credential. When the new hire’s connection to the right person substitutes for the work of developing actual competence. When the team quietly adjusts around someone who isn’t performing because removing them would be awkward for someone above them.

The facility ops test for nepotism is the same as the gatekeeping test: who is the decision serving? If the vendor relationship is serving the building, competitive pricing, reliable performance, genuine accountability; it’s a legitimate preference. If it’s serving the comfort of the person who manages it, the building is paying for that comfort whether the invoice shows it or not.

The Common Thread

Gatekeeping and nepotism aren’t separate problems. They’re the same problem expressed through different mechanisms.

Both involve a person or group controlling access to something valuable; opportunity, resources, trust. Both can be legitimate or corrosive depending on what they’re serving. Both tend to drift from the former to the latter gradually, without any single moment where the line was clearly crossed. And both share the same oxymoron: the mechanism installed to protect quality ends up protecting itself at quality’s expense.

The political version of this movements that become what they hate, systems that produce the dysfunction they were built to prevent plays out at the institutional level too, just more quietly. The hiring process meant to find the best people becomes a filter for the most connected ones. The vendor relationship meant to ensure reliability becomes a barrier to better options. The approval structure meant to maintain accountability becomes the reason accountability is avoided.

Recognizing the pattern doesn’t require cynicism about relationships or authority. It requires honesty about what a given relationship or authority structure is actually producing, and the willingness to ask that question regularly, not just at the beginning when the intentions were cleanest.

What to Watch For

In any institution, political, corporate, or operational, the signs that nepotism has crossed the line are consistent:

The best candidates stop advancing. Not because they aren’t performing, but because performance stopped being the primary criterion.

Problems get absorbed rather than fixed. Bad hires, underperforming vendors, and dysfunctional processes persist because addressing them would mean confronting the relationships that produced them.

Institutional knowledge concentrates in people rather than systems. The building runs on who you know, not on documented processes anyone can follow.

Accountability flows downward but not upward. People below the network are held to standards. People inside it aren’t.

The remedies aren’t complicated, though they require the people benefiting from the current system to implement them, which is where most reform efforts stall. Documented evaluation criteria applied consistently. Competitive processes that aren’t pre-decided. Referrals that are treated as a starting point for evaluation rather than a substitute for it. And a culture where raising concerns about a connected hire or vendor is treated as professionalism rather than disloyalty.

Where This Series Goes Next

Both gatekeeping and nepotism are downstream of something else; the ego and identity of the people operating them. A leader who needs the gate to stay closed to feel secure is a different problem than a leader who keeps the gate closed out of genuine conviction.

That distinction; between ego-driven authority and principled authority, is what the next piece in this series examines. Because understanding why gatekeepers and nepotists behave the way they do is the missing piece in most conversations about how to change them.

The gate is just a gate. The question is always who’s holding it, and what they need to keep feeling like they should.