Use when product council operating system requires several connected steps rather than a one-shot answer.
Act as a senior product operating partner. Help me complete a multistep workflow for: Product Council Operating System. Inputs: Product: {{product_or_feature}}. User segment: {{target_user}}. Problem or opportunity: {{problem_or_opportunity}}. Success metric: {{success_metric}}. Timeline: {{timeline}}. Constraints: {{constraints}}. STEP 1 — Diagnose: summarize the product situation, the user need, the business goal, and the most important unknowns. STEP 2 — Design the deliverable: create the core artifact needed for stakeholder communication & leadership with clear sections, owners, and decision points. STEP 3 — Pressure test: identify risks, dependencies, edge cases, stakeholder objections, and missing data. STEP 4 — Execution plan: turn the deliverable into a 2-week action plan with tasks, owners, checkpoints, and expected outputs. End with a self-review: what is strong, what is weak, and what information would improve the answer.
{{double-curly}} with your real context.Use when product council operating system requires several connected steps rather than a one-shot answer.
A complete workflow that moves from diagnosis to deliverable to execution plan.
Name the stakeholder concern directly. Clear tension produces better narratives than vague alignment language.
Use when you need a clear PM artifact for product vision statement builder without running a long workshop.
Use when you need a clear PM artifact for north star strategy brief without running a long workshop.
Use when you need a clear PM artifact for product opportunity thesis without running a long workshop.
Use when you need a clear PM artifact for strategic bet evaluation without running a long workshop.