Skip to main content
This is a playbook, not product reference. It is written from your point of view: you decide the strategy, we recommend how to run it, and every recommendation links to the product rubric that makes it enforceable. Two questions sit at the center of every rollout:
  1. How do you take a use case from a first idea to production, and then to adoption at scale?
  2. How do you let people build with AI without losing control of security, quality, and compliance?

From a use case to production

The lifecycle in phases, the environments, and when to use a workspace or stay no-code.

Who does what

The operating model: squads, committees, and AI champions, and who holds which right.

One organization or several?

The decision most teams hesitate on, and where groups fit.

Opening strategies

Open to everyone or curate specific use cases, and how to open without chaos.

​
The one principle

Governance on the platform works on levels, and each level can only tighten the one above, never widen it. On conflict, the tightest limit wins. Inside its own envelope, each level distributes freely. Keep that in mind as you read the rest of this playbook. It is detailed in Opening strategies and in Governe.