In company, “Giving a Fish” looks like this:

• Employee: Sends a raw file saying, “Please check this.”

• Manager/HOD: Fixes the typos, finds the missing data, corrects the logic, and sends it back.

When we do this, we aren’t helping. We are crippling the team’s growth. We are creating a culture of Reverse Delegation, where the manager ends up working for the employee.

To break this cycle, we need to understand the Matrix of Responsibility and use a specific Framework to spot the difference between a genuine cry for help and a lazy hand-off.

1. The Philosophy: Fishing vs. Feeding

The goal of every HOD and Leader here is not to be the “Chief Fixer.” It is to be the “Chief Teacher.”

• Feeding (Bad): You ask me to find the errors. You learn nothing. You will make the same mistake next week.

• Teaching (Good): You find the errors yourself. You ask me about the strategy or the approach. You learn how to solve the problem, so next week you don’t need me.

We need to stop feeding and start teaching. But to do that, we need to agree on who holds the rod.

2. The Matrix: Who Holds the Rod?

To stop reverse delegation, we must visualize our roles. We use a simplified Responsibility Matrix (based on RACI) to define who does what.

• The DOER (Responsible): This is YOU (the employee). You hold the rod. You catch the fish. You clean the fish. You are responsible for the accuracy, completeness, and quality of the work.

• The SAFETY NET (Accountable/Consulted): This is the HOD or Founder. We are here to ensure the boat doesn’t sink. We check the strategy and the risk.

The Trap: When you send a document without checking it yourself, you are forcing the HOD to be the Doer. You are asking your boss to hold the rod while you watch. This is not collaboration; it is abdication.

3. The Framework: Is This Genuine or Reverse Delegation?

How do you know if you are delegating properly? Or, if you are a manager, how do you know if your team is “reverse delegating” to you?

Use this “Litmus Test.”

Signs of Reverse Delegation (The “Lazy” Ask)

• The Question: “Is this okay?” or “Please check attached.”

• The Context: None. Just a file.

• The Effort: Typos present, formulas unchecked, obvious gaps.

• The Mindset: “If I miss something, my boss will catch it.”

• Verdict: REJECT. Send it back unread.

Signs of Genuine Requirements (The “Growth” Ask)

• The Question: “I’ve checked the data, but I’m worried about the legal risk in Clause 4. Can you review that specific paragraph?”

• The Context: Clear explanation of why this matters.

• The Effort: The document is polished. The basic checks are done.

• The Mindset: “I own this work, but I need expert advice on one blind spot.”

• Verdict: ACCEPT. This is high-value collaboration.

4. The Solution: The 5-Point “Pre-Flight” Checklist

To make this part of our daily culture, no work should be submitted for review without answering these 5 questions. This is your filter.

If you cannot answer these, you are not ready to send the email.

1. The Context: What is this, and why are we doing it? (Don’t make me guess).

2. The Verification: What checks have you already performed? (Prove you found the typos and math errors).

3. The Specific Doubt: What exactly do you need me to check? (Do not say “everything.” Point me to the risk).

4. The Recommendation: If I wasn’t here, what would you do? (Show me you are a Driver, not a Passenger).

5. The “Ready” Statement: Are you willing to bet your reputation on this draft? (If I signed it without looking, would we be safe?)

Summary

To the Team: We trust you. That’s why we want you to check your own work. We want you to grow into Leaders, not just Task-Doers.

To the HODs: Be a Safety Net for the fall, not a crutch for the walk. If the checklist isn’t there, send the work back. It’s the only way to teach them to fish.

Subscribe now