Dream Big, Then Pull the Brake [83]

Lead build-vs-buy calls: outcome first, then one hard bottleneck question

Show notes

Ava's team kept duct-taping workarounds onto a bought POC platform until one SE built the tool she actually wanted in an afternoon. Nate pushes back on skipping constraints, and together they work out how to pair unconstrained dreaming with a named brake so build ideas don't turn into distractions.

What Nate and Ava discuss

  • Why opening with security and data-protection constraints kills good tool ideas, and how to treat them as problems to solve instead
  • Pairing a builder with one named 'brake' and timeboxing the no-limits phase to one or two hours
  • Spotting when 'buy' is really failing: repeat workarounds and a weekly log of customer asks you couldn't deliver

The move

Give the next build idea a one-to-two-hour session with no constraints. Then have one named person ask whether this is your biggest bottleneck right now. If it's not, park it, and keep a weekly log of 'we couldn't do it' moments so it comes back with evidence.


🔗 Resources & Links: paths.to/presales

📅 Book a Discovery Call: calendly.com/serockstars-tim/discovery-call

New comment

Your name or nickname, will be shown publicly
At least 10 characters long
By submitting your comment you agree that the content of the field "Name or nickname" will be stored and shown publicly next to your comment. Using your real name is optional.