The Atlas Decision

SITUATION BRIEF

DECISION POINT 1 OF 5

Lead with the Atlas-5 vision: "Marcus, this is a generational moment. We need to commit to Atlas-5 — a clean-sheet design that leapfrogs Skyward. Priya's team has the feasibility work done. It's expensive and it's a 4-5 year bet, but anything less locks us into a declining platform."

Lead with the Atlas-3X as the pragmatic response: "We need to respond fast. The 3X gets us 60% of the way there in 18-24 months at a fraction of the cost. It buys us time and keeps customers in the fold while we figure out the longer-term play."

Present both options as a dual-track strategy: "I don't think this is either/or. I want to propose a dual-track: commit to 3X as the near-term response while greenlighting early-stage Atlas-5 development in parallel. It's more complex to execute, but it addresses both the short-term threat and the long-term platform question.

Push back on the timeline: Honestly, I'm not ready to give you a recommendation yet. The engineering team hasn't scoped the 3X's certification path, and I don't want to walk into Friday with a half-baked answer. Can we push the strategy discussion to next week?

CONSEQUENCE 1 + DECISION POINT 2

What do you say to Marcus?

Include the uncertainty in your Friday presentation: Tell Marcus and the board that the 3X timeline has a certification risk that could extend it by 12+ months. Present your recommendation with this caveat explicitly flagged. Accept that this weakens the near-term story.

Present the 3X as 18-24 months and note certification as a "manageable risk": Frame the certification question as a process issue the engineering team will resolve, not a strategic risk. Keep your recommendation clean and confident for the board.

Delay the 3X recommendation and present only Atlas-5: Use the certification uncertainty as evidence that the 3X path is more problematic than it appears. Pivot to recommending Atlas-5 only, arguing that the upgrade path creates more risk than it resolves.

Commission an independent certification assessment before Friday: Call in an external compliance consultant to give a rapid read on the certification risk. You won't have a formal ruling, but an expert opinion would strengthen whatever recommendation you make.

CONSEQUENCE 2 + DECISION POINT 3

How do you handle this uncertainty before Friday's meeting?

Make a conditional commitment to Meridian on the 3X: Tell Kenji you'll commit to delivering Atlas-3X capabilities within 24 months, subject to formal board approval on Friday. Give him enough confidence to delay Skyward's presentation.

Be transparent about where you are: Tell Kenji you're presenting a major strategic response to your board on Friday and can't make specific commitments until that concludes. Offer to brief him personally on Monday. Accept the risk that this isn't enough to hold him.

Offer Meridian a strategic partnership: Propose something bigger — invite Meridian to co-develop the next-generation platform as a launch partner, with early access, preferential pricing, and input into the specification. A longer play, but it repositions the relationship entirely.

Escalate to Marcus for an emergency customer commitment: Call Marcus immediately and explain that Meridian's timeline has accelerated. Request authorisation to make a preliminary commitment before the Friday meeting.

CONSEQUENCE 3 + DECISION POINT 4

What do you tell Kenji?

Accept Marcus's compromise: Agree to the phased approach. It gets the board to yes, funds the immediate response, and keeps Atlas-5 alive in principle. But you suspect it kills Atlas-5 in practice.

Push back — argue both tracks need real funding now: Make the case that the dual-track only works if Atlas-5 has committed resources from day one. Accept the ROIC hit and argue the board should communicate it to investors as a strategic investment.

Propose a middle path with a hard trigger: Accept the phased approach but attach a binding condition: if the 3X certification review (due in 8 weeks) reveals a timeline extension beyond 24 months, that automatically triggers full Atlas-5 funding.

Concede on Atlas-5 and go all-in on 3X: Read the room. The board isn't ready for Atlas-5. Rather than fighting for a dual-track that gets watered down, commit fully to 3X with the strongest possible execution plan. Revisit Atlas-5 in 18 months.

The Atlas Decision

Name

Email

Role Level

Industry