Is this work for me? · 7 min read
Is technical writing right for me? Write instructions someone can follow
Technical writing is about making someone else succeed at a task. Write a short set of instructions, watch a reader use them and revise.
The short answer
Technical writing suits people who like understanding how something works, enjoy making it simple for someone else, and care more about whether readers succeed than about elegant prose. A good first test is to write instructions for a real everyday task, watch someone follow them without help, and revise every place they hesitated. If you find that cycle satisfying, technical writing, documentation and content design are worth exploring.
On this page 8 sections
The reader's success is the measure
Most writing is judged by how it reads. Technical writing is judged by what happens next: did the person install the software, fix the fault, complete the form? That changes everything about how you write. You cut anything that does not help, you put steps in the order people do them, and you test.
The exercise
Choose a task that takes five to fifteen minutes and that a friend has not done before: setting up two-factor authentication on an account, changing a bike's inner tube, making a pivot table, setting a recurring calendar event with a reminder. Write instructions without screenshots first.
A worked revision (illustrative)
| First draft | After watching a reader | Why |
|---|---|---|
| Go to settings and enable two-factor. | Open the app. Tap your profile picture in the top right, then tap Security. | The reader could not find settings. |
| Scan the code with your authenticator. | Open your authenticator app (for example, the one already on your phone). Tap Add, then point your camera at the square code on screen. | The reader did not know what an authenticator was. |
| Enter the code. | Type the six-digit code shown in your authenticator into the box, within 30 seconds. | The code expired while the reader looked for the box. |
Watch someone use it
Give your instructions to a friend and stay silent while they follow them. Note every pause, every backtrack and every question. Do not explain. Each hesitation is a place the writing failed, not the reader.
Revise, then test with a second person who has not seen either version.
What your reactions tell you
- Watching the reader struggle made you eager to fix it: strong sign for documentation or content design.
- You enjoyed understanding the system more than writing: consider support engineering, training or business analysis.
- Testing felt tedious and you wanted to write freely: you may prefer other kinds of writing.
Principles you will use every day
- One action per step, in the order people do it.
- Name things exactly as they appear on screen.
- Say what the reader should see after each step, so they know it worked.
- Put warnings before the step they relate to, not after.
- Cut anything that does not help someone complete the task.
Try applying these to your first draft before the test. Then notice how many problems the reader still finds; it is usually more than you expect.
A second exercise: explain a concept
Instructions are half the job. The other half is explaining concepts. Write 200 words explaining what a browser cookie is for someone who has never heard the term, without jargon. Ask a friend to explain it back to you. If their explanation matches yours, you succeeded. If you enjoyed finding the right example or comparison, that is a good sign for documentation and content design.
Questions people ask
- Do technical writers need a technical background?
- It helps in some fields, such as software or engineering, but many technical writers learn the subject on the job. The core skill is understanding a topic well enough to explain it accurately, and asking experts good questions.
- What do technical writers write?
- Examples include user guides, help articles, API documentation, installation instructions, internal procedures and release notes.
- Is technical writing affected by AI?
- AI tools can draft documentation quickly, which changes some routine work. Checking accuracy, structuring information, testing with users and working with engineers remain human responsibilities. Test whether you enjoy those parts.
- How do I build a technical writing portfolio?
- Write documentation for open-source projects, rewrite a confusing help page and explain your changes, or document a process at work with permission. Show before and after versions.
Exercises are practice, not evidence of career fit or a qualification. How to read our guides and report a correction.
Sources
- Technical Writers (Occupational Outlook Handbook) · U.S. Bureau of Labor Statistics
How this page is written
Sources support the factual background, not a guarantee that an exercise predicts career fit. Fictional practice material is labelled. Dates record content updates; no independent expert review is implied. More about OffLadder.