# 004: Task-Based Narratives or Features Dumps?
¡Hola, Tech Writing Friends!
Ever feel like your documentation isn’t quite connecting with users?
Today, let’s talk about a simple shift to transform how users interact with your docs.
Focus on task-based narratives instead of documenting features.
Your Cool Feature? Nobody Cares.
People don’t come to your product thinking, “That’s a cool feature. How do I use it?”
They come with a problem, looking for a solution.
Yet, so many technical writers fall into the trap of writing feature-focused docs.
The result?
Users feel overwhelmed and lost!
They’re unable to connect the dots between features and figure out how to solve their real-world problems.
I can’t wait to read all about your 9999999 features.
Product documentation often lists alllll the features, with detailed explanations of what each feature can do.
It’s like reading a product manual that tells you everything about the product without showing you how do what you need.
Think of it like buying a new kitchen blender that has 20 buttons and 5 different settings, but the manual just describes each button instead of showing you how to make a smoothie.
Useful? Not so much! 🥤
Feature-Focused Docs Fail…
…because it doesn’t engage users.
Instead of showing folks how to solve their problems, it overwhelms them with technical jargon and irrelevant details.
Here’s the kicker: Users don’t care about all the features.
They care about solving their problem quickly.
If your documentation can’t show them how to do that, they’ll give up on your product— and move on to the next!
Think Tasks, Not Features!
The solution? Task-based narratives.
Instead of just listing features, shift your focus to the tasks users are trying to complete.
Start with the user’s goal. What task do they need to accomplish?
Describe the problem-solving process. Break it down into steps.
Show how your product helps them. Highlight relevant features only as they apply to each step.
When you structure your docs around tasks, users can quickly find the solutions they need without sifting through irrelevant details.
According to the 70-20-10 learning model, 70% of learning comes from hands-on tasks.
When your documentation is task-focused, it aligns perfectly with how users naturally learn and engage.
Empower your users to solve their problems efficiently.
Time For Some Action Steps!
Ready to switch to task-based docs?
Audit your existing docs: Identify where you’ve listed features without connecting them to real-world tasks.
Shift your perspective: Next time you write, start by asking, “What is the user trying to accomplish?”
Apply the 70-20-10 Learning Model: Remember that 70% of learning comes from tasks; make sure your docs reflect that.
Engage with your users: Collect feedback to understand which tasks they struggle with most, and use that insight to improve your docs.
Happy documenting! 📝
Hasta luego,
Quetzalli
