Every organization is, whether it admits it yet or not, becoming a software company — competing, creating value, and growing through systems it builds and maintains, not just systems it buys. That shift changes what “people” means as a resource, because software-driven organizations don’t just need more hands. They need people who can think in systems, and those people have more choice about where they work than almost any other kind of talent in the market. Attracting them is not a recruiting problem. It’s a culture problem wearing a recruiting problem’s clothes.

What attracts them, consistently, is not the tech stack. It’s transparency about the journey — the tools, the mistakes, the lessons, the actual texture of what it’s like to work somewhere, told honestly instead of curated. Engineers and technologists, in particular, can tell the difference between an organization that’s confident enough to talk about what went wrong and one that’s only ever willing to talk about what went right. The second kind reads as marketing. The first kind reads as a place worth joining.

This connects to something more structural than hiring, though. People own purpose, decisions, and accountability, and that ownership doesn’t transfer to a tool no matter how capable the tool becomes — a system can execute a decision, but it cannot be accountable for having made it, because accountability requires someone who can actually answer for the outcome. That’s not a sentimental distinction. It’s the load-bearing reason organizations still need people who are empowered to decide, not just people who are available to execute whatever a plan or a system tells them to do next. An organization that quietly slides people into execution-only roles isn’t becoming more efficient. It’s dismantling the part of itself that was supposed to own anything.

One thing I’ve carried with me from sports is a high expectation of people — not for perfection, but for contribution. On a team, you depend on others, and they depend on you, and nobody gets to opt out of that arithmetic just because they’re having an off week. Organizations are no different, even though they dress the dependency up in job titles and org charts instead of positions on a pitch. People show up with different motivations, different ambitions, different strengths — none of that matters as much as whether, when the work depends on each other, everyone’s contribution actually arrives.

None of this works if it’s carried alone. Flow has a human dependency. Information creates value when it’s shared. Decisions create momentum when they’re made. Ownership creates progress when it’s taken. None of those verbs — shared, made, taken — happens without a person choosing to do it; every principle in this book about capabilities, boundaries, and decisions still passes, at some point, through a person choosing to help another person move. Contribution creates flow the way a single root doesn’t feed a tree; it’s the whole network of small, unglamorous handoffs — the answer given quickly, the blocker removed before anyone had to escalate it — that actually keeps things moving. Trust doesn’t grow from stated values. It grows when people consistently help each other move, the same small transaction repeated often enough that it becomes a reasonable expectation instead of a pleasant surprise. Every organization looks different from the outside — different products, different structures, different vocabularies. The interdependence underneath is not. People, somewhere, are still waiting on other people. How well that waiting resolves is most of what “culture” actually measures.

Flow isn’t created by individuals. It’s created by people who make each other successful.

There’s a lot of discussion right now about what AI will replace, and I think it’s the wrong question to be asking. The real question was never whether AI can do the work — plenty of it, increasingly, it can. The real question is who owns the outcome. People should own the purpose, make the decisions, and carry the consequences; AI should amplify human capability, not replace human accountability. Organizations that get that balance right don’t just become more efficient. They become more adaptive — which, of everything this book keeps returning to, is the one that actually compounds.

The organizations that keep attracting and keeping this kind of person are the ones playing what Simon Sinek called the infinite game — not trying to win once, but treating learning as continuous, because there is no finish line where the organization gets to stop adapting. That posture is contagious in both directions: people who want to keep learning are drawn to organizations that are visibly still learning, and organizations full of people like that get better at everything else almost as a side effect. The real differentiator was never the technology. It’s the culture of learning underneath it, which happens to be the same thing skilled people are actually looking for when they’re deciding where to spend the next several years of their working life.

Capability endures. Ownership creates movement. People are what make either one actually happen — not headcount, not “resources,” but the specific individuals who chose to stay because the conditions were worth staying for.