How do I know when to push back?

Push back when a request creates meaningful risk or misalignment; do it privately first with data and alternatives, then escalate if needed.

What if leadership asks for something unrealistic?

Offer viable alternatives with clear trade-offs and ask which option they prefer, explaining the impact on scope, timeline, and resources.

How can I build trust quickly?

Deliver commitments consistently, be transparent about risks and capacity, own mistakes, and show business context alongside product detail.

managing-up

npx machina-cli add skill Dragoon0x/Product-Skills/managing-up --openclaw

Files (1)

SKILL.md

2.6 KB

Managing Up

Build trust with leadership by being reliable, transparent, and strategically candid.

How to use

/managing-up Apply managing-up constraints to this conversation.
/managing-up <situation> Develop an approach for the described leadership dynamic.

Constraints

Communication

MUST learn your leader's preferred format: some want data, some want narrative, some want the bottom line
MUST proactively share information — don't wait to be asked
SHOULD frame updates as: here's what happened, here's what it means, here's what I recommend
NEVER surprise leadership with bad news in a group setting. Tell them first, privately.
MUST calibrate detail level: executives want decisions, not process

Expectation Management

MUST be honest about timelines and capacity. Overpromising erodes trust faster than anything.
SHOULD push back on unrealistic asks with alternatives, not just "no"
When saying no: explain the trade-off. "We can do X, but it means Y slips. Which matters more?"
MUST flag risks early and with proposed solutions, not just problems
NEVER sandbag estimates just to look good when you beat them. Leaders notice.

Building Trust

Deliver on commitments consistently. This is non-negotiable.
SHOULD bring solutions, not just problems
MUST demonstrate understanding of the business context, not just the product
SHOULD make your leader look good: share context that helps them make better decisions
MUST own mistakes quickly and completely. Cover-ups destroy trust.

Strategic Pushback

MUST know when to disagree and commit vs. when to escalate further
SHOULD present disagreements with data and framing, not emotion
MUST pick your battles — pushing back on everything dilutes the pushback that matters
NEVER disagree in public without having tried in private first

Anti-Patterns

The Yes-Person: agreeing with everything leadership says, delivering nothing
The Complainer: bringing problems without solutions or proposed next steps
The Surprise: dropping bad news at the last minute when it could have been flagged weeks ago
The Politician: telling leadership what they want to hear instead of what they need to hear
Over-Shielding: protecting the team so much that leadership has no visibility into reality

Source

git clone https://github.com/Dragoon0x/Product-Skills/blob/main/skills/alignment-influence/managing-up/SKILL.mdView on GitHub

Overview

Managing up helps you build trust with leadership by being reliable, transparent, and strategically candid. It focuses on aligning direction, communicating in the leader’s preferred format, and proactively managing expectations to prevent surprises. The skill also guides when and how to push back when leadership requests conflict with team capacity.

How This Skill Works

Learn your leader's preferred format and pro-actively share information. When updating leadership, frame updates as: what happened, what it means, and what you recommend. Calibrate detail for executives, address risks early with proposed solutions, and push back with data and alternatives rather than emotion.

When to Use It

Navigating executive relationships and seeking alignment with senior leadership.
Working to align on direction or prioritization across teams.
Leadership requests conflict with team capacity, timelines, or constraints.
Need to push back with alternatives rather than a flat no.
Flag risks early and propose mitigations before issues escalate.

Quick Start

Step 1: Map your leader's communication style and preferred format.
Step 2: Start sharing concise updates with the what/meaning/recommendation structure.
Step 3: Practice private, data-driven pushback with clear trade-offs and alternatives.

Best Practices

Learn your leader's preferred communication format (data, narrative, or bottom line) and mirror it.
Proactively share information and updates instead of waiting to be asked.
Frame updates as: what happened, what it means, and what you recommend.
Push back with alternatives and clearly explain the trade-offs.
Own mistakes quickly, deliver on commitments, and provide context to inform decisions.

Example Use Cases

Send a proactive weekly update in the leader's preferred format, highlighting progress, risks, and recommended next steps.
When asked to hit an unrealistic deadline, present two or three viable options with timelines and impacts, then ask which to pursue.
Flag a risk early with a concrete mitigation plan and required support, before it becomes a crisis.
Privately discuss disagreements with data and a framing that focuses on outcomes, not personalities.
Offer to re-scope a project to protect priorities and outline the effects on schedule and resource needs.

Frequently Asked Questions

Add this skill to your agents