CompTIA Data+ DA0-002 · Free study guide

Objective 3.1 — Choose a communication approach

An analysis is useful only when its audience can understand, trust, and act on it. A correct model can fail if an executive receives row-level detail, an operator receives only a quarterly average, or a color-coded dashboard excludes part of its audience. The exam treats communication as a design problem: identify the decision, persona, sensitivity, and necessary detail before choosing a deliverable.

The best answer is rarely “include everything.” It is the approach that gives a specific audience enough evidence to make its decision without creating confusion or unnecessary exposure.

Confirm the requirement before building

A request such as “show customer performance” is not a complete requirement. The analyst should clarify what performance means, who will consume the result, what action follows, and how current the result must be. Useful confirmation questions include:

• What decision will this analysis support?
• Which measures and dimensions define the question?
• What period, comparison, target, and level of detail are required?
• Who may see the result, and which fields are sensitive?
• Will the audience explore the data or receive a fixed summary?
• How often must the information refresh?
• What would make the audience consider the result successful?

A mock-up is a low-cost representation of the proposed result. It may show placeholder KPIs, chart positions, filters, labels, and navigation without connecting to production data. Mock-ups expose disagreement early. A stakeholder may discover that “monthly revenue” should mean recognized revenue rather than orders booked, or that a regional filter is essential. Correcting a sketch is cheaper than rebuilding a finished dashboard.

Record metric definitions, assumptions, accepted mock-ups, and access constraints as the shared baseline for later changes.

Match detail and language to the persona

Different audiences can need different views of the same underlying analysis.

A C-suite audience needs the signal before the method: what changed, distance from target, business importance, and the requested decision. An individual contributor often needs records behind the signal. A technical reviewer may need logic and limitations, while a non-technical stakeholder needs their practical consequences.

Internal does not mean unrestricted; employees still receive only role-appropriate information. External communication requires additional review because recipients may lack context and authorization for operational detail.

Design for visual and auditory accessibility

Accessibility is part of correctness. If the intended audience cannot perceive the result, the result has not been communicated.

For visual accessibility, use readable type, sufficient contrast, clear labels, and a logical reading order. Do not encode meaning with color alone. A red and green status display should also include text, symbols, or patterns. Give charts descriptive titles, label units, and provide a text summary of the important finding. Tables and interactive controls should be usable with a keyboard and should have meaningful names for assistive technology.

For auditory accessibility, do not make sound the only way an alert or explanation is delivered. Videos and spoken briefings need accurate captions or transcripts. An audible threshold alert should also create a visible notification. If a presentation describes a chart verbally, the speaker should state the pattern and conclusion rather than saying only “as you can see.”

Control sensitive information and granularity

The communication layer should expose the minimum detail needed for the decision. Sensitive information can include personal identifiers, health or payment data, confidential financials, employee records, security information, and commercially restricted partner data.

Useful controls include aggregation, masking, suppression of very small groups, approved extracts, and row- or column-level access. Hiding a field visually is not the same as securing it; the underlying export or query path must enforce the restriction. Detail should also match analytical grain. An executive KPI may be aggregated by month, while an authorized case worker may need individual records.

Combinations of harmless-looking fields can re-identify someone even after a name is removed. External reports need a disclosure review, not merely deletion of one obvious identifier.

Define KPIs so they can guide a decision

A key performance indicator is a measure tied to an objective, not simply any available number. A defensible KPI has a clear formula, owner, unit, time window, population, target, and refresh cadence. “Conversion rate” is ambiguous until the numerator, denominator, qualifying events, and attribution period are defined.

Provide context with the value. A rate of 8% means little without a target, prior period, benchmark, or sample size. Avoid vanity metrics that rise without representing the desired outcome.

Worked scenario: one analysis, three audiences

A retailer finds that product returns rose from 6% to 9%. The analyst first builds a mock-up and confirms that the KPI is returned units divided by delivered units, not orders placed. The mock-up also reveals that finance wants return cost while operations wants affected products and stores.

For the chief operating officer, the analyst presents the return-rate trend, the three categories driving the increase, estimated cost, target, and the requested decision. For store managers, the analyst provides an authorized dashboard with store, product, and reason filters plus the affected transactions needed for follow-up. For an external supplier, the analyst shares only that supplier’s aggregated product results and removes customer and employee fields.

The trend uses labels and markers as well as color. A text summary states that the increase began after a packaging change and is concentrated in two product lines. The executive receives a decision-ready signal, managers receive operational detail, and the supplier receives only approved scope. The calculation is the same; communication changes with persona, purpose, accessibility, and sensitivity.

Common exam traps

• Building immediately from an ambiguous request instead of confirming definitions with a mock-up.
• Giving executives every available detail because more data appears more rigorous.
• Giving individual contributors only a high-level KPI with no path to actionable records.
• Treating technical and non-technical audiences as differences in intelligence rather than differences in context and task.
• Using red and green alone to communicate status.
• Assuming an internal audience may see all fields.
• Removing names but leaving combinations that can re-identify individuals.
• Calling any measured value a KPI without linking it to an objective and target.
• Hiding a sensitive column in a chart while leaving it available in the downloadable data.

Readiness checklist

• I can turn a vague request into decision, audience, metric, detail, cadence, and access requirements.
• I can explain how a mock-up confirms requirements before expensive implementation.
• I can tailor one analysis for C-suite, individual-contributor, technical, non-technical, internal, and external personas.
• I can name visual and auditory accessibility practices and avoid color-only meaning.
• I can choose an appropriate level of detail without exposing unnecessary sensitive information.
• I can define a KPI with a formula, population, time window, target, owner, and context.
• I can recognize when aggregation, masking, suppression, or row- and column-level controls are needed.
• I can justify a communication choice by the decision it enables.