You start your day feeling aligned. You show up, your team shows up. The goals are on the dashboard, the projects are in Confluence, the documentation in Notion, the meetings are happening. And yet, something is still off.
Alignment is one of those things that everyone assumes they have, until the results say otherwise. Most teams do believe they're aligned. They're not. Here are three tell-tale signs your team is not aligned.
You know this one when you see it. Everyone seems busy, working at something. They're at their desks, in meetings. Lots of requests put into other teams, lots of conversations, agenda items, emails, checklist items being checked off. But actual output is difficult to find or measure. It's almost as if time is endlessly spent in "planning" mode, but no one is truly executing at the same level, with the same intensity. There's not much measurable progress, but everyone is busy or overwhelmed.
That's because the motion isn't action — it's avoidance. People on the team don't know who the actual decision makers are — or the decision makers on paper aren't the ones who truly call the shots. So action stalls and swirls around de facto decision makers who stay in pre-action mode because a) it makes them feel powerful and b) they won't pull the trigger because they don't want to be accountable. And the true decision makers don't pull the trigger either because the autonomy to decide was silently stripped away from them — why put your name on something you never agreed to do?
The team didn't understand who owns decisions. So no one really moves. Movement feels like progress. But nothing is shipping.
This one's harder to catch because it looks like high performance. Things ARE happening. Cool things. Things getting internal and external applause. Fast-moving teams, smart people, shipping constantly. From the outside - and to themselves - it looks like exactly what a healthy team should be doing. But the KPIs - the things that truly reflect success —-they ain't budging.
Here's what's actually going on. These are usually companies with a lot of smart, driven people who like to do things their way and are really proud of their work. The ultimate goal may be clear (increase developer app usage by 20% quarter over quarter) but the direction is fuzzy. Each team's corresponding objectives are vague, don't exist, or just haven't been mapped back to how they'll impact that 20% growth. So teams go off and just ship stuff. How are each team's tactics going to help drive that 20%? How will they work together cross-functionally? How will they measure? What are the expectations? The protocols? Nonexistent.
And why? Because overconfidence produces a lack of foresight. These teams skip the alignment step because they assume they already understand. They don't slow down to map how what they're building connects to the target. They execute against their own ideas without pausing to understand first. And then they keep going.
They didn't understand how their work connects to the target. So they move in the wrong direction. Building anything feels like progress. But nothing is moving the needle.
This one is probably the least apparent. On the surface, everything looks fine. Teams are working. Things are happening. But they're not happening together.
Here's a common version of this. One of a company's quarterly targets is to drive customer engagement up by 50%. Cross-team leaders never really discussed how each of their teams would coordinate efforts to hit that target, or what the operational metrics and KPIs are that ladder up to it. The team with the word "Customer" in it becomes the assumed responsible team. So other teams keep doing what they do - not realizing that driving customer engagement may also require the efforts of the product team, the engineering team, the marketing and sales teams. Or they know they'd need help, but the other teams don't see it and de-prioritize any initiatives to support them because they have too much on their plates already. Each team is focused on their own team-specific KPIs and objectives, completely overlooking how their own objectives map back to the company's objectives.
The OKRs that came out of that goal were made to look good on paper. But the "how" was never defined - never translated into coordinated action. So teams defaulted to their norms. Focused on what they needed to do. Threw things over the fence and wiped their hands clean of their contribution and their accountability. Their contribution checked. Their accountability? Gone.
They didn't understand how the goal is shared. So they moved in parallel without ever converging. Doing what we know how to do feels like progress. But no one is sharing the weight.
In each scenario, things probably looked aligned. In their documents, from their meetings, on paper. But in reality, other things - invisible things - were steering the company. A resistance, or an innate deviation, from the work of actually understanding first.
Because alignment isn't a process step you do once. It's a practice you incorporate throughout your work. It's evidence that understanding happened. You can't align on something you don't fully understand. And when you skip understanding - whether because you're paralyzed by accountability, or overconfident in what you already know, or just too heads-down in your own lane - you will build something that eventually falls short or falls apart. Even one person who skips understanding to build will eventually build something that fails.
These teams thought they were aligned. They weren't. Not because they didn't try. But because they didn't understand first.
Alignment requires seeing how things are actually operating - not how they're supposed to operate, not how they look on paper, but what's actually running underneath. Every org has an operating system. Most teams have never seen theirs. That's usually where the real answer lives.
Because true progress only occurs when targets are reached. Everything else is an illusion.