# Managing Up Operating System Pack

---

## 1) Context Snapshot

**Role / scope:** Senior PM, recently started. Reporting directly to VP of Product.

**Org / team context:** VP manages 8 PMs. Large PM org with a VP who has broad span of control and high context-switching load. 3 weeks into the current quarterly roadmap.

**Top priorities (4-8 weeks):**
- Execute the current quarterly roadmap without unnecessary pivots
- Establish a trusted, predictable working relationship with VP
- Build a communication system that reduces surprise priority changes
- Earn enough credibility and trust to push back constructively on pivots

**What "better managing up" means:**
- **Clarity:** Know how the VP makes priority decisions so I can anticipate and influence them
- **Autonomy:** Reduce frequency of mid-quarter pivots by surfacing trade-offs early
- **Speed:** Get faster, more durable decisions on roadmap priorities
- **Boundaries:** Push back on priority changes constructively without damaging the relationship

**Constraints:**
- New to the role (limited relationship capital)
- VP has 8 direct reports (limited attention bandwidth)
- Already 3 weeks into a quarterly roadmap (urgency to stabilize)
- Two pivot suggestions already made (pattern may continue)

**Assumptions:**
- VP has a standing 1:1 cadence (assumed weekly, 30 min)
- Organization uses standard async tools (Slack/email, docs)
- VP's pivot suggestions are driven by external signals (exec pressure, market data, customer escalations) rather than arbitrary preference
- No HR/legal/safety concerns in this relationship

**Unknowns / questions:**
- What specifically triggered each of the two pivot suggestions? (External signal? Exec pressure? Customer escalation? New data?)
- Does the VP have a pattern of pivoting early in the quarter and then stabilizing?
- How do the other 7 PMs handle this pattern? Are some more successful than others?
- What does the VP consider a "good quarter" for a PM on her team?
- Does the VP have a preferred format for updates (written, verbal, slides)?

---

## 2) Manager Profile: "How My VP Works"

### What she optimizes for
- **Responsiveness to new signals:** She values being seen as adaptive and market-responsive. Changing priorities is likely how she demonstrates strategic agility to her leadership.
- **Breadth over depth:** Managing 8 PMs means she cannot go deep on any single PM's roadmap. She needs fast, skimmable context to make calls.
- **Optionality:** Frequent pivot suggestions indicate she wants to keep options open rather than committing irrevocably early in a quarter.

### Pressures / incentives (what she is judged on)
- Quarterly business outcomes across 8 product areas
- Likely receiving pressure from C-suite or board on shifting market conditions
- Needs to show her leadership that the product org is responsive, not stuck on a plan that no longer fits
- Managing 8 PMs means she is spread thin -- she rewards PMs who reduce her cognitive load

### Decision style
- **Fast, intuition-led, revisable.** She makes directional calls quickly and expects to course-correct. This is not indecisiveness -- it is an iterative style. But without guardrails, it creates whiplash for the team.
- She likely values a PM who brings her a structured trade-off rather than asking "what should I do?"

### Risk tolerance
- **Medium-high.** Willing to pivot mid-quarter (high tolerance for change), but likely risk-averse about being blindsided by a miss she did not see coming (low tolerance for surprises).

### Preferred communication (hypothesis -- validate in 1:1)
- **Skimmable async updates** over long meetings (she has 8 reports; meeting time is scarce)
- **Decisions framed as options** rather than open-ended discussions
- **Early warning on risks** rather than optimistic status reports
- Likely prefers Slack or short docs over long emails

### What she wants pulled up vs. handled by me
| Pull up to VP | Handle at my level |
|---|---|
| Priority conflicts that affect quarterly commitments | Day-to-day execution and sprint-level decisions |
| Cross-team dependencies she can unblock | Stakeholder coordination within my domain |
| Risks that could miss a quarterly target | Mitigations I can execute without her |
| Decisions that require budget or headcount | Technical trade-offs within approved scope |
| Customer escalations that reach exec level | Feature scoping and design decisions |

### Common failure modes in our relationship (predicted)
1. **Priority whiplash:** She suggests a pivot; I either comply silently (losing roadmap progress) or push back without data (seeming inflexible).
2. **Information vacuum:** She does not have enough context on my roadmap trade-offs, so she fills the vacuum with her own signals and assumptions.
3. **Reactive relationship:** I wait for her to set direction instead of proactively framing trade-offs, which puts me in a passive position.

### What I will do differently (3 commitments)
1. **Proactively surface trade-offs before she asks.** Every time I hear a pivot signal, I will respond within 24 hours with a structured trade-off memo (not a "no," but a "here is what we gain and lose").
2. **Send a weekly async update optimized for her bandwidth.** Skimmable, under 2 minutes to read, with explicit asks and decisions separated from status.
3. **Validate this profile in our next 1:1.** I will ask 3-4 calibration questions (below) to test my assumptions and adjust.

### Validation questions (for next 1:1)
- "When you think about our org's success this quarter, what are the top 2-3 things you are optimizing for?"
- "When I hear about a potential priority change, how would you like me to bring that back to you -- options and trade-offs first, or do you want to talk it through live?"
- "What kinds of decisions do you want me to escalate vs. handle on my own?"
- "What does a good weekly update look like for you -- format, detail level, timing?"

---

## 3) Upward Communication Cadence: "What Goes Where" Map

### Channel architecture

| Channel | Purpose | Frequency | Format | Response expectation |
|---|---|---|---|---|
| **Async weekly update** (Slack/email) | Progress vs. plan, risks, decisions needed, asks | Every Monday by 10am | Written (template below) | No response required unless flagged |
| **1:1** (30 min) | Priorities, alignment, coaching, relationship, decisions that need discussion | Weekly (existing cadence) | Shared agenda doc, pre-filled by me 24h in advance | Real-time discussion |
| **Trade-off memo** (doc) | Major priority changes, resource conflicts, strategic pivots | As needed (expect 1-2x/month) | 1-page doc (template below) | Decision needed by stated date |
| **Urgent escalation** (Slack DM) | Time-critical risks, customer crises, blocked decisions | As needed | Short message with: what happened, impact, what I need from you, by when | Same-day response |

### What does NOT go in the 1:1
- Pure status updates (these go in the weekly async update)
- FYI items that require no discussion (these go in the weekly update or Slack)
- Detailed technical trade-offs (these go in a doc, linked from the 1:1 agenda if discussion is needed)

### What does NOT go in the weekly update
- Requests for coaching or career feedback (save for 1:1)
- Sensitive interpersonal issues (1:1 or separate conversation)
- Decisions that need real-time discussion (1:1 agenda item)

### Design rationale (optimized for a context-switching exec)
This cadence is designed for a VP managing 8 PMs who context-switches constantly:
- **Monday async update** means she starts the week with a snapshot of all 8 PMs (if they all adopt a similar cadence), without needing 8 separate conversations
- **Pre-filled 1:1 agenda** means she walks in prepared; no time wasted on "so, what's going on?"
- **Trade-off memos** give her a structured way to evaluate pivot suggestions against the current plan -- they slow down reactive pivots just enough to be deliberate
- **Urgent escalation via DM** is reserved for true urgency, which protects the signal-to-noise ratio

---

## 4) Weekly Async Update Template (Exec-Ready)

Optimized for a VP who manages 8 PMs and context-switches frequently. Target read time: under 90 seconds.

---

**Subject:** Weekly update -- [Project/Area] -- Week of [YYYY-MM-DD]

### TL;DR (3 bullets max)
- [Headline: biggest win or most important thing to know]
- [Headline: biggest risk or change from last week]
- [Headline: decision or ask, if any]

### Progress vs. plan
| Initiative | Status | Notes |
|---|---|---|
| [Initiative 1] | On track / At risk / Blocked | [1-line context] |
| [Initiative 2] | On track / At risk / Blocked | [1-line context] |
| [Initiative 3] | On track / At risk / Blocked | [1-line context] |

### Decisions needed (if any)
- **Decision:** [One sentence framing the decision]
  - **Options:** A) [option] / B) [option]
  - **My recommendation:** [A or B] because [one sentence]
  - **Needed by:** [date]

### Risks / blockers
- **Risk:** [description]
  - **Impact if unmitigated:** [what happens]
  - **My mitigation plan:** [what I am doing]
  - **What I need from you (if anything):** [specific ask]

### Asks (leader leverage)
- **Ask:** [specific, actionable request]
  - **Action needed:** [what you need the VP to do]
  - **By when:** [date]

### Trade-offs / context
- [Why results look the way they do. Explicit trade-offs made this week. Connect to quarterly goals.]

**No response required unless:** you disagree with a recommendation above, see a risk I am missing, or want to go deeper on any item.

---

### Example: Filled-in weekly update (Week 1 of pilot)

**Subject:** Weekly update -- Search & Discovery -- Week of 2026-03-16

### TL;DR
- Search relevance v2 shipped to 10% of users; early metrics positive (+4% conversion)
- VP suggested pivoting to AI-powered recommendations; I have prepared a trade-off memo (linked below)
- No decisions needed this week; one ask (unblock design review)

### Progress vs. plan
| Initiative | Status | Notes |
|---|---|---|
| Search relevance v2 (10% rollout) | On track | Shipped Monday. Monitoring through Friday. Full rollout decision next week. |
| Personalization engine scoping | On track | PRD draft complete. Eng review Thursday. |
| AI recommendations pivot (proposed) | Evaluating | Trade-off memo drafted. Linked below for your review. |

### Decisions needed
- None this week. Trade-off memo on AI recommendations pivot is ready for discussion in Thursday 1:1 if you want to review before then.

### Risks / blockers
- **Risk:** Design team is at capacity; personalization engine UX review may slip 1 week.
  - **Impact if unmitigated:** Delays eng kickoff by 1 week; still within quarterly timeline.
  - **My mitigation plan:** Exploring whether we can use an existing pattern library to reduce design load.
  - **What I need from you:** If the slip is unacceptable, I may need you to reprioritize design resources (will confirm by Wednesday).

### Asks
- **Ask:** Unblock design review for personalization engine.
  - **Action needed:** Confirm with Design Lead that this is a priority for her team this sprint.
  - **By when:** Wednesday 3/18.

### Trade-offs / context
- The two pivot suggestions in the last 3 weeks have created some uncertainty on the team about which initiatives are committed vs. exploratory. I have drafted a simple "committed / exploratory / parked" framework (linked in 1:1 agenda) to help us align.

**No response required unless:** you disagree with the search rollout plan, see a risk I am missing, or want to discuss the AI recommendations pivot before Thursday.

---

## 5) Decision / Trade-Off Memo Template (for Priority Pivots)

This is the key artifact for managing frequent priority changes. When the VP suggests a pivot, respond within 24 hours with this memo instead of saying "yes" or "no."

---

**Title:** Trade-off memo -- [Proposed Change] -- [Date]

**Decision needed (one sentence):**
Should we pivot from [current initiative] to [proposed initiative], and if so, what do we deprioritize to make room?

**Decision owner:** [VP name]
**Input from:** [Your name], [other stakeholders]
**Decision needed by:** [date -- propose a specific date to prevent indefinite ambiguity]

### Recommendation
[Your recommendation in 2-3 sentences. Lead with the recommendation, then explain why.]

### Context: what changed and why this is on the table
- [What signal triggered this pivot suggestion? Customer feedback? Exec input? Competitive move? New data?]
- [Why now? What is the cost of waiting vs. acting immediately?]

### Options

**Option A: Stay the course (current roadmap)**
- **What we ship:** [current initiatives and timeline]
- **Pros:** Momentum preserved; team stability; committed metrics stay on track
- **Cons:** May miss the window on [new opportunity]
- **Risks:** [specific risks of staying the course]
- **Quarterly impact:** [what happens to our quarterly goals]

**Option B: Full pivot to [new initiative]**
- **What we ship:** [new initiative and realistic timeline]
- **Pros:** [benefits of the pivot]
- **Cons:** [current initiative] stops; [X weeks] of work is paused or lost; team context-switching cost
- **Risks:** [specific risks -- timeline uncertainty on new initiative, team morale, sunk cost]
- **Quarterly impact:** [what happens to our quarterly goals]

**Option C: Parallel exploration (hybrid)**
- **What we ship:** [current initiative continues at reduced pace] + [new initiative scoped to a spike/proof-of-concept]
- **Pros:** Preserves current momentum while testing the new direction
- **Cons:** Neither initiative gets full resources; slower progress on both
- **Risks:** Team is stretched; quality may suffer
- **Quarterly impact:** [what happens to our quarterly goals]

### Explicit trade-offs
- If we choose A (stay the course), we accept: [what we are giving up or risking]
- If we choose B (full pivot), we accept: [what we are giving up or risking]
- If we choose C (hybrid), we accept: [what we are giving up or risking]

### Dependencies / stakeholders
- **Aligned:** [who has been consulted and agrees]
- **Not yet aligned:** [who needs to weigh in before we commit]

### Next steps once decided
1. [Specific action 1 with owner and date]
2. [Specific action 2 with owner and date]
3. [Communication plan: who needs to know and how we announce]

---

### Why this memo works for a priority-changing VP

This memo is designed to constructively slow down reactive pivots by:
1. **Making the trade-off visible.** The VP can see what is gained AND what is lost. This prevents "free pivot" thinking where new ideas feel costless.
2. **Offering a hybrid option.** Option C gives the VP a way to explore the new direction without abandoning the current plan. This satisfies the "responsiveness" instinct without causing whiplash.
3. **Setting a decision deadline.** Ambiguity is the enemy. The memo forces a decision by a specific date, which prevents the team from operating in limbo.
4. **Framing as partnership, not pushback.** The memo does not say "no." It says "here are the options and my recommendation -- you decide."

---

## 6) Escalation Triggers + Ask Ladder

### Escalation triggers (when to pull in the VP)

| Trigger | Example | Escalation channel |
|---|---|---|
| **Priority conflict** | VP suggests a pivot that conflicts with committed quarterly goals | Trade-off memo + 1:1 discussion |
| **Timeline risk > 1 week** | A dependency slip threatens to push a launch past the quarterly deadline | Weekly update (risk section) + Slack DM if urgent |
| **Cross-team dependency blocked > 3 days** | Another team has not delivered an API I need and their PM is unresponsive | Slack DM with specific ask: "Can you message [PM name] or their manager?" |
| **Resource conflict** | Design or eng capacity is pulled to another PM's project without discussion | 1:1 agenda item with trade-off framing |
| **Repeated pivot suggestion (3rd time)** | VP suggests a third pivot in the same quarter | Trade-off memo that aggregates the cumulative cost of pivots |
| **Customer/brand risk** | A customer escalation that could affect retention or public perception | Immediate Slack DM + written summary within 2 hours |

### Ask ladder (from lightweight to heavyweight)

**Level 1 -- FYI:**
"No action needed. Keeping you in the loop: [one sentence context]. I will handle this."

**Level 2 -- Nudge:**
"I plan to proceed with [approach]. If you disagree, please let me know by [date]. Otherwise I will move forward."

**Level 3 -- Unblock:**
"I am blocked on [specific thing]. I need you to [specific action, e.g., message the Design Lead, approve the budget, confirm the priority]. Can you do this by [date]?"

**Level 4 -- Sponsor:**
"This initiative needs visible leadership support to succeed. Can you [send a message to X team / mention this in the leadership meeting / confirm priority to Y person] by [date]?"

**Level 5 -- Decision:**
"I need you to choose between A and B by [date]. My recommendation is A because [reason]. Trade-off memo attached."

### Leader leverage map (specific to this VP)

| What I need | What the VP can uniquely do | How I will ask |
|---|---|---|
| Priority stability | Commit to a "committed / exploratory / parked" framework for the quarter | Trade-off memo + 1:1 proposal |
| Design resources | Reprioritize design capacity across her 8 PMs | Level 3 (Unblock) ask with specific timeline |
| Cross-team unblocking | Message peer VPs or their PMs directly | Level 3 (Unblock) ask with specific person and action |
| Strategic air cover | Signal to execs that our current roadmap is the right bet | Level 4 (Sponsor) ask before QBR or leadership review |
| Decision durability | Confirm that a decision is final (not revisited next week) | Explicitly ask in 1:1: "Can I treat this as committed for the quarter?" |

---

## 7) Working Agreement + Boundary Scripts

### What I will do consistently

| Commitment | Cadence | Details |
|---|---|---|
| Send weekly async update | Every Monday by 10am | Using the template above; no response required unless flagged |
| Pre-fill 1:1 agenda | 24 hours before our 1:1 | Top 3 items, decisions needed, and any trade-off memos to review |
| Respond to pivot suggestions with a trade-off memo | Within 24 hours | Structured options + recommendation, not a yes/no |
| Escalate risks early | As soon as I see a 1-week+ slip | Via weekly update risk section or Slack DM if urgent |
| Share a monthly "state of the roadmap" snapshot | First Monday of each month | 1-page view of committed / exploratory / parked initiatives |

### What I need from you (propose in 1:1)

| Need | Why it matters | Proposed agreement |
|---|---|---|
| Decision turnaround within 48 hours on trade-off memos | Ambiguity causes team to stall or work on wrong thing | If no response in 48h, I proceed with my recommendation |
| Pivot suggestions come with context | Helps me evaluate urgency and write a better trade-off memo | When suggesting a change, share the signal that triggered it (customer data, exec input, competitive intel) |
| Priority framework | Prevents whiplash and protects team morale | Adopt a simple "committed / exploratory / parked" classification for quarterly initiatives |
| Feedback on my updates | So I can calibrate the right level of detail | Quick thumbs-up or "too much/too little" once a month |

### Boundary scripts (for priority-change situations)

**When the VP suggests a pivot mid-sprint:**
"I want to make sure we evaluate this well. Let me put together a trade-off memo by tomorrow showing what we gain, what we lose, and a hybrid option. Can we make a call in our Thursday 1:1?"

**When the VP suggests a second pivot before the first one is resolved:**
"We have two potential pivots on the table now. Before we add a third track, can we close the decision on the first one? I will send a combined trade-off memo so we can stack-rank all three options."

**When urgency is inflated ("we need to do this NOW"):**
"I hear the urgency. To move on this immediately, we need to drop or delay something. Here are the top 3 things on the team's plate right now -- which one should we deprioritize? I can have a trade-off memo to you in 2 hours."

**When scope creeps on top of an existing commitment:**
"Adding this to the current sprint means we either push the launch date or cut scope on [feature]. Which trade-off do you prefer? I can model both options."

**When asked to present something with insufficient prep time:**
"I can present a rough version by [date] or a polished version by [later date]. Which serves the audience better? If rough is fine, I will flag what is still in-progress."

---

## 8) Influence / Seat-at-the-Table Plan (30 Days)

### Strategic goal
Within 30 days, shift from being seen as "new PM executing a roadmap" to "PM who thinks at the portfolio level and helps the VP make better priority decisions."

### Target forums (1-2)
1. **Weekly product leadership meeting** (VP + PM leads) -- Goal: get invited or get read-in on outcomes so I can contribute asynchronously.
2. **Quarterly business review (QBR)** -- Goal: contribute a section or a supporting analysis for my area.

### Weekly strategic contribution (recurring)
- Every week, include one "strategic observation" in my weekly update: a market signal, a customer insight, or a cross-product connection that is relevant beyond my immediate area.
- Frame it as: "Something I noticed that might be relevant to the broader portfolio: [insight]."

### Pre-wire loop
- **Before each 1:1:** If I have a strong POV on a decision, share a 2-sentence preview via Slack so the VP is not surprised in the meeting.
- **Before leadership meetings:** If I have context that is relevant to an agenda item, send a short note to the VP: "For the [topic] discussion, here is a data point from my area that might be useful: [insight]."
- **Before QBR:** Offer to prepare a 1-page analysis for my product area. Ask: "Would it be helpful if I drafted a summary of [my area] performance and trade-offs for the QBR?"

### Artifacts I will share
| Artifact | Cadence | Purpose |
|---|---|---|
| Weekly async update | Weekly | Demonstrate structured thinking and reliability |
| Trade-off memos | As needed | Show business-level judgment on priority decisions |
| 1-page POV note | Biweekly | Proactively contribute strategic perspective beyond my area |
| QBR contribution | Quarterly | Demonstrate readiness for broader scope |

### Success signals after 30 days
- VP asks for my input on decisions outside my immediate area
- VP forwards my trade-off memos or updates to her peers as examples
- I am invited to (or read into) leadership discussions earlier in the decision process
- Frequency of reactive pivot suggestions decreases because the VP has better context from my updates
- VP explicitly confirms the "committed / exploratory / parked" framework (or an equivalent)

---

## 9) Four-Week Pilot Cadence

### Week 1: Foundation (March 17-21)
**Theme: Establish the system and validate assumptions**

| Action | When | Deliverable |
|---|---|---|
| Send first weekly async update | Monday | Filled-in weekly update (use example above as starting point) |
| Validate manager profile in 1:1 | 1:1 meeting | Ask the 4 validation questions; update the profile based on answers |
| Propose working agreement | 1:1 meeting | Share "What I will do / What I need from you" and get explicit feedback |
| Propose "committed / exploratory / parked" framework | 1:1 meeting | Simple 1-page view of current roadmap classified by commitment level |
| Observe and document | All week | Note how VP responds to your update, what she focuses on in 1:1, what signals she shares |

**Week 1 success criteria:** VP has seen the first weekly update. Manager profile is validated or corrected. Working agreement is discussed (even if not yet finalized).

### Week 2: First trade-off test (March 24-28)
**Theme: Use the system under real conditions**

| Action | When | Deliverable |
|---|---|---|
| Send second weekly update | Monday | Incorporate any format feedback from Week 1 |
| Prepare a trade-off memo (proactive) | Mid-week | Even if no new pivot is suggested, draft a memo on the most likely upcoming decision |
| Pre-wire before 1:1 | Day before 1:1 | Send a 2-sentence Slack preview of your top 1:1 agenda item |
| Practice one "ask" from the ask ladder | 1:1 or async | Use Level 2 (Nudge) or Level 3 (Unblock) on a real issue |

**Week 2 success criteria:** VP has received two updates with no negative feedback. You have used the trade-off memo format at least once. You have made one explicit ask.

### Week 3: Calibrate and adjust (March 31 - April 4)
**Theme: Refine based on what is working**

| Action | When | Deliverable |
|---|---|---|
| Send third weekly update | Monday | Adjust detail level, tone, or format based on VP's behavior (did she read it? reference it? ignore it?) |
| Share first "strategic observation" | In weekly update | One insight relevant beyond your immediate area |
| Test a boundary script | When appropriate | Next time a priority change comes up, use the trade-off memo response pattern |
| Solicit feedback | 1:1 meeting | "How are the weekly updates working for you? Too much, too little, just right?" |

**Week 3 success criteria:** VP has engaged with at least one update (replied, referenced it, or discussed it in 1:1). You have used a boundary script or trade-off memo in response to a real priority discussion. You have initial feedback on update format.

### Week 4: Retrospective and lock in (April 7-11)
**Theme: Evaluate the pilot and commit to the operating system**

| Action | When | Deliverable |
|---|---|---|
| Send fourth weekly update | Monday | Refined format based on 3 weeks of data |
| Run a self-retrospective | Mid-week | Use retro prompts (below) |
| Propose ongoing cadence to VP | 1:1 meeting | "Here is what I plan to continue. Any adjustments?" |
| Update manager profile | End of week | Revise based on 4 weeks of observation |
| Draft month-2 influence plan | End of week | Based on what forums and artifacts gained traction |

**Week 4 success criteria:** Operating system is running smoothly. VP has confirmed (explicitly or implicitly) that the cadence works. You have data on what is working and what to adjust.

### Retrospective prompts (end of Week 4)
- Where did we still get surprised? (Were there priority changes that the system did not catch early enough?)
- Which updates were too noisy or too thin? (Calibrate the signal-to-noise ratio.)
- Where did escalation happen too late? (Adjust triggers.)
- Did we get faster decisions? More autonomy? Better alignment? (Measure against the original goals.)
- What is the VP's default reaction to trade-off memos? (Engaged and decisive? Defers? Ignores? Adjust the format.)
- How often did I use a boundary script? How did it land? (Refine language if needed.)

---

## 10) Risks / Open Questions / Next Steps

### Risks

| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| VP does not engage with weekly updates (too busy, wrong format) | Medium | System fails to reduce surprises; pivots continue | Ask for format feedback in Week 1 1:1. If no engagement by Week 2, switch to a shorter format (3 bullets max) or shift to verbal check-ins. |
| VP perceives trade-off memos as "pushback" or "slowing things down" | Medium | Relationship damage; loss of trust early in tenure | Frame memos explicitly as "helping you make the best call" not "here is why you are wrong." Lead with the recommendation. Pre-wire the concept in Week 1. |
| Other PMs do not use similar systems; VP finds your approach unusual | Low | VP may not value the structure or may feel you are high-maintenance | Observe how peers communicate. Adapt your system to fit the team norm while keeping the core elements (trade-off memos, explicit asks). |
| Pivot frequency is driven by VP's boss (not the VP herself) | Medium | Your system addresses the wrong level; the real decision-maker is above your VP | Ask in 1:1: "When priority changes come up, where is the signal coming from?" If it is from above, adjust your memos to include data the VP can use to push back upward. |
| New relationship means limited trust capital for boundary-setting | High | VP may interpret early boundary scripts as resistance from a new hire | Start with low-stakes boundaries (format preferences, meeting prep). Save higher-stakes pushback (rejecting a pivot) for Week 2-3 after trust is established. |

### Open questions
1. What specifically triggered each of the two pivot suggestions so far? Understanding the source helps predict and preempt future ones.
2. Does the VP have an explicit quarterly planning process, or is the roadmap treated as a living document that changes continuously?
3. How do the other 7 PMs handle this pattern? Is there a PM on the team who is especially effective at managing up with this VP? (Learn from them.)
4. What is the VP's relationship with her boss? Is she under pressure to show agility, or is she genuinely seeing new signals?
5. Is there a product leadership meeting or other forum where priority decisions are discussed? Can I get access or a read-out?

### Next steps

| Action | Owner | Due |
|---|---|---|
| Validate manager profile in next 1:1 (ask 4 calibration questions) | You | This week's 1:1 |
| Send first weekly async update using the template | You | Monday, March 17 |
| Propose working agreement and "committed / exploratory / parked" framework | You | This week's 1:1 |
| Investigate what triggered the two pivot suggestions | You | Before next 1:1 |
| Prepare a proactive trade-off memo on the most likely upcoming pivot | You | By end of Week 2 |
| Run Week 4 retrospective and decide whether to continue, adjust, or expand the system | You | April 7-11 |

---

## Quality Gate: Self-Assessment

### Checklist (all must pass)

- [x] Includes a clear **goal** for managing up and a 4-week success definition
- [x] Includes a **manager profile** with actionable implications (not generic traits)
- [x] Includes a **comms cadence** and "what goes where" map (async / 1:1 / memo / escalation)
- [x] Includes an **exec-ready weekly update** template (skimmable + "no response required" default)
- [x] Includes a **decision/trade-off memo** template for major calls
- [x] Includes an **escalation + ask plan** (triggers + ask ladder + leader actions)
- [x] Includes a **working agreement + boundary script** (respectful, outcome-based)
- [x] Includes an **influence plan** (30-day loop, pre-wiring, forums)
- [x] Includes **Risks / Open questions / Next steps**

### Rubric scores (self-assessed)

| Dimension | Score | Rationale |
|---|---|---|
| Goal clarity + boundaries | 5/5 | Measurable 4-week goals defined; clear "when not to use" from skill; constraints and assumptions explicit |
| Manager profile usefulness | 4/5 | Decision style and comms preferences captured with 3 explicit behavior changes; validation questions drafted; profile is hypothesis-based (new relationship) so scored 4 not 5 pending validation |
| Communication system quality | 5/5 | Clear "what goes where" map; skimmable weekly update with example; decision memo with explicit usage guidance for priority pivots |
| Escalation + ask effectiveness | 5/5 | Triggered escalation plan with specific examples; 5-level ask ladder; leader leverage map with specific VP actions; all asks are time-bounded |
| Boundaries + influence plan | 5/5 | Boundary scripts are outcome-framed and specific to the priority-change pattern; 30-day influence plan with pre-wiring, forums, artifacts, and success signals |
| **Total** | **24/25** | Exceeds threshold of 20/25; no category below 3 |