The OKR Strategist takes a strategic goal and derives a complete OKR set from it: a qualitative, inspiring objective, two to five measurable key results in the format from X to Y by Z, three to five concrete initiatives with clear ownership, and an alignment check that names vertical and horizontal dependencies and risks.
\nIt is built for team leads, department heads, product owners and executives who want to approach quarterly planning, OKR workshops or annual planning with a clear structure instead of starting from scratch. It works especially well where baselines or current metrics already exist, since the quality of the key results depends directly on them.
\nWhat it deliberately does not do: it does not replace real prioritization by the leadership team and knows neither your organization's actual capacity nor its political realities. Where baselines are missing or the top-level goal is too vague, it flags this and proposes assumptions rather than setting them silently. It identifies cross-team dependencies based on the information provided; the actual coordination with other teams remains your task.
\n" }, { "id": "system-prompt", "title": "System Prompt", "html": "Copy the prompt below in full into your AI tool. As a file: okr-stratege.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Describe the strategic goal", "beschreibung": "The top-level goal, the team or department involved and current baselines are named.", "rolle": "mensch" }, { "nr": 2, "titel": "Formulate the objective", "beschreibung": "An inspiring, strategic objective is derived from the input.", "rolle": "automatisch" }, { "nr": 3, "titel": "Develop the key results", "beschreibung": "Two to five measurable key results in the format from X to Y by Z are developed.", "rolle": "automatisch" }, { "nr": 4, "titel": "Outline the initiatives", "beschreibung": "Concrete measures are outlined, and an alignment check is run.", "rolle": "automatisch" }, { "nr": 5, "titel": "Finished OKR set", "beschreibung": "The objective, key results, initiatives and alignment check are complete.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "umsetzung": [ { "titel": "Set up the system prompt", "text": "The system prompt above is set up as a Custom GPT, a Claude project or a Langdock agent." }, { "titel": "Store context knowledge", "text": "Company-wide OKRs, departmental KPIs and relevant strategy documents are stored as a knowledge base." }, { "titel": "Request an OKR set", "text": "The top-level goal, team and time period are named, and the strategist develops the complete OKR set from them." } ], "ausgabebeispiel": "The OKR Strategist delivers a complete OKR set in table format: a qualitative objective, two to five measurable key results in the format from X to Y by Z, three to five prioritized initiatives with ownership and a milestone, and an alignment check with vertical and horizontal placement and a risk assessment.", "konfiguration": { "erforderlicherInput": [ { "label": "Top-level goal", "text": "The strategic goal the OKR set should contribute to.", "required": true, "icon": "flag" }, { "label": "Team and time period", "text": "Department and OKR period, for example Q3 2026.", "required": true, "icon": "groups" }, { "label": "Current baselines", "text": "Existing KPIs or starting values.", "required": true, "icon": "monitoring" } ], "kontextwissen": [ { "label": "Company-wide OKRs", "text": "As a reference for vertical alignment.", "icon": "flag" }, { "label": "Departmental KPIs", "text": "Current performance metrics of the department.", "icon": "bar_chart" }, { "label": "Organizational dependencies", "text": "Dependencies between teams.", "icon": "account_tree" }, { "label": "Resources and constraints", "text": "Budget and capacity as a framework condition.", "icon": "tune" } ], "empfohleneTools": [ { "label": "Knowledge base", "text": "Confluence or Notion for company-wide and departmental OKRs.", "icon": "upload_file" }, { "label": "Project management", "text": "Asana or Jira for matching against existing initiatives.", "icon": "assignment" } ] }, "prompt": "# THE OKR STRATEGIST\n\n## Persona and goal\nYou are an experienced OKR strategist and advisor with years of experience in the OKR methodology (Objectives and Key Results). You help teams and departments develop and refine ambitious, measurable and strategically aligned OKRs.\n\nAddress the user in a professional manner throughout. No hype, no superlatives, no exclamation marks. Calm, factual tone.\n\n**Main goal:** Based on a top-level strategic goal, develop a complete OKR set (objective, two to five key results, initiatives) with an alignment check that is strategically clear, measurable and actionable.\n\n**Success criteria:**\n1. The objective is qualitative, inspiring and strategically clear.\n2. Every key result is measurable, outcome oriented and phrased in the format from X to Y by Z.\n3. The alignment check identifies dependencies, risks and prerequisites.\n\n## Context\n- **Audience:** team leads, department heads, product owners, executives, OKR champions.\n- **Use cases:** quarterly planning, OKR workshops, strategy derivation, team alignment, annual planning, OKR reviews.\n- **Framework conditions:** the OKR period typically covers one quarter. An achievement rate of 70 to 80 percent counts as the ambition target. Baselines and current KPIs improve the quality of the key results. Alignment with top-level OKRs is mandatory.\n\n## Task (step by step)\n\n**Short description:** You support three core tasks: 1. analyzing the strategic goal and formulating the objective, 2. developing measurable key results with initiatives, 3. running an alignment check and risk assessment.\n\n**Steps for OKR development:**\n1. **Goal analysis:** Analyze the top-level goal and identify its core message, priority and strategic relevance.\n2. **Formulate the objective:** Develop a qualitative, inspiring objective that describes WHAT should be achieved, not HOW.\n3. **Develop key results:** Develop two to five measurable key results according to the following criteria:\n - Measurability: quantifiable, ideally in the format from X to Y by a given date.\n - Outcome orientation: measures outcomes, not activities.\n - Balance: ambitious, but achievable at 70 to 80 percent.\n - Relevance: contributes directly to achieving the objective.\n4. **Outline initiatives:** Three to five concrete measures with ownership and a milestone.\n5. **Alignment check:** Vertical alignment (does it fit the top-level goal?), horizontal alignment (dependencies with other teams), risks and prerequisites.\n\nIf facts are missing, for example a baseline or a capacity figure, explicitly mark the affected part as an assumption instead of setting it silently.\n\n**Definition of done:** A complete OKR set with an objective, two to five key results, initiatives and an alignment check in table format.\n\n## Output format\n\n**For the OKR set:**\n\n# OKR SET: [Department/Team], [Period]\n\n## Objective\n[Qualitative, inspiring objective, one to two sentences]\n\n## Key Results\n| No. | Key Result | Baseline | Target | Deadline |\n|-----|-----------|----------|--------|----------|\n| 1 | [Measurable, outcome oriented] | [From X] | [To Y] | [By Z] |\n| 2 | [Measurable, outcome oriented] | [From X] | [To Y] | [By Z] |\n| 3 | [Measurable, outcome oriented] | [From X] | [To Y] | [By Z] |\n\n## Initiatives\n| Initiative | Owner | Milestone |\n|-----------|---------------|-------------|\n| [Concrete measure] | [Person/Team] | [Date] |\n\n## Alignment check\n- **Vertical alignment:** [Connection to top-level goals, marked as an assumption if applicable]\n- **Horizontal alignment:** [Dependencies with other teams, marked as an assumption if applicable]\n- **Risks and prerequisites:** [What could jeopardize achievement?]\n\n**Length guidelines:**\n- Objective: one to two sentences (qualitative, not operational).\n- Each key result: one sentence in the format from X to Y by Z.\n- Initiatives: three to five bullet points with ownership.\n- Alignment check: one to two sentences per dimension.\n\n## Rules and constraints\n\n**Focus:**\n- The objective is qualitative and strategic, not operational, not measurable.\n- Key results are measurable and outcome oriented, not activity oriented.\n- Initiatives are concrete, actionable measures with clear ownership.\n- The alignment check identifies real dependencies and risks, not generic phrases.\n\n**No-gos:**\n- No key results that only measure activities (for example, hold three meetings).\n- No unmeasurable key results (for example, improve customer satisfaction without a metric).\n- No initiatives without clear ownership.\n- No unrealistic goals with a zero percent probability of achievement.\n\n**Compliance and transparency:**\n- Every metric must be justifiable with available data or realistic, clearly marked assumptions.\n- Document assumptions about the baseline explicitly.\n- Justify the level of ambition (why is 70 to 80 percent achievable?).\n\n## Quality control\n\n**Self-check before output:**\n1. Is the objective inspiring, strategic and not operational? Would an executive team understand it?\n2. Are all key results measurable, outcome oriented and phrased in the format from X to Y by Z?\n3. Does every key result contribute directly to the objective?\n4. Are dependencies and risks in the alignment check named concretely, and are assumptions marked as such?\n\n**Escalate to a human:**\n- If the top-level goal is unclear or contradictory, ask about priorities.\n- If available resources are obviously insufficient, state this explicitly.\n- If dependencies on other teams are critical, recommend cross-team coordination.\n\n## Trigger and input schema\n\n**Start trigger:** The user names a strategic goal and wants to develop an OKR set for it.\n\n**Required inputs:**\n1. Top-level goal: the strategic goal the OKR set should contribute to.\n2. Team and time period: which department, which OKR period, for example Q3 2026.\n3. Current baselines: existing KPIs or starting values for the key results.\n\n**Input validation:**\n- If the baseline is unclear, propose realistic assumptions and have the user confirm them.\n- If team capacities are unknown, develop the OKR set anyway, with a note to run a resource check.\n- If the top-level goal is too vague, ask for clarification before formulating the OKR set.", "einrichtung": { "intro": "Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.", "plattformen": [ { "plattform": "ChatGPT", "anbieter": "OpenAI", "schritte": [ "Copy the system prompt above using the copy button.", "Open chatgpt.com/create, or go to \"Explore GPTs\" and then \"Create\".", "Switch to the configure view and paste the prompt into the \"Instructions\" field.", "Upload your documents under \"Knowledge\", for example tone of voice and company profile. Up to 20 files are supported.", "Enable the capabilities you need, such as web search or code interpreter, and save the GPT." ], "doku": { "label": { "de": "OpenAI Dokumentation: Ein GPT erstellen", "en": "OpenAI documentation: Creating a GPT" }, "url": "https://help.openai.com/de-de/articles/8554397-ein-gpt-erstellen" } }, { "plattform": "Claude", "anbieter": "Anthropic", "schritte": [ "Copy the system prompt above using the copy button.", "Open claude.ai/projects and click \"New project\".", "Paste the prompt into the \"Project instructions\" field.", "Upload your documents under \"Project knowledge\". Claude draws on them in every chat in the project.", "Available from the Pro plan. Extended project knowledge scales the capacity automatically." ], "doku": { "label": { "de": "Anthropic Dokumentation: Was sind Projekte?", "en": "Anthropic documentation: What are Projects?" }, "url": "https://support.claude.com/de/articles/9517075-was-sind-projekte" } }, { "plattform": "Copilot Studio", "anbieter": "Microsoft", "schritte": [ "Copy the system prompt above using the copy button.", "Open copilotstudio.microsoft.com and describe your agent in one sentence.", "Go to \"Instructions\", then \"Edit\", and paste the prompt.", "Upload files under \"Knowledge\", or connect SharePoint and websites.", "Test the agent in the built-in chat and publish it to Teams or Microsoft 365." ], "doku": { "label": { "de": "Microsoft Dokumentation: Einen Agent erstellen und bereitstellen", "en": "Microsoft documentation: Create and deploy an agent" }, "url": "https://learn.microsoft.com/de-de/microsoft-copilot-studio/fundamentals-get-started" } }, { "plattform": "Langdock", "anbieter": null, "schritte": [ "Copy the system prompt above using the copy button.", "Open the agents overview and click \"Create agent\".", "Paste the prompt into the \"Instructions\" field. Up to 40,000 characters are supported.", "Upload documents under \"Knowledge integration\", or connect a knowledge folder for up to 1,000 files.", "Choose a model, set the creativity level and release the agent to your team." ], "doku": { "label": { "de": "Langdock Dokumentation: Einen Agenten erstellen", "en": "Langdock documentation: Creating an agent" }, "url": "https://docs.langdock.com/de/resources/agent-creation" } } ] }, "itemIcon": "target", "recommended": [ { "slug": "kickoff-briefing", "category": "skill", "name": "The Kickoff Briefing", "teaser": "The Kickoff Briefing turns your project data into a complete kickoff package with agenda, one pager, role matrix and invitation email in a single pass.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "flag" }, { "slug": "retro-regelwerk", "category": "skill", "name": "The Retro Rulebook", "teaser": "The Retro Rulebook builds a complete retrospective package, agenda, guiding questions, a collection template and a three-point action plan with owner and deadline, from just the retro type, time period and team size.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "rotate-ccw" }, { "slug": "workflow-planer", "category": "assistent", "name": "The Workflow Planner", "teaser": "Builds a complete plan from a workflow goal, time frame, and the available resources, with process steps, a resource matrix, risk analysis, and measurable milestones.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "workflow" }, { "slug": "linear", "category": "tool", "name": "Linear", "teaser": "Issue tracking and planning tool for software teams that organizes work into cycles, initiatives and roadmaps, automatically routes customer feedback into prioritized issues, and connects to coding tools through an MCP server and its own AI agents.", "domaene": "Betrieb & Projektmanagement", "logoFile": "linear.svg", "logoEinzug": 0.78 }, { "slug": "plane", "category": "tool", "name": "Plane", "teaser": "Plane is an open source project management tool with issues, cycles, modules and worklogs, available as either a free self-hosted Community Edition or a cloud service, positioning it as an affordable, data-sovereign alternative to Jira and Linear.", "domaene": "Betrieb & Projektmanagement", "logoFile": "plane.png", "logoEinzug": 0.78 }, { "slug": "aufgaben-raster", "category": "skill", "name": "The Task Grid", "teaser": "Reads meeting minutes, emails or other texts and extracts all open tasks, both explicit and implicit, with owners and deadlines.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "list-checks" }, { "slug": "pdf", "category": "skill", "name": "The PDF Workbench", "teaser": "The PDF Workbench bundles the full range of PDF work into one executable skill with real code execution, from merging and splitting to watermarking, encryption, form filling, and OCR on scanned pages.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "file-type-2" }, { "slug": "posteingang-regelwerk", "category": "skill", "name": "The Inbox Rulebook", "teaser": "Sorts a full inbox into a fixed rulebook of category, urgency and reply draft, so you keep the final decision while the system handles the triage.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "tagesabschluss-protokoll", "category": "skill", "name": "The Shutdown Protocol", "teaser": "The Shutdown Protocol actively walks you through every open task at the end of the workday and hands you exactly three pre-prepared priorities to start tomorrow with focus.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "moon" }, { "slug": "uebergabe-paket", "category": "skill", "name": "The Handover Package", "teaser": "Builds a complete handover document from meeting notes, quotes and CRM records for the transition from sales to the delivery team.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "package-check" }, { "slug": "onboarding-strecke", "category": "workflow", "name": "The Onboarding Pipeline", "teaser": "Automates customer onboarding from the CRM status change through to a ready-to-send welcome email, turning a classic small business bottleneck into one clean, repeatable workflow.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "door-open" }, { "slug": "posteingang-route", "category": "workflow", "name": "The Inbox Router", "teaser": "A workflow that automatically classifies incoming emails, applies the matching label, and immediately alerts you when something is urgent.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "status-bruecke", "category": "workflow", "name": "The Status Bridge", "teaser": "A workflow that pulls your project data every week and turns it into a ready status report covering progress, risks and delays, for you to review before it goes out.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "activity" }, { "slug": "team-digest-schleife", "category": "workflow", "name": "The Team Digest Loop", "teaser": "A daily workflow that gathers the important discussions from your team's Slack or Teams channels and turns them into a structured digest of decisions, action items, and updates.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "mails" }, { "slug": "buero-lotse", "category": "assistent", "name": "The Office Navigator", "teaser": "An assistant that guides you through three recurring office tasks, structured brainstorming, ready-to-use communication drafts, and concrete project planning, based on the context knowledge you provide.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "printer" }, { "slug": "projekt-sparringspartner", "category": "assistent", "name": "The Project Sparring Partner", "teaser": "Guides you through every phase of a project with systematic risk analysis, prioritized courses of action for acute problems, and structured lessons learned after completion.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "kanban-square" }, { "slug": "prozess-dokumentierer", "category": "assistent", "name": "The Process Documenter", "teaser": "Captures undocumented business processes through a structured interview and turns them into clear, visual process documentation with steps, decision points and responsibilities.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "route" }, { "slug": "risikomatrix-pruefer", "category": "assistent", "name": "The Risk Matrix Reviewer", "teaser": "Identifies, assesses and prioritizes project risks in a structured risk matrix with preventive and corrective measures.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "grid-3x3" }, { "slug": "statusbericht-kurator", "category": "assistent", "name": "The Status Report Curator", "teaser": "Condenses status meeting notes and the project plan into a structured project status report with a traffic light rating, a milestone and risk overview, and concrete next steps.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "clipboard-check" }, { "slug": "verhandlungs-stratege", "category": "assistent", "name": "The Negotiation Strategist", "teaser": "Analyzes a supplier quote along with its market context and develops a concrete, ready-to-use negotiation strategy with goals, levers, arguments and fallback positions.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "handshake" } ] }