The Art of Making an Effective Recommendation

As a student, you're evaluated on what you know — tests, papers, exams. But when you transition to internships and ultimately a salaried career, the game changes completely. As a knowledge worker, you're compensated for results. And in most cases, those results come from one critical skill: making observations and turning them into actionable recommendations that you or others will act on.

This isn't something they teach you in school. But it's something you'll do almost every day in your career.

Think about it: Should we pursue this market opportunity? Which vendor should we select? How do we fix this process? What's causing customer complaints? In every case, someone needs to investigate, analyze, and recommend a course of action. That someone will increasingly be you.

This post will teach you who receives recommendations, what makes them effective, how to structure them, and how to deliver them well. Master this skill early, and you'll stand out from day one.

One note before we dive in: a recommendation is rarely the end of the process. Once approved, the next step is typically a draft implementation plan — often called a project charter — that outlines resources, timeline, and key players. That's an essential topic we'll cover in an upcoming post.

Who Receives Recommendations?

Recommendations flow in many directions, and knowing your audience shapes everything — your language, your level of detail, and how you frame the ask.

Here's something important: the more significant the recommendation, the more audiences it will reach. A recommendation might start with your manager, get refined, move to a director, then to an executive team or steering committee — and for major strategic decisions, perhaps even to a board of directors. Your recommendation needs to survive and resonate at each level. Understanding these audiences helps you anticipate how your recommendation will travel.

• Managers & Direct Supervisors — Your most frequent audience. They need recommendations that help them make decisions, solve problems, or improve operations. They have context but still value clarity and efficiency.

• Executive Leadership & Steering Committees — High-stakes audiences. They're time-poor and decision-rich. When presenting to executives, you may have just minutes to make your case. They want to know what you recommend, why it matters, and what it requires.

• Cross-Functional Peers — In collaborative workplaces, you'll often need to influence colleagues who don't report to you. These recommendations require building consensus and demonstrating mutual benefit.

• Boards of Directors — For those who advance into senior roles, board presentations are the ultimate test. Board members want strategic insight and judgment, not operational detail.

• Clients & External Stakeholders — In consulting, sales, or client-facing roles, your recommendations become your product. Your credibility is built one recommendation at a time.

Characteristics of a Effective Recommendation

Not all recommendations are created equal. The best ones share these traits:

• Clear and Direct — Don't bury the lead. State your recommendation upfront. Barbara Minto, the first female MBA hired at McKinsey, developed the "Pyramid Principle": start with your answer, then provide supporting arguments. If your conclusion is on page 12, busy executives may never see it. Put it on page 1.

• Structured for Retention — For significant recommendations, open with an executive summary that captures your recommendation and why it matters. Then follow the classic structure: tell them what you're going to tell them (executive summary), tell them (the full recommendation with supporting evidence), then tell them what you told them (conclusion). This repetition isn't redundant — it's how busy decision-makers absorb information.

• Grounded in Evidence — Your recommendation must be built on facts, data, and observable findings — not hunches. The strongest recommendations point to specific evidence.

• Actionable — A recommendation without a clear path forward isn't useful. Answer not just "what" but "how."

• Aligned with Strategic Goals — Connect your recommendation to organizational priorities. How does this generate revenue, control costs, improve efficiency, or better serve customers?

• Honest About Trade-offs — Every recommendation has costs, risks, and downsides. Acknowledging them builds credibility; ignoring them destroys it. And articulate the risk of not acting — sometimes the cost of inaction is the most compelling part of your case.

• Appropriately Scoped — Know when a recommendation needs executive approval versus when it's within your authority to act. Not everything requires a formal presentation.

The Nine Components of a Effective Recommendation

Structure matters. Here's a proven format that dramatically increases the chances your recommendation gets accepted:

1. Problem Statement What problem are you trying to solve? This aligns everyone before discussing solutions. If people disagree about whether something is even a problem, they'll never agree on the solution.

"Our sales team is losing deals because they can't access customer information while in the field."

2. Methodology How did you investigate this? What data did you analyze? Who did you consult? Explaining your process establishes credibility.

"We surveyed 40 sales reps, analyzed CRM access logs, shadowed three reps on client visits, and reviewed competitors' mobile capabilities."

3. Finding What did you discover? State the facts.

"78% of reps reported pulling over to use laptops between meetings. Average time lost: 35 minutes per day. Reps with tablet access closed 23% more deals."

4. Conclusion So what? Why does this finding matter?

"Lack of mobile CRM access is costing us sales productivity and competitive wins."

5. Alternatives Considered What other options did you evaluate, and why were they rejected? This shows rigor and prevents the "did you think about..." questions.

"We considered (a) providing laptops with mobile hotspots — rejected due to cost and inconvenience; (b) limiting field access to email summaries — rejected as insufficient for client meetings; (c) deploying a mobile CRM app — recommended."

6. Recommendation State the specific action you propose, including anticipated costs.

"Deploy the mobile CRM application to all 40 field sales reps at a cost of $18,000 annually, with a two-week training rollout."

7. Benefit Quantify the upside. Make it concrete.

"Based on pilot results, we project a 15% increase in closed deals, representing approximately $200,000 in additional annual revenue."

8. Risk What could go wrong if we act? What happens if we don't? Sometimes the risk of inaction is greater than the risk of moving forward.

"Risks include adoption challenges and initial productivity dip during training (mitigation: phased rollout with super-users). However, doing nothing means continued lost deals and falling further behind competitors who already have mobile access."

9. The Ask What specifically do you need from your audience? Approval to proceed? Funding? A decision by a certain date? Assignment of resources? A recommendation without a clear ask leaves people nodding but not acting. Be explicit about what you need and when you need it.

"We are requesting budget approval of $18,000 and IT support to begin the pilot rollout on March 1."

This format works because it forces alignment on the problem, demonstrates rigorous analysis, shows you considered alternatives, honestly assesses both upside and risk, and closes with a clear ask.

Delivering Your Recommendation

How you deliver matters as much as what you deliver.

• Consider Pre-Distribution — Should you share your recommendation before the meeting? There are trade-offs. Pre-reads give decision-makers time to absorb and formulate thoughtful questions. But sometimes it's more effective for everyone to hear the same information simultaneously — it ensures consistent understanding and lets you control the narrative. Consider your audience and the political dynamics.

• Lead with the Answer — In school, you build to a conclusion. In business, flip it. State your recommendation first, then provide supporting logic. This respects your audience's time and lets them decide how deep to go.

• Know Your Audience — Some executives want data; others want the strategic view. Engineers appreciate evidence; sales leaders want the benefit. Adapt your emphasis.

• Anticipate Objections — Before you present, think about pushback. Address concerns proactively. If possible, talk to key stakeholders beforehand to understand their reservations.

• Be Prepared to Go Deeper — Have your detailed analysis ready, but don't lead with it. If decision-makers want more, they'll ask. Think of your presentation as a pyramid: main message at the top, supporting arguments in the middle, detailed evidence at the base.

• Match Medium to Stakes — Not every recommendation needs a deck. Sometimes a well-crafted email works. Sometimes a brief conversation is enough. Match your approach to the complexity and significance of the decision.

• Build an Effective Deck — When you do present, keep it tight. Every slide should earn its place. Use visuals to clarify, not decorate. Avoid walls of text — if you're reading slides aloud, you've lost the room. Your deck should guide the conversation, not replace it.

Why This Matters for Your Career

Making effective recommendations is core to how knowledge workers deliver value. It's how you demonstrate strategic thinking, not just task completion. It's how you earn a seat at the decision-making table.

Early in your career, you might think your job is to gather information and let others decide. But professionals who advance are those who develop a point of view, back it with evidence, and have the courage to say: "Here's what I recommend."

Start Now: What You Can Do as a Student

You don't need to wait for your first job to build this skill. Here's how to practice today:

• In class projects, don't just present findings — make a recommendation. State what your team thinks should happen and why.

• In student organizations, when you see something that could be better, structure your idea using the nine components. Problem, methodology, finding, conclusion, alternatives, recommendation, benefit, risk, and the ask.

• In internships, look for small opportunities to recommend improvements. Even suggesting a better way to organize files or run a meeting counts — it shows initiative and structured thinking.

• When making any request, practice leading with the ask and following with the justification. Flip your natural instinct to build up to the point.

• Get feedback. Ask a mentor, professor, or supervisor: "Was my recommendation clear? Did I miss anything? How would you have structured it?"

The skill of making effective recommendations isn't just about getting your ideas approved. It's about becoming the kind of professional others turn to when important decisions need to be made.

Start practicing now.

References

1. Minto, B. (1987). The Pyramid Principle: Logic in Writing and Thinking. Pearson Education.

2. Leadership Strategies. "Keys to Writing Powerful Recommendations." https://www.leadstrat.com/

3. Chambers, A. "5 Steps to Crafting an Impressive Recommendation." Entrepreneur, 2023.

4. Ranadive, A. "The Pyramid Principle." Lessons from McKinsey, Medium.

5. O'Hara, C. "The Right Way to Present Your Business Case." Harvard Business Review, July 2014.