What Nike and Apple Can Teach Us About Cross-Functional Alignment

The Problem Nobody Wants to Admit

Most companies don’t have a strategy problem. They have a coordination problem dressed up as one.

The roadmap is ambitious. The talent is there. The budget got approved. And yet, somehow, the product ships late, the campaign misses the moment, and the customer experience feelsstitched together by people who never talked to each other. Sound familiar?

Cross-functional alignment the ability to get marketing, product, engineering, design, legal, and finance moving in the same direction at the same time is one of the most underrated drivers of business performance. It rarely shows up on earnings calls. It doesn’t make for clean case studies. But the companies that crack it tend to produce work that feels impossible to compete with. And two of the most instructive examples aren’t tech startups or management consulting darlings. They’re Nike and Apple.

Nike: When the Story Owns the Room

Nike’s internal culture is, by design, story-driven. Not in the vague “we believe in storytelling” way that fills too many corporate decks, but in a structural, operational sense. At Nike, the narrative of a campaign what it means, who it’s for, what emotion it needs to carry gets established before the silos start pulling in separate directions.

The “Just Do It” campaign didn’t stay coherent across three decades because of a style guide. It stayed coherent because the emotional brief became load-bearing. Designers, athletes and partnerships teams, retail merchandisers, and digital product teams all oriented around the same north star feeling rather than the same set of KPIs. The metrics varied by function. The meaning didn’t.

This is a subtle but critical distinction. Most cross-functional efforts try to align people on outputs shared dashboards, OKRs that cascade, weekly syncs. Nike essentially aligned people on a shared emotional contract first, then let each function execute against that contract in its own language. The result is that a Nike retail store, a Nike app, a Nike Super Bowl spot, and a Nike athlete endorsement can all feel like they came from the same mind even when they came from different continents and different business units.

What Nike understood, perhaps intuitively, is that alignment isn’t about uniformity. It’s about coherence. You can have wildly different executions and still feel unified, as long as every team can answer the same question the same way: what is this supposed to make someone feel?

Apple: Structure as a Weapon

Apple’s approach to alignment is architecturally different, and in some ways more demanding. Where Nike aligns through cultural narrative, Apple aligns through a management philosophy that Steve Jobs codified and that Tim Cook has, to his credit, largely preserved: the Directly Responsible Individual, or DRI.

The DRI model is deceptively simple. For every decision, every project, every deadline, there is exactly one person whose name is attached to it. Not a team. Not a committee. One person. That person is accountable for coordinating across functions, surfacing conflicts, and making the call when perspectives diverge.

What this does, structurally, is eliminate the diffusion of responsibility that kills cross-functional projects at other companies. In most large organizations, when something falls through the cracks, the honest answer to “who was responsible?” is a collective shrug. At Apple, that answer is never ambiguous. Somebody owns it. Which means somebody has a genuine incentive to make sure engineering has talked to industrial design, that legal has reviewed the supply chain implications, that the retail team knows what’s coming three quarters out.

The DRI model also changes the nature of meetings. When one person owns the outcome, meetings become decision venues rather than alignment theater. There’s a difference between a meeting where six people update each other and a meeting where one person makes a decision with input from six people. Apple runs the latter. Most companies run the former, and then schedule another meeting to figure out why nothing got decided.

There’s a harder truth embedded here. The DRI model only works if the organization actually trusts individuals with real authority. If every DRI decision has to get ratified by two layers of management before it can move, the model collapses into bureaucracy. Apple’s ability to operate this way is inseparable from its culture of deep functional expertise the expectation that if you own something, you know it better than anyone else in the room.

Where Most Companies Go Wrong

It’s worth sitting with why cross-functional alignment fails so reliably everywhere else, because the failure modes are instructive.

The first and most common failure is confusing visibility with alignment. Companies invest in dashboards, all-hands meetings, shared Slack channels, and OKR software, and then act surprised when teams still move in different directions. Visibility means everyone can see what everyone else is working on. Alignment means everyone has internalized why it matters and how their piece connects to the whole. These are not the same thing, and no amount of tooling converts one into the other.

The second failure is structural misalignment between incentives and collaboration. If the engineering team is measured on system stability, the marketing team on campaign reach, and the product team on feature velocity, you’ve built three functions that are fundamentally in tension with each other even when everyone is doing their job correctly. The org chart says they should collaborate. The compensation plan says they should optimize separately. The compensation plan wins.

The third failure, which is harder to diagnose, is a lack of shared vocabulary. Nike’s emotional brief and Apple’s DRI model both solve a communication problem at their core. When functions speak different languages when “done” means something different to engineering than it does to marketing, when “launch” has a different timeline in the product org than in the retail org coordination becomes translation work, and translation work is slow and lossy. The companies that align well have usually done the unsexy work of building a common operating language.

What You Can Actually Take From This

The instinct, when studying companies like Nike and Apple, is to reach for the parts that look transferable. Implement OKRs. Hire a Chief of Staff. Redesign the org chart. Run more cross-functional workshops. These things can help at the margin. But they tend to miss the deeper lesson.

What Nike and Apple did wasn’t implement a framework. They built alignment into the operating system of how they make decisions and how they tell stories about what they’re doing. For Nike, that operating system is emotional and narrative. For Apple, it’s structural and accountability-driven. Neither model is perfect Nike’s narrative-first approach can drift into vagueness when leadership changes; Apple’s DRI model can create bottlenecks when the wrong person owns the wrong thing. But both companies committed to a consistent philosophy over time, which is itself the point.

The companies that struggle with cross-functional alignment usually aren’t lacking for frameworks. They’re lacking for conviction about what kind of company they want to be and how that should shape the way decisions get made. The moment a company gets honest about that, the alignment question gets a lot easier to answer.