Larger axis/legend text and a continuous fill scale improve readability when differences are subtle (Ch. 24). A 2D polygon map avoids distortions (Ch. 26).
Why this topic. I examined U.S. market acquisition patterns to understand where activity concentrates and how it changes over time. This topic aligns with my work need to demonstrate performance and compliance in a way that’s clear to non‑technical stakeholders. …
Why these visuals. I combined six views, each with a specific job. A choropleth highlights spatial coverage, while a symbol map overlays relative magnitudes without clutter. A ranked bar chart surfaces the top cities and communicates exact values with labels. The compliance band presents a shaded “in‑compliance” region and a dashed threshold so small differences are easy to see. A boxplot summarizes distribution and potential outliers across states, and a state–time heatmap (or bar fallback) shows temporal clustering. These choices follow the week’s guidance: use larger labels for readability, avoid ambiguous line drawings, and don’t use 3D effects. …
Why this format. A flexdashboard keeps all visuals in one printable PDF with consistent styling and sectioning. Stakeholders can scan quickly, then focus on the panel most relevant to their decisions. …
Findings. Acquisitions are unevenly distributed: a subset of states and cities contributes a disproportionate share. Where dates are present, periods of increased activity appear, which can inform staffing or outreach. The compliance view makes pass/fail status immediately visible even when results are near the target. …
Ethical impacts. Mapping and ranking geographies can unintentionally stigmatize locations or enable over‑targeting. If combined with store‑level or customer identifiers, there are privacy risks and potential re‑identification concerns. Color choices can also imply value judgments. …
Mitigations. Aggregate to appropriate geographies; anonymize or suppress sensitive fields; document data quality and collection limits; use neutral color palettes; and include context about how the data should (and shouldn’t) be used. Provide the compliance definition, denominator, and thresholds explicitly so results are interpreted correctly. …