Alignment failure, breakdown, whatever you want to call it… Is, I think, borderline inevitable in creative work and fields. As much as I wish there was a quick and easy solve for it, there’s just not. Part of the problem is that it’s not always easy to see when it has happened (so I tend to assume it’s always happening) which leads to the second problem - it tends to grow and compound, rather than being a clear, easy to clear up, misunderstanding or miscommunication.
What I’ve seen happen, particularly in experienced teams that are running to a perceived goal, is that as they view that work, the deliverables, and the targets through their own lens, what they’re aiming at starts to shift. To make matters worse, from a production and creative-ops perspective, that’s not all bad. I know I’d much rather the team work to solve the problems that come up during development than to just freeze up or stall.
The downside, though, is that over time, those micro pivots and seemingly small direction shifts add up and compound. And then we end up in a meeting early Friday afternoon where your designers walked through a change they’d made — and it’s a good change. Art’s response to it also made sense, because it’s what art is supposed to do when design shifts. Engineering, meanwhile, had bumped into a small constraint they’d worked around in a way that, honestly, ended up cleaner than the original spec. Every discipline had something to report, all of it was reasonable, and none of it looked worth flagging.
Yet, by Monday morning, we feel that something is off. We’re not actually building the thing we said we were going to build.
It’s not vastly different, and shifts were subtle (but additive) so those one-to-two-degree shifts in direction now have us thirty degrees off the kickoff target - enough that if we set the current state of the work next to the original commitment, the difference is clear.
And everyone who was in the meeting helped get us there - one small good decision at a time.
Drift Isn’t the Same as Misalignment
I want to be careful with the vocabulary here, because “alignment problem” gets used to mean a bunch of different things, and they don’t all need the same fix.
There’s the clarity version — people leaving the same conversation with different interpretations of what got decided. That’s a real problem, but it’s a different one, and I want to hold it for another piece.
This specific issue is drift: a team that was genuinely aligned at kickoff and then, over the course of just doing the work, ended up somewhere they didn’t agree to go. It’s a slow-burn issue paved with good intentions the entire way, with small execution decisions. Time after time. Looked at in the moment. All ended up driving the development off course.
And I don’t think this is specific to any one kind of creative work. Anywhere different disciplines are shaping the same deliverable - brand campaigns, launch creative, animated pieces, milestone builds - the same drift is available. The artifact changes; the underlying problem doesn’t.
The Dangerous Decisions Are the Reasonable Ones
If drift only happened through bad calls, it’d honestly be a much easier problem to catch. Bad calls typically create friction, so somebody flags them and pushes back, then room (or commonly a Slack thread - or six) has a conversation, and the decision gets revisited.
Drift moves through the small, reasonable decisions - the ones that don’t feel worth escalating in the first place. Each one, in isolation, is the kind of call I’d probably approve if someone asked me. The catch is that nobody’s asking, because from where they’re sitting, the call looks small enough to just make on the fly and mention later, if it comes up at all. They’re pushing hard to their goal, and making the call lets them keep their momentum.
That’s not a criticism - it’s just how cross-discipline work has to move. If every design tweak and art pass and engineering workaround needed a leader in the loop, nothing would ship. Teams have to make these calls without you all the time, and that isn’t the problem.
The problem is that individually reasonable calls, in aggregate, absolutely change what the finished thing is going to be - not in obvious ways, just… a little. And A little at a time, across a handful of disciplines, across three or four weeks, adds up to something that no longer really matches the commitment.
By Friday, the work is still coherent. It just isn’t the work you said you were building on Monday.
Status Meetings Aren’t Built for This
Status meetings are actually pretty good at what they’re designed to do. I want to be fair about that. If you run a decent one - people report what they got done, what they’re working on, what they need - and the plan you’re tracking against is roughly current, you’ll leave the meeting knowing whether the team is on track by the definition you set.
But the definition you set is exactly the thing drift changes.
Which means a drifted team will still report on track, because from where they’re sitting, they are on track. They’re on track to deliver the thing that the accumulated decisions turned the work into. They’re just not on track to deliver the thing you all agreed to at kickoff - and nobody’s actively tracking that version anymore, so nobody sees the gap.
That’s why status is basically blind to drift. It fundamentally assumes the target hasn’t moved. Drift is the target moving.
I’ve watched teams (and, sure, run teams) where three weeks of clean green status reports lined up back to back, and the milestone review was where we all figured out together that the work no longer matched the commitment. Which is a real bad place to have that conversation. Everything about a milestone review (the audience, the expectations, the goals) is set up assuming we’re going to talk about how well we hit the target. Not renegotiating what the target actually was.
What Leadership Actually Owes
The answer is less about a process fix and more about habit, and it’s uncomfortable enough that I’ve watched a lot of experienced leaders (myself included) skip it, or do it inconsistently, or do a version of it that doesn’t quite work.
It’s got to be done though. We owe it to our teams to - at some cadence, separate from status, ask a different question. Not “What did you get done this week” - we already have that answer from status. What we don’t typically probe is: “What decisions were made this week that would have been worth calling out?”
That question is uncomfortable, because on the surface it can sound like an accusation, or micromanaging. It’s not something I would likely actually vocalize. I’d use it more as a rhetorical frame when I chat with my leads. It’s a viewpoint we can use to help surface the calls that are, over time, changing what we’re all actually building.
This is not about asking anyone to escalate every decision. Just taking the time to look more deeply to notice the ones that would sound different if we all heard them for the first time now, in a kickoff meeting, rather than as one of forty little adjustments made along the way. That’s where the drift hides.
I’ll admit, I don’t have a great name for this discussion, or check-in, or whatever you want to call it. I’ve called it different things in different places, and honestly none of them have really stuck. The name isn’t the important part. The important part is that you’re working with your team to look at the work differently than pure status, and that you do this before the milestone review becomes the accidental place drift gets surfaced.
Related to this - from experience, one thing that seems small but really isn’t: You gotta capture the answers somewhere the team can find them again. Drift conversations have a way of dying inside meeting notes no one ever revisits, and then you get to have the same conversation six weeks later, at a much worse time, and it feels like you’re noticing the pattern for the first time - even though you’d actually seen it before.
What It Costs to Not Do This
The visible cost is the stuff you can measure - rework at the milestone, missed dates when the actual work has to snap back to what was committed, uncomfortable conversations with a stakeholder who’s now looking at something noticeably different from what they were pitched.
The less visible cost is trust in the plan itself, and that one is harder to catch, because you mostly notice it after it’s already gone. Teams that keep experiencing the “we’re on track… oh, wait, we aren’t” pattern don’t make a decision to stop trusting the plan. They just kind of absorb it as how things go around here. And they start protecting themselves - hedging their own commitments, treating kickoff as directional rather than binding, holding a little back so the eventual reset doesn’t hit as hard.
That’s the point at which the leadership job changes underneath you, and it’s a lot slower and harder to rebuild that trust than it was to lose it.
The Short Version
Alignment isn’t a thing you set at kickoff and verify at review. Unless you enjoy misery. It’s something you have to keep an eye on while the work is happening, because the work is going to change, and small good changes often accumulate into something no one actually agreed to.
The teams I’ve been on that handled this best weren’t the ones with the tightest status meetings. They were the ones where somebody - usually the producer, sometimes the creative lead, occasionally me on a good day - treated “what has changed about the work” as its own recurring question, separate from progress, and asked it out loud early enough that the answer was still useful.
Status will tell you whether the team is moving, but it won’t tell you where. That second question is one leadership has to keep bringing into the room deliberately, because nobody else is going to add it to the agenda for you.
Author note: I’ve spent my career leading and supporting cross-discipline creative teams, primarily in game development, with a focus on production clarity, alignment, and communication. I’m currently building AI-assisted planning tools for creative leaders who need to turn ambiguous direction into execution plans their teams can actually use. You can connect with me on LinkedIn