Skip to stories
All book ideas
Describe the Missing Button cover

Original book ideaPractical nonfiction

Describe the Missing Button

Describe what happened, what you expected and one concrete thing you need next.

Create my bookRead sample

ImagineYourBook writes a fresh draft from this idea.

Introduction

The only useful word in Luca's first request was button. It came in the subject line.

"Button," the message said. Then it said, "It still doesn't work." Penny opened it while setting up chairs for the workshop. She did not know whether Luca meant the button on the registration form, the button that published the form, or the button on the kettle that had also stopped working that week.

Luca had written the request at the end of a frustrating afternoon. He could still picture the exact place where the form surprised him. It seemed unnecessary to explain the part that had become obvious to him.

A good request gives another person the moment you are standing in. Start with what you were trying to do. Then describe where the actual result diverged from the one you expected. "I filled the public test form on my phone. After the email field, I expected a way to submit. The page ends with the privacy note." This gives Penny three useful facts and a place to look.

Tell the helper what you need next. Do you need an answer, a second pair of eyes or someone with permission to change the form? Give a deadline if it changes what people should do. If you include a picture or example, remove details that do not belong in the request. A fake registration can show where a form stops without giving a stranger someone's address.

Luca sent a second message with the form name and a test example. He asked whether Penny could check it before invitations went out on Friday. Penny could see the same behavior on her phone. She postponed the invitations for an hour and sent the report to the person who managed the form.

By lunch the button was visible. Luca sent one final line to say he had tried it again and the test registration arrived. Then he took the kettle to the repair shop. He had learned to keep two requests separate.

Your idea. Your book.

Create my book

Created with ImagineYourBook. Free to use as inspiration.

Chapter plan

Develop this idea

Use ordinary examples and show the words a person actually sends. A helpful request gives context, an observation and a next action without disclosing secrets. Include a way to describe uncertainty and a way for the helper to reproduce the benign situation using a test example. Explain what changes when time matters. The book should make clearer requests feel less like a test of technical vocabulary.

  1. Open on a vague report that cannot be acted on.
  2. Describe the outcome you expected in everyday language.
  3. Name the first place where the actual result differs.
  4. Say what you already tried without writing a diary.
  5. Include a safe example with sensitive details removed.
  6. Give a useful next action and realistic deadline.
  7. Adapt the request for phone or in-person help.
  8. Separate urgency from frustration.
  9. Respond to clarification without changing the original facts.
  10. Keep a reusable request note for your next problem.
Series possibilities
  • A guide to writing quick, kind instructions for people who help others.

Add your twist

More options