Claude for SaaS Strategy Managers: Write a Process Doc Guide

You are an expert SaaS strategy execution consultant with 13 years of experience building process documentation systems that bridge the gap between quarterly strategy sessions and the daily work decisions that either advance or undermine strategic priorities. Help me write a process documentation guide so I can run more effective meetings by giving every meeting a documented process foundation that eliminates repeated context-setting and lets the team spend meeting time on decisions rather than on catching up. My situation: - My company stage and strategy execution challenge: [e.g., Series B SaaS — 45-person company — strategy is defined clearly at the leadership level but individual contributors do not connect their daily work to the quarterly OKRs — meetings feel disconnected from strategic priorities] - The 3 core processes that most urgently need documentation: [e.g., 1. the product prioritization decision process — how features get from idea to roadmap — 2. the customer escalation response process — who owns it and what the resolution timeline is — 3. the monthly business review prep process — who pulls what data and by when] - The meeting types where lack of process documentation wastes the most time: [e.g., product roadmap reviews (60 min, 40 min spent re-explaining context), customer escalation calls (45 min, first 20 min spent finding the right owner), and monthly business reviews (90 min, always start 15 min late because the data is not ready)] - The team's current process documentation culture: [e.g., some processes are documented in Confluence but the pages are 18 months out of date — the team has learned not to trust documentation and goes directly to people instead — this creates bottlenecks around the 3 people who know the most] - The format and detail level that works for my team: [e.g., one-page process maps with a clear owner column, a decision point column, and a "what good looks like" standard — team resists long written guides but will use visual flowcharts and concise reference cards] - The tool I use for documentation and the team's adoption level: [e.g., Confluence — all team members have accounts — fewer than 30% of pages have been opened in the last 60 days] - My target for meeting time recovered through better process documentation: [e.g., reduce per-meeting context-setting time from an average of 22 minutes to under 5 minutes within 60 days of implementing the guide] Deliver: 1. Write a process documentation template — a one-page format with sections for process name, process owner, trigger condition, step-by-step actions with decision points marked, "what good looks like" standard for each step, and a last-reviewed date — formatted for Confluence but also printable as an A4 reference card. 2. Write a process audit framework — a 6-question assessment for evaluating each of the 3 priority processes to determine which documentation gaps are causing the most meeting time waste, ranked by impact on meeting efficiency. 3. Write the product prioritization decision process document — completed in full using the template from item 1 — covering how a feature request moves from submission to roadmap decision, who participates at each stage, the criteria used to prioritize, and the maximum calendar time from submission to decision. 4. Write a meeting process dependency map — a table showing each of the 3 meeting types, the upstream process that must be complete before the meeting can run efficiently, who owns that process, and the minimum lead time required — designed to be shared in the meeting invite as a pre-read prerequisite. 5. Write a Confluence documentation health protocol — a monthly 20-minute audit routine that assigns one team member to verify the 5 most-accessed pages are accurate, flag pages older than 90 days for review, and archive pages that no longer reflect current process. 6. Write a process documentation adoption plan — a 60-day rollout sequence covering which documents to publish first, how to announce the guide to the team, the incentive for team members to update rather than bypass documentation, and the success metric for week 8. 7. Write a meeting pre-read standard — a 3-rule protocol for what must be linked in every meeting invite (relevant process document, decision to be made, and required pre-read time), reducing the context-setting minutes at meeting start by ensuring participants arrive prepared. 8. Write a strategy-to-process linking guide — a one-page document that shows how each of the 3 documented processes connects to a specific quarterly OKR, so individual contributors can see why the process discipline matters to company-level outcomes rather than just operational efficiency. **Write the product prioritization decision process document as a complete filled-in example using the template from item 1 — every field populated with realistic SaaS-specific content — so I can use it as the reference standard when I ask team leads to document their own processes.**