Phases 1 & 2
Discovery: tell the story, then map the process
Interactive workshops that turn tribal knowledge into maps your whole team—and ours—can build from.
Step 1: Telling the business story
Business storytelling · 4 to 6 hours, usually split over two sessions
We gather your core stakeholders—founder, ops lead, customer success, sometimes sales—and walk through your business like a narrative. Who are the actors? What frustrates them today? What does the ideal journey look like from first touch to outcome delivered?
We capture the language your business already uses: customers, vendors, cases, quotes, verifications, clients—whatever your business calls them. That vocabulary becomes the backbone of screens, emails, and support docs so nothing gets lost when we build.
Session format
- Format
- Interactive workshop (remote or on-site)
- Duration
- 4–6 hours total
- Deliverable
- Visual business map & shared glossary
Who should attend
- · Founder or product owner
- · Person who knows day-to-day operations
- · Someone who talks to customers weekly
What we explore
- · Current workflows & workarounds
- · Pain points & failure modes
- · Success metrics for v1
What you leave with
- · Jargon-free scope boundaries
- · Prioritized scenarios for MVP
- · Agreement on “done” for launch
Step 2: Rapid business process mapping
Process mapping · 8 to 12 hours across iterative sessions
This is where we make the workflow visible. We map the business as a timeline of key moments—invoice sent, customer onboarded, report delivered. For each step we identify who is involved, what tools they use, where things slow down, and what should happen automatically.
Why it works
Instead of a 50-page requirements doc, you get an interactive map of behavioral mechanics. Hot spots—manual steps, handoffs, compliance risk—show up early, before they become expensive surprises after launch.
What we produce
- · End-to-end workflow timeline
- · Handoffs with payments, email, CRM, and partner systems
- · Version-one scope: minimum workflow for first revenue or outcome
- · Clear build plan your team can review and approve
Note: Process mapping works for new products and for replacing spreadsheets or older tools. If you already have software, we map the desired workflow—not a copy of today's workarounds.
After discovery
Workshops aren't shelf-ware—they feed directly into product planning and delivery.
Within a few days we deliver a short written summary: glossary, event map photos or Miro export, MVP scope, and open questions. Then we move to architecture design and implementation—see Build & scale for how sticky notes become production code.