MAGNET LABS
Start a Lab

Velocity EngineExecution Game

Solve for Yes

from we can't because→to yes, if

The Goal

Turn the constraint that has stalled a team into a small, testable next step it owns.

Ideal For

Teams stuck on a blocker where everyone is waiting on someone else, and where budget, risk or timing keep “happening” to the team.

The Shift

From we can't because to yes, if.

The Science

People tend to stick with the current state of affairs, even when change would serve them better. Moderate constraints tend to help creativity, while too few or too many tend to hurt it. In a randomized trial, founders taught to treat their ideas as hypotheses to test were more likely to drop or change weak ones, and setting stop rules in advance tends to guard against throwing good money after bad.

Solve for Yes, step by step

  1. Name the “no”Each person names a “no” the team is carrying: “We can’t … because …”. The group picks one to work on.
  2. Price itEstimate what the “no” costs per month in rough dollars (lost revenue, cost of delay, people’s time), with the assumption written beside it. Work the most expensive one the team can influence.
  3. Collect the objectionsList every “no, because…” without arguing.
  4. Flip to “yes, if…”Turn each objection into the conditions that would make yes possible. Keep only those in the team’s hands within 30 days; if the “if” removes the team’s agency, it’s not a real yes.
  5. Design the testThe smallest 7–14 day test, with a guardrail, one success metric and a kill trigger set before it starts. Check that it costs far less than a month of “no”.
  6. CommitOne owner, a first step inside 48 hours written as “When [time and place], [owner] will [step],” and a booked review to continue, adjust or stop.

The techniques, and why they work

Price the “no”

Name the stuck point and estimate what it costs per month, in rough dollars, with the assumption beside it. People tend to overlook what staying put costs unless it’s made explicit, and the figure picks which “no” to work on and sizes the test.

Flip to “yes, if…”

Turn each objection into the conditions that would make yes possible, then keep only those in the team’s hands within 30 days. Moderate constraints tend to help creativity rather than kill it.

Test with stop rules

The smallest 7–14 day test, with a guardrail, a success metric and a kill trigger set before it starts; one owner, a 48-hour first step written as an if-then, and a booked review. Treating ideas as hypotheses tends to drop weak ones sooner.

Selected research

From the research

The thinking behind this lab, published in full:

Related labs

Run this lab with your team Try it first: 60-Minute Challenge LabBrowse all labs