Navigating the Maze
summary
Claims a repeatable win: a structured documentation plan template that lists documents, priorities and links, tracked in Jira and drafted in Google Docs while publishing via a docs‑as‑code workflow. Planning runs on ~one-week research sprints per feature, scopes by user journey and use cases, and prioritizes over tech‑debt. Measured with coverage and a thumbs‑up “content usefulness” metric and sees a notable jump in both, though not solely attributed to the plan. Challenges include SME delays and heavy source volume.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:51User-centric docs shift
- 3:38What is a doc plan
- 6:05Plan creation milestones
- 12:38Use cases and scope
- 15:47Content types and prioritization
- 18:15Template walkthrough
- 22:06Measuring success
- 23:29Q&A: Stakeholder buy-in
- 30:31Q&A: Personas and metrics
- 31:35Q&A: Agile sync
- 33:03Q&A: No UX team
- 34:30Q&A: Practical challenges
- 36:39Closing
related talks
39mA Strategic Documentation Template for Startups
37mTaking a step back: Analysing your documentation
51mGetting Real Value out of your Planning Efforts with Story Mapping
18mNavigating the Dev's Journey: Crafting an Effective Roadmap for Success
46mManaging The Process
27mThe art and practice of documentation triage
26mJust-In-Time Documentation: Employing Agile Methodology To Create Living Documentation
38mThe Stuff You Don't Want to Write... Documentation