How we work
From mess to usable system
Engagements stay deliberate: understand the real constraints, design the smallest structure that works, prove it in interaction, then hand it off without theater.
-
01
Discover
Map the people, workflows, data, and failure modes. Name what is actually broken before proposing tools.
Deliverables: constraint map, stakeholder notes, risk list, success criteria draft.
-
02
Structure
Define boundaries: what is a product, what is a path, what stays human. Architecture before decoration.
Deliverables: information architecture, workflow diagram, data provenance rules, scope gates.
-
03
Build
Ship working surfaces. Prefer preview lanes and reversible changes. Keep production safe until approval.
Deliverables: working prototype or system slice, preview URL, change log, open questions.
-
04
Prove
Interaction over decks. Case frames, walkthroughs, and systems you can click through.
Deliverables: walkthrough, validation notes, known gaps, readiness statement (honest).
-
05
Hand off
Document ownership, deploy lanes, and rollback. Leave the client with levers, not a black box.
Deliverables: ownership map, runbook, rollback card, next-step options.
Example timeline
A contained engagement shape
Timelines vary by scope. This is a common shape for a focused systems or AI-workflow engagement, not a promise for every project.
- Week 1: Discover. Interviews, artifact review, constraint map.
- Weeks 2 to 3: Structure. Architecture, scope gates, success criteria locked.
- Weeks 3 to 6: Build. Working slice on a preview lane; weekly check-ins.
- Week 6 to 7: Prove. Walkthrough, validation, readiness honesty.
- Week 7 to 8: Hand off. Runbook, ownership, optional retainership discussion.
Larger product builds (for example YBRP modules) stretch the Build and Prove phases and keep the same governance: preview first, production only with approval.
Bring the mess
You do not need a finished scope. Start with the constraint that hurts most.
Start a conversation