download dots

🪜 Start Small and Grow the Programme

Put a sensible process around how your organization uses AI, without stopping anyone getting work done. These prompts build the approval queue, the register of what is running, the log of what each tool actually did, and the policy an assistant checks submissions against. Written for the person who has been asked to own this and given no software to do it with.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Start Small and Grow the Programme

Copy

I have been asked to set up AI governance and the scope keeps growing until nothing starts. Build me a roadmap app. Define phases, each with the capabilities it delivers, the effort, the owner and the target dates, and let me park everything not in the current phase visibly so it is recorded rather than argued about now. Keep the first phase deliberately small, typically a tool inventory and a working approval queue. Measure progress by adoption, such as the proportion of known tools registered, submissions coming through the process, and reviews happening on time, rather than by documents produced. Record what has actually gone wrong, since that is the honest justification for adding the next control. Add an AI agent that reviews our current position and recommends what is genuinely worth doing next based on our own gaps and incidents rather than a generic maturity model, and that tells me plainly where we have added a control nobody uses. Automate two things: a scheduled monthly progress summary, and a prompt to review the roadmap whenever an incident suggests a missing control. Two logins: a phase owner who updates their own area, and a governance owner who sets the roadmap.

STATUS · LIVE
v1

01 / Spark - intelligence awakens

Start Small and Grow the Programme

Run governance as a staged rollout with a deliverable first phase, parked later phases, and adoption-based progress.

// the spark catches · intelligence awakens · the answer unfolds

Governance programs fail by trying to be complete on day one. This defines a small first phase, gets it working, and adds the rest deliberately.

What's Included

  • A small first phase that can actually be delivered.
  • Later phases parked visibly so nothing is lost or argued about.
  • Progress measured by what works not by what is documented.
  • An assistant that says what is worth doing next.

How To Use

  1. Start with an inventory and an approval queue. Nothing else on day one.
  2. Park later phases visibly so people stop arguing about them now.
  3. Measure adoption, not documentation.
  4. Add a control when something has gone wrong or is clearly about to.

Deliver phase one with the governance office, and justify it with the business case.