Head in the Clouds Is Not an Insult

Years ago, during an interview for a senior leadership role, someone pulled me aside and told me what my detractors were saying.

"They say you have your head in the clouds."

It was not meant as praise.

It was a challenge question. It meant I was too far ahead. Too willing to challenge the established path. Too focused on what the system could become instead of staying inside the safe lines of what it already was.

My answer was not defensive.

I welcomed the question because it was the right one. In a utility, vision is not a poster on the wall. It has to meet consent orders, capital programs, field conditions, public trust, political reality, and the operator's day.

Miami-Dade was not dealing with an abstract management problem. The 2013 federal consent decree required major wastewater system improvements, and the Department of Justice described that decree as updating, replacing, and superseding two earlier consent decrees. DOJ settlement summary. Miami-Dade's own consent-decree page describes a 15-year, $1.6 billion improvement commitment. Miami-Dade consent decree background.

That changes the question in the room.

The question is not only: how do we comply with this order?

The better question is: what do we do now so the next generation is not sitting under the next one?

That is where vision and execution have to meet. Strategy, tactics, operations, finance, engineering, regulators, field crews, elected leadership, and public trust all have to come into the same frame. I had lived in those different altitudes. Public works. Capital delivery. Utility operations. National and international agency work. City systems work. The whole point was to operationalize the vision, not admire it from a distance.

So the honest answer is this:

I have always had my head in the clouds, and I am unapologetic about it.

That is where the next system becomes visible before everyone else has a name for it. That is where strategy lives. That is where you can see the connections that are invisible when everyone is buried in the task list, the inbox, the compliance calendar, or the latest crisis.

But having your head in the clouds is only useful if your feet still know where the ground is.

Vision without execution is fantasy. Disruption without follow-through is chaos. But execution without vision is how broken systems survive for another decade while everyone calls it discipline.

That is the distinction we need to recover.

Fig. 01 / Vision under testThe Systems Lens

Vision has to come back to the ground

The insult is usually early recognition

When someone calls you unrealistic, sometimes they are right.

Some ideas really are vapor. Some leaders like the feeling of disruption more than the work of building. Some people create motion, noise, and pressure, then mistake the reaction for progress.

That is not the kind of disruption I am defending.

The kind I am defending has a job.

It names the failure people have learned to tolerate. It makes the cost of comfort visible. It gives the organization a better question. It forces the record, the data, the workflow, the budget, and the people in the room to admit what they already know but have not wanted to say out loud.

That kind of disruption is uncomfortable because it interrupts a story the system tells itself.

We are fine.

This is how it works.

The process is the process.

No one has complained loudly enough.

We will get to it next year.

I have heard versions of that story my entire career. In infrastructure, the story can sound responsible because it wears the clothes of procedure.

But a procedure that protects delay is not governance.

A process that cannot prove the outcome is not accountability.

A plan that never reaches the field is not strategy.

Sometimes the person with their head in the clouds is the only one saying the ground is cracking.

“

Vision without execution is fantasy. Execution without vision is how broken systems survive.

Hardeep AnandThe Systems Lens

Disruption carries a burden of proof

This is where the conversation gets difficult.

Disruption carries a charge right now. Political disruption. Technological disruption. Institutional disruption. AI disruption. Regulatory disruption. Cultural disruption. Someone is always pulling on a thread that another group thought was settled.

President Trump is one public example that makes the boundary hard to discuss calmly, because many people react before the sentence is finished.

Some people see disruption they support. Some see recklessness. Some see both at once. I am not asking the reader to agree with any policy, tactic, word, or fight.

I am asking a more useful question:

Why does disruption keep finding an audience?

One explanation is that disruption finds an audience when people believe the system is no longer listening. It finds an audience when the old language of patience sounds like protection for insiders. It finds an audience when citizens, workers, operators, and communities are told to trust a process that does not seem to produce better results.

That does not make every disruption good.

It does mean the discomfort did not come from nowhere.

The honest test is not whether disruption feels polite. The test is whether it can carry a burden of proof.

What gets fixed?

What evidence improves?

What decision becomes clearer?

What risk is made visible?

What human work becomes easier to do well?

If disruption cannot answer those questions, it may only be noise.

If it can answer them, then discomfort may be the price of movement.

Fig. 02 / Burden of proofThe Systems Lens

Disruption earns credit only when it can show what improves

The utility test

Take the politics out for a minute and bring the question back to a utility.

Imagine a pump station that keeps giving the team trouble. The work orders are scattered. The operator notes live in one place, the maintenance history in another, the capital plan somewhere else, and the person who remembers the real sequence is close to retirement.

Someone walks into the room and says the current process is not working.

That person will make people uncomfortable.

Good.

But now the burden of proof starts.

Can they show which records are missing? Can they explain what decision is weaker because of that gap? Can they identify who owns the source, who has authority to act, and what would change if the team connected the information? Can they protect the operator's judgment while making the knowledge easier for the next person to reach?

That is useful disruption.

It does not insult the people doing the work. It respects them enough to stop pretending the structure around them is fine.

The opposite is also true. If the person only creates heat, attacks the room, and leaves no better way to decide, that is not leadership. That is disturbance with a microphone.

The field can tell the difference.

Fig. 03 / Utility testThe Systems Lens

Follow one decision back to its sources

Comfort can become a hidden operating model

Organizations do not usually announce that comfort is their strategy.

They call it stability. Continuity. Process maturity. Risk management. Respect for how things have always been done.

Those things can be real and valuable. A utility cannot run on theatrics. Public infrastructure needs discipline. Operators, engineers, finance teams, permit managers, field crews, and public works leaders cannot chase every new idea that walks through the door.

But comfort becomes dangerous when it protects the wrong thing.

When the data is fragmented and everyone knows it, comfort says to keep using the spreadsheet.

When the person who understands the old system is close to retirement, comfort says there is still time.

When an AI tool can help organize the evidence behind a decision, comfort says the organization is not ready.

When a capital plan depends on assumptions no one can trace, comfort says not to slow the meeting down.

Comfort is not always rest. Sometimes comfort is the agreement not to look too closely.

That is the version that kills innovation in infrastructure. Not because people are lazy. Most people inside these systems are working hard. The problem is that hard work inside a broken structure can still preserve the broken structure.

We have to respect the people and still challenge the pattern.

AI is forcing the adaptation question

AI is forcing this question because it presses on the same weak points that were already there.

That sentence is not meant as a threat. It is meant as a clock.

The useful response is not panic. It is not denial. It is not pretending every AI product is wise because it speaks confidently. AI without provenance is confident nonsense. If it cannot show its sources, boundaries, and chain of evidence, it has not earned trust.

But refusing to learn is not a safety strategy either.

In water and public infrastructure, the weak points are familiar: fragmented data, undocumented tribal knowledge, unclear ownership, untraceable assumptions, slow handoffs, and decisions that depend on people who are not always available when the question arrives.

AI does not create all of those problems.

It exposes them.

That is why the adaptation question matters. The goal is not to become an AI person. The goal is to become more useful in the work because the tools changed.

Can you ask better questions?

Can you check the source?

Can you see the missing handoff?

Can you tell the difference between a confident answer and an accountable answer?

Can you use the tool without surrendering judgment to it?

That is adaptation.

Not worship. Not resistance. Practice.

That is also where the "head in the clouds" insult starts to look different.

The person looking ahead is not always escaping the work. Sometimes they are trying to protect the work before the old tools stop being enough.

Fig. 04 / Adaptation loopThe Systems Lens

Adaptation is repeated practice, not a speech about change

The next generation is watching what we model

There is also a personal side to this.

We tell our children, our teams, and younger professionals to be resilient. We tell them to learn, adapt, take feedback, and move with the world.

Then they watch us.

They watch whether we learn the new tool or only mock it. They watch whether we admit the old process is failing or defend it because it is familiar. They watch whether we use authority to protect the mission or to protect our comfort.

That is the part that should make us quiet for a minute.

Legacy is not only what we leave behind financially. It is what we normalize. It is what we make acceptable. It is whether the people after us inherit cleaner water, cleaner data, clearer decisions, stronger institutions, and a habit of learning when the world changes.

If we leave them broken systems and a lecture about resilience, they will see the contradiction.

They should.

The head-in-the-clouds mandate

So yes, I will keep some part of my head in the clouds.

Not because I want to escape the ground. Because the ground is exactly what I care about.

The pump. The pipe. The permit. The plant. The operator's day. The capital decision. The community that does not care how elegant the org chart looks if the result does not show up in their life.

Someone has to look far enough ahead to see what the current system is about to cost.

Someone also has to come back down and build.

That is the mandate.

See the system before everyone has language for it. Name the cost of comfort. Separate useful disruption from chaos. Connect the vision to evidence, people, authority, and follow-through.

Then do the work.

The question for the next meeting is simple:

What discomfort are we avoiding because it would protect the mission, and what discomfort are we avoiding because it would disturb the comfort zone?

That one question can change the room.

It may not feel comfortable.

It is not supposed to.

What to take into your next uncomfortable meeting

Do not ask whether disruption feels good. Ask whether it makes the work more honest, traceable, and useful.

Email takeawaysShare on LinkedIn

1. Name the protected comfort. Identify the habit, process, or assumption that everyone works around but no one wants to challenge.
2. Ask for the operating result. Useful disruption should make a decision clearer, a risk more visible, or a handoff easier to trust.
3. Respect the people while challenging the pattern. Most broken systems are held together by people working hard inside structures that need to change.
4. Use AI as a readiness test. If the tool cannot show its sources, ownership, and boundaries, the work underneath is not ready for trust.
5. Model adaptation before asking for it. The next generation learns from what leaders practice, not what they preach.

One question to ask: What discomfort are we avoiding because it would improve the mission, and what discomfort are we avoiding because it would expose the comfort zone?

Head in the Clouds Is Not an Insult
Hardeep Anand · The Systems Lens
https://hardeepanand.com/writing/head-in-the-clouds-is-not-an-insult/