There's a quiet claim running through everything we do. It's that relationships are the substrate of good work, and growing people is the most important thing a leader does.
This isn't a sentimental claim. It's a strategic one. In an era where the routine parts of most jobs are compressing, the differentiator is the caliber of the people doing the non-routine parts. And the caliber of the people is downstream of one thing: whether someone, somewhere, took the time to grow them.
Most companies say they care about this. Very few act like it.
What growing a person actually looks like
Growing a person isn't a training program. It isn't a learning and development line item. It isn't a mentorship scheme announced at an all-hands.
It's the senior person who takes the time to pull apart a junior person's work and show them the three places their thinking got sloppy. It's the manager who gives someone a stretch assignment and stays close enough to catch them if they fall. It's the peer review where someone says the hard thing kindly. It's the 1:1 where a leader asks a question that makes someone rethink what they thought they knew.
None of this shows up on a dashboard. All of it compounds.
A person who has had three of those moments a year for five years is a different person than one who hasn't. Not incrementally different. Categorically different. They see more, judge better, make fewer unforced errors, and carry more weight. They become the kind of person other people want to work with.
Most of what people call "talent" is accumulated attention from someone who cared enough to give it.
Why most companies fail at this
Every leader claims to value developing people. Most organizations are structured in ways that punish it.
Senior people are rewarded for output, not for growing the people underneath them. The senior engineer who ships the feature looks more valuable than the one who coached two juniors into shipping it themselves, even though the second contribution is worth more over time.
Performance review cycles reward visible wins and punish the slow, invisible work of development. A manager who takes a bet on a promising junior and stays patient for eighteen months while they grow looks worse in the short term than one who hires in someone already fully formed and burns them out in the same eighteen months.
The time it takes to grow someone well cannot be compressed by adding more resources. You can't throw four senior people at a junior for a quarter and expect the same outcome as one senior person for five years. Growth is a function of relationship, attention, and time. It is not a function of dollars.
So in most organizations, growing people becomes the thing that gets cut when the quarter looks tight. Which is always.
What changes when AI arrives
The instinct when capable AI enters an organization is to use it to do more with less. That's fine for a while. It produces real productivity gains in year one.
But the pattern we see in the companies that do AI well over the long term is different. They use the time AI frees up to invest it back into people. The senior engineer whose code review queue got shorter uses that time to do more mentorship. The manager whose status-update burden got lighter uses it to have more 1:1s that actually matter. The leader whose strategic synthesis got faster uses it to be more present with their team.
The companies that treat AI as a cost-cutting tool will get a one-time savings and then stall. The companies that treat it as a way to free up senior time for the work that compounds will keep compounding.
Which kind of company you are is a choice, not an accident.
Relationships as infrastructure
There's a concept in systems thinking called load-bearing. In a building, some walls carry the weight; others are just there. If you remove a load-bearing wall, the building falls down. If you remove a non-load-bearing one, nothing happens.
Every organization has load-bearing relationships. The senior engineer who mentors three juniors is load-bearing. The manager whose team will follow them anywhere is load-bearing. The old-timer who knows why the weird thing in the code is weird is load-bearing. The customer success lead who has the trust of the top ten accounts is load-bearing.
Most companies don't know where their load-bearing relationships are. So they cut them by accident. A restructure, a reorg, a return-to-office mandate that ignores where the actual collaboration happens, and suddenly a bunch of walls that were holding things up are gone. The building doesn't fall down right away. It falls down later, in ways that are hard to trace.
The hardest thing to rebuild in an organization is trust. The easiest thing to destroy is trust. The math is not in your favor if you're not careful.
What this means for the work
When we engage with a company, we spend a lot of time on the things that don't show up on a consulting deliverable list. Who actually trusts whom. Where the real mentorship is happening. Which relationships are load-bearing, which are ornamental, and which are quietly toxic. Where a leader is growing their people well, and where they're stalling careers without realizing it.
This is the underneath of any transformation that actually takes. The strategy on paper is never the hard part. The people who have to hold two contradictory things at once while they learn how to do something new, that's the hard part. And whether they can hold it depends almost entirely on whether the people around them have been growing them well for the last five years.
If they haven't, no deck is going to save the transformation.
If they have, almost any reasonable strategy will work.
Why we chose a collective
The same belief about growing people shapes how Rexicon is organized.
A collective is, fundamentally, a commitment to staying in relationship with peers over time. It's a structure where senior operators can do their best work, without the hierarchy of a firm flattening their judgment. It's a place where we pressure-test each other, share the hard calls, and get better at the work by staying in conversation with people we respect.
We're not a large organization. We're not trying to be. But the small version of this idea — senior people staying close to each other and to the work — is the version we believe in for our clients, too.
Solutions for humans, built by humans, shaped by relationships. It's the only part of the work that was ever going to matter.