Bash’s Post

The sequel to last week's guide on writing great product updates is live. This time, we talk narrative design, and how it will make you a better product storyteller: https://lnkd.in/eqKjtsD7

Great reminder from Mike Cohn that PBIs need not always be user stories and the 3 different types of stories highlighting the “when” to use them. Choose the story type that makes most sense for what you and your team are trying to accomplish. What story type do you mostly use with your teams please comment!

An actionable tip if you've found yourself struggling with coercing your backlog items to fit the traditional user story template.

Agile frameworks are just that - frameworks. It's not as simple as applying a template or a recipe. My team often calls the third examples "technical tasks" because they are back-end but needed for successful realization of a feature. Try these variations on your user stories to see if they fit the work better in your product.

Great and concise visualisation on user requirements

You won't be able to write that perfect copy unless you go through the grind of creating an imperfect one first. Every masterpiece was once a rough draft riddled with issues. 📑 Embrace the process of refining your work. It's worth the time and energy. ⏲️ Consistent practice and iterative improvement are key to creating exceptional content.

When and why to create a Product Glossary for your team

I was writing a product-led content piece for a new client. And I made 2 mistakes: 1. I analyzed the SERP first. This restricted my thinking to the top 3-4 use cases the competing articles mentioned. Instead, I should've: A. Researched the product B. Understand how it fits into my ICP's workflows C. Read customer testimonial and case studies. This would've given me a clean slate with enough information to come up with my set of use cases. D. Finally, analyze the SERP to ensure I haven't missed an important use case. 2. I prioritized my product over the problem. The first objective of PL-content is to provide value. Answers the audience's questions. Then, introduce my product as a solution to help them achieve their goals. Ideally, I should've researched key value points before my product's features. But since I did the opposite, I was trying to find solutions centered around my product. Again, I noticed I didn't cover major points that didn't fit into the product. 2 days into the article, I knew something was wrong. Thank goodness I was in the research phase only. Had I started #writing, it would've been a lot difficult to start from scratch. I took a day, researched from square one and made a new outline. I'm sure this approach is much better. New article, new learnings! 🥂

🚨 Error messages might seem small, but they play a huge role in the user experience. As I’ve been diving into technical writing, I’ve realized just how crucial it is to craft messages that are clear, actionable, and user-friendly. In this carousel, I’m sharing some key principles I’ve learned about writing better error messages—things that can reduce frustration and help users resolve issues more easily. 🔑 What I’ve learned so far: - How to make error messages clear and concise - Common pitfalls to avoid - Real-world examples of effective error messages I’m excited to continue learning and sharing what I find along the way. If you’ve worked on error messages or have any tips, I’d love to hear from you. 💬 Let’s discuss in the comments! Your feedback and insights are always welcome. #TechnicalWriting #ErrorMessages #UXWriting #UserExperience #ContentStrategy

Writing is clarity at scale. If tech is about shipping working code and design about creating beautiful visuals, I'd argue product management is mostly about writing clear docs. Writing good copy is crucial for clear communication of user research, product requirements, and release notes. It's key for collaboration across teams and keeping everyone aligned⁠. Our first product decision at Cycle App was to build our atomic unit as a natively collaborative doc. It didn't make our life easy (no kidding, building an extraordinary real-time editor is no joke) but it was a statement. No wonder why product folks spend an average of 2 hours and 30 minutes per day in Cycle. They just do their job: they write ✍️