The “One Week Prototype” Playbook for B2B Products

B2B teams get stuck because everything feels complex: roles, permissions, integrations, edge cases. The “one week prototype” is how you keep momentum without pretending complexity doesn’t exist.

The goal: in one week, de-risk the core workflow and the adoption story.

Day 1: Define the narrow slice

Pick:

• one primary persona
• one job-to-be-done
• one success moment (“user gets value when…”) Define what’s out of scope. Aggressively.

Day 2: Sketch 3 approaches

Force divergence:

• approach A: simplest workflow
• approach B: power-user workflow
• approach C: guided workflow You’re not choosing yet. You’re mapping options.

Day 3: Build a clickable prototype

Focus on:

• the happy path
• one meaningful edge case
• realistic copy and data B2B prototypes fail when they use fake data that hides real complexity.

Day 4: Test with 5 users

Use task-based tests:

• “Show me how you’d do X.” Watch where they hesitate, where trust breaks, and what they expect.

Day 5: Synthesize into decisions

Deliverables:

• chosen direction + rationale
• top 3 usability risks
• top 3 trust requirements
• what must be true for MVP
• what can wait

This playbook wins because it doesn’t aim for completeness. It aims for confidence.

Interview line:

“In B2B, I use a one-week prototype sprint to de-risk workflow fit and trust. We narrow scope, diverge quickly, test with real users, and exit with decisions.”

---