By Cheryl Detrick Founder & Strategic Navigator, Detrick Strategy
I am a sci-fi geek. I admit it and fly my geek flag proudly. I also admit that I love most space movies and that includes the movie, Armageddon. Yes, I know it isn’t great prose or the best minutes ever put on film, but I love it and can recite most of it from memory.
Armageddon, like many movies depicting NASA launches, features the launch status check, also known as the “go/no-go” poll. During the poll, the launch director queries the leaders responsible for critical systems to confirm readiness. Each reports go or no-go, and the launch director makes the final call to proceed, hold, or stand down.
In Armageddon, after everyone responds with their “Go, Flight,” the flight director says, “it’s pucker time.” I’m pretty sure the real NASA flight director doesn’t actually say that, but it would fit with what is about to happen out on that launchpad! This also applies to preparing to launch any major change at a business. When you are the leader, and you say go … here.we.go. And it is usually a *moment.* Exciting, but scary too.
Because of that and more, Align may be the simplest point in the Compass technically — and one of the hardest to lead through well. It is where everything learned, designed, and decided becomes launch readiness. You have done the hard thinking. Now are you ready to go?
Orient established the truth of where the organization is now. Envision established the future the organization is choosing. Design worked backward from that future and forward from current reality to build the path, sequence, dependencies, assets, barriers, and capabilities required. Align is not another round of strategy creation. It is where the organization prepares to implement what it has already designed.
Design creates a credible path. Align makes sure the organization is ready to walk it. Align is likely one of the most compressed points in the framework because most of the intellectual work has already occurred.
Align is technically simple — and the hardest for the humans making the decisions. The technical mechanics are relatively straightforward: Revisit, verify, resolve, sequence, assign, resource, date, and ready. By Align, the transformation is no longer conceptual. It is about to become real. The difficulty is emotional, logical, and instinctive. People decisions become real. Budget decisions become real. Role changes become real. Dates appear on calendars. Owners are named. Fear and excitement can exist simultaneously. Risk-averse leaders may be especially vulnerable here because "one more thing to examine" can sound responsible while actually functioning as avoidance.
Align is preparation for movement, not a place to hide from movement. There is a parallel with Envision: just as Envision can become endless possibility until you talk yourself out of choosing, Align can become endless preparation until you talk yourself out of launching.
First though, Align begins by going back to everything the earlier work exposed: we return to the backward/forward maps created during Design; revisit all the barriers, capacity concerns, capability gaps, people issues, structural issues, technology needs, resource needs, and other "Negative Nelly" concerns that surfaced during Orient, Envision, and Design. Not in a “dive into all the details and rework it” way, but in a “where are we *now*?” way.
During Align, it is important to take the time to assess the organization that exists now — not simply the organization documented during Orient. We take the work of Design and turn it into launch readiness; a good Design process has already established sequence and dependencies, Align operationalizes them.
Earlier in the framework, an issue could sometimes remain identified and unresolved because the organization was still determining the destination and design. Align is where "we know" has to become "we changed it," "we addressed it," or "we have a deliberate plan for when it will be addressed."
The question is not simply whether each barrier still exists, but whether it has been resolved, rendered irrelevant by changes in the organization, or joined by something new. Be aware that like all good continuous quality improvement processes, the Detrick Compass has the principle that an organization does not remain static while doing the framework. Shining a light on a gap often begins addressing it and assessment itself creates movement. Identifying an asset can change how it is used; identifying a gap can cause people to begin closing it before a formal intervention begins.
Once the review of barriers and gaps is complete, the work is to determine what must happen before launch, what can occur later in the sequence, what can proceed while implementation is underway, and what depends upon something else being completed first. This process ensures required funding is ready, critical people are in place, and technology, outside expertise, approvals, contracts, equipment, or other necessary resources are available when the Design requires them.
Going through the process accounts for known delays before they become surprises. Every meaningful dependency needs a named owner, a date, and a visible connection to the whole. The organization may execute in parts, but it designed for the whole. Each owner should understand what their piece enables and what depends upon them.
Often at this point, people will seek a middle ground between stopping or going by recommending a phased rollout or pilot. Phasing should come from Design. It determines what happens first, what follows, and which dependencies must be satisfied between phases. Align makes sure the first phase is ready and later phases are properly positioned. Now, a pilot is different because it is intentionally designed to learn before full-scale commitment. A pilot makes sense when the final output is genuinely uncertain, the proposed change is substantially different from current operations, stakeholders reasonably want evidence before making a larger financial or operational commitment, or real-world conditions may reveal "unknown unknowns." But a pilot should have clear learning objectives, assumptions being tested, success/failure criteria, and implications for the larger Design. A well-designed pilot is not simply a smaller launch. It is a learning mechanism. Pilots are not appropriate when the change cannot be meaningfully isolated at smaller scale or the learning would not affect the eventual rollout. Do not use a pilot as an excuse to avoid commitment because leadership is afraid. Phasing follows the Design. Piloting tests uncertainty. Neither should become a disguise for hesitation.
It is critical to note that there may be difficult conversations that cannot be avoided. Align is not just about systems, structure, funding, or technology. People can create the fastest and most damaging form of misalignment. Leaders must dig in and distinguish healthy dissent from destructive misalignment. Healthy dissent challenges assumptions, exposes risk, and strengthens Orient and Design. Someone can disagree with the chosen decision and still support it professionally and in good faith once the organization commits. However, persistent animosity, active resistance, protecting the old way, undermining decisions, or hoping the transformation fails is different.
Leadership eventually has to ask whether people fit this organization, in this role, headed toward this future. A highly capable person can still be the wrong fit for the future state. This is about organizational fit and responsibility, not punishment for dissent. This is where "right people, right seats" — and sometimes wrong people off the bus — conversations become real. These conversations are difficult, but leaving strong misalignment unresolved can be toxic to the strategy and the organization.
That is why these decisions cannot be deferred until the final go/no-go poll. By the time the organization reaches the launchpad, the crew should already be chosen, committed, and prepared. Discovering at the final poll that a critical leader has been actively resisting the transformation is not simply a no-go condition; it is evidence that Align failed to do its work earlier.
Once people are aligned, the next step is near-launch communication. A reminder, communication should not *begin* in Align. Significant transformations require ongoing communication throughout the earlier points in the Compass. But communication is not merely transmission, it is also translation. People hear information through their own frame of reference and especially hear what they believe affects them. They may not fully hear or process messages until the change becomes concrete enough that they can see themselves in it. Communication therefore needs to be repeated, layered, and increasingly specific as launch approaches. Then, immediately before go, there should be as close to an all-hands communication as practical. Clearly communicate again what is changing, why, when, what people should expect, what is expected of them, and where questions and concerns should go.
The world being what it is, it may change suddenly on you. If circumstances materially change, pull back far enough to test what changed. Recent history offers more than enough examples: 9/11, the 2008-09 financial crisis, and March 2020. A shock of that magnitude can justify deeper movement back into Design or even reconsideration of the destination. Moving backward in the framework is not failure. It can be disciplined adaptation. Do not automatically assume disruption means abandoning the strategy. The better asks are do we do it anyway — or do we do it especially now? The important question is whether the changed environment alters the destination, the design, the sequence, or the readiness decision.
Align and Navigate are tightly coupled, so don’t force an artificial wall between the two stages. Align creates readiness. Navigate creates movement. Align gets enough of the organization into position that responsible movement can begin. Not everything required later in the transformation must be complete before Navigate starts. For example, if a tech platform is required six months into a two-year transformation, it does not necessarily need to be installed before launch; its requirement, timing, ownership, resources, and dependencies need to be understood and positioned so it is ready when required. Again, part of Align is identifying the sequencing and critical path.
The heart of Align is reaching a responsible go/no-go decision. The heart of the transition into Navigate is making the real call, but it can be a hard call.
By Align, the CEO, owner, or significant leader is probably deeply invested in the transformation or it would not have reached this point. As humans, attachment can distort judgment just as fear can. Leaders have to separate "I love this idea" from what the evidence, research, best practice, earlier Compass work, and trusted leaders are actually saying. Listen especially carefully to people who own critical components. The leader's role is not to prove the transformation is right. It is to determine whether the organization is ready to carry it. A go/no-go decision is not a test of confidence in leadership - it is a readiness test.
To effectively use the go/no-go poll process, there must be psychological safety at the launchpad. The leader making the ultimate call may bear the greatest consequence if the transformation fails. That is part of significant leadership. But, because that leader holds disproportionate authority, they must be especially careful not to contaminate the information coming upward. If the CEO has already made it clear that only "go" is acceptable, a go/no-go meeting becomes ceremonial rather than meaningful. People with component ownership must be able to say, "I am no-go, and here is why," without punishment. If people cannot safely say no-go, then "go" means nothing. Psychological safety at the launchpad is also a test of the earlier process. If people cannot tell the truth during Align, leadership should question whether Orient, Envision, and Design ever received the full truth either.
Who should participate in your go/no-go poll? That depends on your organization and structure. The group should include the owner or executive leader who bears responsibility for the decision and consequences; people with meaningful ownership of critical components; and, when appropriate, governance leaders who have participated meaningfully throughout the process. Go/no-go authority follows informed responsibility and involvement, not title alone. Someone should not parachute into the end of the process and suddenly become a go/no-go authority without understanding the design, dependencies, tradeoffs, and risks.
You are probably asking, what if one person says no-go? In an organization, a lone no-go is not automatically a veto, but it automatically deserves examination. The first question is whether the person has identified a true no-go—or whether they are experiencing understandable fear or uncertainty. Every no-go deserves investigation. Not every no-go deserves delay.
So what is a true no-go? It is not discomfort, nervousness, disagreement, or imperfection. A true no-go is a missing or unresolved condition materially necessary for responsible launch. True no-go conditions may include a critical person becoming unexpectedly unavailable; necessary financing not closing or a required line of credit being unavailable; a required approval not being obtained; necessary equipment not being in place; or a major disruption changing the environment around the enterprise. Most other things mean “ready enough” because perfect readiness is impossible and should not be the standard. Ready enough is not the absence of problems. It is the absence of unresolved critical problems. Experienced leadership judgment matters here: there is often a recognizable difference between "messy but manageable" and "this is going to bite us immediately." Courage does not require feeling fearless. It requires distinguishing legitimate evidence of no-go from the ordinary fear of consequential action.
Strong unease from a trusted, informed leader may be pointing toward a problem that has not yet been voiced. By this stage, most mechanical problems should already be visible. The remaining danger may be the thing nobody can quite articulate yet. It is there, but feels ethereal. Don't ignore the gut. Don't ignore intuition. Test both. Intuition should be investigated, not worshipped and not ignored. One of the most consequential failures at Align may be ignoring a gut warning — your own or that of a trusted, informed leader. The process says go, but someone who knows enough to matter feels no-go — and nobody stops to find out why.
Once every critical component has been tested, meaningful no-go conditions have been resolved, remaining risk is understood and accepted, and the responsible leaders are genuinely go, someone has to make the final call.
More preparation cannot eliminate uncertainty. Eventually continued alignment work becomes hesitation. Navigate will inevitably reveal information that causes further adjustment and realignment. That is not evidence that Align failed. It is what happens when a Design leaves the launchpad and meets reality.
Next, we move into Navigate: how leaders maintain disciplined movement while adapting the route. In Navigate, leaders must distinguish between changing course thoughtfully and abandoning direction reactively. That is how the organization keeps moving toward True North.
But first, someone has to make the call.
The hardest point is when it is time—when leadership says go and Navigate begins. It’s pucker time.
In the meantime, have a thought, question, or perspective this article raised for you? I’d love to hear it.
If you are reading this article and want more in the Detrick Compass™ framework series, explore The Birth of the Detrick Compass™ ; First, We Orient; Envision, A Future Worth Choosing, and Design, Now We are Making It Real.