Which customer patterns needed product attention, readiness work, or a stronger measurement path?
Customer Signals at Scale · Participatory research · evidence architecture
Designing customer research at scale.
A connected research system turned structured participation from 100+ customer practitioners into evidence that could be compared, interpreted, and reused.
Public-safe caseNames, values, visual language, and identifying details are reconstructed.
Priority vs. measurability Priority Confidence
Question → pattern → decision
Five linked participatory activities
Governed workbook + decision views
A large customer gathering created access to many perspectives at once, but without a research system it could have ended as a wall of disconnected notes.
I led the research framing, designed the evidence structure with collaborators, owned the workbook and synthesis, and created the interactive dashboard.
Five interconnected activities used a common customer-level structure, allowing patterns to be joined across metrics, blockers, readiness, and capability states.
The dashboard and synthesis were reused in leadership and product-excellence discussions and became the foundation for continued customer and measurement work.
Public-safe dashboard reconstruction
Four views, four different decisions.
The figures are synthetic. The interaction preserves the research logic while removing customer, product, and commercial details.
Priority versus measurability
PriorityMeasurement confidenceSynthetic index · low to high
Deflection
AI impact
Knowledge
Experience
Capacity
Resolution
LowerHigher
The event was one moment inside a longer research program.
Earlier customer work had surfaced a proof problem. The large gathering became the scale-validation and activation phase, with questions designed to test whether those patterns held across a much broader customer population.
Interconnected activities produced comparable evidence without flattening context.
The activities examined what customers needed to measure, what blocked adoption, how ready organizations were for AI, and whether capabilities were proven, felt but unmeasured, or dormant. The same customer marker connected the evidence across activities.
The strongest pattern was an inversion between importance and measurability.
The outcomes customers most needed to defend were often the ones with the weakest measurement path. The research distinguished this from a generic request for more dashboards and connected it to product, enablement, and adoption decisions.
The dashboard turned a one-time room into a reusable evidence system.
A governed workbook preserved denominators, source notes, joins, interpretation, and confidence. The interactive layer let leaders move from a portfolio pattern to the underlying activity without exposing customer identities.
What the work enabled
A reusable customer evidence system.
Converted structured participation into a governed, reusable dataset rather than a workshop recap.
Separated core adoption barriers from AI-specific readiness barriers.
Made the gap between capability purchase, activation, felt value, and provable value visible.
Supported leadership discussion, product-excellence follow-up, and a continued research roadmap.
Public case boundary
The public reconstruction uses synthetic values and neutral labels. It demonstrates the research logic, not the original customer dataset or internal commercial interpretation.