← Back to home
Engineering Leadership

When Your Team Stops Thinking for Itself: The Hidden Cost of Excessive Control

When people stop making decisions, stop challenging ideas, and start waiting for instructions, don't immediately question their capability. First, examine the environment in which they are expected to work.

One of the most concerning things I have observed in organizations is not a lack of technical skills or experience.

It is the gradual disappearance of independent thinking.

You attend a meeting and ask for recommendations.

Nobody offers one.

You ask a technical lead how they would approach a problem.

They respond by asking what you would prefer.

You assign an initiative and expect the person responsible to come back with a plan.

Instead, they return with a list of questions about what they should do next.

At some point, you begin to wonder whether the team has the necessary capability to operate independently.

But I think there is another possibility worth considering.

What if the organization has gradually trained people not to think for themselves?

It doesn't happen overnight.

It develops through repeated interactions, management practices, and organizational behaviors that unintentionally discourage initiative.

How independent thinking disappears

Consider a technical design discussion.

An architect presents a proposed solution.

The manager immediately questions the approach, suggests an alternative, and directs the architect to revise the design.

The architect goes back and makes the changes.

A few weeks later, another design is presented.

The same thing happens.

Eventually, the architect stops putting forward a recommendation.

Instead, they ask the manager what approach they should take before investing time in developing a solution.

From the manager's perspective, the architect may appear to lack initiative.

But from the architect's perspective, there is little incentive to exercise independent judgment when the manager consistently overrides it.

The behavior is learned.

People begin to understand what is expected of them.

They stop preparing recommendations and start preparing options for someone else to decide.

They stop challenging assumptions and start seeking agreement.

They stop owning outcomes and start following instructions.

This is how excessive control gradually weakens independent thinking.

The approval culture

Another common symptom is an organization where almost everything requires approval.

A technical lead cannot finalize a design without managerial sign-off.

An engineering manager cannot adjust priorities without seeking permission.

A team member cannot communicate a delivery risk to a stakeholder without first consulting their manager.

Even routine operational decisions become escalation points.

Of course, some decisions should require approval.

Financial commitments, significant architectural changes, security exceptions, and business-critical risks may need formal governance.

But when the approval process extends to routine decisions, it creates unnecessary dependency.

It also sends a message.

The message is that independent judgment is not trusted.

Over time, people adapt.

Why take responsibility for a decision when someone else can make it?

Why risk disagreement when approval is safer?

Why think through alternatives when the manager will eventually prescribe the answer?

The organization ends up with a culture of compliance rather than ownership.

The difference between asking questions and challenging thinking

I believe managers play an important role in developing independent thinking.

But this requires changing how we interact with people.

Imagine an engineer approaching you with a technical problem.

One response is to immediately provide the solution.

You know the technology, understand the architecture, and have probably encountered something similar before.

Providing the answer is quick.

But consider a different response.

Ask the engineer:

  • What do you believe is causing the problem?
  • What alternatives have you considered?
  • What are the trade-offs?
  • Which approach would you recommend?
  • What risks do you see?
  • What would you do if I weren't available?

The conversation becomes an opportunity to develop reasoning.

You can challenge assumptions, introduce considerations they may have missed, and help them evaluate alternatives.

But the individual still owns the thinking.

I don't believe a manager needs to have the answer to every question.

Sometimes, asking the right question is far more valuable than providing an immediate solution.

This is particularly important in technology leadership, where problems are rarely identical and solutions require context-specific judgment.

We should be developing people who can reason through unfamiliar situations, not simply reproduce solutions from previous experiences.

Psychological safety and the fear of being wrong

There is another important dimension to this problem.

People will not exercise independent judgment if they believe every mistake will be treated as a failure.

Think about an engineering team working on a modernization initiative.

One engineer proposes an alternative architecture.

The proposal is challenged aggressively in a meeting. The engineer is criticized for not considering every possible dependency.

The discussion ends with the manager prescribing the solution.

What does the rest of the team learn?

Probably not that they should bring better proposals next time.

They learn that proposing something different can be risky.

They begin to keep their ideas to themselves.

This is why I believe psychological safety matters in leadership.

It doesn't mean lowering standards or avoiding difficult conversations.

It means creating an environment where people can disagree respectfully, raise concerns, challenge decisions, and admit uncertainty without fear of humiliation.

A team should be able to say:

"I disagree with this approach, and here is why."

It should also be able to say:

"I made the wrong decision. Here is what happened, and here is what I learned."

Leaders need to distinguish between an honest mistake made through responsible decision-making and careless behavior that disregards established expectations.

If we want people to think independently, we must make it safe for them to express independent thinking.

When agreement becomes more important than good decisions

I have always believed that a team where everyone agrees with the manager is not necessarily a healthy team.

In fact, it can be a warning sign.

Consider an architecture review where everyone accepts the proposed solution without questioning its scalability, security implications, operational complexity, or long-term cost.

The meeting finishes quickly.

But has the organization made a good decision?

Perhaps not.

Healthy technical organizations need constructive disagreement.

Architects should challenge engineering decisions. Engineers should question architectural assumptions. Security teams should identify risks. Operations teams should challenge designs that create unnecessary operational complexity.

The objective isn't to win arguments.

It is to make better decisions.

A leader should welcome a well-reasoned disagreement, even when it challenges their own recommendation.

If people learn that agreement is rewarded more consistently than critical thinking, they will eventually optimize for agreement.

And the organization will lose one of its most valuable capabilities: the ability to challenge itself.

Autonomy needs guardrails, not constant supervision

There is an important distinction between giving people autonomy and allowing everyone to operate without alignment.

Independent thinking does not mean independent direction.

Teams need shared objectives, architectural principles, security standards, financial boundaries, and clear accountability.

For example, an engineering organization can establish enterprise architecture standards and security requirements while allowing individual teams to determine how best to implement solutions within those boundaries.

Similarly, a platform engineering organization can provide golden paths, standardized deployment pipelines, and reusable capabilities without dictating every engineering decision.

The purpose of guardrails is to make responsible decision-making easier.

They should not become another mechanism for centralizing control.

Good leadership creates clarity about what cannot be compromised while allowing flexibility in how outcomes are achieved.

Rebuilding a culture of independent thinking

If a team has become accustomed to seeking instructions, changing that behavior requires patience and consistency.

Managers cannot spend years centralizing decisions and suddenly expect everyone to become autonomous.

It requires deliberate effort.

A few practices can make a meaningful difference.

Ask for recommendations, not just updates.

Instead of asking what someone has completed, ask what they recommend doing next and why.

Give people ownership of decisions.

Start with decisions that have manageable risks and gradually expand their authority.

Encourage constructive disagreement.

Make it clear that challenging an idea is not the same as challenging someone's authority.

Avoid immediately providing answers.

Give people time to think, evaluate, and propose solutions before stepping in.

Recognize good judgment, not just successful outcomes.

A well-reasoned decision can still produce an unexpected result. Recognize the quality of the thinking, not only whether the outcome was perfect.

Be consistent.

If managers encourage independent thinking but repeatedly override decisions without explanation, the culture will not change.

The behavior of leadership must match the expectations being placed on the team.

My perspective: Don't create followers when you need thinkers

I believe one of the biggest responsibilities of leadership is to develop people who can think beyond the instructions they receive.

A team that executes instructions efficiently has value.

But a team that can identify problems, challenge assumptions, evaluate alternatives, make decisions, and take ownership creates much greater organizational capability.

This becomes even more important as technology organizations evolve.

With automation and AI increasingly taking over routine execution, the value of human judgment, problem-solving, critical thinking, and decision-making becomes even more important.

We should be building teams that can think, not simply teams that can execute.

I would rather have an engineer who challenges my technical recommendation with sound reasoning than one who agrees with everything I say.

I would rather have an architect who identifies a weakness in an enterprise design than one who simply implements it without question.

And I would rather have an engineering manager who independently resolves difficult situations than one who constantly escalates decisions that should be theirs to make.

As leaders, we should periodically ask ourselves:

Are we developing people who can make better decisions, or are we developing people who are simply getting better at asking us for decisions?

There is a significant difference.

If your team has stopped thinking independently, don't start by demanding more initiative.

First, examine whether your leadership practices actually encourage it.

Because people don't develop ownership simply because it appears in their job description.

They develop it when they are trusted, given opportunities, supported through challenges, and held accountable for meaningful outcomes.

The goal of leadership is not to create a team that follows instructions perfectly. It is to create a team that understands the purpose, thinks critically, makes sound decisions, and takes responsibility for the results.

Don't measure your team's effectiveness by how well they follow your instructions.

Measure it by how well they think and perform when you aren't giving any.


If every decision requires your opinion, you may have built a team that knows how to follow you but has never learned how to lead itself.

END OF ARTICLEExplore more thinking ↗
DISCUSSION

Reactions & comments

Sign in with GitHub to react or join the conversation.

Discussion is not configured yet.

Add your giscus repoId and categoryId to site.config.ts.