Chapter 1.6 · Communication Fundamentals
Analysis creates value only when another person can understand its meaning and decide what to do next. An executive rarely needs to see every calculation, while a finance reviewer may need the full reconciliation and source definitions. Communicating findings well therefore requires both accuracy and judgement about the audience.
In Meridian Retail, a chart showing declining revenue is not yet a recommendation. The analyst must explain how the movement was measured, where it is concentrated, what competing explanations remain possible and which next step is reasonable. This chapter develops the discipline of turning numbers into a clear, decision-ready story.
- Tailor messages to audiences
- Separate observations, insights and recommendations
- Select honest chart formats
- Explain evidence and limitations
- Prepare a one-page executive insight brief with next actions and owners
1.6.1 Know your audience and the decision
Start every communication with two questions: “Who will use this?” and “What decision must they make?” A board-level audience may want headline risk, business impact, options and the recommended next action. A commercial manager may need channel detail and an experiment plan. A data owner may require exact definitions, filters and exception counts.
The facts should be consistent across audiences even when the presentation differs. Simplification must not mean changing definitions or concealing uncertainties. A strong analyst can explain the same finding in one sentence, one chart and a detailed appendix without contradicting any of them.
1.6.2 Observation, insight and recommendation
An observation describes what the data show: “September revenue was 20% below August.” An insight interprets a consequential pattern: “The online channel contributed 80% of the total observed decrease, so it should receive initial diagnostic attention.” A recommendation proposes a defensible action: “Verify online traffic and order tracking, then review the checkout funnel before allocating promotional spending.”
These statements have different levels of inference. If the recommendation depends on an untested assumption, name it. Avoid confident causal language merely because executives prefer decisive slides. Being clear about evidence is a sign of professionalism, not indecision.
1.6.3 Charts that make comparisons fair
Choose charts for the question. Use bars when comparing categories, lines for consistent time intervals, and tables when exact values and definitions matter. Clearly label units, reporting dates and categories. A bar chart with a truncated axis may make small differences appear dramatic; a time-series chart with missing periods can imply an artificial trend.
For Meridian, two side-by-side bars showing August and September channel revenue make the online decline easy to see. A waterfall could show how online and store movements contribute to the overall change. A line chart would be useful for day-by-day patterns only if the underlying daily measurements were reliable and comparable.
A chart should have one clear point. The title can express the conclusion—“Online accounted for most of September's sales decline”—provided the numbers support it. Footnotes should state data sources and relevant limitations, not be used to bury them.
1.6.4 Building an executive narrative
A useful one-page brief follows a simple reading sequence: decision needed, headline finding, evidence, caveats and recommended next actions. Start with the main answer, not an extended explanation of how the spreadsheet was created. Support it with a small number of well-labeled figures.
For example: “September net revenue declined by ₹2,00,000 (20%). The online channel represented ₹1,60,000 (80%) of that movement. Order volume declined while average order value remained at ₹2,000. Before making changes, the team should validate online session tracking and investigate checkout and availability trends.”
This paragraph gives the reader the scale, location and plausible priority without overstating the evidence. It also explains what information should be gathered next.
1.6.5 Explaining assumptions, limitations and uncertainty
Uncertainty can arise from missing records, inconsistent definitions, small samples, seasonal effects, incomplete data access or the absence of a controlled comparison. The analyst should distinguish limitations that may materially change the conclusion from minor issues. For example, if website sessions were collected differently between months, the conversion comparison may not be valid until the tracking change is understood.
Never present a forecast as a certainty or an association as proof of cause. Where practical, show ranges, alternative scenarios or the exact population used. Explain the implications in business language: “Traffic tracking needs validation before we can rely on the conversion-rate movement.”
1.6.6 Recommendations with owners and measures
A recommendation becomes more useful when it includes an action, owner, deadline and measure of success. “Improve sales” is not actionable; “E-commerce operations will check checkout error logs and compare completion rates by device by Wednesday” can be assigned and reviewed.
| Next action | Owner | Evidence to collect | Decision point |
|---|---|---|---|
| Verify session tracking | Analytics engineering | Event definitions and tracking changes | Can conversion be compared fairly? |
| Inspect checkout friction | E-commerce operations | Errors, device breakdown, funnel stages | Is a targeted test justified? |
| Review stock availability | Merchandising | Out-of-stock products by day | Were affected products material? |
1.6.7 An example one-page insight brief
Finding: Net revenue fell 20% month on month. Online explained 80% of the total revenue reduction; store revenue also declined.
Supporting evidence: Completed orders declined from 500 to 400. Average order value was ₹2,000 in each period. Online session-based conversion was 5.00% in August and approximately 3.67% in September, assuming comparable session definitions.
Limitation: These comparisons do not establish the cause of the decline; traffic measurement and contextual business changes require validation.
Next action: Validate tracking, review checkout and stock patterns, and return with a prioritized, measurable test plan.
1.6.8 Chapter and module summary
Good analytical communication is concise without becoming careless. Choose a story that matches the audience's decision, distinguish observation from interpretation, use fair visuals, state caveats and propose actions that can be tested. Across Module 01, the complete professional habit is to frame a business problem, understand its data, define its metrics, follow a controlled methodology and communicate evidence for action.