Atiba de Souza.Start a conversation
WritingLeadership

Your Team Won't Take Ownership Because Nothing Is Actually Theirs

By Atiba de Souza

Atiba de Souza sitting in a chair with a thoughtful expression, wearing a blue cap with a Superman logo and a black shirt. The cover reads: LEADERSHIP Your Team Won't Take Ownership Because Nothing Is Actually Theirs

The four yards

I was coaching football many years ago. End of the game. We were behind, but there was time on the clock and we had the ball, so we could still win it.

We called the play. We needed five yards to keep the drive alive.

The kid with the ball gained four. And he was excited about his four yards.

We lost by the one yard he did not get.

We needed five yards. He gained four. Two real numbers, and only one of them was the win.

That kid was not lazy. He was not selfish. He won. He hit a number, felt the success of it, and celebrated it. He succeeded by his own definition of winning and by nobody else's on that field. Two definitions of winning is not a motivation problem. It is two different goals being worked toward by people who believe they are on the same team.

That is almost always what a leader is describing when they tell me their team will not take ownership.

Ownership is not a personality trait you hire for

You have run the tape in your head. Somebody on your team does not step up, does not decide, does not own the outcome. You read it as a character flaw, and you start thinking about who you need to replace.

Look again. Ownership is not a quality that lives inside a person and waits for the right hire to switch it on. Ownership is a property of the system around them. People take hold of things that have edges. They take hold of things that were handed to them with a sentence attached: this is yours, this is what winning looks like, this is the number I will check.

If nothing has a border around it, nobody can pick it up.

Your team is not refusing to take ownership. You never handed them anything with a border around it.

What you are actually building

The thing you are building, whether you have named it or not, is what I call Organizational Independence.

Organizational Independence: building a company that can think without you. A stronger organization, and a freer you.

It is not a vibe and it is not a delegation tip. It is three questions answered in order, with a learning loop that runs back to the start. Here is the whole thing at a glance.

Learning loop

1. Alignment
Do we know where we are going and what we own?
Vision, Org chart, the Big 3

2. Movement
Can they decide and act without me?
Values, Frameworks, Culture

3. Measurement
Can we tell if we were right?
Start past the end, everyone has a KPI

All of it stands on Trust. All of it lives inside the Brain of the business, the written memory that lets a decision outlast the person who made it.

Rank these before you start

Most people read a model like this and try to run all three at once. Do not.

Alignment is the whole game. If you only do one thing from this piece, do this. Everything downstream is built on it, and every downstream failure traces back to it.

Measurement is the one leaders skip, because it feels like admin. It is not admin. It is the difference between a team that improves and a team that stays busy.

Movement is the slow burn. It matters, it compounds, and it is the worst place to start. If alignment is broken, values and frameworks just give people better tools for moving confidently in the wrong direction.

Alignment: do we know where we are going and what we own?

Alignment has three working parts. Vision, a clear and compelling future. Org chart, which is really who owns what thinking, not who reports to whom. Theory of Constraints, which is how you keep everybody pointed at the same Big 3 instead of thirty.

This past July, I found out I had skipped it.

I own marketing for TrueMD, a three-founder venture, and I had my team building its LinkedIn presence and producing assets. Then work started getting dropped. Then assets started appearing that made no sense to me, things that had nothing to do with what we are. I traced it back, and I found something I did not want to find.

Most of my team had never been told what TrueMD actually is. Only a subset knew. I had assumed every person working on it did.

Read that again, because the failure does not land where you expect it to. The dropped tasks and the wrong assets were not a team problem. They were an assumption problem, and the assumption belonged to the guy at the top. I was the only one holding the vision, which means I was the only one who could have transmitted it, and I never did.

Now here is the part that gets sold to you as easy. Write down what the venture is, then confirm every person working on it has read it. An hour of writing would have prevented every dropped task and every off-target asset.

I still believe that. I also know the hour is not the cost.

The cost is what happens after you write it. You sit in a room and find out that the thing you were certain was obvious has never once been said out loud. Then you say it, and you find out saying it is not enough, because people nod at vision documents the way they nod at safety briefings. So you go person by person and ask each one to tell you back what this thing is, and you hear it come back slightly wrong a few times before it comes back right.

That is the price of alignment, and it is not an hour. It is the week you did not want to spend saying the same sentence to five adults. There is a reason founders keep the vision in their head instead of on paper: written down, the gap between what you say you are and what you actually do becomes visible. The writing is easy. Being held to the writing is not.

And the fear underneath it is quiet. If everyone knows where we are going, everyone will know when we miss. You are about to make your own scoreboard public.

Movement: can they decide and act without me?

Once people know where they are going, the question turns to whether they can move without asking you. That is built from values that guide decisions, frameworks that make thinking simple enough to reuse, and culture, a team that improves together instead of a team that waits.

Do not install this into a team that cannot yet tell you what the business is. You will get speed without direction, and fast wrong is worse than slow right.

Assuming alignment is real, here is the decision. Pick the single decision your team brings to you most often. Not the biggest one. The most frequent one. Write down the value or the framework that settles it. One page, plain language. Then hand it over and stop being the answer.

That last part is the whole thing, and it is where most leaders quietly quit.

Because the first time they use your framework, they will decide something differently than you would have. Not wrong. Differently. And you will be sitting in that meeting knowing your answer, watching them walk toward theirs, and you will have to let it happen. If you overrule it, you have just taught the room that the framework is decoration and the real system is your mood. Overrule it enough times and the whole structure is dead.

The rewiring is personal. You have been the decider for so long that being the person who writes down how decisions get made feels like a step down. It is not. Principle six of the leadership spine I work from is build to replace yourself. A business that cannot run without you is not an asset. It is a job with extra steps.

Measurement: can we tell if we were right?

Start past the end. Define what success looks like, then walk backward to today. Then make sure everyone has a KPI, so each person has a clear signal of whether their part is working.

Go back to the football field. The play needed five yards. That is a definition of winning you can check. Four yards is also a definition of winning you can check. They are not the same, and the kid carrying the ball only had one of them.

That was my failure, not his. I knew the win and never said it out loud in terms he could hold. So state the win in a form that can be checked, and make sure every person on the field is holding the same one.

Which sounds like a sentence you would nod at. Here is what it costs.

It costs the conversation where you tell a proud person that four yards was four yards. Not a good carry, not almost, not a great effort in a tough spot. Four. Because the moment you soften the number to protect the feeling, you have handed the whole team back the second definition of winning.

And it costs you the warm version of your relationships. The day someone owns a KPI is the day their work stops being a conversation and starts being a scoreboard. Some of your people will not like it. A few will test it, to see whether the number applies to them. Holding that line, calmly, every week, is the job. If you cannot stand the discomfort of a number somebody can fail, do not assign the number. Assigning it and then not looking at it is worse than never assigning it at all.

The loop that keeps it alive

The moment you finish measuring, the lesson goes back into alignment. That is the arrow nobody draws. Without it, you build the organization once, it calcifies around a version of the business that no longer exists, and within a year you are the only one who has noticed.

The spouse at the table

Here is the picture I want you to keep.

Picture a married couple who own a business together. Ask the one who is not the "face" about the company, and watch what happens. They answer at one remove. They say things like, well, we are trying this, or I think we are going after that market. The answers come back thin, because they are answering as the person standing next to the owner instead of as one of the two people who own it.

Ownership has to be claimed in the language before it shows up in the decisions.

Now hear your own team. Listen to how they talk about their work. Most of them answer about your business the way that spouse answers about the company. And they learned it from you, because for as long as they have worked there, you have answered for them.

The owner-dependent wayThe independent way
The vision lives in the founder's headThe vision is written down and every person on the work has read it
The team waits for the founder to decideValues and frameworks let them decide without a meeting
"It went well" is the founder's gut feelingSuccess was defined first and every person has a KPI
The founder absorbs the lesson and nobody else learns itThe lesson flows back into alignment and the system gets smarter

What to do Monday

Pick one thing your team is working on this week.

Write down what it is. One page, plain language. Send it to every person touching that work, not the subset you happen to talk to. Then ask each one to tell you back, in their own words, what the win is. Four yards or five.

Expect the first pass to come back wrong in ways that mildly annoy you. Expect to be slower for a while, not faster, because you are about to spend time saying things you assumed were already understood.

That is the tuition. It is real, it arrives before the benefit does, and there is no version of this where you get the outcome without paying it. The alternative is what you have right now: a team that looks like it will not take ownership, and a founder who is still the only one who knows where the ball was supposed to go.

A stronger organization. A freer you.