Rolling out AI know-how in a company of 250 people

In a company of 250 people, AI use usually starts everywhere at once. Marketing has its prompts, sales has a shared document, engineering has rules files in a few repositories, and the rest of the company asks whoever seems to know. Nobody planned it, and nobody knows which version is the right one.

Bringing order to that does not need a big programme. It needs a library, a few clear rules and someone who owns each piece.

Step 1: Start with one team and one skill

Pick the team that already uses AI most and the knowledge they repeat most often. In marketing, that is usually the brand voice. In support, the product knowledge. Write it down as a skill, connect the tools the team already uses, and let them work with it for two weeks.

The point of the first step is not coverage. It is to show that one well-kept skill changes the answers people get.

Step 2: Decide who owns what

Every skill needs an owner: the person who keeps it current. The brand lead owns the brand voice, product management owns the product facts, the platform team owns the coding conventions. Ownership is not a job title in the tool; it is a decision you write down.

In sqemes, who may see a playbook and who may edit it are set separately. Most skills can be visible to everyone and editable by a few. Some, like pricing answers or a hiring plan, should be visible only to the people who need them.

Step 3: Set the defaults once

Instead of deciding every playbook by hand, set workspace defaults for how new playbooks start: who can see them and who can edit them. Use the three roles as they are meant: members use playbooks, editors write them, admins set the rules.

If you want a second pair of eyes, switch on review. New playbooks then stay with their author until they are released, and a change to a shared one becomes a proposal. The team keeps working with the released version until the change is approved.

Step 4: Add personas for the roles

Once two or three teams have their skills, add personas for the roles that use AI every day. A persona knows which skill or prompt to load for which task, so people do not have to choose. This is where the library starts to feel like part of the work instead of another tool.

Step 5: Keep it current

Knowledge goes stale silently. Three habits help:

• Update in one place. When something changes, change the skill, not the chats.
• Look at what is used. Usage statistics show which playbooks are used in which channel, never who used them. A skill nobody uses is either not needed or not found.
• Use versions. Every saved change is kept, so a bad edit is one restore away.

What to keep in mind about data

Before a rollout, people will ask where the content goes. Be ready with clear answers: where the library is hosted (for sqemes, in the EU), whether content is used to train models (it is not), and whether you can use your own AI provider keys (you can). If a team needs everything on its own servers, sqemes can be self-hosted.

See how governance works or what sqemes does for team leads.