HKSM

Data representation is the use of visual or structured formats to organize, summarize, and communicate information for shared understanding and decision-making. It includes charts, diagrams, matrices, and maps chosen to fit the purpose and audience.

Key Points

• It is an umbrella technique that turns raw data into visuals such as charts, diagrams, matrices, and maps.
• The choice of representation depends on the question being answered and the needs of the audience.
• Common formats include affinity diagrams, mind maps, stakeholder maps, matrices, histograms, heat maps, and dashboards.
• Effective visuals reduce cognitive load and support collaborative discussion and decisions.
• Representation should be accurate, current, traceable to source data, and clearly labeled.
• It complements data gathering and analysis techniques by making insights visible and actionable.

Purpose

• Reveal patterns, relationships, and trends that are hard to see in raw text or numbers.
• Align stakeholders around a shared view of information and insights.
• Enable faster, evidence-based decisions and prioritization.
• Facilitate workshops by focusing attention and structuring conversations.

Facilitation Steps

1. Clarify the objective and audience: define the question to answer and who will use the visual.
2. Select an appropriate format: choose diagrams or charts that best fit the purpose (e.g., affinity for themes, matrix for trade-offs).
3. Prepare and validate data: gather sources, clean entries, and confirm definitions and scales.
4. Draft the visual: apply clear titles, labels, legends, and consistent units and colors.
5. Facilitate a review or working session: populate, discuss, and refine the representation with stakeholders.
6. Capture assumptions and insights: note key takeaways, thresholds, and unanswered questions.
7. Test for usability: check that the audience can interpret the visual correctly and quickly.
8. Publish and maintain: version, store, and update the artifact as data or decisions change.

Inputs Needed

• Objective or decision to be supported.
• Source data and references, including definitions and timing.
• Stakeholder list and audience needs or preferences.
• Criteria, thresholds, or categories to apply.
• Templates, tools, and style guidelines.
• Governance rules for data quality and version control.

Outputs Produced

• Completed visual artifacts (e.g., affinity diagram, matrix, heat map, dashboard).
• Summarized insights, themes, and patterns.
• Agreed classifications, priorities, or decisions.
• Documented assumptions, data sources, and update cadence.
• Follow-up actions or backlog items derived from the discussion.

Tips

• Start simple and add complexity only when needed.
• Use consistent scales, colors, and labels to avoid misinterpretation.
• Annotate outliers and key thresholds so meaning is obvious.
• Include source and date to reinforce trust and recency.
• Design for accessibility: sufficient contrast, readable fonts, and alt text where applicable.
• Pilot the visual with a small group to check clarity before broad use.

Example

A project team conducts interviews and collects open-ended feedback from stakeholders. To synthesize results, the facilitator uses an affinity diagram to group similar comments into themes, then creates a priority matrix plotting impact versus effort. The combined visuals guide the team to select high-impact, low-effort actions for the next iteration and to document higher-effort items in the backlog.

Pitfalls

• Choosing a format that does not match the question or data type.
• Overloading the visual with too much information and clutter.
• Using biased scales or inconsistent categories that skew interpretation.
• Letting visuals go stale without update dates or version control.
• Assuming stakeholders can interpret the visual without a legend or guidance.
• Skipping data cleaning or validation, leading to misleading conclusions.

PMP Example Question

After a workshop, the team has dozens of sticky notes with qualitative feedback. Which data representation should the project manager use first to organize the information into meaningful themes?

1. Histogram.
2. Affinity diagram.
3. Burndown chart.
4. Control chart.

Correct Answer: B — Affinity diagram.

Explanation: An affinity diagram groups qualitative ideas into themes for sense-making. Histograms, burndown charts, and control charts are quantitative and not suited to initial clustering of text feedback.