A month or two back, in Zalando's Global Project Management Organization, we had the pleasure of hosting senior leader Carolin Reese (Director of Compliance) for a session on Addressing Ambiguity at the Start of a Project.

Her talk hit home. In an environment where we constantly balance high-stakes strategic initiatives with complex regulatory and compliance requirements, her perspective sparked a lot of reflection. As Program Leaders, we've all seen how unaddressed ambiguity can quietly derail even the most critical roadmaps.

Inspired by Carolin's talk, I wanted to share my key takeaways alongside my perspective on how we can actively handle ambiguity — and empower our teams to navigate it, across every strategic lifecycle.

1. Ambiguity vs. Uncertainty: Diagnosing the Problem

Before you can lead your team out of the fog, you have to understand what kind of friction you're facing. While people often use "ambiguity" and "uncertainty" interchangeably, they require completely different leadership responses.

Uncertainty = The answer sits in the future.

It is the classic "known unknown." You cannot remove uncertainty through hard work alone; it is simply a reality of time and external factors.

• Strategic Example:Will external brand partners accept our updated platform terms next quarter?
• Compliance Example:Will EU regulatory bodies grant final approval or issue updated enforcement guidelines before our target go-live date?

Ambiguity = The answer exists today, but it is unclear or conflicting.

Ambiguity is not a feature of the future; it is a clarity gap in the present.

• Strategic Example:Do Legal, Product, and Business teams share the exact same definition of "Minimum Viable Product" for a new market rollout?
• Compliance Example:Is a specific technical feature an absolute mandatory requirement for Day 1 compliance, or is it a nice-to-have risk mitigation that can be phased in later?

2. The Danger of Early Ambiguity in Strategic Initiatives

Carolin highlighted a concept during her talk that resonated strongly: The Scope Death Spiral.

In massive cross-functional programs, a single degree of misalignment at kickoff magnifies into kilometers of wasted effort down the road. When compliance boundaries or strategic priorities are left ambiguous:

• Teams waste critical sprint cycles: Tech and operational teams end up building features based on assumptions that eventually get rejected by legal or compliance stakeholders.
• Trust erodes rapidly: Because new, cross-departmental teams rarely have a long history of working together, early confusion breeds executive anxiety.
• Micromanagement creeps in: When sponsors don't see clear alignment on the "What," they start pulling levers on the "How."

3. How Program Leaders Can Direct Teams to Handle Both

As program leaders, our job isn't to predict the future — it's to structure the path forward.

A. Managing Uncertainty: Scenario Planning & Courage

• Normalize saying "We don't know yet": Foster a culture where admitting an external unknown is a valid, professional starting point — provided it's followed by a plan to find out.
• Build contingency scenarios: When waiting on regulatory decisions or market responses, map out clear fallback plans (Plan A, Plan B, Plan C) based on probability and impact.
• Build executive trust: Being transparent about external unknowns demonstrates that you aren't hiding risks, which reinforces delivery confidence.

B. Dismantling Ambiguity: Active Clarification & Ownership

• Treat ambiguity as a leadership vacuum: Ambiguity rarely resolves itself. Whether caused by accidental miscommunication or an intentional hesitation to make hard calls, program leaders must step in to fill the vacuum.
• Ask simple, uncomfortable questions early: Don't let stakeholders nod along in meetings when terms like "compliant" or "ready" mean completely different things to different departments. Strip away the jargon and pinpoint exact deliverables.
• Escalate strategically: If clarity doesn't emerge in working sessions, raise the issue to your Steering Committee or Project Sponsor. It's better to force a difficult scope decision on Day 10 than face a failed go-live on Day 100.

When early ambiguity is left unaddressed, projects quietly drift, waste resources, and lose stakeholder trust. It is always better to face the uncomfortable questions around project scope on Day 1 than to manage an avoidable failure six months later.

4. Practical Mindsets for Your Next Project Launch

To translate these principles into daily practice across strategic and compliance roadmaps, here are four habits to instill in your project teams:

• Document Unknowns Immediately: Use dependency logs and risk registers on Day 1 to bring unspoken assumptions into the light.
• Keep Core Decision Groups Lean: Larger committees tend to dilute accountability and increase noise. Keep core decision-making pods small so alignment happens quickly.
• Work Backwards from Hard Deadlines: Plan backward from fixed go-live dates or regulatory enforcement deadlines, keeping a sharp eye on dependencies like peak trading windows, legal review cycles, or external partner onboarding.
• Bring Solutions, Not Just Blockers: When escalating ambiguity to senior leadership, never just present "we aren't aligned." Present the conflict alongside two clear options and a recommended path forward.

Final Thoughts

Leading through strategic complexity isn't about having all the answers on Day 1 — it's about having the discipline to ask the right questions until the path becomes clear. By separating future uncertainties from present ambiguity, we give our teams the clarity, focus, and momentum they need to deliver high-impact results.