It’s mid-December, and you know what that means: everyone is simultaneously checked out mentally while also panicking about Q4 deliverables, your Slack is full of messages that say “quick question” followed by paragraphs of anxiety, and someone just announced another reorganization that will be “fully implemented” by January 2nd. (Spoiler: it won’t be.)
Welcome to December in tech, where the chaos is the only constant and your job as an organizational change manager is to somehow make sense of it all.
Here’s the thing that no one tells you about change management: it’s not actually about managing change. Change is going to happen whether you manage it or not. Your job is to manage the narrative around change so that people understand why it’s happening, what it means for them, and how they’re supposed to show up differently starting January.
And the narrative you create in December? That’s what determines whether your organization enters 2026 energized and aligned or exhausted and cynical.
So let’s talk about how to close this year with a story that actually resonates, because I’m tired of watching talented change managers get crushed between executive “vision” that sounds like it came from a corporate buzzword generator and employees who just want someone to be honest about what’s actually happening.
The December Storyline Problem
Every December, the same pattern plays out in tech organizations:
Executives spend November in offsite strategy sessions where they decide on new priorities, new structures, new “strategic initiatives” that are going to define next year. They emerge excited, aligned, and ready to transform the organization.
Then they hand this vision to you, the change manager, and say “make everyone understand why this matters and get them excited about it.” Oh, and by the way, we’re announcing it December 20th, everyone needs to be onboard by January 6th, and we don’t have budget for any real change management activities. Good luck!
Meanwhile, the actual employees in your organization are tired. They’ve spent a year executing on this year’s priorities, which may or may not have been last year’s priorities rebranded. They’ve survived layoffs or at least layoff rumors. They’ve watched colleagues leave for better opportunities. They’re skeptical of grand announcements, and they’re really skeptical when those announcements come in late December.
Your job is to bridge that gap. And you can’t do it with a deck full of inspiring quotes and a vision statement that says absolutely nothing specific.
What Makes a Storyline Actually Compelling
Here’s what most executives get wrong about organizational narrative: they think compelling means aspirational and vague. “We’re going to be the industry leader in innovative solutions that empower our customers to achieve transformational outcomes.”
Cool. What does that actually mean for the engineer who’s debugging production issues at 2am? What does it mean for the product manager who’s trying to figure out whether to prioritize feature A or feature B? What does it mean for the team that just got told their entire project is being sunset?
A compelling storyline isn’t inspirational nonsense. It’s honest context plus clear direction plus respect for what people have already been through.
Let me break that down:
Honest context means you acknowledge reality. If this is the third reorganization in two years, you name that. If people are exhausted, you name that. If the market has changed and we need to change with it, you explain specifically how and why. Don’t gaslight people by pretending everything has been great and this is just “exciting growth.” People aren’t stupid. They know when they’re being managed.
Clear direction means you get specific about what’s changing and what’s not. Not “we’re shifting our focus to strategic priorities” but “we’re sunsetting these three product lines, doubling down on these two, and here’s exactly how that affects headcount, roadmap, and team structure.” Ambiguity breeds anxiety. Clarity breeds trust, even when the news isn’t what people wanted to hear.
Respect for what people have been through means you acknowledge the cost of change. Change management often focuses so much on the future state that it glosses over the fact that getting there is hard, exhausting work. People need to hear that their effort is seen and valued, not just that there’s more effort required ahead.
Building the Narrative Arc for 2025-2026
When I’m working on the December storyline for an organization, I structure it as an actual story arc, because humans are hardwired to understand narrative structure. We need a beginning, middle, and end. We need tension and resolution. We need characters we care about (hint: the characters are your employees).
Act One: Where We Were
This is where you acknowledge the reality of 2025. Not a sanitized highlight reel, but an honest assessment. What were we trying to do? What worked? What didn’t? What changed externally that we had to respond to?
I literally use language like “Remember when we started 2025 thinking X was our biggest priority? We learned that actually Y was the real challenge, and here’s how we responded.”
This section is critical because it validates people’s experience. If they felt like this year was chaotic, don’t tell them it was actually perfectly executed. Tell them why it felt chaotic and what you learned from that.
Act Two: Where We Are
This is the bridge. What’s the current state? Not aspirationally, but actually. What’s working that we want to keep? What’s not working that we need to change? What new information do we have about market, competition, technology, or customer needs that’s shaping our path forward?
This is where you introduce the tension that drives the story forward. “We’ve built incredible technology, but our go-to-market motion isn’t scaling. We have amazing talent, but our structure is creating silos that slow us down. We’re profitable, but we’re not positioned for the growth we need.”
Be specific. Use real examples that people will recognize. Don’t hide behind corporate speak.
Act Three: Where We’re Going and Why It Matters
This is where you introduce the change. But here’s the key: you frame it as a logical response to everything you just laid out in Acts One and Two. The change isn’t arbitrary. It’s not executives being bored and wanting to reshuffle the org chart. It’s a specific response to specific challenges and opportunities.
“Given that we learned X about our market and Y about our execution challenges, we’re making these specific changes: Z1, Z2, and Z3. Here’s what success looks like. Here’s how we’ll know we’re on track. Here’s what this means for you.”
And then, this is the part that most change managers skip: “Here’s what this is going to require from all of us. It’s going to be hard. You’re going to have to learn new ways of working. Some of you are going to have new roles or new teams. It’s going to be uncomfortable before it gets better.”
Don’t sugarcoat the transition. People respect honesty more than false optimism.
The “Why” That Actually Answers Employee Questions
When you’re crafting your December storyline, you need to answer the questions people are actually asking (even if they’re not asking them out loud):
“Why now?”
Don’t just say “the time is right.” Explain what changed that makes this the right moment. Is it market conditions? Competitive pressure? New technology capabilities? A specific insight from customer research? Be concrete.
“Why this specific approach?”
Employees are smart enough to know there are always multiple ways to solve a problem. If you’re doing a reorganization, why this structure instead of another? If you’re changing processes, why this process? You don’t have to justify every decision, but you should be able to articulate the reasoning.
“What does this mean for me specifically?”
This is where so many change narratives fall apart. They talk about organizational transformation in abstract terms without ever getting specific about what changes for individuals. You need to be able to say “if you’re an engineer on team X, here’s what changes for you” or “if you’re a manager, here’s what we need from you differently.”
“What if I don’t agree with this direction?”
Most change management approaches pretend everyone is going to enthusiastically support every decision. That’s fantasy. Acknowledge that some people might disagree with the direction, might wish resources were allocated differently, might be disappointed about how this affects their project or team. And then be clear: disagreement is fine, but we’re moving forward anyway, and here’s what constructive disagreement looks like versus destructive resistance.
“What happens if this doesn’t work?”
I love asking executives this question because it makes them deeply uncomfortable. But it’s a question employees are definitely thinking. You don’t have to have a perfect answer, but you should be able to say something like “we’re going to measure these specific indicators, review progress at these intervals, and be willing to course-correct if the data tells us we need to.”
Navigating the Politics of the December Narrative
Let’s be real: as a woman in organizational change management, you’re often in an impossible position. You’re expected to sell a vision that executives created without your input. You’re expected to make people feel heard while ultimately telling them they don’t get a vote. You’re expected to be both empathetic and tough, both transparent and diplomatic.
And if the change goes poorly? You’ll get blamed for not managing it well. If it goes well? The executives will get credit for their brilliant strategy.
I know. It’s infuriating.
But here’s what I’ve learned about navigating this: your power is in the narrative itself. When you control the story, you control how people make sense of the change. And that gives you more influence than you might think.
When the executive vision is vague or contradictory: I go back and ask clarifying questions until I get specificity. “When you say we’re focusing on customer experience, do you mean we’re reallocating engineering resources from feature development to reliability? Are we changing our quality metrics? What specific trade-offs are we making?” Don’t accept buzzwords. Push for concrete answers.
When the rationale doesn’t make sense: I play devil’s advocate in the room with executives before the messaging goes out. “Here’s what people are going to ask when they hear this. Here’s where the logic breaks down. Here’s what will feel like doublespeak.” Better to surface this before the announcement than after.
When the change is genuinely bad: This is the hardest one. Sometimes the change is short-sighted, poorly thought out, or actively harmful. You have three choices: try to influence it to be less bad, quit, or decide that you can still help employees navigate it even if you don’t agree with it. There’s no right answer here. Just know your own boundaries.
The Communication Cascade That Actually Works
The December storyline isn’t just one announcement. It’s a communication cascade that carries you from mid-December through January.
Mid-December: The Executive Announcement
This is where leadership shares the high-level vision and strategy. It should be honest, specific, and acknowledge both the opportunities and the challenges ahead. I always push for these to include Q&A time where leaders answer actual hard questions, not just softballs.
Late December: The Manager Enablement
Before managers communicate anything to their teams, they need to be enabled. I run sessions where I walk through the narrative, answer their questions, give them scripts and FAQs, and help them think through how this lands with their specific teams. Managers are your force multipliers. If they don’t understand it or don’t believe it, you’re sunk.
Early January: The Team Conversations
This is where managers cascade the message to their teams with team-specific context. Not just “here’s what leadership said” but “here’s what this means for our team specifically, here’s what’s changing in our day-to-day, here’s what I need from each of you.”
Mid-January: The Follow-Up and Course Correction
By mid-January, you’ll have learned what’s landing and what’s not. Do another round of communication that addresses the questions and concerns that surfaced. Adjust the narrative if you need to. Show that you’re listening and responsive.
Measuring Whether Your Storyline Worked
You can’t manage what you don’t measure, and that includes narrative effectiveness. Here’s what I track:
Qualitative feedback from managers: After they do their team cascades, I ask: What questions came up? What concerns did people raise? What didn’t make sense?
Employee survey data: I run a pulse survey in mid-January asking: Do you understand the direction for 2026? Do you know how your work connects to organizational priorities? Do you feel like leadership is being honest about challenges ahead?
Behavioral indicators: Are people showing up to town halls and asking questions, or are they checked out? Are they leaning into the new direction, or quietly continuing to do things the old way?
Executive feedback: Are executives hearing the same concerns bubbling up, or different ones? Are they surprised by employee reaction, or did the narrative prepare them for it?
The goal isn’t perfect alignment. Perfect alignment is a fantasy. The goal is informed, constructive engagement.
The Pep Talk You Need
Listen, I know December is exhausting. You’re managing other people’s anxiety while dealing with your own. You’re trying to spin straw into gold and make a mediocre strategy sound compelling. You’re probably underpaid and definitely underappreciated.
But here’s the thing: the work you do matters. When organizations go through change, people look for sense-making. They look for someone who can help them understand what’s happening and why. That’s you.
You’re not just writing communications and planning town halls. You’re shaping how people experience transformation. You’re building trust or eroding it. You’re creating clarity or confusion.
Do it well. Do it honestly. Do it in a way that respects people’s intelligence and honors their experience.
And when you get to January and someone inevitably says “that was the smoothest reorg we’ve ever had,” even though it wasn’t actually smooth at all, you’ll know it’s because you created a narrative that made the chaos feel purposeful.
That’s the power of a good December storyline.
