The procedure that exists and cannot be found
It is in a doc somewhere. Under pressure nobody finds it, so everybody improvises and the result varies by who was on shift.
Werkwijzeplaybooks
Playbooks, lenzen en workshops
Hoe we het doen, opgeschreven waar je het onder druk vindt.
Een playbook zegt wanneer je het gebruikt, de stappen, de schermafbeeldingen en de uitzonderingen, als volgorde, checklist of stroomschema. Ernaast staan de lenzenbibliotheek met beoordeelde manieren om naar een probleem te kijken, de werkbank die meerdere lenzen tegelijk draait, workshops op basis van geïmporteerde kaarten, en brainstorms die in een peiling kunnen eindigen.
- 9 parts of the business a playbook files under
- 20 lens families in the library
- 3 shapes one playbook can take
1 van 3 in Werkwijze
In de werkruimte
De pagina's die hier onder vallen
- PlaybooksWrite the procedures the team runs: a trigger, the steps with screenshots, and the exceptions.
- LensesReusable ways of looking at a problem: the cards maintained in the repository, and where each one breaks.
- Multi-lens workbenchExplore an idea through independent AI perspectives, then compare insights and disagreements.
- WorkshopsChoose a Pip Deck card, run a guided session and keep the inputs, discoveries and next actions.
- BrainstormsExplore a central question together, connect ideas and turn selected ideas into a decision.
Hoe het werkt
Van leeg record tot iets waar je op kunt handelen, in de volgorde waarin je het doet.
- 1
Pick the shape and the part of the business
Sequence, checklist or flowchart, filed under one of nine areas so the list groups the way people look.
- 2
Write the trigger, then the steps
The last row stays empty for the next step, and a pasted list splits into steps on its own.
- 3
Add the screenshots and the exceptions
The cases where the steps do not apply are the part that saves somebody an hour.
- 4
Name an owner and a review date
Required before it can go active, because a playbook nobody owns goes stale quietly.
In de applicatie
Zo ziet het eruit
Vastgelegde schermen uit Growth-OS zelf, met voorbeelddata in plaats van onze eigen records.
Het probleem dat dit oplost
Wat er misgaat als dit werk verspreid staat over spreadsheets, documenten en iemands geheugen.
An AI suggestion rewriting the wrong step
A suggestion names the revision it read and says so, rather than editing whatever now occupies a removed step's slot.
A session that changes under you
A saved workshop keeps the original prompts and a snapshot of the card it came from, so editing the library later does not rewrite what you ran.
Kernpunten
Waarom dit belangrijk is
The trigger is the finding aid
Use this when is both the first line and what search matches, so the playbook is findable at the moment you need it.
A flowchart is still readable as text
Every save also writes numbered lines, so Ask Growth Kit, Time Machine and the record dialog keep reading it.
A session cannot be completed empty
Completing a workshop needs every step checked, an output written, and at least one next action.
Eerlijke grenzen
Wat dit wel en niet belooft
Freshness is measured from the review date. Growth-OS cannot know when a playbook was last followed, and the insights verdict is an opinion about the text rather than a claim that any automation exists.
Workbench results are exploratory and session only. They clear when you leave, so copy what you want to keep. Lens cards are reviewed repository content and cannot be added from the screen.
Vragen
Veelgestelde vragen
Hiernaast gebruikt
Deze pagina's delen records met deze, dus wat je hier schrijft komt daar terug.
Doe dit werk in Playbooks, lenses and workshops
De pagina opent met de records van dit project. De ingebouwde gids beschrijft elk veld.