Lessons from failed prototypes

I have a folder on my computer called “the graveyard.” It's where dead projects go. A vocabulary app nobody used for more than three days. A fire-detection model that also panicked when I toasted bread. A website I finished and then lost the domain password for.

For a while I was embarrassed by that folder. Friends showed off projects that worked; I mostly had things that broke. But then I realized each broken thing was trying to tell me something specific. The vocabulary app died because I solved a problem no one had. The fire model cried wolf because I was greedy with data and lazy about cleaning it.

Now I open “the graveyard” the way you'd open an old diary. It isn't a list of failures. It's a list of the times I figured out exactly where I was wrong — which I never would have learned without building the thing first.

I don't believe in “failure is the mother of success” as a slogan. Failure teaches nothing unless you sit down and ask why. The hard part isn't failing. The hard part is being honest enough to look straight at it.