When Nobody Reports to You

There is a line in Dune that I have kept coming back to:

"A great man doesn't seek to lead. He's called to it. And he answers."

It sounds philosophical until you try to run a company where people do not formally report to the person leading the work.

We are running into that question at Cars24. Everyone is a Builder. Work is starting to form more around problems in pods and less inside permanent boxed teams. The right group for a pricing problem may be different from the group needed for a customer journey or a risk problem. The captain can change too.

That person may not be the oldest in the pod. They may not have the most years of experience or the highest salary. The other Builders may not report to them at all.

So why should anyone follow them?

What the old structure solved

It is easy to say hierarchy was only about power and ego. That is not true. Permanent teams and reporting lines solved a real coordination problem.

Context was expensive to gather and move. Somebody had to ask each person where things stood, carry information across functions, route decisions, follow up and remember what was agreed in the meeting nobody documented. Companies bundled that work into management and gave the manager standing authority over a fixed set of people.

Over time we started confusing that coordination work with leadership itself. Distance from the work became seniority. Having more people report to you became evidence that you mattered more.

AI makes that bundle unstable.

Agents can gather context, maintain memory, prepare the state of a problem, route routine work and follow up. They can make a pod more legible without one person spending the day asking five people for updates and turning them into a sixth update. We are still early in building this at Cars24, but I have seen enough in my own work to know that coordination over reporting is becoming much more practical.

The human work remains. In fact, it becomes easier to see.

Somebody still has to make the call when the data has run out and the decision cannot wait. Somebody has to know which problem matters, what good looks like, which standard cannot slip and what the group may be missing. Somebody has to hold the relationship through a hard conversation and carry the consequence when the call is wrong.

None of that comes from a title.

Waiting for the mandate

A few years ago, I ran into this while discussing how some of our data science work was organized. People were waiting for business owners to hand them problems. Once a task arrived, they would solve it. But they were not coming back with the problems they had found themselves.

My reaction was blunt. If you are waiting for me to tell you what you can do for me, it defeats the purpose.

This was not really about data science. Any team can fall into the same trap: waiting for work to be assigned instead of seeing what needs doing.

That conversation helped me see the difference in the first few questions someone asks.

The person seeking to lead starts with the mandate. Who is on my team? What decisions do I own? Will my title reflect the scope? Why is this other person in the room?

These questions are not always unreasonable. Clear decision rights matter. But they show where the energy is going. For years I rewarded some of this too, because asking for a larger mandate looked like ambition and ambition looked like leadership.

The person called to lead starts somewhere else. They see a real problem and begin moving it before every boundary has been settled.

Nobody had to anoint them. The work was already moving.

Captain feels like a better word than leader when we talk about a pod. Captaincy is work somebody does for this problem and this part of the journey. It does not create a permanent class of people above everyone else. When the problem changes, the right captain may change.

Experience still matters. Expertise matters. Some Builders should carry more weight in a particular decision because they have seen the pattern repeatedly and built good judgment. Flatland does not ask us to pretend everyone knows the same amount. It asks us to stop using age, salary and title as shortcuts for finding out who knows what.

Being called is not evidence

There is a danger in this idea. Almost anyone can declare that they feel called to lead. That can quickly become ego with better vocabulary.

The call has to be visible outside the person claiming it.

There has to be a real problem that others can see. The evidence and the work have to be open to inspection. Builders with relevant context have to trust the person's judgment enough to move with them, while remaining free to disagree. The person has to carry the broken version too.

The responsibility is temporary. It lasts only as long as the problem and the pod need it.

Removing titles does not remove power. Handled badly, a flat company simply hides it. Decisions drift towards whoever is loudest, closest to the founder or oldest in the building. An invisible ladder is worse than a visible one because nobody can name it or challenge it.

So the problem has to be written down. Evidence has to travel. Decision rights have to be clear enough for the pod to move. A captain can make a call, but proximity, personality and mystery cannot be the argument.

Service creates pull

When positional power weakens, service becomes the practical source of authority.

I do not mean being agreeable. Serving the purpose may require an unpopular decision, a higher standard or a direct disagreement. Servant leadership is not soft leadership.

It means the purpose comes before the person's need to look important. The customer problem comes before ownership of turf. The quality of the decision comes before who gets credit. The growth of other Builders comes before keeping them dependent.

The captain creates context, removes friction, asks for disagreement and makes the difficult call when the group cannot remain undecided. People follow because that person helps them do better work on something that matters.

That creates pull. I have been thinking about pull a lot. Push can get work done and every company needs some of it. But an institution cannot run forever on a few people pushing everyone else. Pull comes from inside. It comes when a Builder sees the bigger picture, feels the consequence and wants to move the problem without waiting for instruction.

The person leading has to create more of that pull, not more dependence on themselves.

The work should outgrow the captain

A harder test comes later. Does the work still move when the captain leaves the room?

If every decision waits for one person, every conflict returns to them and every new Builder needs their private explanation of how things work, the system has made that person important. It has not become strong.

A good captain makes their own judgment less scarce over time. They share the context, make the standards visible, build tools and agents for the routine work and leave behind a feedback loop that tells the pod whether the call was right. Other Builders can teach the method, question it and improve it without asking the original captain for permission.

That is how a project becomes a movement. It stops being dependent on the person who began it and keeps getting larger in the direction of the original purpose.

This is a correction for founders too. We spend years becoming useful by having answers, pushing through resistance and staying close to important decisions. Being needed feels a lot like leading. I know that feeling well.

Flatland will fail if it replaces a pyramid of managers with the founder in the middle of every pod. My job is to make more context available, help judgment get stronger across Cars24 and then step out of decisions that no longer need me.

The line in Dune ends with the person answering the call. In Flatland, the answer is not a coronation. You take the problem, serve the purpose, carry the consequence and build a system that can continue without you. When that part of the journey is over, you put the authority back down.

I will know we are getting this right when I am surprised by who leads the next important problem, and when they no longer need me in the room.