Focus PDP Brainstorming — Dot Vote Analysis & Clustering

Source: Miro — "Focus PDP Brainstorming Session", frame "DOT Vote Results"

Compiled 2026-09-23 · Read from the live board via browser automation

TL;DR — 15 dots were placed across 13 ideas/prototypes that came out of the Crazy‑8 sketching round. Votes are heavily concentrated (5 of 13 ideas got 0 votes). The clear winner is a geometry/fit visual diagram replacing the plain spec table (4 votes), followed by a tie between an on‑page navigation / sticky feature‑tab sub‑nav and an inspiration‑style, less "hard sell" discovery layout (3 votes each), and embedding a short brand video (2 votes). These four should be the seed for the first ticket(s).

1. How the voting worked

Six colored dot types were available for voting (cyan, green, yellow, red, pink, purple) — no name labels were attached to the colors on the board, so we can't attribute a vote to a specific person, only count colors as independent "voter tokens".

15 dots were used in total and, notably, split perfectly evenly — 3 dots per color for 5 of the 6 colors, and the pink color was never used. This strongly suggests a "3 dots per participant" voting rule with 6 participants, one of whom (pink) did not vote or was absent for that round.

📎 Reference screenshot — dot‑voting legend + on‑page‑navigation cluster (click to expand)

Dot voting legend and on-page navigation cluster

2. Full tally — all clustered ideas, ranked

#	Idea / prototype (as written on the sticky)	Votes	Dot colors	Priority read
1	HMW show a geometry/fit diagram instead of a plain spec table, so visitors understand sizing visually (+ "highlight more important stuff in bigger fonts" note, + rough numeric spec table sketch)	4		Top pick
2	HMW let the user know what area/section he is in on the PDP (on‑page navigation) — sticky sub‑nav with tabs (Overview/Features/Specs&Geo/FAQ) + collapsible configurator sidebar (accessory add‑ons)	3		Top pick
3	"Move away from direct sales without making it a scavenger hunt to buy" — inspiration board of magazine/discovery‑style layouts (DJI‑like "Inspiration in every direction")	3		Top pick
4	HMW embed a short brand video on the PDP or support page, similar to Rimowa	2		Worth exploring
5	Sticky/persistent e‑commerce bar (price + Add to Cart always visible while scrolling)	1		Nice‑to‑have
6	HMW make bike/color/size selection feel as guided & confident as live visual feedback (Porsche‑style configurator)	1		Nice‑to‑have
7	Model comparison / switching cluster — 3 overlapping HMWs: "show/switch to other bike models within…", "compare the bikes in the PDP", "add a visual comparison against other models" (next to a Cayenne‑style 3‑card layout and a "Which ATLAS is right for you" spec‑comparison table)	1		Ambiguous — vote may apply to any of the 3 stacked notes
8	"Like the tabs" (reaction sticky on a Model Y‑style spec card)	0	—	No signal
9	HMW add the configurator in a nice spot ("Pushes boundaries" lifestyle hero + Find a Dealer/Configure CTAs)	0	—	No signal
10	HMW tell a story (SRAM Rival XPLR AXS product‑story hero image)	0	—	No signal
11	Storytelling copy reference (Colnago C72 "La Scala" exclusive‑edition narrative copy example)	0	—	Reference only
12	3‑card model comparison reference (Cayenne Electric / S Electric / Turbo Electric style layout)	0	—	Reference only
13	"Which ATLAS is right for you" full spec‑comparison table reference (PROPAIN‑style)	0	—	Reference only

📎 Reference screenshot — clusters 1‑5 (inspiration board, on‑page nav, configurator‑spot hero, brand‑story hero)

📎 Reference screenshot — clusters 6‑10 (e‑commerce bar, model comparison cards, spec table, HMW compare stack)

📎 Reference screenshot — Frame 2: geometry/fit diagram idea + guided configurator idea (clusters 1 & 6 in tally)

📎 Reference screenshot — Frame 1: brand video idea (rank 4)

3. Clustering — grouping the 13 ideas into themes

Theme	Ideas in it	Combined votes
A. Orientation & navigation within the PDP	On‑page sub‑nav w/ configurator sidebar (#2)	3
B. Visual/emotional storytelling & discovery	Inspiration/discovery layout (#3), Brand video (#4), Tell‑a‑story hero (#10, 0 votes), Storytelling copy ref (#11, 0 votes)	5
C. Sizing & specs comprehension	Geometry/fit diagram (#1)	4
D. Model comparison / configurator guidance	Model comparison/switching (#7), Porsche‑style guided config (#6), Comparison cards ref (#12, 0), ATLAS spec table ref (#13, 0)	2
E. Persistent purchase CTA	Sticky e‑commerce bar (#5)	1
F. Configurator placement/entry point	Configurator "nice spot" hero (#9, 0 votes)	0

4. Insights & conclusions

Sizing is the single strongest pain point — the geometry/fit visual diagram idea outscored everything else. The team believes today's plain spec table doesn't let customers self‑assess fit, and a visual/diagram treatment is seen as high‑value.
Wayfinding on a long PDP is the #2 concern — a persistent sub‑nav (Overview/Features/Specs&Geo/FAQ) tied for 2nd place, indicating the current PDP is felt to be long/scroll‑heavy and users may lose orientation.
There's real appetite to soften the "hard sell" feel — the inspiration/discovery‑style layout tied for 2nd, and brand video (Rimowa‑style) came 4th. Combined, "make the PDP feel more editorial/inspirational rather than a spec sheet" attracted 5 of 15 votes (a third of all votes) — the single biggest combined theme.
Model comparison ideas underperformed expectations despite three separate HMWs and two reference images dedicated to it — only 1 vote total. This may mean the team already has partial confidence here, or the ambiguity of 3 stacked stickies split attention/votes.
Configurator placement and "tell a story" hero got zero votes even though they were sketched — deprioritize unless new evidence emerges.
Voting distribution (3/3/3/3/3/0) suggests 6 people had 3 dots each and one participant abstained — worth double‑checking attendance/voting completeness before treating the "0‑vote" ideas as fully rejected.

5. Suggested ticket(s) to open

Recommendation: split into up to 3 tickets by theme so they can be sized/prioritized independently, or a single epic with these as sub‑tasks.

Ticket 1 (highest priority) — Visual geometry/fit diagram on PDP

Problem: The current spec table lists numeric geometry values only; customers can't easily tell if a bike/size fits them.
Proposal: Replace/augment the plain spec table with a visual geometry diagram (labeled bike silhouette with key measurements), and increase font size/prominence of the most decision‑critical specs.
Votes: 4/15 (highest)
Next step: UX to produce a hi‑fi mockup; validate against real geometry data source (currently sketchy numbers: 623 / 18 / 7.5 / 850‑1150 / 3500 mm — need real field mapping).

Ticket 2 — Sticky on‑page navigation for long PDPs

Problem: Long PDP makes it hard to know which section (Overview/Features/Specs&Geo/FAQ) you're currently viewing.
Proposal: Sticky sub‑nav bar with tab‑style anchor links + scroll‑spy active state; evaluate bundling the configurator/accessory sidebar (Prep Pocket/Hawaii Rack style options) into the same nav.
Votes: 3/15 (tied 2nd)

Ticket 3 — More "editorial" / inspiration‑led PDP sections

Problem: PDP currently feels transactional/hard‑sell; team wants a more inspirational, magazine‑like feel (DJI‑style "Inspiration in every direction") to soften the direct‑sales impression, potentially combined with a short brand video (Rimowa‑style).
Votes: 3 + 2 = 5/15 combined (largest combined theme)
Next step: Needs a content/asset owner (video production) — flag as a bigger, cross‑functional effort vs. the two engineering‑only tickets above.

Lower‑priority / defer: sticky e‑commerce bar (1 vote), Porsche‑style guided configurator (1 vote), model‑comparison/switching (1 vote) — revisit once the top 3 are shipped and if user research reinforces demand.

6. Caveats

Dot colors aren't mapped to names on the board, so we can't weight votes by role (e.g. PM vs. engineer) or check for a single person dominating a category.
The "model comparison" cluster has 3 overlapping HMW stickies sharing 1 dot — worth clarifying with the team which exact idea the vote was for before scoping a ticket.
This analysis covers the "DOT Vote Results" frame only (plus its embedded "Frame 1"/"Frame 2" sub‑groups); it does not re‑derive conclusions from the earlier Crazy‑8s or "How might we" frames beyond what's already reflected here.