When “That’s Not My Job” Becomes an Organizational Disease

An anti-CEO article for Leaders, Project managers, and CXO’s

Executive Insight

Organizations rarely fail because of lack of talent. They fail because talent gets trapped inside silos. When people begin protecting roles more than outcomes, collaboration weakens, accountability shrinks, and business agility collapses.

The invisible walls employees build—and why leaders must keep tearing them down

“Unless you keep breaking it, they will keep making it.”

Press enter or click to view image in full size

Photo by Igor Omilaev on Unsplash

The Most Dangerous Wall Inside Organizations Is Invisible

As usual one morning, I was having a casual call with my wife. We were almost out of topics, so I casually asked, “How’s the project going? Anything interesting happening there?”

She replied, “Nothing new except a rollout this Friday for which the team is preparing. There is a resource crunch, though, which is becoming a threat.”

Working deeply in leadership and organizational behavior, such moments always catch my attention. Hidden inside normal conversations are often real business problems.

So I poked further.

“Why suddenly at this phase?”

She explained that the challenge was around testing.
"The team is divided into frontend and backend, and then there is testing… handled by only one person.”

At that moment, the issue became obvious to me.

Still, I continued the conversation carefully because sometimes solutions are less about logic and more about mindset.

I asked,
"Since you are already near UAT (User Acceptance Testing), I’m sure the development and functional teams must be relatively lean on effort now. Why don’t they help execute some test cases?”

I added,
"Everyone in an IT team broadly understands testing. Surely they can extend support.”

She paused and then she responded thoughtfully.
"Yes, the team can help. But they will mostly do positive test cases, not negative scenarios.”

I replied,
"That's still a great start. Let the tester focus on the negative cases while others take some load off. The overall test planning can always ensure that it covers both positive and negative cases properly.

Because honestly, any meaningful help is better than repeatedly saying

“We need additional resources.”

While she was processing the idea, I also warned her:

You can only propose such an idea if you are willing to step beyond your role. And if you do, be prepared — some people may dislike you for increasing collective responsibility.”

She smiles and says she is already extending her project management role while doing some testing.

That is where I realized that I should write about this.

The Invisible Walls Inside Organizations

Away from this story, this is a classic example of the term

“employee mindset”

Over time, people slowly build invisible walls around themselves using designations, KRAs, and job descriptions.

The more frequently an organization hears the following:

“This is not my job.”

…the stronger those walls become.

And once those walls harden, collaboration dies silently.

Let me be clear—role clarity is important. This article is not against specialization or accountability but something deeper.

Every employee has a valid right to ask the following:

• “What’s in it for me?”

• “Why should I work beyond my role?”

• “Will the company pay me extra?”

• “Why should I stretch while others don’t?”

These are fair questions.

But organizations built entirely on transactional thinking can function—it's just they rarely become great.

One small incident often exposes the deeper culture of a company.

Culture is not what is written in the HR deck. Culture is what people do when work falls outside their designation.

Employee Mindset vs Entrepreneur Mindset

This is one reason I never prefer calling my team members as “employees.”

I see teams as associate partners.

Whenever one unit becomes overloaded, another unit provides support wherever possible. The team itself decides how to contribute.

Because business problems do not arrive department-wise.

Deadlines don’t care about job descriptions.

Clients don’t experience “frontend issues” or “testing issues.” They only experience delivery.

That is why the difference between an employee mindset and an entrepreneur mindset (even in a job) is very real.

An employee mindset asks:

“What is my scope?”

An entrepreneur mindset asks:

“What does the situation need?”

If not addressed consciously, wall-building eventually creates a toxic culture where people proudly share stories over tea breaks like:

“I barely work and still got a good appraisal.”

The moment such stories become normal, organizational decline has already started.

What Organizations Must Do

Organizations that do not yet have a collaborative culture should start slowly and intentionally.

Because forcing cross-functional ownership suddenly can backfire badly.

If handled poorly, it can create:

• Friction between delivery and clients

• Internal resentment

• Role confusion

• Missed timelines

• Rising organizational conflict

• Burnout without ownership

And eventually, leadership starts blaming external factors like market slowdown, immigration policies, or AI disruption for the bottom-line decline.

Yes, when the market was easy, these issues were under the rug.

But often the real issue is internal fragmentation.

It is a slow poison.

And like most slow poisons, organizations realize it too late.

This Is What I Recommend

1. Build “Mission Ownership,” Not Just Role Ownership. Teams should understand the larger business outcome, not just their task list.

2. Reward Contribution Beyond Designation. Most organizations unintentionally reward territorial behaviors like late nights, being too busy with meetings, hanging out more with bosses, etc.

What gets rewarded gets repeated.

3. Normalize Temporary Role Fluidity. During crunch situations, temporary role overlap should become culturally acceptable starting with leaders.

4. Train Teams in Adjacent Awareness. A frontend developer does not need to become a tester, but they should understand testing basics. A designer may not write copy but should understand communication goals.

Organizations become resilient when people understand neighboring functions and prioritize the team over individual comfort.

5. Leadership Must Demonstrate the Behavior First. I have already highlighted that no team will stretch if leadership behaves in a territorial manner. The culture always mirrors the emotional behavior of leadership.

6. Stop Treating People Like Replaceable Resources. The word “resource” itself is dangerous when overused. People who feel emotionally disconnected from the mission naturally shrink into minimum responsibility mode.

Ownership grows when people feel respected, trusted, and included.

Press enter or click to view image in full size

High Ownership vs Low Ownership Culture

Final Thought

Organizations do not collapse in one day. They slowly weaken when compartmentalization replaces collaboration.

The strongest companies are not the ones with the best org charts. They are the ones where people step forward without being asked.

Because in the end:

“Unless you keep breaking the walls, people will keep building them.”

Summary

• Pressure situations most clearly expose organizational culture.

• “This is not my job” may protect individuals temporarily but weakens collective growth.

• Great organizations are built when people optimize for mission success, not designation boundaries.

Press enter or click to view image in full size

_______________________________________________________________

If the message resonated, the book is available on [Amazon India — link]. I’d love to hear where you think you are in the 4S journey right now; reply or comment below.

If you find my perspective useful, we can connect at through medium and LinkedIn: https://www.linkedin.com/in/unbinarykundan/