The documents and structures behind the case studies — the kind of thinking that shapes decisions before a designer opens Figma or an engineer opens a ticket. Some are full PRDs. Some are lighter frameworks. All are here to make the decision layer visible.
A product requirements document exploring how intelligent nudges could reduce checkout anxiety in QR payments — surfacing real-time bank health signals before users get stuck in a failed flow, not after.
A permission-aware AI knowledge assistant for LMS policy and support queries — designed with grounded retrieval, citation requirements, escalation paths, and safe refusal logic built into the spec from the start.
A one-page structure for aligning on who the user is, what's broken, and why existing options fall short — before any solution discussion begins.
Derived from case study workA working structure for defining AI-powered features — covering user need, trust edge cases, error states, and success criteria before design work starts.
Derived from case study workA lightweight decision framework for comparing ideas across value, effort, risk, and confidence — before committing to build. Derived from RICE applied across both PRDs.
Derived from case study workA working format for defining success metrics, guardrails, failure conditions, and confidence signals for AI-assisted product behaviour. Safety-conscious from the start.
Derived from LMS RAG PRDA staged launch approach — narrow the risk first, validate usefulness, expand only after trust and quality are proven in a controlled cohort.
In preparationA product-facing view of system logic — how retrieval, permissions, ranking, or signals shape what the user actually sees and experiences at runtime.
In preparationNothing here is presented as shipped production output. Concept and assignment work is marked as such, so you always know what you're looking at.
They show the most complete picture — discovery, prioritization, feature spec, metrics, and risk thinking in one document. Frameworks sit behind them.
This page exists to show the decision-making layer, not fill a portfolio. Some artifacts are full documents. Others are lighter structures. The goal is making the thinking visible.
Explore the case studies for the full context behind these artifacts — or get in touch to walk through the thinking directly.