samarv/leveraging-leadership-to-bulldoze-obstacles

Proactive leadership leverage shifts your relationship with your manager from "reporting status" to "accelerating execution." Your primary job is not to do everything yourself to prove competency; it is to get the project done correctly and efficiently by using every tool at your disposal—including your manager’s authority and perspective.

The "HPM" Status Framework

Maintain a consistent "heartbeat" of information so that when you need a leader to intervene, they already have the necessary context. Send this as a short, written update (Slack/Email) weekly.

• Highlight: What are the 1–3 big-ticket items the leader needs to know? Focus on outcomes, not just activities.
• People: Who is doing amazing work that needs a shout-out? Who is at risk of burning out or leaving?
• Me: How are you personally doing? What is your current capacity or morale?

The "No Response Required" Update

Use this to maintain high visibility without creating a "ping-pong" of unnecessary meetings.

• Format: A 5–10 sentence email or message.
• Trigger: When a project reaches a minor milestone or shifts slightly in direction.
• Closing: Explicitly state: "No response required. I will proceed with this plan unless I hear otherwise by [Time/Date]."

High-Leverage Unblocking

When you are genuinely stuck (e.g., a cross-functional partner is non-responsive or a technical dependency is slipping), do not just report the problem. Provide the "bulldozing" tool for the leader to use.

1. Diagnose the Delta: Identify exactly why the project is stalling (e.g., "Team B has a different priority list").
2. Frame the Choice: Give the leader a binary or multiple-choice decision. "I think we should do X to solve Y. Do you agree? (Yes/No)"
3. Provide the "Ghost-Write": Include a draft email the leader can send to the blocker. This makes it "cheap" for the leader to help you.

Examples

Example 1: Cross-functional friction

• Context: You are a PM waiting on an Engineering team in a different org to approve an API change. They haven't responded in a week.
• Input to Manager: "I’m currently blocked by the Platform team on the API spec. It’s been 7 days since my last follow-up. I need you to help me bulldoze this."
• Application: Provide the manager with a pre-written Slack message to the Platform Lead: "Hey [Name], my team is blocked on [Project] waiting for the API approval. Can we get this reviewed by EOD tomorrow to keep us on track for the launch?"
• Output: The manager copies/pastes the message, and the "Eye of Sauron" effect clears the blocker within hours.

Example 2: Strategic Misalignment

• Context: You receive a vague brief for a new feature and aren't sure which "weeds" matter to the CEO.
• Input to Manager: "I'm starting the Discovery on [Feature]. I want to make sure I'm in the right weeds."
• Application: Present three low-fidelity mocks representing different strategic directions.
• Output: The manager identifies which direction the CEO will actually care about (the "Eye of Sauron" focus), saving you three weeks of work on the wrong mocks.

Common Pitfalls

• The "Identity Threat" Mistake: Thinking that asking for help is an admission of defeat. In reality, managers want you to be awesome because it makes their lives easier.
• The "Surprise" Failure: Waiting until a "plate falls" (a project fails) to tell the manager. Leaders hate surprises; they love "rotational velocity" updates.
• Treating All Managers the Same: Some managers want deep technical details; others want high-level strategy. Ask explicitly: "How do you like to get information? What is your preferred cadence?"
• Failing to Address Premise: If you try to communicate a conclusion before the leader accepts your premise (the "why"), they will ignore you. Always start by acknowledging the current issue or fear the leader has.