Book Jason to Speak

AudienceUX designers, product teams, design leaders

Why low-fi wireframes fail stakeholders, and how investing in high-fidelity prototypes earlier in the process leads to better decisions, fewer surprises, and products that land the way you intended.

• Why wireframes mislead stakeholders — and what to show instead
• How fidelity level shapes the feedback you get (and don't get)
• A practical framework for deciding when high-fi is worth the investment

AudienceUX designers, product managers, accessibility advocates

Practical frameworks for communicating accessibility requirements to development teams — without jargon, without conflict, and without compromising the design intent.

• Translating WCAG requirements into developer-friendly specifications
• How to frame accessibility as a shared goal, not a design constraint
• Scripts and tools for making accessibility part of the handoff process

AudienceUX designers, interaction designers, design researchers

A new lens for understanding how users experience digital products as events unfolding over time — not just static screens. Draws on cognitive science, film theory, and thirty years of interface practice.

• Why static screens fail to capture how users actually experience interfaces
• Borrowing from film theory to design transitions, pacing, and state
• Practical techniques for mapping time into your design process

AudienceProduct teams, UX designers, founders

Web3 promises decentralization, but most interfaces fail basic usability tests. This talk applies decades of UX thinking to blockchain-based products — showing where the field is failing users and how to fix it.

• The five UX patterns Web3 products keep getting wrong
• How to apply established usability principles to decentralized systems
• Onboarding strategies that don't require users to understand the blockchain

AudienceDesign teams, design managers, cross-functional product teams

A hands-on workshop that gives teams a repeatable methodology for giving and receiving design feedback — structured, specific, and free of personal bias. Participants leave with a critique framework they can apply the next day.

• A four-step critique framework that keeps feedback specific and actionable
• How to separate personal taste from design intent in any review
• Techniques for making cross-functional feedback sessions actually productive

AudienceDesign and engineering teams, design leads

How to build a design system that actually gets adopted — from token architecture and component naming to governance and documentation. Covers what most teams get wrong, and how to course-correct without a rewrite.

• Why most design systems fail adoption — and the organizational fix
• Token architecture and naming conventions that scale across platforms
• A governance model teams can actually maintain without a dedicated team