Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
Managing Up
The most career-defining skill nobody teaches is invisible by design. Managing up -- the deliberate cultivation of a productive relationship with one's boss -- receives no curriculum in business school, no chapter in the onboarding manual, and no line item in the performance review. Yet the gap between what a leader accomplishes and what their boss perceives them as accomplishing determines promotions, resource allocation, and institutional survival more reliably than raw competence ever will. The uncomfortable truth is that talent unwitnessed is talent wasted. Effective leaders do not merely perform; they ensure the right people understand what they are performing, why it matters, and how it connects to the organisation's strategic arc.
The Framework
Managing up is not flattery, nor is it political manoeuvring. It is a structured practice built on four pillars: information management, strategic visibility, boss comprehension, and expectation calibration.
Pillar 1: Information Management -- Close the Gap
Most leaders dramatically underestimate how much information their boss needs. The assumption that a competent manager "already knows" is both common and dangerous. Bosses operate under information asymmetry by default: they manage multiple reports, navigate competing priorities, and cannot read minds. The effective leader treats upward information flow as a design problem, not an afterthought.
The information gap manifests in two directions:
- Under-reporting: Assuming the boss knows more than they do. Projects stall, problems escalate, and the boss is blindsided -- all because a direct report confused autonomy with silence.
- Over-reporting: Flooding a manager with granular detail, forcing them to extract signal from noise. This is not diligence; it is delegation of cognitive work upward.
The discipline lies in matching information type, frequency, and format to the boss's actual needs. Some managers want a daily stand-up summary. Others want to hear nothing until something is on fire. Neither preference is wrong; failing to learn it is.
Pillar 2: Strategic Visibility -- Be Witnessed Thinking
Competence alone does not earn advancement. Senior executives need to witness strategic thinking in action. This means preparing for meetings not merely to contribute but to demonstrate the altitude of one's perspective. Before a strategy session, the effective leader blocks time to think through the agenda, considers cross-departmental implications, and prepares a point of view that shows they are not thinking in a vacuum.
Three methods for demonstrating strategic thinking:
- Reframe operational updates as strategic contributions. Instead of "We shipped feature X on time," try "Feature X positions us to capture the mid-market segment three months ahead of the competitor timeline."
- Ask questions that reveal long-term thinking. In skip-level conversations, ask about five-year milestones, industry trends the team should respond to, or how the team's contributions might evolve given strategic priorities.
- Play CEO for a day. Periodically imagine holding the top job and viewing current meetings, projects, and emails from that vantage. What value would a CEO find in the work? What would they change?
Pillar 3: Boss Comprehension -- Map Their World
To manage up effectively, a leader must understand the boss's operating context with granular precision. This is not about manipulation; it is about alignment. The essential map includes:
| Dimension | Questions to Answer |
|---|---|
| Goals | What are their organisational and personal objectives? |
| Pressures | What demands come from their peers, their own boss, and the board? |
| Working style | Do they prefer email, meetings, instant messages, or hallway conversations? |
| Strengths | Where do they excel, and where can you complement their gaps? |
| Weaknesses | What do they struggle with, and how can you shield them without overstepping? |
| Decision patterns | Do they decide quickly or deliberate? Do they want options or recommendations? |
This mapping must be refreshed continuously. A boss's priorities shift with quarterly targets, organisational restructuring, and personal circumstances. The leader who mapped their boss's world in January and stopped paying attention by March is operating on stale intelligence.
Pillar 4: Expectation Calibration -- Ask, Don't Assume
The burden of understanding what the boss expects falls on the direct report -- not the other way around. Formal systems like planning processes and performance reviews provide a skeleton, but they never capture the full picture. Expectations exist on a spectrum from broad ("what kinds of problems should I escalate?") to granular ("what format should interim project reports take?"). The leader who passively assumes they know what their boss expects is building on sand.
Two corrective habits:
- Proactive clarification: At the start of any significant project, explicitly ask what success looks like from the boss's perspective, what updates they want, and what decisions they wish to be consulted on.
- Realistic boss expectations: Accept that most managers are not mind-readers. They have competing demands and limited bandwidth. Rather than resenting what the boss fails to provide, take responsibility for articulating what is needed.
Prompts
Prompt 1 -- Boss Communication Audit:
Analyse my current communication pattern with my boss. I report to [describe role and style of your boss]. My typical update frequency is [describe]. My boss's preferred communication channels are [describe]. Identify gaps in my information flow: Am I under-reporting, over-reporting, or mismatching format to preference? Design a communication cadence that matches my boss's needs while keeping me efficient.
Prompt 2 -- Skip-Level Meeting Preparation:
I have a meeting with my boss's boss [describe their role and what you know about their priorities]. Prepare five strategic questions I can ask that demonstrate long-term thinking about the business, awareness of industry trends, and understanding of how my team's work connects to company strategy. The questions should feel natural, not performative.
Prompt 3 -- Boss Mapping Exercise:
Help me build a comprehensive profile of my boss. Here is what I know: [describe their goals, pressures, working style, strengths, and weaknesses as best you can]. Identify blind spots in my understanding and suggest specific observations or conversations that would fill them. Then recommend three adjustments to how I work with them based on this profile.
Prompt 4 -- Expectation Alignment Conversation:
I suspect my boss and I are not aligned on expectations for [describe project or role area]. Draft a conversation framework that lets me clarify their expectations without seeming uncertain or incompetent. Include specific questions to ask and phrases that signal proactive ownership rather than dependency.
Use Cases
Growth-Stage CTO Preparing for Board Visibility
A CTO at a Series B company does excellent technical work but is invisible to the board. The CEO fields all board questions about the technology roadmap. The CTO applies boss comprehension to understand the CEO's board pressures, then offers to prepare a quarterly technology brief that the CEO can present -- or, better, that the CTO can present directly. By framing this as reducing the CEO's preparation burden rather than as a personal visibility play, the CTO gains board exposure without threatening the CEO's authority. Within two quarters, board members begin directing technical questions to the CTO directly.
Early-Traction Founder Managing an Investor-Board Chair
A first-time founder treats their lead investor like a passive shareholder, sending updates only when milestones are hit. The investor grows anxious and begins making back-channel inquiries to team members. The founder recalibrates by mapping the investor's information needs: monthly updates sent on the same day, proactive flagging of risks alongside wins, and a quarterly phone call to discuss strategic direction. The investor's anxiety drops, back-channel inquiries stop, and the relationship shifts from surveillance to partnership.
Scale-Stage VP Navigating a New Boss
A VP of Product has thrived under a hands-off CEO for three years. A new CEO arrives with a detail-oriented style and expects weekly written updates. The VP initially bristles, interpreting the request as micromanagement. After applying the boss comprehension framework, the VP recognises that the new CEO is under board pressure to demonstrate operational control during a strategic pivot. The VP redesigns their reporting format to match the CEO's needs, and what felt like surveillance becomes a vehicle for demonstrating strategic alignment.
Anti-Patterns
-
Confusing managing up with managing impressions. Managing up is about alignment and effectiveness, not about curating a personal brand. The leader who manages up well solves real problems for their boss; the one who manages impressions solves only their own visibility problem. Bosses eventually distinguish between the two.
-
Waiting for the boss to create the relationship. A pervasive and costly passivity. The assumption that a good boss will proactively provide information, clarity, and development is reasonable in theory and unreliable in practice. Most managers are overwhelmed. The direct report who waits will wait a long time.
-
Treating all bosses identically. Applying the same communication style, frequency, and format to every manager is a failure of adaptation. A data-driven CFO and a relationship-driven Chief People Officer require fundamentally different upward management strategies.
-
Bypassing your boss to impress their boss. Skip-level visibility is valuable only when the direct boss supports it. Going around a manager to build relationships with senior leaders creates distrust that no amount of strategic questioning can repair.
-
Assuming expectations are static. Clarifying expectations once and never revisiting them. Priorities shift, contexts change, and what mattered in Q1 may be irrelevant by Q3. Expectation calibration is a recurring practice, not a one-time conversation.
By Stage
| Stage | Focus | Key Difference |
|---|---|---|
| Validation | Investor-as-boss management | The "boss" is often a lead investor or advisor. Information flow and expectation alignment directly affect funding continuity. |
| Early Traction | First manager relationships | Founders begin hiring leaders who report to them while they themselves report to a board. Managing in both directions simultaneously is a new skill. |
| Growth | Skip-level visibility | As layers multiply, the leader's relationship with their boss's boss becomes strategically important. Demonstrating strategic thinking to senior executives determines career trajectory. |
| Scale | Institutional upward management | Managing up becomes systemic: executive communication cadences, board reporting rhythms, and cross-functional alignment processes replace individual boss relationships. |
At every stage, the foundational principle holds: the burden of the relationship falls on the person who has the most to gain from its effectiveness -- which is almost always the direct report.
Output Template
markdown# Upward Relationship Audit: [Boss Name / Role] ## Boss Profile - **Goals (organisational):** [What they are measured on] - **Goals (personal):** [What they care about beyond metrics] - **Key pressures:** [From their boss, board, peers, or market] - **Preferred communication:** [Channel, frequency, format] - **Decision style:** [Quick vs. deliberative; options vs. recommendations] - **Strengths I can leverage:** [Where they excel] - **Gaps I can complement:** [Where they need support] ## Current Information Flow Assessment | Dimension | Current State | Ideal State | Gap | |-----------|--------------|-------------|-----| | Update frequency | [Current] | [Needed] | [Over/Under/Matched] | | Update format | [Current] | [Preferred] | [Aligned/Misaligned] | | Risk escalation | [Current pattern] | [Expected pattern] | [Gap description] | | Strategic context | [How much I provide] | [How much is needed] | [Gap description] | ## Expectation Alignment - **Confirmed expectations:** [What has been explicitly discussed] - **Assumed expectations:** [What I think they expect but have not confirmed] - **Unknown expectations:** [Areas where I have no clarity] ## 30-Day Action Plan | Week | Action | Purpose | |------|--------|---------| | 1 | [Specific action] | [Alignment, visibility, or comprehension goal] | | 2 | [Specific action] | [Alignment, visibility, or comprehension goal] | | 3 | [Specific action] | [Alignment, visibility, or comprehension goal] | | 4 | [Specific action] | [Alignment, visibility, or comprehension goal] |
Related Skills
- Trust Equation -- The trust a boss places in a direct report is decomposable into credibility, reliability, intimacy, and self-orientation; managing up is the practice of building all four deliberately.
- Radical Candor -- Upward candor -- telling a boss what they need to hear rather than what they want to hear -- is a high-risk, high-reward form of managing up.
- Giving Feedback -- Providing constructive upward feedback to a boss requires all four pillars of managing up to be functioning; without trust and comprehension, upward feedback backfires.
- Strategic Thinking and Alignment -- Strategic visibility with senior leaders is the outward expression of strategic thinking capability; the two skills are mutually reinforcing.
- Delegation and Empowerment -- Effective delegation creates the time and headspace required for upward relationship management; leaders who cannot delegate cannot manage up.
- Emotional Courage -- Delivering bad news upward and pushing back on a boss's flawed direction require the incremental courage-building practices this companion skill develops.
