ValidationEmerging Pattern

Launch with features you need yourself rather than waiting to collect feedback—if you need it, users likely do too

Q: How many founders have validated "launch with features you need yourself rather than waiting to collect feedback—if you need it, users likely do too"?

1 founder has proven this pattern works. Examples include David Heijl (Vist).

When dogfooding reveals you need a feature now, ship it rather than waiting to validate through user feedback. Your own urgent need is validation. Collecting feedback first adds delay when you already have evidence from your own usage.

When to use

When you are your own target user and dogfooding reveals a feature you urgently need

Don't do this

Holding back features you desperately need yourself while waiting for external validation that may never come

1 Founder Who Did This

Vistby David Heijl

Originally planned to wait and collect feedback on MCP integration, but started using Vist himself and realized he needed the integration now

Result:Launched with MCP integration from day one rather than waiting—reasoned 'why would users be different?'

Read full story →