Compare development paths without hiding the tradeoffs

Define what the project is optimizing for

The best path depends on the customer's priorities. Establish how the team weighs approval certainty, speed, return, capital exposure, program quality, flexibility, and long-term operating value.

Make tradeoffs explicit. A scenario cannot be optimized honestly when every objective is treated as equally important.

Create alternatives that are materially different

Scenarios should change decisions, not presentation. Vary program, density, phasing, approval strategy, infrastructure response, acquisition structure, or capital timing enough to expose real optionality.

• Lower-discretion path
• Intended program
• Higher-value alternative
• Trigger for switching paths

Compare every path on the same basis

Use consistent assumptions and disclose every exception. Compare approval exposure, schedule character, capital timing, design implications, infrastructure requirements, expected return, and primary downside.

Avoid a single composite score. Decision-makers need to see why one path is stronger for this project and this organization.

Test the assumptions that could reverse the choice

Identify the variables with enough influence to change the recommended path. Test realistic movements in schedule, cost, rents, yield, capacity, required mitigation, and approval conditions.

Worked example: three credible paths for one project

Consider an illustrative residential and neighborhood-retail project. Path A keeps the program within a lower-discretion envelope and reaches an earlier approval target, but produces less density. Path B pursues the intended program through a longer review process. Path C phases the site so early infrastructure and a first building can advance while a later portion remains flexible.

The highest projected return may sit in Path B, but only if the approval duration, carrying cost, and utility timing remain within a narrow range. Path A may protect schedule and capital. Path C may preserve upside while reducing the amount exposed before key answers arrive.

The team should see those tradeoffs side by side, with the assumptions that make each path credible. That makes the recommendation an explainable choice, not a model output that can only be accepted or rejected.

Avoid scenarios that only confirm the preferred answer

Scenario work loses value when the alternatives are cosmetic, the preferred case receives better assumptions, or schedule and approval risk disappear inside a blended score. It also fails when the team optimizes one variable while ignoring the customer's capital constraints or operating goals.

Name who set the priorities, keep assumptions consistent, and show exceptions openly. If two paths are too similar to change a decision, combine them and create a more meaningful alternative.

• Materially different alternatives
• Consistent comparison basis
• Visible tradeoffs
• Variables that can reverse the ranking
• A defined trigger for switching paths

Record the choice and preserve the alternatives

State the selected path, the priorities it serves, who approved it, and which conditions would reopen the decision. Preserve the other scenarios as alternatives, not abandoned files.

The decision brief should include the recommended path, a comparison table, critical assumptions, sensitivities, required authorizations, and the next actions needed to keep the selected path credible.