Atiba de Souza.Start a conversation
WritingLeadership

Your Team's Eye-Roll Is the Answer, Not the Objection

By Atiba de Souza

Atiba de Souza standing in a modern, well-lit indoor walkway with glass walls and a metal frame structure. The cover reads: LEADERSHIP The change you can see Install it where?

Try This On Yourself First

Pick one habit. Not a bad one. A good one you keep meaning to fix.

Now here is the change. For the next quarter, you write down what you did each day and whether it worked. Ten minutes. Every night.

Pay attention to what just happened in your chest.

It was not "great idea." It was a small, quiet eye-roll. A "sure, when exactly." Nobody is standing over you. Nothing lands on you if you skip tonight. The cost arrives in ten minutes, tonight, and again tomorrow night. The payoff arrives somewhere in the fog of next year, for a version of you you have not met yet.

That eye-roll is the whole article. It is also what is happening in the room when you announce the change that objectively, undeniably, obviously benefits your team.

The cost of the change is felt now. The cost of not changing is felt later. Your team is not wrong to notice that. You noticed it too, thirty seconds ago, about a habit you picked yourself.

Stop Reading Resistance as a Character Flaw

You have been misreading it. The pushback that meets a good change is not laziness. It is not a bad attitude. It is not a culture problem you fix with a better slide deck.

It is an invoice. You are handing people a bill that comes due tonight and a refund that comes due someday. Most humans decline that trade. They are not being difficult. They are being accurate.

And here is the part that makes you dangerous as a leader: you can demonstrate this faster than you can explain it. You just did, with a habit you chose and a person you cannot fire. You.

Delegation Leadership: hand over the thinking, not the task list. The measure of a leader is not what they can get done while they are in the room. It is who can explain the why when they are not.

Delegate thinking, not tasks. Everything below is just that sentence, aimed at a team that does not want to hear it yet.

Two Ideas, and They Are Not Equal

Most writing about change fails because it treats every idea as the same size. Here, two things matter, and they are ranked.

One. This is nearly the whole thing. The change is not installed in your team until it is installed in your managers. Not announced. Installed. And installation is not a memo. It is a culture change inside a small number of people who have to believe it before it can travel anywhere.

Two. This is housekeeping. The tooling. The tracker, the dashboard, the form. This is what every leader grabs first, and it is the least important part of the work. Pick whichever one you like. I will not argue with you about it. It is not the problem.

What actually moves a change is vision, openness, and asking great questions. That is the spine underneath all of it. Vision, so people know where this is going and why. Openness, so they can tell you it is stupid without losing their job. Great questions, so the answer comes out of their mouth instead of yours.

I am going to leave two of those three alone for now and pick them back up at the end, in the only place they actually get tested. Listing them here would make this feel solved. It is not solved here.

The word is openness. Not vulnerability. Get that word wrong and you will run a therapy session and call it leadership.

Eighteen Months Earlier, In My Own Building

I once explained to Lyca why Steve Derrington's data problem would take a year instead of a week. I did it by pointing at our own company.

Eighteen months before that conversation, nobody here recorded what they did or whether it worked. We fixed it. But how long that fix really took has almost nothing to do with tracking, tooling, or which system we picked.

Here is the real version. I had to change the culture between Lyca, Stephanie, and Mekka first. I had to get those three to understand why recording the data and reporting the data mattered. Only after that could it permeate down into the team. That, not the software, is why it took as long as it did.

You expect the story to end with a better tool. It does not. It ends with three managers deciding it mattered.

A year. Not a sprint. That was the honest number for a data problem that looked like a one-week job, and the tracking software was never what made it long.

Now hear this part if you are the one rolling out the change. If I had pushed the recording discipline straight at the team while those three managers were not yet bought in, I would have gotten compliance for a few weeks and no data at all. Not a slow start. A fake start. You pay for a system and you get theater.

So when someone tells you they want data discipline installed, size it as a culture change that begins with their managers, and say the number out loud on day one.

The Same Job, Done Two Ways

The leader who fights the roomThe leader who works the room
Announces the change to everyone on MondayLands it in the managers first, weeks before the team hears the word
Calls it a rolloutCalls it a culture change and says out loud that it takes a year
Buys the tool and trains the teamChanges what the managers believe, then lets the tool be boring
Reads the eye-roll as attitudeReads the eye-roll as data
Answers the hard objection in the meetingLets the objection stand there and does not flinch
Stays the go-to for the work they are good atSets a date 120 days out and stops
Measures adoptionMeasures who can explain the why when they are out of the room

The Sentence From a Man I Did Not Like

Years ago, a business owner I worked with, a mentor I plainly did not like, stood in front of a room full of overachievers and said the thing I have been repeating ever since.

The man was an absolute jerk. I am not going to soften that.

He said one of the most profound things I have ever heard for people built like us.

Every 120 days, replace yourself. Anything you are doing right now, in 120 days, stop.

You expect that to stay a nice quote. It did not. I started actually doing it, quarter after quarter. Years of it means there is now a lot of work I used to do that I have no clue how it gets done. I honestly could not describe the process to you if you asked.

That is not a failure. That is the finish line.

Here Is What You Are Actually Avoiding

Reading resistance in your team is easy. Reading it in yourself is where it gets uncomfortable.

Leaders announce to the whole team instead of working the manager layer first because rolling it out to everyone feels like momentum, and sitting down with three people one at a time feels like a stall. It is also a risk. They might say the change is stupid. They might have a reason you cannot answer. You would have to sit in that silence and not fill it.

That conversation is the work. Everything else is admin.

The 120-day rule costs you something specific too. Every job you still do because you are good at it is part of how you know who you are. It is the proof that you are valuable, that you are needed, that the place would wobble without you. Putting a date on the calendar is the easy half. The hard half is what happens on day 121, when you stop and let yourself not know how it gets done anymore. Forgetting a job you were excellent at is a small death of an identity you built on purpose.

That is why "just delegate it" fails. It is not a scheduling problem. It is a grief problem.

When Not to Do This

A rule with no exceptions is a slogan. So here are the exceptions, ranked.

Hold the wheel if the road is bad. If the business is in a cash crisis right now, the 120-day clock waits. You do not hand off the thing holding the roof up while the roof is still moving. Start the clock when the ground is steady.

Do not run the manager conversation as a meeting. It is one conversation per person, alone, or it is theater. A group session buys you agreement in the room and nothing on Tuesday.

Do not skip the layer because your team is small. If you have two people and no managers, then you are the manager layer. You are the culture that has to change first. Skipping that step is exactly how you buy the compliance-for-a-few-weeks outcome.

The Whole Framework on One Screen

Straight to the team

Into your managers first, one at a time

Openness: you do not defend, you do not fill the silence

You explain harder

The change you can see

Install it where?

Compliance for a few weeks, then no data

Vision: where this is going, in words they can repeat

Great question: what would have to be true for this to be worth it to you?

The answer lands

They own the thinking

Team owns the thinking

Ownership

Read it left to right. The change stops dead at the first branch if you send it straight to the team. And it stops dead at the second branch if, when the manager gives you the answer you cannot fix, you reach for the slide.

The Conversation You Keep Postponing

Cancel the all-hands. Not forever. This week.

Book an hour with one manager. Not all three in a room. One, alone, and you do not bring the deck.

Then ask the question the whole rollout is actually made of: what would have to be true for this to be worth it to you?

This is where the three legs stop being a list and start costing you something.

Openness is what you do when the answer is not the one you wanted. Your manager says this is the third system in two years. Or says they think you want this so you can stop doing the work. Or says something true and inconvenient that you cannot repair inside the hour.

Openness is not vulnerability. It is not telling them your feelings. It is that you do not defend, you do not sell, and you do not reach for the slide that answers it. You let the sentence stand in the room and you leave it standing.

That costs you the thing you like most about your job: being the person with the answer. For about ninety seconds you will not have one. Every instinct you own will want to fill that silence, because silence feels like the change dying. It is not dying. It is being told the truth for the first time.

Great questions are what you do inside the silence instead of talking. Not "how do we get you on board." Something closer to: what part of this do you think is a waste of your time? Or: what would make you the person who owns this instead of the person who complies with it?

Both of those put the answer in their mouth instead of yours. That is the entire mechanic. You are not extracting agreement. You are handing over the thinking.

Vision is the only piece you get to prepare. Where this is going and why, in language a person can repeat to somebody else on Tuesday. Not the mission statement. The reason this specific change is worth this specific cost.

Do it with one manager this week. Then a second one, with the next person.

And expect it to go badly the first time. You will fill the silence. You will answer a question you should have asked. You will hear resistance and reach for the old reflex, which is to explain harder.

Do it again the following week anyway.

There is no second move. There is the next conversation, with the next person, and a silence you are slowly getting better at not filling. That is what a culture change between three people actually looks like from the inside. Not a rollout. A series of uncomfortable hours you chose to have.

That Eye-Roll Was Yours First

The next time it shows up in your own chest, do not argue with it. That is your team talking, out of your own body. You finally got the chance to feel the invoice before you hand it to anybody else.

Most leaders never take that chance. They roll out a change they would have eye-rolled at themselves, then act surprised when the room hands the same look back.

The look was never the objection. It was the invoice, arriving early, from the only person in the building who cannot fire you.