Reports, procedures, meeting notes and planning. 4 reviewed prompts for operations.
Designs the structure, ownership, page templates, and upkeep routine for a team or company knowledge base so people find answers and content stays current. Use when starting a wiki or help center, or fixing one nobody trusts.
Builds a practical plan for rolling out an organizational change: impact by group, stakeholder map, communication calendar, resistance handling and adoption metrics. Use it when introducing a new process, system or structure.
Builds a program charter and execution plan for a multi-team technical initiative: scope, milestones, dependencies, risks, decision rights, and status cadence. Use when kicking off or re-planning a large engineering program.
Diagnoses how a team currently plans and delivers work and builds a phased plan to adopt agile practices that fit, with metrics and risks. Use when starting, resetting, or rescuing an agile rollout.
