Hiring smarter people is the easy part

I've been watching this pattern for years. The same leaders who cite 'hire people smarter than you' in public sessions go back to their teams and subtly signal, in a hundred small ways, that they are still the smartest person in the room. Credit for good work somehow ends up attached to the manager's name in reviews. Tough decisions are narrated as their own insight. Public recognition of subordinates is consistently hedged. The aphorism has been said. The behaviour has not followed.

The insecurity dynamic

The thing that makes this hard to fix is that the underlying driver is usually insecurity, not malice. A manager who hires someone more talented than themselves has to live with that choice every day. If the manager's own identity is built around being technically sharp, the talented hire becomes a standing threat. The natural response - subtly diminishing the subordinate's contributions, treating their suggestions with extra skepticism, reframing their ideas as the manager's own - is a protective instinct. It happens mostly below conscious awareness. Most of the managers doing it would sincerely deny they were doing it.

The irony the original post points to is the most important part. The instinct to protect your position accelerates the thing you're trying to prevent. Smart people notice credit-hoarding within weeks. They start thinking about leaving within months. They leave within a year. Your team's ceiling is then bounded by the people who didn't notice or didn't mind, which is a lower ceiling than you had available. The manager who tried to stay the smartest person in the room ends up being exactly that - and the room becomes smaller.

What the successful version looks like

Managers who do this well share a specific pattern. They've worked out what their role is, and it doesn't depend on being the smartest person in the room. The job definitions they operate under are sharper: 'the coach', 'the connector', 'the protector of focus time', 'the editor of bad decisions', 'the one who goes to bat for the team in resource meetings'. None of these require technical superiority. All of them are essential to a team performing well, and they're the roles that a talented hire cannot do for themselves because they require organisational context and relationships.

Once you have a clear non-technical role for yourself, subordinate brilliance stops being a threat. A brilliant engineer still can't hire. A brilliant designer still can't negotiate the roadmap with the VP. A brilliant product manager still can't protect the team from political churn. Whatever they bring, you bring the thing that complements it, and the partnership scales. The successful senior managers I've worked with all have this sharp sense of what they specifically contribute, and it's almost never 'I'm smarter than everyone reporting to me'.

Your team's ceiling is literally bounded by your comfort with your subordinates' success.

The credit-sharing operating behaviour

Sharing credit is one of the most under-specified pieces of management advice in common circulation. People quote it. Almost nobody writes down what it actually looks like. The specific behaviours that constitute visible credit-sharing: naming the person in the room when discussing their work, forwarding their work unedited to the next tier with attribution, crediting the individual contributor before yourself in every presentation, deferring to them on technical questions in public forums, not signing your name to their output, and actively writing public recognition in company communications.

Each of these is a thirty-second behaviour. Together they take perhaps thirty minutes a week. The effect on retention is substantial. In organisations that track it, the managers with the lowest voluntary attrition among top performers are reliably the ones who do most of these things consistently. The managers with the highest attrition are usually the ones who do some of them occasionally. The difference looks small from outside. It is enormous in cumulative effect.

The counterfeit version

One failure mode to watch for in yourself is the public-credit-private-gatekeeping pattern. Some managers have learned that saying 'great work, team!' in public is the right behaviour, and they do it regularly. In private - in promotion calibrations, in backchannel references to leadership, in the quiet decisions about who gets the next opportunity - they still behave in ways that advantage themselves over their subordinates. The performance is credit-sharing. The operating behaviour is credit-hoarding. Direct reports learn to distinguish the two within a quarter, and the manager's reputation calibrates accordingly.

The honest test is not what you say in all-hands. It's what happens in the room you never attend, when senior leadership is discussing the next promotion or the next opportunity or the next role. If the person's name comes up with their actual work attached, you've done the credit-sharing properly. If their work has been attributed generally to 'the team' or, worse, to your leadership, the signal has been reversed. You don't get to control that moment. You get to build the habits that make the right version happen by default.

The retention observation

The commercial case for amplifying subordinates' credit is unglamorous but real. A senior engineer leaving a team typically costs 50-100% of annual compensation in replacement costs, ramp-up time, and knowledge transfer overhead. A manager who successfully retains a strong team of smart hires for two extra years has saved their organisation several hundred thousand pounds at minimum. The 30 minutes a week spent on credit-sharing has a ROI that no other management activity matches, and the organisations that explicitly measure and reward this are rare. Most organisations leave it to the individual manager's discretion, which is why the practice is uneven.

The uncomfortable truth

The harder version of this advice is that managers who can't tolerate subordinate brilliance should step aside - into individual-contributor roles, into technical specialties, into domains where their comfort zone isn't being violated daily. The alternative is spending a career capping your team's potential because your own identity can't accommodate their growth. This is uncomfortable advice to give. It is also the right advice for a specific population of mid-career senior engineers who took the management track without examining whether they could do the job well.

For everyone else, the practical takeaway is simpler. Hire the smartest people you can find. Spend thirty minutes a week on visible credit-sharing. Work out what your specific contribution is that doesn't depend on being smarter than your team. Accept that your best hires will outgrow you, and be visibly proud of it when they do. These are the behaviours that compound, and they're the ones that make 'hire people smarter than you' into something other than a platitude. The advice is fine. The operating model is the part nobody is writing down.