{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Not-Boring Tech Writer","title":"Kate sounds off on lovable docs","html":"","width":"100%","height":180,"duration":1931,"description":"In this solo episode, I share my latest content updates progress and reflect on my takeaways from Jacob Moses’ interview (S3:E32). I also share some thoughts on applying concepts about lovable neighborhoods to documentation.—I updated the KnowledgeOwl Support Knowledge Base (Support KB) to create all the documentation for our new Owl Analytics Export API, including API endpoint documentation and a public Postman collection of the endpoint. I also wrote a release note and documentation for several new import tools, including HubSpot and a generic CSV importer. My change management toolkit is more or less ready for release, which will happen in two phases: a larger toolkit released for KnowledgeOwl customers only, and a more streamlined version released to the general public. I’ll share more once that streamlined version is available so you can check it out if you’d like!I reflect on my interview with Jacob Moses, especially all the skills he took from his tech writing career and used in his real estate development work at Care Block. I share five ideas that came up in our discussion around neighborhoods and community development that are equally applicable to documentation:You don’t necessarily have to plow a lot of resources into big changes to have a big impact on your reader experience.Have conversations–or at least, bear witness to conversations–where your readers are most comfortable having those conversations.Don’t just copy and paste best practices or templates from other places; use them as starting points and iterate as you go.Incorporate documentation into your customer and employee onboarding.Support readers who have differing levels of engagement styles.I also dig a lot deeper into the idea of lovable neighbors and lovable documentation, sharing some insights from Henrik Kniberg’s blog post on earliest testable/usable/lovable products and trying to apply those principles to documentation. I argue that documentation can be one of the most lovable parts...","thumbnail_url":"https://img.transistorcdn.com/JlP4_zZATprOmI0COWYcSJZswo0AzjaOmxyE_M5gX6M/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kNTdh/ZjBlMjA5ZmEwZDhh/NTNjZWFiOWM2NWY1/ZDAzNS5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}