How Do You Turn Complex Analysis into Clear, Decisive Action? Recommendations & Judgment

Most early-career analysts make the same mistake. They present everything they found, usually in the order they found it, and leave the decision-maker to infer the conclusion. That is a data dump, not a recommendation. It transfers the burden of synthesis to the audience and often produces one of two outcomes: the audience focuses on the wrong detail, or the volume of information slows the decision. The difference is visible in a simple comparison.

Data dump: "The property is a 240-unit garden-style asset built in 1999. In-place rents average $1,450. Submarket vacancy is 5.1%. Three comparable sales traded between 5.5% and 6.1% cap rates. Renovation is estimated at $18,000 per unit. The seller is asking $66 million. Rates have risen this year. Here is everything we found."

Recommendation: "Recommend acquiring Brookhaven Commons at $66 million, a 5.8% going-in cap. Renovating 60% of the units produces a 13.3% yield on renovation cost and a 14.6% base-case levered IRR over a five-year hold. The return still clears our 10.0% downside threshold if rent growth underperforms the base case by 150 basis points. The primary risk is lease-up pace; the mitigant is phasing renovations so that no more than 30 units are offline at one time."

Both analysts may have done the same work. The first presents inputs without synthesis. The second states the recommendation, identifies the price, compares the return to a decision threshold, addresses the downside, and pairs the main risk with a mitigant. Only the second has finished the analyst’s job.

Barbara Minto formalized this approach in The Pyramid Principle, originally developed from her work in consulting communication. The core idea is that effective business communication usually inverts the academic model. Academic writing often builds from evidence toward a conclusion; business communication should start with the conclusion, then organize the supporting evidence underneath it. The reasoning is practical. Decision-makers are busy, time-constrained, and selective in how they process information. When the conclusion comes first, the audience knows what claim the evidence is meant to support. When the evidence comes first, the audience must hold disconnected facts in working memory while waiting for the point. That is a poor fit for complex investment decisions, where the audience must evaluate price, risk, return, financing, timing, and alternatives at once.

The application to real estate is direct. Every investment committee memo, acquisition recommendation, disposition analysis, refinance proposal, and hold-sell recommendation should state the conclusion in the first paragraph. The rest of the document should support, qualify, and stress-test that conclusion. The analyst’s role is not to show all the work in the order it was performed; it is to convert the work into a decision-ready recommendation.

Preview, Deliver, Recap

Spoken recommendations follow a similar discipline: preview the point, deliver the support, and recap the decision. A strong oral recommendation opens with the conclusion and a brief roadmap, develops two or three supporting points, and closes by restating the recommendation and the specific decision requested. The repetition is not filler. A listener cannot re-read a spoken sentence. The preview helps the audience know what to listen for, and the recap ensures the recommendation survives interruptions, questions, and the natural limits of attention. A clean spoken structure is:

• Preview: "I recommend we acquire Brookhaven Commons at $66 million for three reasons."
• Deliver: Explain the two or three reasons, supported by the most relevant evidence.
• Recap: "For those reasons, I recommend approval to acquire at or below $66 million, subject to final debt terms and diligence."

The Situation-Complication-Resolution Structure

The Situation-Complication-Resolution structure provides a narrative backbone for a recommendation. It is a simplified version of Barbara Minto’s Situation-Complication-Question-Answer framework; the three-part version folds the question into the resolution. It answers three questions:

• Situation: Where are we now? The shared starting point the audience already accepts.
• Complication: What changed? The problem, opportunity, risk, or tension that requires a decision.
• Resolution: What do I recommend, and why? The answer, stated clearly and supported by the strongest evidence.

Applied to Brookhaven Commons — Situation: the fund has approximately $22 million of multifamily equity to deploy in supply-constrained submarkets this vintage. Complication: a 240-unit value-add asset is available at a 5.8% going-in cap, but rising rates have increased exit-cap uncertainty, and the renovation thesis depends on achieving the underwritten rent premiums. Resolution: recommend acquiring Brookhaven Commons at $66 million and phasing the renovation so no more than 30 units are offline at one time. The base case produces a 14.6% levered IRR, and the downside case still clears the fund’s 10.0% return floor.

Core principle: a recommendation is the synthesis of the analysis, not the analysis itself. The analyst’s job is to convert evidence into a decision-ready answer, then organize the strongest support beneath it. Where the structure breaks down: leading with the answer assumes the analyst has reached a defensible conclusion. If the analysis is genuinely unsettled, the honest recommendation may be provisional ("Do not approve yet; complete these three diligence items first"). The structure also depends on audience — a decision-maker usually needs the answer first, while a technical reviewer auditing the model may need the evidence and assumptions in detail.