a single source, nothing corroborates it

Shelve the project when the signals stack up

Lukewarm feedback, a crowded market you had not seen, and a wide gap between your version and what buyers already use are three reasons to stop rather than push on. Cory Zue killed a side project once the realistic version of it turned out to be a large enterprise product he had no capacity for. The test is whether the thing it would have to become is still the thing you set out to build.

The method

1. 01

   Kill a side project when its realistic form no longer matches why you started it; a weekend showcase turning into a full enterprise product is a reason to stop, not to push.

2. 02

   Shelve a project when several signals stack up: lukewarm feedback, discovering a crowded existing market, and a large gap between your MVP and what buyers already have.

What it returned

• Zue started RepoStory to exercise his boilerplate and concluded the version he could see it becoming was a large B2B application he had no capacity for.

• Zue paused RepoStory after continued tepid feedback, finding many existing tools, and realizing closing the gap would be substantial work just as a second child was arriving.

Sources

• The Calm Before the StormCory Zue · coryzue.com · What’s the RepoStory Story? · 2020-09-01