Your VP rewrote the project scope in April, championed it in the all-hands in June, and by September, when the integration failed and three teams were blocked, opened the incident review with “Help me understand what went wrong on the execution side.” You were the execution side.
This isn’t a story about a bad manager. It’s a story about a system that rewards a specific kind of leadership failure: being visible in success and invisible in failure. If you’ve worked in product management long enough, you’ve seen it more than once.
The Sunshine Manager
The sunshine manager is present, engaged, and visible when things go well. Product launch goes smoothly? They’re in the Slack thread celebrating. Stakeholder demo lands well? They’re in the room taking partial credit. Quarterly review looks positive? They’ll present the numbers themselves.
When things go wrong (a critical escalation, a stakeholder conflict, a failed release, a team member burning out) they become unreachable. Not literally, usually. They respond to messages. They join calls. But their role shifts from leading to distancing. The warmth disappears. The ownership transfers. “I’m leading this” becomes “What’s your plan to fix this?”
This isn’t cowardice in the traditional sense. Most sunshine managers don’t consciously decide to abandon their team. They simply never defined crisis support as part of their job. Success feels like leadership. Failure feels like someone else’s operations problem.
For PMs, this creates a confusing dynamic. You get positive reinforcement when you don’t need it and silence when you do. Over time, you learn to stop escalating problems, because escalation just results in the problem being handed back to you with more pressure and less support. You become self-reliant not out of strength, but out of learned helplessness.
The organizational damage follows the warmth-withdrawal cycle directly. When your team watches a leader celebrate wins publicly and then go quiet during a production incident, they learn that visibility is only safe in one direction. People stop surfacing risks early because they’ve seen what happens: the sunshine manager engages when you bring good news and deflects when you bring bad news. So the bad news stops flowing upward. Knowledge sharing drops because showing vulnerability in this dynamic gets you a meeting where you’re asked to explain your remediation plan, not one where your leader helps you build it. Risk-taking stops because failure has one-sided consequences. The team that once proposed ambitious integration approaches starts scoping everything to what they can survive alone. Innovation doesn’t stall because people lack ideas. It stalls because nobody trusts the safety net.
Why the Org Chart Makes This Worse
The sunshine manager doesn’t operate in isolation. They exist inside a structure that enables and often rewards their behavior. Understanding that structure is the first step toward protecting yourself inside it.
Role clarity decreases as you move up. A junior PM typically has a well-defined domain, clear KPIs, and known stakeholders. A Head of Product often works with a role description that could mean almost anything. A CPO’s responsibilities are frequently impossible to tell apart from those of a CTO or COO, depending on the company’s mood that quarter.
This vagueness isn’t accidental. Senior roles are left open on purpose to allow for “strategic flexibility.” But in practice, a role description broad enough to cover everything effectively covers nothing. Senior leaders can take credit for anything that succeeds and distance themselves from anything that fails, because their responsibilities were never clearly defined. The sunshine manager doesn’t even need to actively dodge accountability. The org chart does it for them.
Territorial overlap creates invisible conflicts. When two senior leaders both believe a domain belongs to them, the PM in the middle becomes the battlefield. You end up managing upward into conflicting expectations with no clear way to escalate. In these situations, the sunshine manager’s instinct to step back during conflict isn’t just a personal weakness. It’s a rational response to an ambiguous power structure where taking a clear position carries political risk.
The Accountability Split
The structural problem underneath all of this has a simple name: the split between accountability and responsibility.
When your VP changes scope three times but the delivery failure ends up on your performance review, you’re experiencing this split in real time. Healthy organizations align these two things. The person with authority to make the call also owns the outcome when it goes wrong. Dysfunctional ones push authority upward and responsibility downward.
This is especially harmful in regulated environments, where decisions have compliance consequences. If your VP overrules a risk assessment but the audit finding lands on your desk, you’re not just dealing with bad management. You’re absorbing institutional liability.
The warning sign isn’t the failure itself. It’s who speaks first in the post-mortem. If your leadership opens with explanations about downstream execution problems, the accountability structure is broken.
What Actually Works
The sunshine manager is a structural problem, and structural problems need structural solutions. Here’s what moves the needle.
Agree on crisis roles while things are still going well. The sunshine manager disappears during a crisis because crisis support was never part of the deal. Make it part of the deal while the sun is still shining. During planning: “If this integration fails, I’ll need you to handle the VP-level escalation on their side. Can we agree on that now?” Get the commitment documented while they’re in a generous mood. When the crisis hits, you’re not asking for help. You’re calling in a specific agreement.
This works because it removes the decision from the moment of stress. The sunshine manager doesn’t have to choose between stepping up and stepping back. They already committed. Most people honor explicit commitments, especially documented ones, far more reliably than implicit expectations.
Keep a decision log that names names. Not a meeting summary. A running document that captures three things: what was decided, who made the call, and what we agreed would happen if it went wrong. Share it after every important decision meeting.
Most people won’t object to accurate notes in the moment. But when things fall apart months later, the log is the difference between “we all decided this together” and a clear record of who actually made the call. In regulated industries, this isn’t just smart politics. It’s your compliance paper trail.
Make the accountability split visible without making it personal. If you’re in a position to give feedback (skip-levels, 360 reviews, retrospectives), describe the structural problem rather than the individual. “We lack a clear escalation path when stakeholder priorities conflict” produces more change than “My manager avoids hard decisions.” One is a system problem that can be solved. The other is a character judgment that will be defended.
Test the safety net before you need it. Don’t wait for a real crisis to find out whether your manager will show up. Escalate something medium-sized early. A minor stakeholder conflict, a small scope disagreement, a resource question that needs senior input. Watch what happens. If they engage, you have a baseline to build on. If they deflect, you have the information you need to adjust your strategy before the stakes are high.
When the system won’t change, plan your exit on your own terms. If the patterns are built into the organization, if sunshine management is rewarded, if accountability is permanently disconnected from authority, then you’re not failing to manage up. You’re in the wrong system. The smart move is to document what you’ve learned, build case studies from the dysfunction (without burning bridges), and leave before the system teaches you its habits.
The most dangerous outcome isn’t that you can’t change your manager. It’s that you stay long enough to stop noticing the problem.
The Uncomfortable Truth
Product management frameworks assume functional leadership. Stakeholder management advice assumes stakeholders act rationally. Escalation models assume someone at the top will catch what falls.
Real organizations are messier than that. The leaders above you are sometimes the constraint, not the enabler. And the hardest version of that constraint isn’t the openly incompetent manager. It’s the one who stands next to you in the sunshine and is nowhere to be found in the rain.
Recognizing that isn’t cynicism. It’s a requirement for doing effective work in imperfect conditions. And it’s stakeholder management at its most honest.