Cory Berg
Roadmap: Day 2 of 7 · Managing up, down, and across

How managing up, down, and across should work
(and where it breaks)

Most leadership breakdowns don't start with bad decisions. They start before the decision is ever made.

The hidden pressure point

They start in the relationships surrounding it.

Managing up, down, and across is not a "soft skill."
It is the system that determines:

  • what information you see
  • how safe people feel telling you the truth
  • how decisions propagate
  • where pressure accumulates

When this system is weak, even good decisions collapse on impact.

How managing up, down, and across is supposed to work

At its core, this system has one job:

Move reality through the organization without distortion.

That requires three things to be true at the same time:

  • information flows upward without fear
  • decisions flow downward without confusion
  • coordination happens sideways without politics

When those conditions exist, leadership feels almost boring.

When they don't, everything becomes harder than it should be.

Managing up (how it should work)

Managing up is not flattery.
It is not obedience.
It is not "keeping your boss happy."

It is about reducing uncertainty for the people above you.

That means:

  • making tradeoffs visible
  • surfacing risk early
  • translating execution details into business impact
  • being predictable in how and when you communicate

Strong leaders don't surprise their managers.
They give them time to think.

Where managing up breaks

1. Filtering bad news

Under pressure, leaders soften reality.

They wait.
They reframe.
They "don't want to bother."

By the time the issue surfaces, it's no longer a decision.
It's a crisis.

2. Confusing loyalty with silence

Loyalty becomes:

  • not pushing back
  • not disagreeing publicly
  • not naming uncomfortable truths

This feels respectful.
It actually creates blind spots.

Strong managing up includes principled dissent.

3. Overloading with detail

Some leaders respond to pressure by dumping information upward.

They explain everything.

This doesn't create confidence.
It creates noise.

Executives need clarity, not exhaust logs.

Managing down (how it should work)

Managing down is not about control.

It's about creating conditions where people can make good decisions without you.

That requires:

  • clear intent
  • clear boundaries
  • consistent expectations
  • psychological safety to surface problems early

When managing down works, teams don't wait for permission.
They move with judgment.

Where managing down breaks

1. Ambiguity disguised as autonomy

Leaders say:

  • "Use your judgment"
  • "I trust you"
  • "You're empowered"

But they haven't:

  • clarified priorities
  • defined success
  • explained tradeoffs

Under pressure, people freeze or guess.

2. Micromanagement under stress

When things go wrong, leaders revert.

They:

  • step into decisions
  • rewrite work
  • override judgment

The message becomes clear:

You're trusted until it matters.

That erodes confidence quickly.

3. Inconsistent reactions

The same issue gets different responses on different days.

Sometimes it's fine.
Sometimes it's a problem.

This unpredictability trains the team to manage you, not the work.

Managing across (how it should work)

Managing across is the least discussed and most fragile part of leadership.

There is no authority.
Only influence.

Managing across works when:

  • incentives are understood
  • constraints are respected
  • commitments are explicit
  • conflicts are surfaced early

It fails when assumptions replace agreements.

Where managing across breaks

1. Unspoken expectations

Teams assume alignment that doesn't exist.

Deadlines, ownership, and priorities are "understood" but never stated.

Under pressure, those assumptions collide.

2. Avoiding conflict to preserve harmony

Leaders delay hard conversations to "keep things smooth."

Tension doesn't disappear.
It goes underground.

When it resurfaces, it's sharper and more personal.

3. Escalation as a substitute for coordination

Instead of resolving issues directly, leaders escalate.

This feels efficient.
It damages trust.

Escalation should be a last resort, not a workflow.

Why pressure breaks this system

Pressure activates fear:

  • fear of looking incompetent
  • fear of conflict
  • fear of blame
  • fear of being seen as "difficult"

When fear enters the system:

  • information gets filtered
  • intent gets obscured
  • trust erodes
  • decisions slow down or explode

In hierarchical systems, information reliably degrades as it moves upward and sideways, especially when people fear consequences.

People don't act badly.
They act defensively.

The key takeaway

Managing up, down, and across is a system, not a set of behaviors.

If it only works when everyone feels safe and unpressured, it's not a system.
It's a fair-weather arrangement.

Reflection

Think about a recent situation where things felt harder than they should have.

Which direction broke down first?

  • up
  • down
  • across

What information was missing?
What truth was softened?
What conversation was delayed?

Don't fix it yet.

Just notice where pressure distorted the flow.

Up next

Day 3: How communication should work - and why it stops landing under pressure.

References

  • Janis, I. L. (1982). Groupthink. Houghton Mifflin.
    (Fear-driven information suppression)
  • Edmondson, A. (2018). The Fearless Organization. Wiley.
    (Psychological safety and information flow)
  • Tourish, D., & Robson, P. (2006). “Sensemaking and the distortion of information.” Journal of Management Studies, 43(4), 711–730.
    https://doi.org/10.1111/j.1467-6486.2006.00608.x