← Back to list

Cross-functional Alignment Without Authority

Nobody Reports to You. But Everything Depends on You.

Ro Fernandez in Startup Stash · 2026-05-17 09:12 · 10 claps · 7.3 min read
#coss #management-and-leadership #growth-mindset #business #leadership
Open on Medium ↗
Wiki topics: SAF · Safety & Alignment BIZ · Business Strategy LIT · Literature & Writing

Cross-functional Alignment Without Authority

Nobody Reports to You. But Everything Depends on You.

Photo by Raj Rana on Unsplash

Photo by Raj Rana on Unsplash

Authority doesn’t create alignment. Clarity does. Here’s the difference.

The Chief of Staff at a 136-person company called me on a Tuesday evening, because nothing was moving.

She’d spent three weeks trying to get the Product, Marketing, and Sales leads to agree on a single go-to-market timeline. They all understood the stakes. They’d all said they were aligned. And every time she tried to move the work forward — something stalled. A “let me get back to you.” A missed deadline. A meeting that got cancelled and never rescheduled.

“I don’t have authority over any of them,” she said. “I can’t make them move.”

And I fully understand that feeling. I’ve been there too.

There’s a huge challenge for anyone in a CoS, COO, or cross-functional leadership role — where success depends on all parts playing their part, but stepping into someone else’s territory feels like overreach. In my last role, I was managing the product, operations, and design teams, and I needed the marketing team to launch a product. The person running that department started going directly to my team and reprioritizing their work — the opposite of what I’d asked them to focus on. The team was confused. Chaos followed.

So finding a way to create alignment without triggering that kind of turf war?

That’s not a soft skill.

That’s the job.

So here’s what I told her:

“That’s not your problem. Your problem is that nobody has made the cost of not deciding visible yet.”

Cross-functional work is the hardest kind.

Not because people are difficult or lazy — though there’s an unfortunate tendency right now to assume that’s the case. Not because the work is technically complex.

But because when nobody owns the outcome — from the top to every person on the team — and when roles and responsibilities aren’t crystal clear, everybody can defer. And they will. Until they can’t.

The trap most CoS and COO-level operators fall into is trying to push cross-functional work forward through relationships, persistence, and goodwill.

And those things matter. But they’re not the engine.

The engine is clarity. Clarity at every level — and giving leaders the resources and rituals to bring that clarity to the people who will ultimately execute.

Let me say something uncomfortable.

Authority is overrated.

I’ve seen senior leaders with full organizational authority fail to create alignment. And I’ve seen Chiefs of Staff with zero direct reports move entire companies. The difference isn’t title. It isn’t tenure. It isn’t even relationships.

It’s the ability to make the work clear — and to put in place the systems and non-negotiable rituals that span all departments.

Clear enough that people know what they’re deciding. Clear enough that the cost of not deciding is visible. Clear enough that there’s no comfortable ambiguity left to hide in. Clear enough that nobody’s waiting for Maria to do it while Maria is waiting for John.

“Clarity is not a luxury. It’s the fuel that makes scaling sustainable.”

Gartner research found that 80% of cross-functional projects fail to meet their objectives. Not because of misaligned strategy. Because of misaligned execution — different teams operating on different assumptions about what matters and who’s responsible for what.

That’s a clarity problem. Not an authority problem.

Here’s what misalignment actually looks like in practice.

Most of the time, people aren’t resistant to alignment. They’re resistant to ambiguity that looks like alignment.

When a decision isn’t real — when there’s no clear owner, no clear deadline, no clear definition of done — people don’t default to chaos. There is so much noise in every conversation, so many competing signals, that it becomes genuinely difficult to know when to listen, when to act, and when to let something go. So people default to their own priorities.

Which is completely rational. It’s completely human. 🙂

Which is exactly why your job isn’t to force alignment. It’s to build it.

💥 Here’s the reframe:

You’re not trying to get people to follow you.

You’re trying to make the work so clear that not moving becomes the uncomfortable option.

That’s cross-functional alignment without authority. That’s where the leverage is.

The 4-Layer Clarity Model 🗺️

(The mental model I use with every cross-functional team I work with — regardless of company size or industry.)

🔹 Layer 1: Disagree and Commit

In anything that starts, there is one key rule — teams must disagree and commit.

And for this to happen, you can’t just hope people feel safe enough to speak up. A lot of companies get stuck believing that if they just post the right values or send an inspiring message, trust will follow. Anyone who’s been in a room where the CEO asks “any questions?” and gets silence knows how that plays out. 😅

Trust isn’t declared. It’s designed.

It starts with how meetings are structured and led. Every leader needs to learn this: meetings aren’t held to find agreement — they’re held to find disagreement. Specifically and safely.

I always recommend removing the classic “Does anyone have any questions or comments?” from your meeting closings. That question assumes agreement already exists. Instead, build in deliberate friction. Ask questions that surface where people don’t align. Use tools like Nova that ensure every participant has a voice — not just the loudest ones in the room.

Once disagreements are on the table — discuss potential solutions, considerations, and non-negotiables. Then, when a direction is proposed, ask directly: “Are you in — or is there something you still don’t agree with? If you’re in, you commit to being an ambassador for this.”

One key boundary: disagreement has a phase. It belongs in the discovery and discussion stage. Once a decision is made and committed to, new opinions need to wait for the next review cycle. There is more to learn from moving imperfectly than from standing still while everyone finds one more thing to debate.

🔹 Layer 2: Named Decision Rights

For every key decision in the initiative, name one person who makes the call.

Not “the team.” One person. 👉 Even if others have input — define who has input, and when that input is due.

Ambiguous ownership is where cross-functional work goes to die. You don’t need authority to clarify this. You need the courage to ask for it.

One thing I see constantly: managers who are afraid to assign ownership, so they walk into a meeting and ask “who wants to take this?” Not only does the same overloaded person raise their hand every time — creating quiet burnout and unfairness — but you also risk choosing the wrong person entirely.

Here’s what I know to be true: a good manager knows what each person was hired for, what they’re good at, what they enjoy, their current capacity, and their workload. Ownership isn’t volunteered. It’s proposed — and then discussed.

And always — I’ll say this again — always: when something is added, something else must move or be removed.

🔹 Layer 3: The Visible Cost of Delay

Make the cost of not deciding explicit. Not as a threat — as a fact.

“If we don’t confirm the launch date by Friday, the campaign window closes and we push six weeks.”

That’s not pressure. That’s clarity. And it changes the conversation completely.

Once the cost is visible, have the real conversation: What do we need to deprioritize? What can I unlock for you? Where do you need more support?

“People don’t resist change. They resist being changed without understanding why.”

This is why making the cost visible works. It removes the ambiguity that lets people stay comfortable in their hesitation. It turns a vague “we should probably move on this” into a concrete choice with real consequences.

And if your work lives inside a system — not scattered across meetings, messages, and email threads — anyone can step into a process, support a team, or pick up where someone left off. No 99-meeting onboarding required.

Systems prepare teams for the reality of work. People leave. People get sick. Workloads shift. Departments overlap. Most companies fail not because the strategy is wrong, but because the day-to-day coordination of how the work happens was never designed. And so the meetings, the messages, and the back-and-forth eat the day.

🔹 Layer 4: One Shared Artifact

Not a meeting. Not a Slack thread. One place where the decisions, owners, and deadlines live — visible to everyone involved.

When the work is visible, accountability becomes structural. You stop chasing people. The artifact does it for you.

This is the difference between a team that runs on relationships and a team that runs on systems. Both can work. Only one scales.

❓ Here’s what I’d ask you to sit with:

In your most stuck cross-functional initiative right now — is the problem that people are resistant?

Or is the problem that there’s enough ambiguity for everyone to reasonably wait?

Because if it’s the second one — that’s not a people problem. That’s a design problem.

And design problems are fixable.

Try this in the next 24 hours:

Pick one stuck initiative. List two to six key decisions that need to be made — and name one decision-maker for each. If you can’t name a person, that’s the root of the stall. Start there.

Make the cost of delay explicit in one sentence. Share it with the key stakeholders before your next meeting. Watch what changes.

✅ Create one shared place for this initiative’s decisions, owners, and deadlines. Not another meeting. A doc. A log. Something people can access without having to ask you. If you’re using Nova, add it there.

✅ Choose one meeting this week and change how you lead it. Stop running meetings as spaces for agreement — run them as spaces for progress and productive disagreement. Three meeting types cover almost everything you’ll ever need:

  • Informative — the goal is to share information clearly
  • Opinion/Discussion — the goal is to capture perspectives, ideas, and experience
  • Decision — the goal is to make a call or get something approved

Know which one you’re running before you walk in. The process almost builds itself from there. You can find the templates for each at novatools.org/meetings.

You don’t need authority to create alignment.

You need clarity sharp enough that staying unaligned costs more than moving.

That’s leadership. Even without the title.

So here’s the question I’ll leave you with:

In the cross-functional work you’re trying to move right now — is the problem that people won’t align, or that you haven’t yet made the path clear enough for alignment to happen naturally?

Drop your answer in the comments — I read every single one.

And if you’re working through this with a real team and want a structured way to do it, we’ve built free tools at Nova designed exactly for this. → novatools.org

Or reach out directly. I take on 2–3 companies per month for strategy clarity and leadership work. If the timing feels right, let’s talk.

Resources:

Strategy Clarity Process

Productive Meetings (templates) < Find them here


메타데이터
post_id
2b4e461b4d7a
slug
cross-functional-alignment-without-authority-2b4e461b4d7a
url
https://blog.startupstash.com/cross-functional-alignment-without-authority-2b4e461b4d7a
canonical_url
https://blog.startupstash.com/cross-functional-alignment-without-authority-2b4e461b4d7a
author_url
https://medium.com/@rociofernn
status
ok
fetched_at
2026-06-15 20:49:13