You pulled the relevant data, built the model, validated the output, and wrote a clear summary. You shared it with the leadership team. And then, nothing. No questions, no discussion, no decisions that you can point to as a result.
This happens regularly in finance. The question worth asking is what makes the difference between analysis that drives action and analysis that quietly disappears?
Solving the Wrong Problem
You identified an interesting pattern in customer churn. You spent a week analysing it. You produced findings showing that customer tenure is declining in specific segments.
One problem, nobody was focused on customer tenure. The business was concentrated on expanding revenue from existing accounts. Your analysis answered a question leadership was not asking.
The most impactful analysis addresses questions that decision-makers are actively working through. Before investing significant time, confirm if this question is on anyone's radar? Will the answer change a decision that is currently in progress?
Burying the Key Finding
Your communication opens with methodology, i.e., data sources, time period covered, analytical approach. The person you are presenting to has stopped reading by the second sentence.
Lead with the conclusion. What did you find? Why does it matter? What should happen as a result?
Everything else is supporting material for those who want to go deeper. Most people will not go deeper. They need the finding quickly, and if it is interesting, they will ask questions.
“Customer churn is accelerating in mid-market accounts at 15% against a historical rate of 8% driven by competitive losses. I recommend piloting a pricing adjustment in the next quarter before this pattern reaches enterprise accounts.” That gets read and discussed. Six paragraphs explaining the methodology does not.
No Recommended Action
Your analysis concludes with "this trend bears watching" or "this is worth monitoring." Those are not action items. They are observations with no follow-through attached.
If something is significant enough to analyse, it is significant enough to have a view on what should happen next. That recommendation might be exploratory. It might be more direct. You might be wrong and that is fine. A concrete recommendation starts a useful conversation. What is not useful is presenting analysis and leaving the decision to someone else with no guidance on where to start.
Wrong Level of Detail
You are presenting to the CFO. Twenty slides of transaction-level detail and granular segment breakdowns. The CFO needs to understand the strategic implication at the business unit level, not the specifics of individual transactions.
You are presenting to an operational team. High-level trends with no actionable specifics. They need to know which locations, products, or customer groups require a response.
Match the level of detail to the audience. Executives need strategic summary with the option to explore further. Operators need specific and actionable findings. One version does not serve both audiences well.
Poor Timing
You completed a detailed review of Q4 performance and shared the findings in February. The leadership team is deep in Q1 execution. Nobody has mental space for Q4 retrospectives right now.
Timing matters significantly. Pricing insights need to reach decision-makers when pricing decisions are being considered. Budget variance analysis is most valuable during the monthly business review cycle. Deliver findings when they connect to active conversations, not when the analysis happens to be complete.
Understand your organisation's decision calendar and build your analysis schedule around it.
Working in Isolation
You completed the analysis independently, then presented the findings. The business unit leaders hearing the conclusions for the first time immediately identify context you were not aware of, and question your assumptions accordingly.
This is not obstruction. They genuinely have information you do not. If you had spoken to them during the analysis, you would have uncovered that context and produced stronger findings.
Involve the right people earlier. Share your hypothesis before you have finalised the analysis. Check your assumptions with the people who run the business day-to-day. Analysis developed collaboratively is much harder to dismiss.