Use What Works on Meltdowns to Handle Your Manager

What each one is actually for

Collaborative Problem Solving

Collaborative Problem Solving is for the moment a child's behavior looks like defiance or a meltdown but is actually a signal that a specific situation, a particular transition, a particular demand, exceeds a skill the child doesn't yet reliably have. Rather than assuming the child is choosing to misbehave, the adult works through three concrete steps: first, empathize, asking the child directly what's hard about the situation and genuinely listening without proposing a solution yet, which is the step that actually surfaces the unsolved problem; second, share the adult's own concern about the situation plainly, so the child understands why it matters; and third, brainstorm together until landing on a solution both people find realistic and are actually willing to try. The method rests on the idea that a behavior which looks like misbehavior is usually a mistaken strategy aimed at a real, legitimate need, not an expression of badness, and that naming the actual unsolved problem is what lets a solution stick where punishment or reward alone hasn't.

Managing Up

Managing up is for the ordinary gap between what a manager needs to support you well and what they actually notice on their own, which is usually a lot less than it should be, because most managers are stretched across several people's work and simply don't have the bandwidth to reliably track everyone's blockers, wins, and needs unprompted. The practice means actively figuring out how a specific manager prefers to receive information, a quick written update versus a scheduled conversation, high-level summary versus detail, and volunteering status, obstacles, and needs before being asked, framed in terms that connect to what your manager is actually accountable for rather than only your own concerns. It's a deliberate shift from waiting to be noticed to actively shaping how your work gets seen and supported, on the theory that most managers respond well to being made easier to help you, and poorly to being expected to guess.

What you get out of pairing them

A child's difficult behavior often has a specific, fixable driver, a transition that's genuinely hard for them in a way that isn't visible from outside, and naming that driver out loud is what lets an adult build a solution that actually addresses it, instead of a punishment or reward that only suppresses today's version of the same problem and leaves tomorrow's version fully intact. A manager's unhelpful-seeming behavior, a canceled meeting, vague feedback, has a comparable hidden driver more often than it looks like from the outside, usually their own overload or a communication style you haven't yet adapted to, and figuring that out puts you in a position to actually get what you need instead of quietly resenting a situation you never tried to change.

What Collaborative Problem Solving rests on

• Externalizing makes pattern visible randomised trials
  Putting an internal pattern into an external, structured form makes it visible and available for examination instead of remaining implicit and merely enacted.
• Parts have positive intent clinical practice
  A behavior that looks like misbehavior is usually a mistaken strategy aimed at meeting a legitimate underlying need rather than an expression of badness itself.
• Collaborative solution generation increases buy in observational studies
  Jointly generating a solution with the person who has the problem produces more durable follow-through than an imposed solution.

What Managing Up rests on

• Perspective taking expands frame randomised trials
  Deliberately adopting a vantage point other than one's own default view widens the range of interpretations or options available for a situation.
• Adapting to anothers style improves collaboration observational studies
  Matching communication frequency and format to a manager's stated preferences produces smoother collaboration than expecting them to adapt to yours.
• Proactive disclosure builds trust observational studies
  Volunteering relevant information and progress updates before being asked builds a manager's trust and reduces their need to monitor closely.

Where they actually meet

Both practices replace an adversarial default with an investigative one, aimed at what's actually driving behavior rather than what it looks like from the outside. Collaborative Problem Solving assumes a child's outburst signals a real, specific unsolved problem rather than a character flaw, treating even difficult behavior as a mistaken strategy aimed at meeting a legitimate need. Managing up assumes a manager's frustrating behavior, curt messages, a canceled check-in, seemingly arbitrary shifts in priority, more often reflects their own pressures and constraints than genuine indifference, and takes the same step of deliberately imagining their situation before reacting to the surface of it. Different relationships, same underlying refusal to take a difficult behavior at face value.

The principle underneath both

A difficult interaction usually has a real, specific reason behind it that isn't visible from the outside, and taking the extra step to surface that reason, by asking directly, listening carefully, or deliberately imagining the other person's situation, produces a workable path forward that simply reacting to the visible behavior never does.

What that makes the real goal

Understand the actual situation driving someone's behavior, from their seat rather than yours, before responding to it, so the response addresses the real cause instead of the visible surface of it.

Other practices that serve the same goal

Nonviolent Communication, developed by Marshall Rosenberg, teaches the practice of guessing at the unmet need behind another person's words before responding to the words themselves, a close structural parallel with clinical and observational support behind its broader framework. Motivational Interviewing, widely used in behavior-change and addiction treatment, is built around meeting apparent resistance with curiosity rather than confrontation, on the assumption that resistance usually signals ambivalence or a hidden concern rather than simple opposition, and it carries a substantial randomized-trial evidence base. The fundamental attribution error, a well-studied finding in social psychology describing people's tendency to explain others' behavior by character rather than circumstance, names the exact failure mode both of these practices are built to counteract, with a large experimental literature behind the bias itself.

A tradition that already does this

The instruction to "assume positive intent," adopted as an explicit workplace norm at a number of organizations over the past two decades, already applied Collaborative Problem Solving's core stance, that difficult behavior usually has a legitimate reason behind it, to adult workplace relationships specifically, independent of and before this page's pairing of the two.

Naming Your Manager's Unsolved Problem Before Reacting to Them

When a manager repeatedly cancels your one-on-ones or gives feedback that stays frustratingly vague, the easy read is that they don't care about your growth. Run a version of Collaborative Problem Solving's first step on that situation instead. Treat it as a real, nameable unsolved problem the same way you'd treat a child's struggle with a specific transition, is their calendar genuinely overloaded, do they find giving direct feedback uncomfortable, is there a skill gap in how they manage rather than a gap in how much they care. Then, in your next interaction, do the second and third steps: share your own concern plainly, I want to make sure I'm getting your input on this project, and propose a concrete, low-friction alternative, a fifteen-minute version of the meeting, or a written update instead of a live one, the way Collaborative Problem Solving moves from empathizing to sharing concern to building a solution together, aimed sideways at a manager instead of downward at a child.

Adapting the Conversation's Format the Way You'd Adapt to a Manager

Managing up's core move, figuring out how someone actually prefers to receive information and adapting to it rather than expecting them to adapt to you, applies directly to how a Collaborative Problem Solving conversation itself gets run with a child. Some kids answer the empathy step's questions more honestly sitting side by side doing something with their hands, walking, drawing, building with blocks, than seated face to face being asked directly, the same way some managers respond far better to a short written update than to a scheduled meeting. Matching the format of the conversation to how a specific child actually communicates, rather than defaulting to the format that's easiest for the adult to run, tends to produce real information in the empathy step instead of a shrugged I don't know, the same payoff managing up gets from matching a manager's preferred format instead of your own default.

The same week, a bedtime meltdown and a ghosted status update

Your eight-year-old melts down every night at the screens-off-for-dinner transition, and separately your manager has stopped responding to your written status updates entirely. This week you try both moves at once. With your kid, instead of announcing five more minutes and bracing for the fight, you sit down beside them mid-game, not across from them, and ask, genuinely curious, what's hard about stopping right at that moment, and it turns out they hate leaving a round unfinished, a specific, fixable problem, not defiance, so you agree together that transitions happen at the end of a round rather than at a fixed clock time. At work, instead of another status document that goes unread, you notice your manager only ever replies fast to short Slack messages, so you send your update that way instead, and get a reply within ten minutes for the first time in weeks.

When this is worth reaching for

You are already running Collaborative Problem Solving with a child at home and are separately navigating a manager whose behavior reads as unsupportive or hard to reach. The moment that matters is right before a difficult behavior, a meltdown, a canceled meeting, would normally get responded to reactively rather than investigated first.

Where this does not apply

Collaborative Problem Solving assumes an unsolved problem that's genuinely workable through a joint conversation, and it isn't built for situations involving safety risk to the child or someone else, where an adult needs to intervene directly and immediately rather than run a full empathize-share-brainstorm conversation in the moment. And managing up has a real ceiling: if a manager's behavior reflects a genuine values or competence problem rather than a preference or bandwidth issue, adapting your own communication style indefinitely won't fix what actually needs fixing, and treating it as something you just need to adapt to can mean tolerating a situation that actually needed to be escalated or exited.

What the evidence does and does not support

Collaborative Problem Solving's core components, externalizing a difficult pattern into something jointly examined, and treating hard behavior as a mistaken strategy rather than defiance, carry real controlled-trial and clinical support inside child-behavior treatment research. Managing up's claims come from workplace-effectiveness writing and observational practice rather than controlled studies, and while adapting to a manager's communication style and disclosing proactively are widely reported to help, neither has been isolated and tested the way structured child interventions have. Running Collaborative Problem Solving's specific three-step structure on a manager relationship, or importing managing-up's style-matching into a child conversation, is what this page is proposing as a transfer between two separately evidenced practices, not a combination either literature has actually measured.