Methodology Work Perspectives Contact
hello@jeremysmith.pro

Strategic Framework

The Experience
Algorithm.

Role

Framework Author

Responsibilities

Framework design, AI prompt engineering, Stakeholder rollout

Collaborators

Product Management, Investment Council, New Product Development Teams

Usable Equitable Useful Enjoyable SustainableSuccess Engaging Accessible Universal Delightful Inclusive Functional Empowering Intuitive

01 · Context

Capital
Misallocation.

The enterprise exhibited a recurring pattern of misallocated capital: funding and launching high-investment products based on executive mandate rather than validated market need. Ethnographic research was routinely bypassed to accelerate development timelines.

To bridge the gap between qualitative user risk and quantitative financial outcomes, I architected The Experience Algorithm. This framework translated standard UX heuristics into a predictive risk model, establishing a direct correlation between usability pillars and financial imperatives like Customer Lifetime Value (CLV) and Monthly Recurring Revenue (MRR).

02 · Architecture

The Logic
Engine.

To operationalize this model without adding administrative friction, I developed an LLM-driven parsing engine. This tool ingested standard product documentation - PRDs, MRDs, and Investment Memos - and objectively scored the proposed features against the Experience Algorithm matrix.

By defining specific downstream business impacts (Operational Efficiency, Market Penetration, Consumer Relationship Capital, Value Proposition), I translated "design speak" into the explicit language of an Investment Council. Explore the algorithmic logic below.

System Depth

Select Pillar

03 · Resolution

Governance
Over Guidance.

During initial piloting with New Product Development, the algorithm successfully exposed critical validation gaps in multiple investment-stage products that human review had overlooked. However, the pilot revealed a critical organizational insight: the friction was not methodological, it was structural.

Product managers are intrinsically incentivized to advance through funding gates, creating a disincentive to self-report validation gaps or pause for research. It became evident that the strategic value of Experience Algorithm was not as a guidance tool for PMs, but as an automated diligence gate for the Investment Council.

A framework that predicts adoption failure before funding is approved is most valuable to those allocating the capital. While organizational restructuring paused full programmatic deployment, the architectural logic remains a viable, scalable mechanism to prevent the funding of unvalidated products. Identifying a single flawed PRD prior to engineering allocation represents hundreds of thousands of dollars in preserved capital and protected opportunity cost. This systemic approach continues to serve as the foundation for how I frame research investment and risk mitigation with executive leadership today.

Sample Report

Usable (70): Strong onboarding plan (navigators, funnel), but no hard usability metrics.

Equitable (65): Inclusive research diverse, but WCAG and AT test coverage absent.

Enjoyable (72): Personalization, visual system, and consumer engagement proxies strong. No UEQ data.

Useful (85): Strongest area. Clear problem-solution fit, workflow integration, business KPIs, and evidence from market tests.

Prioritized Actions

U2: Conduct usability sessions to measure task success

High impact | Medium effort

U3: Capture time-on-task benchmarks

Medium impact | Medium effort

U4: Track error rates during pilot

Medium impact | Low effort

E1: Commit to WCAG 2.2 AA compliance

High impact | Medium effort

E2: Add AT test coverage (screen reader, keyboard, contrast)

High impact | Low effort