Designing experiments that keep teams aligned

Teams often agree on the destination but disagree on the first step. Our discovery experiments act as a lightweight contract—allowing every contributor to understand the goal, the signals to validate, and the timeline to decide the next move.

Start with a shared learning objective

We begin every sprint with a learning statement: a concise sentence that states what we believe, why it matters, and how customers will tell us we're wrong. This creates traceability from stakeholder intent to customer evidence.

Prototype for conversations, not consensus

Artifacts are built to reveal tension. Our designers co-create with product and engineering, simplifying experiments to the riskiest assumption. When everyone sees their ideas tested, collaboration becomes continuous rather than staged.

Measure what enables the next decision

Success metrics are tied to behavior change and operational impact. Each experiment ends with a playback: what we tried, what we observed, and the recommendation for the next iteration.

“We value experiments that unblock a decision. The insight is useful only when it empowers the team to move forward with confidence.”

For LumaPay we used this approach to refactor onboarding. Within two experiments the team validated the new ledger model, accelerating engineering by three weeks.