How often should I send written status updates to my boss?

Weekly is the modal cadence at line-manager+ tiers. The format varies — some leaders use a structured Slack post, some use a shared doc with a running log, some use an email summary. Length: 1 page typical, longer at director+ with more strategic context. Content: operational status (projects, hiring, key metrics), people decisions in flight, strategic issues for input, cross-functional issues. The discipline produces leverage when the boss can hand the status to their boss without modification — that is the test of the right level of detail and framing.

How do I handle disagreement with my boss without damaging the relationship?

Three patterns Horowitz, Lopp, and Larson all name. (1) Surface the disagreement in 1:1 first, in private. The boss should not be surprised by your disagreement in a public meeting. (2) Frame the disagreement as a question or a request for input, not as a position. 'I'm thinking about X differently — can we walk through it?' beats 'I disagree with X.' (3) Once the decision is made, support it publicly. Private disagreement continues in 1:1; public position aligns with the decision. Horowitz's 'disagree and commit' framing applies.

What if my boss is a bad manager?

An edge case Lopp's Managing Humans addresses directly. The patterns: (1) operate as if the boss were a strong manager — provide clear written status, manage up explicitly, ask for feedback proactively. The discipline doesn't depend on the boss's craft. (2) build the outside-the-company peer-leader network explicitly to compensate for what you're not getting internally. (3) name what you're missing — calibration, sponsorship, strategic context — and ask for it explicitly. (4) if all three fail and the situation is structural, plan the transition. Some bad-boss situations are recoverable; some are not.

How do I build cross-functional alignment with a strong-willed PM partner?

The structural pattern: shared written documents that surface disagreement before execution. The PRD, the engineering strategy doc, the joint OKR — all are alignment artifacts. The discipline: when the PM and engineering positions diverge, name the divergence in writing, articulate both positions with their reasoning, and either resolve in conversation or escalate to the joint boss. The failure mode: avoiding the divergence and discovering it at execution time, when the cost of resolution is much higher.

How do I tell the difference between a routine cross-functional issue and a strategic conflict?

Three diagnostic questions Larson and Horowitz both indirectly name. (1) Is the disagreement about resourcing or priority at the multi-quarter scale? Strategic. (2) Is the disagreement about specific feature scope or short-term execution? Routine. (3) Does the disagreement involve C-suite peers or only operational leaders? Strategic if the former. Routine cross-functional issues should be resolved peer-to-peer at the operational tier; strategic conflicts surface to the boss and possibly to the C-suite.

What is the right way to manage up about a hiring loss?

The pattern: surface to the boss within hours of learning the IC has accepted elsewhere. Provide the context (who, where, your read on whether a counter is appropriate, your contingency plan). Avoid the trap of waiting until the IC has formally resigned — your boss should hear it from you first, while the situation is still in flight. Larson's 'no surprises' principle applies most strongly to senior-IC departures because they have the highest cross-org impact.

How does managing up change at the director and above tier?

Becomes 60%+ of the calendar. The boss relationship at director is with a VP-Engineering or CTO; the cross-functional peer relationships are with C-suite peers (CTO, CPO, CFO). The strategic-conflict pattern Horowitz names becomes more central. The structured-memo discipline matters more because the C-suite operates on written argument. The 'no surprises' principle applies more strongly because the company-level visibility of director-level decisions is higher. Pragmatic Engineer's coverage of director-and-above schedules confirms the calendar shift.

Engineering Manager Hub

Managing Up and Cross-Functional for Engineering Managers (2026 Field Guide)

By Blake Crosley · Last verified 2026-04-30

In short

Managing up and cross-functional partnership becomes the dominant calendar item from senior-manager (M2) through director and beyond — by D1 it is 60%+ of the calendar. The canonical references: Michael Lopp's Managing Humans (chapters on managing your manager), Will Larson's lethain.com posts on managing-up at senior tiers, Ben Horowitz's The Hard Thing About Hard Things on hard conversations with bosses and politics. The most-cited principle across the literature: 'no surprises in writing.' The most-cited failure mode: silent disagreement with the boss that festers for two quarters and is then revealed at the worst possible time.

Key takeaways

Managing up and cross-functional partnership is the dominant calendar item from M2 through D1+ — by director it is 60%+ of the calendar per Pragmatic Engineer's coverage of FAANG director schedules and Larson's writing on senior-leadership work.
Lopp's Managing Humans (chapters on 'managing your manager' and 'shields up') and Larson's lethain.com posts on managing-up at senior tiers are the canonical references for the boss relationship.
Horowitz's The Hard Thing About Hard Things (chapters on hard conversations and senior-leadership politics) is the canonical reference for difficult upward conversations and cross-functional strategic conflict.
The single most-cited principle: 'no surprises in writing.' The boss should never learn about something serious in your org from someone other than you. Hiring losses, performance issues at senior-manager+ tier, cross-functional escalations, technical incidents — all surface to the boss before they surface elsewhere.
The most-cited failure mode: silent disagreement with the boss that festers for two quarters and is then revealed at a worst-possible-time moment. The prevention: surface disagreement explicitly in 1:1s and in writing. Horowitz's framing: 'tell people the truth, especially when it is hard.'
Cross-functional partnership at senior tiers is structured-and-written. The partnership conversations that produce real alignment are the ones where the engineering leader has prepared a written memo, named alternatives, and engaged the partner's perspective explicitly.
Politics at senior tiers is real. Horowitz: 'most political fights at the C-suite are about resourcing and priority; the leader who turns them into evaluable written decisions wins; the leader who turns them into personal contests loses.'

The boss relationship: the most consequential single relationship

The boss relationship is the most consequential single relationship at every tier of engineering management. At line-manager and senior-manager it is one of several important relationships; at director and above it becomes the dominant single signal channel. Misalignment with the boss produces the canonical management failure mode (slow drift over 6–12 months, then sudden replacement or role change); strong alignment produces the canonical success pattern (sustained tenure, clear strategic mandate, durable team). The mechanics drawn from Lopp's Managing Humans, Larson's lethain.com posts, Horowitz's The Hard Thing About Hard Things, and Pragmatic Engineer's coverage:

Cadence. Weekly 1:1, 30–60 minutes. Monthly career and strategic conversation that goes longer. Quarterly written status to the boss that the boss can hand to their boss without modification. The written-status discipline is the second-most-mentioned mechanic across the references (after the 1:1 itself).
Topic balance in the 1:1. The 1:1 should split across: (1) operational status (10–20%), (2) people decisions you are making and want their input on (30%), (3) strategic and cross-functional issues (30%), (4) your own development and career (10–20%), (5) calibration on their thinking and the company's direction (10–20%). The default failure mode is 1:1s that are 80% operational status — that is a misuse of the boss's calendar.
No surprises in writing. Larson's most-cited principle generalizes: the boss should never learn about something serious in your org from someone other than you. Hiring losses, performance issues at the senior-manager+ tier, cross-functional escalations, technical incidents that hit the company's external reputation. Surface-level signal goes in the weekly written status; serious signal goes by Slack or in a same-day 1:1 ping.
Ask explicitly for feedback. The manager who does not ask their boss for explicit feedback on strategic choices and people-management calls is operating without calibration. Lopp's Managing Humans is direct on this: 'your boss is your most reliable signal source about the company's actual priorities, distinct from the stated priorities.'
The pre-mortem on misalignment. If the manager and boss disagree on a major call, surface the disagreement explicitly in writing and in 1:1. Avoid the most-cited failure mode: the silent disagreement that festers for two quarters and is then revealed at the worst possible time. Horowitz's chapter on having hard conversations with your boss is the reference.

The 'no surprises' principle in operation

The 'no surprises' principle is the most-cited operational pattern in the engineering management literature on managing up. The application:

Routine surface-level signal. The weekly written status to the boss includes operational status (projects shipped, hiring progress, key metrics), people-decisions in flight, and any strategic issues that may need the boss's calibration. The written status is the boss's primary information channel between 1:1s.
Performance-issue signal. A senior-IC or line-manager performance issue surfaces to the boss before it escalates. The pattern: name the situation, name what you've tried, name what you're doing next, name what you might need from the boss. The boss is informed before the issue becomes a cross-org problem.
Hiring-loss signal. A senior IC accepting an offer elsewhere surfaces to the boss within hours, not days. The pattern: name the IC, name the destination, name your read on whether a counter-offer is appropriate, name your contingency plan if not. The boss is informed before they hear it from HR or from a peer leader.
Cross-functional escalation. A serious disagreement with a peer leader surfaces to the boss before it becomes adversarial. The pattern: name the disagreement, name the alternatives, name your recommended path, name what you need from the boss. The boss is informed before the peer leader escalates separately.
Technical incident. A production incident with external-reputation impact surfaces to the boss in real-time, not in the post-mortem. The pattern: name the incident, name the impact, name the response in flight, name the next-steps. The boss is informed before they see it on Twitter or hear it from leadership.
The discipline. The 'no surprises' principle requires the manager to actively bring information to the boss, not to wait for the boss to ask. Lopp's framing: 'your boss's job is harder when they're surprised; your job is to make their job easier with appropriate signal.'

Cross-functional partnership: the structured-and-written craft

Cross-functional partnership at senior tiers is structured-and-written. The conversations that produce real alignment are the ones where the engineering leader has prepared a written memo, named alternatives, and engaged the partner's perspective explicitly. The mechanics:

The PM partnership. The PM partner at every tier is the engineering leader's closest non-eng collaborator. At line-manager: weekly 30-min 1:1. At senior-manager: weekly 30–60-min 1:1 plus structured project-level partnership rhythm. At director+: weekly 1:1 with the senior PM peer plus structured strategic-conversation rhythm. The pattern that produces alignment: shared written documents (PRDs, engineering strategy docs, joint OKRs) that surface disagreement before execution.
The design partnership. Variable in importance by company. At Stripe and Linear (triadic culture) the design partnership is co-equal with PM and engineering. At Meta and Google (product-led culture) the design partnership is closer to a service relationship. Engineering leaders adapting across companies need to recalibrate the design partnership cadence and authority.
Peer engineering-leadership partnership. Senior-managers, M3s, and directors have peers across other engineering orgs whose work intersects theirs. The partnership produces leverage when the peers share information about hiring pipelines, technical-strategy alignment, cross-team initiative coordination. Larson's writing on lateral leadership names this directly.
Sales / customer-facing partnership (B2B). At enterprise-software companies (Stripe, Databricks, AI-labs in B2B contexts), the sales-engineering and customer-success partnership is a major calendar item. The pattern: structured customer-feedback loops, clear escalation paths, joint executive-business-review cadence with key customers.
The structured memo as the alignment artifact. Larson's writing on cross-functional alignment names the same pattern: alignment that depends on verbal-only conversations decays; alignment that depends on a shared written memo persists. The discipline: when a cross-functional partnership conversation surfaces important alignment, write the memo within 24 hours, share with the partner, refine until both agree.

Strategic conflict at senior tiers: Horowitz's framing

Strategic conflict — multi-quarter disagreements between engineering leadership and other functional leadership at the C-suite or senior-director tier — is real and consequential. Horowitz's The Hard Thing About Hard Things has multiple chapters on this. The mechanics:

The structural pattern. Most strategic conflicts at the C-suite tier are about resourcing and priority. Engineering wants more headcount; product wants more feature velocity; sales wants different-than-current product priorities; finance wants lower burn. Each function has legitimate reasoning; the conflict surfaces when the company's resources are not sufficient for all of them.
The structured-decision-memo as the resolution mechanism. Horowitz's framing: 'most political fights at the C-suite are about resourcing and priority; the leader who turns them into evaluable written decisions wins; the leader who turns them into personal contests loses.' The discipline: when a strategic conflict surfaces, write the structured memo first. Name the diagnosis, name the alternatives, name the trade-offs of each, name the recommendation. The memo becomes the conversation; verbal-only positioning loses to written argument.
The boss as the decision-maker. Strategic conflicts at the senior-director / VP level are typically resolved by the CEO or the relevant C-suite peer. The engineering leader's job is to surface the decision honestly with the alternatives evaluated, not to win the position. Once the decision is made, the engineering leader executes the decision — even if it's not the recommendation — and reports up on execution.
The post-decision discipline. Engineering leaders who continue to argue after the decision is made damage the boss relationship and the cross-functional partnership. The discipline Horowitz names: 'disagree and commit.' The decision is made; the engineering leader supports it publicly; private disagreement is voiced to the boss in 1:1, not to the team or to peers.
The escalation-pattern failure mode. Engineering leaders who escalate routine disagreements to the C-suite undermine their cross-functional partnerships and their boss relationships. The pattern: most disagreements should be resolved peer-to-peer at the senior-director tier; only the genuinely-strategic conflicts (multi-quarter, multi-million-dollar, structurally-consequential) surface to the C-suite.

Frequently asked questions

How often should I send written status updates to my boss?: Weekly is the modal cadence at line-manager+ tiers. The format varies — some leaders use a structured Slack post, some use a shared doc with a running log, some use an email summary. Length: 1 page typical, longer at director+ with more strategic context. Content: operational status (projects, hiring, key metrics), people decisions in flight, strategic issues for input, cross-functional issues. The discipline produces leverage when the boss can hand the status to their boss without modification — that is the test of the right level of detail and framing.
How do I handle disagreement with my boss without damaging the relationship?: Three patterns Horowitz, Lopp, and Larson all name. (1) Surface the disagreement in 1:1 first, in private. The boss should not be surprised by your disagreement in a public meeting. (2) Frame the disagreement as a question or a request for input, not as a position. 'I'm thinking about X differently — can we walk through it?' beats 'I disagree with X.' (3) Once the decision is made, support it publicly. Private disagreement continues in 1:1; public position aligns with the decision. Horowitz's 'disagree and commit' framing applies.
What if my boss is a bad manager?: An edge case Lopp's Managing Humans addresses directly. The patterns: (1) operate as if the boss were a strong manager — provide clear written status, manage up explicitly, ask for feedback proactively. The discipline doesn't depend on the boss's craft. (2) build the outside-the-company peer-leader network explicitly to compensate for what you're not getting internally. (3) name what you're missing — calibration, sponsorship, strategic context — and ask for it explicitly. (4) if all three fail and the situation is structural, plan the transition. Some bad-boss situations are recoverable; some are not.
How do I build cross-functional alignment with a strong-willed PM partner?: The structural pattern: shared written documents that surface disagreement before execution. The PRD, the engineering strategy doc, the joint OKR — all are alignment artifacts. The discipline: when the PM and engineering positions diverge, name the divergence in writing, articulate both positions with their reasoning, and either resolve in conversation or escalate to the joint boss. The failure mode: avoiding the divergence and discovering it at execution time, when the cost of resolution is much higher.
How do I tell the difference between a routine cross-functional issue and a strategic conflict?: Three diagnostic questions Larson and Horowitz both indirectly name. (1) Is the disagreement about resourcing or priority at the multi-quarter scale? Strategic. (2) Is the disagreement about specific feature scope or short-term execution? Routine. (3) Does the disagreement involve C-suite peers or only operational leaders? Strategic if the former. Routine cross-functional issues should be resolved peer-to-peer at the operational tier; strategic conflicts surface to the boss and possibly to the C-suite.
What is the right way to manage up about a hiring loss?: The pattern: surface to the boss within hours of learning the IC has accepted elsewhere. Provide the context (who, where, your read on whether a counter is appropriate, your contingency plan). Avoid the trap of waiting until the IC has formally resigned — your boss should hear it from you first, while the situation is still in flight. Larson's 'no surprises' principle applies most strongly to senior-IC departures because they have the highest cross-org impact.
How does managing up change at the director and above tier?: Becomes 60%+ of the calendar. The boss relationship at director is with a VP-Engineering or CTO; the cross-functional peer relationships are with C-suite peers (CTO, CPO, CFO). The strategic-conflict pattern Horowitz names becomes more central. The structured-memo discipline matters more because the C-suite operates on written argument. The 'no surprises' principle applies more strongly because the company-level visibility of director-level decisions is higher. Pragmatic Engineer's coverage of director-and-above schedules confirms the calendar shift.

Sources

About the author. Blake Crosley founded ResumeGeni and writes about engineering management, hiring technology, and ATS optimization. More writing at blakecrosley.com.