From strategy to shipped product
Product design consulting for teams building AI-powered products, scaling design systems, and shipping faster.
Product Design Strategy
Clarity before pixels — a credible plan your team can fund and ship.
Best for: Product and engineering leaders shipping 0→1, redesigns, or pivots where scope and risk are both high.
Discovery that connects business decisions to user reality: problem framing, research synthesis, journey mapping, and a prioritized roadmap.
The output is decision-grade: explicit trade-offs, funding-ready scope options, and implementation constraints engineering can estimate without re-discovery cycles.
Not a fit if: Teams looking for a visual-only reskin without revisiting product strategy or success metrics.
Deliverables
- Executive-ready problem framing and success metrics
- Journey maps, opportunity areas, and prioritized bets
- Interaction models and narrative prototypes for alignment
- Design direction that de-risks the next build cycle
Fixed scope (4–10 weeks)
2–3×
faster stakeholder alignment on what to build first
30–50%
fewer late scope changes once engineering starts
Weeks not months
to produce an executive decision artifact with measurable success criteria
Best-fit scenarios
- A programme is blocked by conflicting stakeholder definitions of the problem.
- Leadership needs a funding decision artifact before committing engineering capacity.
- A product pivot needs defensible scope options and measurable success criteria.
Method → artifact → business outcome
Domain routes
Case studies
AI-Native UX Design
Interfaces and workflows for products where AI is the product — not a bolt-on.
Best for: Teams building copilots, agents, retrieval workflows, or AI-assisted operations tools.
Design for probabilistic systems: prompt UX, confidence and uncertainty, review loops, traceability, and safe escalation paths.
The focus is customer outcomes: faster decisions, lower correction burden, and auditable human override paths that satisfy compliance and operational risk teams.
Not a fit if: Teams looking for AI only as a drafting shortcut in Figma. This engagement is product UX for AI-powered experiences.
Deliverables
- Task models, states, and edge-case maps for AI-assisted flows
- UI patterns for verification, edits, and human-in-the-loop review
- Content and interaction specs for prompts, outputs, and failures
- Measurement plan for trust, quality, and operational impact
Fixed scope (6–12 weeks) or ongoing (3–6 months)
20–40%
reduction in correction loops after first production release
2–3×
faster iteration on high-risk AI flows once baseline instrumentation exists
Higher trust
through clearer confidence signals, fallback states, and escalation design
Best-fit scenarios
- A copilot or agent experience needs trust and verification designed in from day one.
- Teams need to reduce rework from ambiguous AI outputs in production workflows.
- Compliance and operations require clear human override and audit-ready interaction flows.
Method → artifact → business outcome
Domain routes
Case studies
Proof signals
Design Systems & Component Architecture
Tokens, components, and Figma↔code parity your team can maintain.
Best for: Growing product orgs where UI drift, rework, and handoff tax are slowing delivery.
Audit or build a token-first system, component API design, accessibility defaults, and documentation that matches how engineers actually ship.
The goal is speed without chaos: consistent patterns, fewer one-offs, less design-dev ping-pong, and governance that keeps Figma and production aligned over time.
Not a fit if: A purely marketing-site component library with no product surface area.
Deliverables
- Token taxonomy and semantic mapping to implementation
- Component inventory, consolidation plan, and migration notes
- Figma libraries aligned to coded components
- Guidance for contribution, versioning, and governance
Ongoing (3–6 months) or fixed audit (3–5 weeks)
25–45%
less repeated UI work across squads after baseline
Top journeys
documented accessible patterns for the highest-traffic flows
Faster onboarding
new designers and engineers ship with shared primitives instead of local variants
Best-fit scenarios
- Multiple squads are shipping similar UI with inconsistent quality and naming.
- Design and engineering teams need Figma-to-code parity and governance.
- A product org wants to reduce handoff tax and component drift before scaling.
Method → artifact → business outcome
Domain routes
Case studies
Proof signals
Fractional Design Leadership
Senior design leadership embedded part-time — craft, process, and cross-functional traction.
Best for: Startups and scale-ups with strong IC designers but no seasoned design leader in seat.
Operating as an embedded lead: critique and standards, design-dev partnership, planning with PMs, and hiring support when you need a senior seat at the table without a full-time hire yet.
This is hands-on leadership: reviews, rituals, decision hygiene, and cross-functional unblocking that improves execution quality week over week.
Not a fit if: A full-time Head of Design replacement on a fractional calendar — scope stays bounded and explicit.
Deliverables
- Weekly design reviews and quality bar for shipped work
- Rituals with product/engineering for alignment and velocity
- Role definitions, loops, and lightweight documentation
- Interview loops and rubrics when you are hiring design leaders or ICs
Ongoing (3–6 months)
1–2 quarters
to stabilize design quality and delivery predictability
Weekly
design critique and alignment loop embedded with product and engineering
Lower execution drift
through clearer ownership, better review rituals, and repeatable decision frameworks
Best-fit scenarios
- A growing team needs senior design leadership without immediate full-time hire risk.
- Delivery quality is uneven because ownership and decision rituals are unclear.
- Product and engineering need a stronger design governance loop across active workstreams.
Method → artifact → business outcome
Domain routes
Case studies
Proof signals
Why design and engineering literacy matters
For a deeper look at how I think about discovery, delivery, and AI-native programs, read what I bring. If you need embedded programme governance after service strategy, continue to Work with me.
I bring both design craft and engineering literacy — which means I speak your developers' language and ship work that doesn't fall apart in implementation.
FAQ
Practical questions teams ask before a first call.
How are service engagements scoped and priced?
Services are scoped around outcomes, explicit deliverables, and timeboxed milestones. Pricing reflects complexity, decision risk, and collaboration cadence — quoted after a short context call, not by day-rate alone.
What is the difference between Services and Work with me?
Services are product/design-led outcome packages (strategy, AI-native UX, design systems, leadership). Work with me is engagement-model and delivery-operations support (programme, project, advisory). If you need an embedded delivery lead alongside service outcomes, start with Services and continue into Work with me.
How quickly can a service start showing value?
Most services are designed to produce a concrete decision artifact in the first 1-2 weeks (scope, architecture direction, or risk map), then compound into implementation-ready outputs over the engagement window.
Do services include implementation-aware guidance?
Yes. Every service is shaped for implementation handoff: constraints, trade-offs, and technical implications are documented so engineering and delivery teams can execute without narrative loss.
What does the first service milestone usually cover?
The first milestone is usually a scoped problem-definition or design-direction sprint: decision context, constraints, success metrics, and prioritized next actions. If ongoing delivery support is needed after that, transition into Work with me engagement models.
Related pathways
Start from a service, then branch to methods and proof.
Services
Proof pathway
Work phases
Ready to scope the first milestone?
Exploring options? Start with engagement shapes on Work With Me. Ready to scope? Jump straight to contact.