Quantum computing has a communication problem. Ask three people to explain it and you will hear about cats in boxes, “trying every answer at once” and a vague promise that everything will change. Most of those explanations are pitched at an audience of everybody, so they land with nobody. What follows is a checklist you can run over any quantum explainer, your own or someone else’s, to see whether it truly serves a reader. The test is simple: could you hand it to one specific person and be confident she would finish it and understand something new?

For the checklist, meet Devika. She teaches physics at a secondary school, has a little time between lessons, remembers the maths of waves but not much linear algebra, and wants to answer a student’s question about why everyone talks about qubits. Keep her in mind as you go.

Check 1: Is the reader named in your head?

Before reading anything, write one sentence about who it is for. “Devika: physics teacher, limited time, curious, no linear algebra.” If you cannot write the sentence, the piece will drift. Every later check depends on this one.

Check 2: Does the opening answer her real question?

Devika’s question is practical: “What can a quantum computer do that my laptop cannot, and why is that hard?” If the first paragraph spends its time on history or hype, she will drift away. A good opening answers the question in plain words, even if roughly, and promises to refine it later.

Check 3: Are the borrowed pictures honest?

Analogies are powerful and dangerous. “A qubit is both zero and one” is a shorthand that leaves readers with a wrong picture of how measurement works. If you use it, follow within a sentence or two by what actually happens: the system is described by amplitudes, and measuring it gives one outcome with certain probabilities. Devika, a physics teacher, will notice if you skip this step, and her students will repeat the error.

• Is each analogy labelled as an analogy?
• Does the text say where the analogy breaks down?
• Would an expert wince, and if so, can you fix it in one sentence?

Check 4: Is the maths sized for her, not for you?

Writers who know the maths tend to include it. Writers who do not tend to hide it. Neither suits Devika. She has wave intuition, so you can use it: interference of amplitudes is something she understands, and it is the heart of why some quantum algorithms work. Keep equations to those she can read at a glance, and explain every symbol once.

If you want an example of an algorithmic idea that leans on wave-like reasoning, read our look at the transform that sits inside many quantum routines and ask how you would pitch it to a teacher between lessons.

Check 5: Does it show one concrete use, not a list of ten?

“Quantum will transform finance, medicine, logistics and materials” is a list of nobody’s problems. Pick one use that Devika could relate to and explain it properly. Factoring large numbers is a good candidate because it connects to the cryptography her students already use online. A gentle starting point is this simple account of how quantum methods approach factoring. One example, done well, teaches more than a catalogue.

Check 6: Is the honesty about limits visible?

Today’s machines are small and noisy, and many promised speed-ups depend on hardware that does not yet exist at scale. A reader like Devika deserves to be told this plainly, without cynicism and without hype. A short paragraph on what works now, what is expected later and what is uncertain builds more trust than any amount of enthusiasm.

Be careful not to quote numbers you cannot source. If you do not know a figure, describe the trend in words and move on.

Check 7: Could she act on it?

Does the reader finish with something to do? For Devika it might be a classroom demonstration of interference with water waves, a suggested short reading list or a sentence she can use to answer her student. Without an action, an explainer is entertainment. That is fine, but it should be a choice.

Check 8: Is the length right for her minutes?

Devika has a break between lessons. Can she read the core of it in that time? If the piece is longer, does it have a clear first half that works alone and a second half that goes deeper? Layering, a short answer on top and extra depth below, respects both her time and her curiosity.

Check 9: Where will she find the next step?

A good explainer leaves a trail. That might be a link to a related post, a recommended book or a place to keep up with the writer’s work. Many people who write about emerging science keep a lightweight personal blog for this. A platform like iBlogUp, a writing site with personal subdomains for each author’s stories and an RSS feed for followers, lets a curious reader subscribe and come back when the next piece appears, without needing an account on yet another social service.

Check 10: Read it aloud to a real person

Finally, try it on someone who resembles Devika. Watch where she frowns. Wherever the frown appears, a term is undefined, a leap is too large or a sentence is trying to do two jobs. Fix those spots and try again. One honest reader teaches you more than a committee.

A quick worked pass

Suppose you have drafted a piece titled “Why qubits matter”. Run it past Devika. The opening praises the future of computing (check two fails: no answer to her question). It says a qubit is “both zero and one” with no follow-up (check three fails). It lists six industries (check five fails). It never says that machines are small and noisy today (check six fails). Four fails out of ten is not a disaster; it is a to-do list. Replace the opening with a plain answer, add the sentence about measurement, keep only one industry and write a short paragraph on limits. The piece will be shorter and Devika will thank you.

Notice what did not need changing: the facts were mostly right. The problem was never accuracy. It was aim.

Scoring yourself

You do not need a spreadsheet. Give each check a quick yes, partly or no. A piece with mostly yeses is ready. A piece with several noes is not a failure; it simply has an unclear reader, which is the cheapest problem to fix. Go back to check one, write a sharper sentence about who it is for and revise from the top. Often the improvement is not additional material but removal: the piece gets shorter and clearer when the reader gets more specific.

Why this matters for emerging tech

New fields attract hype because hype is easy to write for everybody. Careful writing for one reader is harder and rarer, and it is what builds lasting trust. When Devika can answer her student without bluffing, one more person has understood a small piece of quantum computing properly. Multiplied across enough readers, that is how a difficult subject becomes part of ordinary conversation.