User Profile
JonManweillerQC
Advocate IV
Joined 1 year ago
User Widgets
Contributions
PitchSide Pro : Reading the revenue game
The brief asked one question: what is driving changes in revenue over time, and where should the business focus next to sustain growth? The audience is executive leadership - people who check the report daily, start with the top line, and want to drill in when something looks off. So the report is built to be instantly clear at a glance and trustworthy under interrogation. This is a 5-page report for PitchSide Pro, a fictional global e-commerce retailer of football merchandise. The headline insight, in one line: growth has been volume-led, not conversion-led - and because revenue is concentrated, the business can add roughly $257K a year with no new traffic by fixing the three things the data points to. The argument runs across five pages, each led by its finding rather than a chart title: Executive Summary 00 - Executive Summary. A stadium-lit cover with a live KPI scoreboard (Net Revenue $2.6M, Orders 23.2K, Margin 53.0%, Conversion 3.23%, each with its year-over-year delta) over four clickable chapter tiles that each preview their own finding. The Growth Engine 01 - The Growth Engine. The driver decomposition: sessions +38% and revenue +43% over five years while conversion held flat at 3.2% - so growth came from more visits, not better conversion. A seasonal sparkline shows the Aug/Sep new-season launch peak, where conversion still barely moves. The Funnel Frontier 02 - The Funnel Frontier. The funnel diagnosis: Web and Mobile close the sale identically (21.7% cart-to-order, both channels), so the entire channel gap is upstream at add-to-cart - and the Americas is the floor (12.6% Web add-to-cart). Where It Comes From 03 - Where It Comes From. The cross-dimension view: two of five categories - Kits + Footwear - drive 79% of revenue; a "Break down by" toggle re-tests the concentration across Region and Segment; and a promo-margin bar shows Launch Week builds margin (55.1%) while Holiday Promo dilutes it (51.0%). Focus Next 04 - Focus Next. The recommendation, made interactive: three what-if levers an exec can move - lift Web conversion (+$198K), extend the already-proven price increase to the flat-priced categories (+$27K), scale the high-margin Collectibles line (+$32K) - totaling $257K/year with no new traffic. Accessibility was treated as a first-class, audited property - not a checkbox. Every one of the 57 visuals carries alt text . For 15 of those visuals the alt text is dynamic and measure-bound - it reads the live values, so the spoken description can never drift from what is on screen (for example, the scoreboard's alt text recomputes net revenue, orders, margin, and conversion for the latest year). Navigation, slicers, and static text carry authored static alt text. Reading order is deliberately banded - title first (100s), then content (1000s), then slicers (7900-8200), then the navigation rail last (9000s) - so a keyboard or screen-reader user gets the finding before the chrome. To make this normally-invisible property reviewable, I built a tooling pass that renders each page with numbered tab-order markers plus a table of every visual's alt text and whether it is static or dynamic. Additionally, a WCAG Compliance validation was done and baked into the theme. My challenges: 1) 5 page limit. I wanted to give the executives the ability to drilldown and drill through into more detailed tables and views. In the end, I chose to tell an end to end story while including as much interaction as possible without overwhelming or overcrowding the page. 2) Limiting the use of HTML/Deneb. With the ever-increasing accessibility of AI and AI tools (skills/CLI/etc) it is easier and easier to let imagination lead the design and have AI build the "impossible" visuals. Thank you so much for looking, I'm happy to answer any questions you may have.Miniviz Week 4: Rhythm of the world
For week 4, I went with one simple idea: colour every country by its local time of day, right now (using six time-of-day buckets) A few things to try within this shape map: Use the legend to spotlight one part of the day and see how many countries are in it Hover any country for its name and local time Drag the time-travel bar (or hit Play) to watch a whole day race around the world Your own time zone is outlined in white It's genuinely live, instead of a stored list of times, each country's local time is worked out right in your browser with Deneb (Vega) so it always shows the real "now," no refresh needed. The world map is embedded straight into the spec so it renders properly once published. Built with Power BI, Deneb (Vega), a little Python for the time-zone data, and a world TopoJSON. One honest simplification: each country uses a single principal time zone (the big ones span several). Thanks to the moderators and this community for another challenge that nudged me to learn something new, would love to hear what you think!
