From “Why it cannot work” to “Under what conditions could it?”

The kick-off is done. Now the real planning begins.

Project Orion’s kick-off is complete. The objectives have been discussed, expectations shared, and the core team has gathered for its first planning session. The questions are familiar: When will we deliver? With what budget? Using which resources? And how will we achieve the expected quality and business outcomes?

During kick-off, we are trying to define the boundaries of the project. Where can we adapt, and where is flexibility genuinely limited? Is the delivery date non-negotiable? Is the budget a hard ceiling, or can additional investment be justified by the value it creates? Does every feature need to be included in the first release? Which safety, performance and regulatory requirements must be met?

Without these distinctions, a plan can become a shared schedule approved by people who are working from very different assumptions.

A familiar meeting—and a familiar trap

Experienced specialists often arrive at planning meetings with compelling explanations of why the target cannot be achieved under current conditions. Engineering capacity is committed elsewhere. Supplier lead times are too long. The test schedule is full. The proposed solution cannot meet the financial target.

These concerns matter. They often reflect hard-earned experience and real constraints. The problem begins when they become the conclusion of the discussion instead of the starting point for developing alternatives.

The meeting gradually shifts from “What could we change?” to “Why can’t this work?” If the project leader gets caught in the same cycle, the next steering committee presentation may become a polished explanation of why the objectives are unattainable.

The reporting is professional. The analysis is convincing. The presentation is clear. Yet the people expected to make a decision still have too few options.

Sometimes the original target really is infeasible. The team’s contribution is then to make the boundary explicit and show which changes could create a viable way forward.

A strong planning discussion turns valid constraints into choices leaders can act on.

Planning beyond the iron triangle

Time, cost and quality remain essential. But they do not fully describe the decisions modern project teams face.

Two plans with the same delivery date can have very different implications for capacity, supplier dependency, profitability and organisational workload. A lower-cost option may destroy more value through a delayed market launch. A faster schedule may divert scarce experts from another strategically important project.

Customer expectations, cash flow, operational readiness, regulatory requirements, sustainability and stakeholder risk tolerance also shape the decision.

Before searching for the best plan, we need to agree what we are trying to optimise—and which boundaries must be respected. A scenario that scores well overall may still be unacceptable if it violates a mandatory requirement.

Turn constraints into decision options

Imagine the Project Orion team reframing the discussion: “What options could move us towards the goal, and what would each one require?”

The team might consider accelerating delivery with additional capacity, delivering later with current resources, or releasing priority scope first through a phased approach. These are different business decisions, each with its own consequences.

Every scenario should make its expected value, resource needs, critical dependencies and remaining risks visible. Risk mitigation belongs in the comparison too: what does the action cost, who will own it, how feasible is it, and how much risk is likely to remain? Naming a mitigation action does not mean the risk has disappeared.

Opportunities deserve equal attention. What is an earlier launch worth? Could a phased release produce useful customer feedback sooner? Would additional investment create a capability that benefits future projects as well?

The message to the steering committee then becomes more useful: “Under the current conditions, we cannot meet the target. Here are the alternatives we assessed, the value each could create, and the resources and risks involved. This is our recommendation, and this is the decision we need.”

Why good scenario analysis is difficult to sustain

In practice, this approach creates a substantial preparation burden. Data lives in different files. Capacity information is out of date. Lessons from previous projects remain in people’s memories. A change in one supplier commitment can require several scenarios to be recalculated.

Teams can end up spending more time maintaining the analysis than discussing its implications. Repeated preparation, shifting assumptions and an expanding list of alternatives can erode motivation and productivity.

The answer is not an unlimited number of scenarios. Teams need a manageable set of meaningful alternatives, analysed with enough depth to support the decision.

This is where we position the project planning use case within Building NEXA.

Where NEXA could contribute

Building NEXA explores how an AI project team member could support this work. In our illustrative Project Orion story, NEXA begins by organising the available information: objectives, constraints, assumptions, dependencies and missing inputs.

A delivery date described as “fixed” in one document may appear as a “target” in meeting notes. Surfacing that inconsistency creates value before a schedule has even been built.

With access to relevant, authorised data and suitable planning tools, NEXA could help draft scenarios, retrieve comparable historical examples and compare the effects of changing inputs. Schedule and cost calculations would rely on traceable models; NEXA would help translate their outputs into material the team can review.

The team could then explore practical questions. Would another specialist shorten the schedule, or is the bottleneck elsewhere? If we change suppliers, what new qualification risks arise? Could phased delivery create earlier value? Which scenario becomes infeasible when a critical assumption changes?

Sensitivity analysis helps reveal how strongly an outcome depends on particular assumptions. It can direct attention towards the inputs that matter most, instead of giving every variable equal discussion time.

Missing data, weak historical comparisons and unvalidated assumptions must remain visible. A precise date or an AI-generated confidence percentage is not evidence of reliability on its own. Estimates need a clear basis, and uncertainty needs to be communicated honestly.

Give experts more time for judgment

The opportunity is to shift more of the team’s effort towards work that requires expertise: validating assumptions, improving alternatives and assessing real-world feasibility.

Engineering evaluates whether the proposed parallel activities are technically possible. Procurement checks the readiness of an alternative supplier. Finance challenges the business value attributed to earlier delivery. The project leader brings the cross-functional consequences together.

NEXA supports analysis and preparation. Experts validate the outputs. Sponsors and the steering committee make the trade-offs and accept risks within their authority.

That division of responsibility is central to the concept. The value comes from combining analytical support with accountable human judgment.

Agree on the conditions for success

The selected scenario should be accompanied by the assumptions, resource commitments, accepted risks and review triggers on which it depends.

If additional capacity is not available by the agreed date, what decision needs to be reopened? If a supplier commitment changes, which alternative should be reassessed? Who owns the next action?

Recording these conditions helps prevent a conditional forecast from becoming an unconditional promise. It also gives stakeholders a shared reference point as circumstances change.

This does not remove the need for ongoing communication. It makes that communication more specific and makes emerging expectation gaps easier to address.

A stronger outcome for Project Orion

At the end of the planning meeting, the Project Orion team has more than a Gantt chart. It has assessed alternatives, a reasoned recommendation, explicit resource needs and visible risks.

The team understands the conditions under which it can proceed and the changes that would require another decision.

That is the value we are exploring with Building NEXA: bringing AI’s analytical support together with the team’s experience to make planning a stronger decision process.

Because the question that moves a project forward is often: “Under what conditions is it possible—and is it worth it?”

“Under what conditions is it possible—and is it worth it?”

What slows your planning down most: missing data, scenario preparation or agreement on trade-offs?