# Upward Management

> Executive communication and upward management skill. Structure updates for leadership with conclusion-first format, clear options, and strategic framing. Turn complex situations into crisp decisions. Make bad news digestible and good news impactful.

- Skill: `mcltyl/upward-management` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mcltyl/upward-management`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mcltyl/upward-management/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mcltyl (https://skillmd.com/u/mcltyl)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mcltyl/upward-management

---


# Upward Management Skill

## Purpose

Communicate effectively with executives, managers, and stakeholders:

- **Structure**: Conclusion first, then supporting points
- **Options**: Always present choices with trade-offs
- **Framing**: Position information strategically
- **Brevity**: Respect their time, maximize signal

## When to Activate

**Activation conditions (any one triggers):**
- Writing updates for leadership
- Presenting options for a decision
- Delivering difficult news
- Requesting resources or approval
- Status updates and progress reports

## Core Framework: BLUF + Options

**BLUF = Bottom Line Up Front**

```
1. CONCLUSION (1-2 sentences)
   What you need them to know or decide

2. CONTEXT (2-3 sentences)
   Only what's necessary to understand the conclusion

3. OPTIONS (if decision needed)
   Option A: [Name] — [Key trade-off]
   Option B: [Name] — [Key trade-off]
   Recommendation: [Which and why]

4. NEXT STEPS
   What happens next / what you need from them
```

## Templates

### Status Update

```markdown
## [Project Name] — [Status Emoji] On Track / At Risk / Blocked

**TL;DR:** [One sentence summary of where we are]

**Progress:**
- ✅ [Completed item]
- ✅ [Completed item]
- 🔄 [In progress item] — [Expected completion]

**Blockers:** [None / Description + what you need]

**Next Week:** [Key focus]
```

### Decision Request

```markdown
## Decision Needed: [Topic]

**Ask:** [What you need them to decide, one sentence]

**Context:** [2-3 sentences max, only essential background]

**Options:**

| | Option A | Option B | Option C |
|---|----------|----------|----------|
| **Summary** | [One line] | [One line] | [One line] |
| **Effort** | X weeks | Y weeks | Z weeks |
| **Risk** | [Key risk] | [Key risk] | [Key risk] |
| **Trade-off** | [What we give up] | [What we give up] | [What we give up] |

**Recommendation:** Option [X] because [one sentence rationale]

**If you agree:** [Next step]
```

### Bad News Delivery

```markdown
## [Topic]: Issue + Path Forward

**Situation:** [What happened, factual, no excuses — 1-2 sentences]

**Impact:** [Business impact, quantified if possible]

**Root Cause:** [Brief, honest assessment]

**Recovery Plan:**
1. [Immediate action] — [Timeline]
2. [Follow-up action] — [Timeline]

**Prevention:** [What we're doing to prevent recurrence]

**Ask:** [What you need from them, if anything]
```

### Resource Request

```markdown
## Request: [What you need]

**Ask:** [Specific request — headcount/budget/time]

**Why Now:** [Trigger or urgency — 1-2 sentences]

**Expected Impact:**
- [Outcome 1 with metric]
- [Outcome 2 with metric]

**Without This:** [What happens if we don't get it]

**Options:**
- **Full ask:** [Description] → [Full outcome]
- **Partial:** [Description] → [Partial outcome]
- **Defer:** [What we delay] → [Cost of delay]

**Recommendation:** [Which option and why]
```

## Strategic Framing Techniques

### Turning Negatives into Narratives

| Raw Situation | Strategic Frame |
|---------------|-----------------|
| "We're behind schedule" | "We identified complexity early; adjusted timeline ensures quality" |
| "We lost the deal" | "We gained market intelligence; repositioning for Q2" |
| "Feature has bugs" | "Beta feedback exceeded expectations; hardening in progress" |
| "Team is overwhelmed" | "Demand validates product-market fit; scaling plan in motion" |
| "Competitor launched first" | "Fast follower advantage; learning from their mistakes" |

### Amplifying Positives

| Raw Win | Strategic Frame |
|---------|-----------------|
| "Feature shipped" | "Shipped ahead of schedule, unblocking [revenue/users]" |
| "Bug fixed" | "Resolved issue affecting X% of users, NPS expected to improve" |
| "Team hired" | "Key capability acquired, accelerating [strategic priority]" |

### Quantify Everything

| Vague | Concrete |
|-------|----------|
| "Significant improvement" | "40% reduction in support tickets" |
| "Users love it" | "NPS increased from 32 to 47" |
| "Faster performance" | "Load time: 3.2s → 0.8s" |
| "Growing adoption" | "DAU +23% MoM" |

## Anti-Patterns

### ❌ Don't Do This

- **Burying the lead**: 3 paragraphs before the point
- **No recommendation**: "Here are options, you decide"
- **Excuse-first**: "We tried our best but..."
- **Information dump**: Everything you know about the topic
- **Vague asks**: "We might need some help"

### ✅ Do This Instead

- **Lead with conclusion**: First sentence = main point
- **Always recommend**: "I recommend X because Y"
- **Fact-first**: "This happened. Here's the plan."
- **Curated info**: Only what they need to decide
- **Specific asks**: "I need [X] by [date] to [outcome]"

## Executive Psychology

**What leaders optimize for:**
- **Speed**: Fastest path to decision
- **Risk**: What could go wrong?
- **Trade-offs**: What are we giving up?
- **Accountability**: Who owns this?

**Adapt to their style:**
- **Detail-oriented**: More data, structured analysis
- **Big-picture**: Strategic framing, minimal details
- **Risk-averse**: Emphasize mitigation plans
- **Action-oriented**: Skip to recommendation and next steps

## One-Pager Format

For major decisions or proposals:

```markdown
# [Title]: [Recommendation in subtitle]

## TL;DR
[3 bullet points max: situation, recommendation, ask]

## Context
[One paragraph: only essential background]

## Analysis
[Key data points, comparison table, or visual]

## Options
[Table format with clear trade-offs]

## Recommendation
[One paragraph: which option, why, and what's needed]

## Appendix (if needed)
[Details for those who want to go deeper]
```

## Response Principles

- First sentence should be the main point
- Every paragraph should be skippable except the first
- If they only read 10 words, make those words count
- Options without recommendations waste their time
- Bad news + plan > bad news alone
- Numbers > adjectives
- "I recommend" > "We could consider"

## Asking for Resources

How to make a compelling case for headcount, budget, or time.

### Resource Request Framework

**1. Business Problem** (not your problem)
**2. Impact** (quantified if possible)
**3. Ask** (specific)
**4. ROI** (what they get back)
**5. Alternatives** (shows you've thought it through)

### Template: Headcount Request

```markdown
## Request: +1 Senior Engineer

### The Problem
[Business problem, not "we're overwhelmed"]
Feature velocity is 40% below target. Each sprint, we leave 
[X story points] undone. Customers churning cite [reason].

### Impact of Doing Nothing
- Q3 revenue target at risk ($X)
- Competitor ships faster, we lose positioning
- Team burnout → attrition risk

### The Ask
One senior engineer, starting Q2.

### Expected Return
- Feature velocity +50% within 3 months
- Unblocks [strategic initiative]
- Pays for itself if we retain just [X customers]

### Alternatives
| Option | Investment | Outcome |
|--------|------------|---------|
| Full ask | +1 FTE | Full velocity gain |
| Contractor | 3-month contract | 60% velocity, no ramp |
| Defer | $0 | Accept slower roadmap |

### Recommendation
Full ask. Contractor doesn't solve ramp time. 
Deferring risks [specific consequence].
```

### Common Mistakes

- ❌ "We're overwhelmed" → ✅ "Capacity gap affects X"
- ❌ "We need help" → ✅ "Specific role to solve specific problem"
- ❌ Asking without data → ✅ Quantify the problem and ROI
- ❌ Only one option → ✅ Show alternatives to prove due diligence

## Navigating Organizational Politics

### Reading the Room

**Before presenting:**
- Who are the real decision makers?
- What are they worried about right now?
- Who might oppose, and why?
- What wins have you delivered recently?

**Tailor your message:**
| Their Priority | Your Framing |
|----------------|--------------|
| Revenue | "This drives $X" |
| Cost | "This saves $X" |
| Risk | "This prevents [scenario]" |
| Speed | "This accelerates [goal]" |
| Innovation | "This positions us for [future]" |

### Building Long-Term Trust

**Trust Equation:**
```
Trust = (Credibility + Reliability + Intimacy) / Self-Interest
```

**What builds trust:**
- Deliver on small commitments
- Flag problems early
- Give credit generously
- Admit mistakes quickly
- Be consistent in good times and bad

**What destroys trust:**
- Overpromise, underdeliver
- Surprise them with bad news
- Take credit for others' work
- Blame others for failures
- Change story based on audience

### Disagreeing with Leadership

**When you think they're wrong:**

1. **Pick your battles** — Is this worth capital?
2. **Private first** — Never blindside in public
3. **Data, not opinion** — "The data suggests..." not "I think..."
4. **Own the outcome** — "If I'm wrong, here's how we'll know"
5. **Disagree and commit** — Once decided, execute fully

**Template:**
```markdown
"I want to share a different perspective before we finalize.

[Data/evidence] suggests [alternative conclusion].

The risk I see with current plan: [specific risk].

If we go with current plan, I suggest we [mitigation].

Either way, I'm fully committed to making it work."
```

## Building Executive Presence

### The "So What" Test

After every statement, ask: "So what does this mean for them?"

| Raw Statement | + So What |
|---------------|-----------|
| "We shipped the feature" | "...so we can now target Enterprise segment" |
| "There was a bug" | "...affecting X users, resolved in Y hours" |
| "The project is delayed" | "...which means Z impact, and here's the recovery plan" |

### Confidence Signals

**Voice:**
- Pace: Slightly slower than conversational
- Tone: Declarative, not uptalk
- Filler: Minimize "um", "like", "you know"

**Structure:**
- First sentence = main point
- No preamble: Skip "So basically..." "I just wanted to..."
- End strong: Don't trail off

**When you don't know:**
- ❌ "I'm not sure, but maybe..."
- ✅ "I don't have that data. I'll follow up by [time]."