What Is a Recommendation?
A recommendation is the final answer you give after completing all analysis, insights, and synthesis.
It tells the client what they should do, why, and how.
A strong recommendation is:
- Clear
- Actionable
- Prioritized
- Evidence-backed
- Feasible within constraints
It is the point where all your consulting tools come together.
Why Recommendation Structure Matters
Leaders don’t have time to go through pages of analysis.
They want:
- The answer
- The reasoning
- The impact
- The next steps
A good recommendation makes decision-making fast and confident.
A weak one leaves stakeholders confused.
The Consulting Recommendation Structure (Step-by-Step)
1. Start with the main recommendation (answer-first)
This is the one-sentence headline.
Example:
“Improve onboarding speed by optimizing Step 2 to reduce churn by 5–6 percentage points.”
It must directly answer the problem statement.
2. Give 2–3 supporting reasons
These are the strongest insights from synthesis.
Example:
- 70% of churn comes from first-week users
- 55% drop-off occurs at Step 2
- Slow load time is the primary complaint from new users
These convince the client why the recommendation is correct.
3. Describe the expected impact
This shows business value.
Example:
“Fixing Step 2 improves retention by ~5–6%, increasing net revenue by ₹12–15 crores annually.”
Impact makes recommendations compelling.
4. Provide immediate next steps (action plan)
Clients love clarity on what to do starting tomorrow.
Example:
- Conduct technical review of Step 2 backend logic
- Set performance benchmark targets
- Run A/B test for speed vs completion
- Roll out update to 100% of new users
This moves the client from insight → action.
5. Outline risks and dependencies
Be transparent and professional.
Example:
- Engineering bandwidth needed for fixes
- Dependency on third-party API
- Possible dip in conversion during testing
Acknowledging risks builds trust.
6. Provide a timeline or roadmap
Not too detailed — just high level.
Example:
- Weeks 1–2: Diagnosis & redesign
- Weeks 3–4: Implementation
- Week 5: Testing
- Week 6: Full rollout
This helps leaders visualize execution.
Mini Example (Complete Recommendation)
Recommendation:
“Optimize onboarding Step 2 to reduce friction and lower churn.”
Supporting reasons:
- Step 2 accounts for 55% of drop-off
- Slow load time increased after the March update
- Early users drive 70% of total churn
Expected impact:
“Reducing load time to under 2 seconds can improve retention by 5–6%.”
Next steps:
- Conduct backend performance audit
- Redesign content load sequence
- Launch A/B test
- Roll out improvements
Risks & dependencies:
Potential engineering delays.
Concise. Clear. Action-focused.
The 3 Types of Consulting Recommendations
1. Strategic Recommendations
High-level choices affecting long-term direction.
Example:
“Enter Tier 2 cities via marketplace model.”
2. Operational Recommendations
Improvement of internal processes.
Example:
“Reduce warehouse picking time by redesigning the layout.”
3. Tactical Recommendations
Short-term or granular actions.
Example:
“Move help-center CTA to the home screen.”
Common Mistakes to Avoid
- Giving too many recommendations at once
- No prioritization or impact sizing
- Recommendations not linked to insights
- Overly generic suggestions
- Too high-level with no action plan
- Not addressing risks or feasibility
A great recommendation should feel:
👉 Practical
👉 Logical
👉 Backed by data
👉 Easy to act on
Where Recommendation Structure Is Used
- Final slides
- Board meetings
- Case interviews
- Strategy projects
- Operational improvement
- Product recommendations
- Every problem-solving engagement
A recommendation is the final output of the consulting toolkit.