A decision must be made now and the information needed will not be available for six months. What should the approach be?

The approach

Reduce the cost of being wrong rather than trying to be right.

• Identify what would change the answer, precisely. If it is a scale threshold, a customer commitment, or a regulatory outcome, name it — and set a review trigger on it rather than deciding as though it were known.
• Choose the option that preserves the most future choices, even if it is not the best under the most likely scenario. The value of optionality rises with uncertainty, and under high uncertainty a slightly worse reversible option beats a slightly better irreversible one.
• Stage the commitment. Make the smallest decision that unblocks progress, and defer the rest until the information arrives. Much of what feels like one decision is several with different information needs.
• Buy information cheaply where possible: a spike, a prototype, a conversation with a customer, a small experiment. A week of evidence frequently resolves what six months of deliberation would not.

What to avoid

• Deciding as though the uncertainty were resolved, which produces confident designs built on an assumption nobody wrote down.
• Deferring past the point where deferral has a cost. The last responsible moment is a real point, and passing it means the decision gets made by circumstance.
• Choosing the most flexible option regardless of cost. Optionality is not free, and a design that keeps every door open is usually expensive and mediocre at everything.

What must be recorded

The assumption, explicitly, with the trigger that would invalidate it. "We are assuming fewer than five thousand tenants; if we exceed two thousand we revisit the tenancy model." That sentence in a decision record is worth more than any amount of analysis, because it converts an invisible assumption into a monitored one.

The framing for stakeholders

"We are deciding X now because deferring costs Y, and we are deferring Z because the information arrives in March." Separating the two makes the uncertainty visible without making the team look indecisive — and it sets the expectation that a revisit is planned rather than a failure.