My kids got me a guitar tuner for Father’s Day and I almost threw it against the wall.

A little piece of paper changed my mind. Your developer docs should include an electronic version of the note that came with my tuner.

I was excited to get the gift because some mystery force (those with kids will understand) had broken my other tuner a month earlier. Plus, my guitar needed the tune.

So, I immediately grabbed the instrument after unwrapping the gift. I clipped the tuner to the guitar neck, pushed its button, and plucked a string. The screen delivered a note I did not expect.

After some frustration, I picked up the small pamphlet from the tuner’s packaging.

It had a picture and a couple of bullet points.

In under a minute, I was able to diagnose my problem: my new toy was in violin mode.

See that “V” in the photo? It needed to be a “G.”

A quick switch to guitar mode and it worked as expected. The “get started” bullet points got me on the right track.

I imagine whoever wrote the words on that piece of paper was not involved in making the tuner. They didn’t choose the default tuning mode. And who knows, I may have switched modes accidentally when I turned it on. That probably happens all the time—how frustrating for those supporting the product!

Yet… somebody found a way to get me started.

This meant I was able to use the tuner that first time and many times since.

Here’s what it means for you:

You may or may not have any control over your developer product.

But you can definitely control those little electronic pieces of paper that are your docs.

The only reasonable way to earn a second visit from a developer is to nail that first experience.

Devs will need your documentation many more times, but only if they make it through your version of “hello world.”

Three cheers for whoever wrote the compact manual that came with my guitar tuner—and to you for your upcoming documentation edits.

P.S. Not sure what should go in your get started bullet points? Reach out to EveryDeveloper for help.