Welcome to the Worksona Leadership Runbook Chatbot!
How to use:
1. Enter your OpenAI API key above
2. Paste your leadership challenge, project idea, or team situation
3. Get instant runbook analysis with actionable commands
Available runbook commands:
• /demonstrate-not-decorate - Ship proof, not polish
• /map-before-make - Draw the terrain, then march
• /drive-through-documentation - Docs are a control surface
• /orchestrate-by-theme - Fewer, bigger, better
• /enforce-measurement - Evidence or it didn't happen
• /champion-adoptability - Adoption is the product
• /mandate-interoperability - Open by default
Ready to lead like you ship? 💻
Full Canvas View
🚀 Worksona Leadership Runbook Help
How to Use
Paste your leadership challenge, project idea, or team situation into the input field.
The AI will analyze it against all 7 runbook commands and provide specific, actionable guidance.
Available Commands
1. /demonstrate-not-decorate
Ship proof, not polish - Focus on 7-day demo cycles
We're spending too much time perfecting the UI instead of getting real user feedback. Our team has been polishing features for weeks without shipping anything users can actually test. How do we shift to rapid demo cycles and prove value quickly?
2. /map-before-make
Draw the terrain, then march - Create user journeys and workflows first
Our development team keeps building features without understanding how they fit into the overall user experience. We have no clear user journey maps or workflow diagrams, and different teams are making assumptions about how users will interact with our product. How do we create shared understanding before we build?
3. /drive-through-documentation
Docs as control surface - Treat documentation as a leadership tool
Our documentation is scattered, outdated, and nobody knows how to contribute to it. New team members struggle to onboard, and we're losing institutional knowledge. How do we make documentation a strategic asset that actually drives our engineering culture?
4. /orchestrate-by-theme
Fewer, bigger, better - Align under 2-3 major themes
We have 15 different initiatives running simultaneously and teams are confused about what's most important. Resources are spread thin, and we're not making meaningful progress on any single area. How do we consolidate around fewer, bigger themes that will actually move the needle?
5. /enforce-measurement
Evidence or it didn't happen - Require metrics and avoid anecdotes
We think our new feature is successful because the team says users love it, but we don't have any concrete data to back this up. Decisions are being made based on gut feelings and anecdotes rather than evidence. How do we build a culture of measurement and data-driven decisions?
6. /champion-adoptability
Adoption is the product - Focus on ease of onboarding and time-to-value
Our API is incredibly powerful with tons of features, but it takes new developers 2-3 weeks to get their first integration working. The onboarding process is complex, documentation is hard to follow, and time-to-value is too slow. How do we make adoption the primary success metric?
7. /mandate-interoperability
Open by default - Prevent silos with discoverable interfaces
Our microservices architecture is turning into isolated silos that can't communicate effectively with each other. Teams are building custom solutions instead of reusable components, and we're creating data inconsistencies across systems. How do we enforce interoperability by default?
Pro Tips
Be specific about your situation for better analysis
Use the "Run Full Runbook Analysis" button to get comprehensive coverage
Copy individual responses or the entire conversation for documentation
Ask follow-up questions to dive deeper into specific commands
Press Enter to send messages, Shift+Enter for new lines
System Nomenclature Examples
Using Real Command Syntax
/demonstrate-not-decorate --bias "Favor SVS" --advise "Propose 2-3 demo candidates for mobile app, select 1" --critique "Block UI polish theater, enforce tangible user value" --build "Create 7-day prototype demo plan with user testing" --analyze "Measure user engagement and feedback quality" --learn "Capture learning from demo cycle and refine approach"
Our mobile app team is spending 3 weeks on UI polish but hasn't shown users a working prototype. Apply this command to shift us to rapid demo cycles.
/map-before-make --bias "Always map before build" --advise "Output API user journey + service workflow diagrams" --critique "Flag missing interfaces between services and ownership gaps" --build "Break API redesign map into thin backlog slices" --analyze "Validate service integration contracts and dependencies" --learn "Update architecture maps and spread mapping discipline"
Our API redesign project team wants to start coding immediately, but we haven't mapped user journeys or defined clear interfaces between services.
/drive-through-documentation --bias "Docs as leadership tool" --advise "Propose README/DECISIONS/RUNBOOK/CHANGELOG structure" --critique "Review discoverability and freshness of scattered wikis" --build "Set up doc scaffolds and CI for automated freshness checks" --analyze "Run documentation freshness audit across 5 tools" --learn "Update CI policies and simplify doc contribution process"
We have scattered documentation across wikis, outdated READMEs, and no decision logs. Make docs a strategic control surface.
Try All Three Commands Together
Copy all three command examples to see how they work as an integrated approach to leadership challenges.
Full Runbook Analysis Example
Run complete runbook analysis: Our SaaS startup has 12 engineers, $2M runway, 6 months to Series A. We're building a developer tools platform but struggling with: 1) Feature creep - engineering wants to build everything, 2) No user feedback loops - we haven't shipped anything users can test, 3) Scattered documentation across 5 different tools, 4) 8 different "priority" initiatives running simultaneously, 5) Decisions made in Slack with no record, 6) New developers take 3 weeks to contribute, 7) Each team uses different tools and processes. We need systematic leadership approach to get to product-market fit.
Situation-Based Examples
Our startup team is building an AI platform but we're not sure how to prioritize features and get user feedback quickly. We have limited runway and need to prove product-market fit within 6 months. The team keeps wanting to add more features instead of validating what we have.
I'm leading a product team that's struggling with unclear requirements and constantly changing priorities. Stakeholders give conflicting feedback, engineering is frustrated by scope creep, and we're missing deadlines. How do we establish clear decision-making processes and stick to our roadmap?
We need to improve our developer onboarding process - it currently takes new hires 2-3 weeks to become productive. Our codebase is complex, documentation is sparse, and senior developers spend too much time helping newcomers instead of building features. How do we scale knowledge transfer?