Managing up

Managing Up: Building the Relationship That Earns Autonomy

This skill addresses the relationship between a Director-level demand gen or RevOps leader and the person they report to: a CEO, CRO, VP of Marketing, or other executive. The goal is not to manage around the manager. The goal is to build enough trust and communication quality that the manager stops needing to manage closely, because they have confidence in what is happening and what will happen.

Most friction in the upward relationship is a communication problem, not a competence problem. The manager micromanages because they are uncertain. They change priorities because they do not trust that the current priorities are right. They get pulled into details because they have not seen evidence that the details are being handled. Fixing the communication often fixes the relationship.

This skill does not assume the manager is right and the practitioner is wrong. Sometimes the directive is genuinely bad. Sometimes the manager does not understand the function well enough to evaluate the program. This skill addresses both situations: how to work effectively with a good manager and how to professionally push back on a bad directive.

---

HOW TO SET UP THIS SKILL

Provide:

• Who you report to: CEO, CRO, VP of Marketing, or other
• How long the relationship has existed
• The specific friction or challenge: micromanagement, changing priorities, disagreement on strategy, lack of autonomy, or something else
• Whether this is a new relationship you want to start well, or an existing relationship you need to repair or improve
• What you have already tried

---

Diagnosing the Type of Upward Friction

---

Type 1: The manager who does not understand the function

A CEO or CRO who came up through sales often does not have a practitioner's understanding of demand gen or RevOps. They know what they want the function to produce (pipeline, revenue, data clarity) but not how it works. This produces friction when they give directives that are technically wrong, question decisions that are correct, or set expectations that are disconnected from how long things actually take.

The signal: the manager asks questions that reveal a fundamental misunderstanding of how the work is done. They expect immediate results from programs that take months to compound. They question attribution methodology without understanding why it is complex.

The approach: do not correct them in a way that makes them feel uninformed. Educate through outcomes and process transparency, not through explaining how marketing works. When a CEO asks why a campaign is not producing leads yet, the answer is not "ABM programs take 90 days to produce results." The answer is "here is what we have set in motion, here is what we are seeing at the early indicators, and here is when I expect to have pipeline data to share with you."

The goal is to move the manager from evaluating whether the approach is right to evaluating whether the milestones are being hit. That is a conversation they can participate in productively regardless of their functional knowledge.

---

Type 2: The micromanager

A manager who is involved in every decision, who asks to be copied on every communication, and who questions decisions that are clearly within your authority is managing out of uncertainty, not out of malice. They do not yet have evidence that they can trust you to handle things correctly.

The signal: they ask to be included in conversations you should own, review work that is at your level to approve, and want frequent updates on things that do not require their input.

The approach: give them what they are looking for before they ask for it. A weekly update that proactively covers what is happening, what decisions were made, and what is coming next reduces the anxiety that produces micromanagement. If they know what is happening before they have to ask, they stop asking.

Simultaneously, start expanding your decision-making sphere by making small decisions confidently and reporting on them afterward. Not asking for permission and then reporting what happened builds the pattern that you own your domain. Asking for permission on everything reinforces the pattern that they should be in every decision.

The timeline for shifting a micromanager: 60 to 90 days of consistent, proactive communication and confident execution. This is not fast. It cannot be accelerated. Trust is built through pattern, not through a single conversation.

---

Type 3: The manager who changes priorities frequently

A CEO who pivots strategy quarterly or a CRO who adds new initiatives every month creates a situation where nothing gets finished and everything feels urgent. This is often a leadership maturity problem at the company level, not a problem the Director can solve. But there are ways to manage within it.

The signal: you receive new directives before previous ones are complete. You are constantly starting things that do not have defined outcomes. You feel like you are running fast and producing nothing.

The approach: create a documented priority stack and require explicit prioritization decisions when new work is added. When a new initiative arrives, respond with: "I can move on this. To make space for it, I would need to deprioritize one of these three things. Which one should come off the list?" This forces the manager to make the trade-off rather than adding to your plate without removing anything.

Document every priority decision in writing. Not to create a paper trail for political protection, but because people forget what they agreed to deprioritize. A short follow-up email that says "following our conversation, I am reprioritizing X in favor of Y" creates shared accountability without being adversarial.

---

Type 4: Disagreement with a specific directive

A manager gives a directive you believe is wrong. It may be wrong on the facts, wrong for the business, or wrong for your function. How you handle this disagreement determines whether you build credibility or lose it.

The sequence matters:

First: understand the directive fully before disagreeing with it. Ask one or two clarifying questions to make sure you understand the reasoning, not to buy time but because sometimes the directive makes sense once you understand the context you did not have.

Second: state your disagreement once, clearly, with your reasoning. Not in a meeting with others present. In a one-on-one or a direct conversation. "I want to make sure I raise this before we move forward — I have a concern about this approach. Here is what I am seeing and why I think it might not get us where we want to go."

Third: propose your alternative. The disagreement is only useful if you have a better idea. A concern without a recommendation is just resistance. "What I would suggest instead is X because it addresses the same goal through a path that has fewer risks."

Fourth: if the manager hears your perspective and still wants to proceed, execute the directive professionally. You are not required to agree with every decision. You are required to execute the decisions that are made. The exception is if the directive is unethical or illegal, which is a different situation entirely.

The failure mode: pushing back repeatedly after the decision has been made. One clear statement of disagreement builds credibility. Continued resistance after the decision signals that you cannot execute decisions you disagree with, which is a Director-level liability.

---

The Update Structure That Prevents Micromanagement

The most effective tool for managing up is a consistent, brief, predictable update that gives the manager everything they need to feel informed without requiring them to ask.

Send this weekly, on the same day, in the same format. The format:

This week: Three to five bullet points on what happened, stated as outcomes, not activities. Not "ran three ABM campaigns" but "ABM campaigns against the named account list generated 12 new opportunities this week, six of which are with accounts that had no prior engagement."

Decisions made: One to three decisions you made this week, stated briefly. This builds the pattern that you are making decisions within your authority. If the manager disagrees with a decision, they will say so. If they do not say anything, that is implicit approval of your decision-making authority.

Coming next week: What you expect to happen and what you will be focused on. This gives the manager a preview they can react to if they see a problem coming.

One thing I need from you: Optional, but when you do need something, state it explicitly rather than burying it in a longer update. One specific ask is easier to respond to than a vague request for guidance.

This update takes ten minutes to write. It is more valuable to the relationship than any other single investment of time.

---

Building Credibility to Earn Autonomy

Autonomy is not asked for. It is earned through a pattern of good judgment and reliable execution that makes the manager comfortable with not being in every decision.

The three things that build this credibility faster than anything else:

Correct predictions: When you say a program will produce X by a certain date, and it does, you build prediction credibility. Make specific commitments and deliver on them. Under-promise when uncertain. Over-deliver when possible. Never miss a self-imposed deadline without flagging it in advance.

Surfacing problems before they surface to the manager: If something is going wrong, tell the manager before they find out from someone else. Deliver bad news with a plan attached. "Our paid pipeline is down 30 percent versus last month. Here is why and here is what I am doing about it" is significantly better than the manager discovering the number in a report and asking what happened.

Having an opinion on things outside your function: A Director who only talks about their own function is a functional operator. A Director who understands the business context and offers informed perspective on adjacent decisions is a business partner. The manager will pull a business partner into more decisions and give them more latitude on the ones they own.

---

Deliver the Managing Up Plan

Output in this format:

MANAGING UP PLAN
Reports to: [title and relationship type]
Friction type: [one of the four types, or combination]
Relationship status: [new / established / damaged]
Built: [today's date]

SITUATION ASSESSMENT
[What is driving the friction based on what the user described.
Be direct. If the manager is behaving reasonably given what they
know, say so. If the manager has a genuine problem that is not
fixable through the practitioner's behavior, say that too.]

THE IMMEDIATE CHANGE TO MAKE
[The single most impactful behavioral change the user can make
in the next two weeks. Specific, not generic.]

THE WEEKLY UPDATE STRUCTURE
[A template for the weekly update formatted for this specific
relationship and communication style of the manager as described]

THE DISAGREEMENT CURRENTLY ON THE TABLE
[If the user has described a specific disagreement, the exact
language to use when raising it once, and the alternative to
propose. If no specific disagreement, skip this section.]

HOW LONG THIS TAKES
[An honest assessment of the timeline for this type of friction
to improve given what has been described. Do not promise fast
results when the situation requires sustained effort.]

WHAT WILL NOT WORK
[The thing the user is probably considering that will make the
situation worse. Named directly.]

---

Output Rules

• Do not assume the manager is wrong. Diagnose the type of friction before prescribing the approach. Sometimes the manager is behaving entirely reasonably and the practitioner needs to adjust their behavior, not the relationship.
• Do not recommend going over the manager's head. That is almost never the right answer for the upward relationship. It is the right answer for ethics and legal violations and almost nothing else.
• Be honest about timelines. Trust-building takes 60 to 90 days of consistent behavior. Do not imply it can be resolved in a single conversation.
• The "what will not work" section must be specific to this situation. Not generic advice. The one thing this user is probably tempted to do that will make things worse.
• No em dashes. Use commas or periods.