Leverage with AITeam and rules
Some use AI quietly, some fear it, and there are no rules
Hands-on sessions on your own work, and a short written document about what is allowed.
Who this is for Teams of a few to a few dozen where AI is already being used, only nobody talks about it.
The problem
The team does not know what is allowed
Some people already paste work text into free tools, because it is faster. Others try nothing, because they do not know whether it is allowed and suspect it is about their jobs. There is no written rule, so everyone decides alone, and both the risk and the benefit land at random.
You will know it by
- You do not know which tools your team already uses.
- AI comes up as a joke, or not at all.
- Somebody has already pasted customer data somewhere they should not.
- There was a training session, and nothing changed after it.
Possible solutions
Not every road leads to me
Leaving it as it is
Changing nothing and trusting people to work it out.
Where it stands An honest choice in a very small team. The limit is that an unwritten rule protects neither the person nor you.
An internal announcement and one document
Writing the rules yourself and publishing them.
Where it stands Half the job, and better than nothing. Without practice most people still never try the tool.
A generic online course
Recorded courses about AI in general.
Where it stands Cheap and fine for orientation. The limit is that they talk about somebody else's work, so people return to their old habits.
Practice on your own work, with the rules alongside
Sessions where everyone tries a task of their own, plus a short document about what is allowed.
Where it stands This is the one I build. Worth it when you want something to actually change afterwards.
What I set up
Hands-on sessions on your own work, not a slide show. We start with what people are worried about: whether this is about their jobs, who answers for a mistake, what may and may not be pasted in. Then everyone tries a task of their own and leaves with the thing that worked. Alongside it comes a short written document: which tools are allowed, what data may go into them, what to do when something goes wrong, and why customer data belongs only on plans that come with a data processing agreement.
How it goes in
- I talk briefly with a few people, so the session is about their actual work.
- The session: the worries, the limits, then practice on their own tasks.
- The rules are written after the session, from what it surfaced.
- A short return a few weeks later: what stuck and what did not.
The limit This is not legal advice. Contracts, a data protection impact assessment or an employment law question need a lawyer, and that is said at the outset rather than afterwards.
The work The session and the document fit into a short engagement, but the value shows only if somebody comes back a few weeks later to see what stuck.
The prices on this site are final.
What it brings
People stop hiding it
When the rules are clear you can see what is really being used, and only then can it be managed.
Customer data stays where it belongs
A written limit protects both the company and the employee who would otherwise decide alone.
Something changes afterwards
Someone who tried their own task comes back to it the next day. Someone who watched a presentation does not.
How you check it yourself
Before the session, ask the team two things anonymously: which tools they use for work, and whether they know what is allowed. Ask the same two questions two months later.
Is this your job?
Tell me how this runs at your place now. On a 30 minute call I will say whether it is worth automating, where I would start and what it needs.
Book a 30 minute callThe call is free, with no obligation and nothing to sign.
Not sure which job is first for you? The free assessment says where the hours go. Start the assessment
Common questions
Will this frighten the team about their jobs?
That question is asked first rather than avoided until the end. The honest answer depends on your intentions, and if they involve cutting headcount, a training session is not the place to disguise it. In practice people settle once they can see the limits.
Whole team, or a few people?
It is often better to start with a few people from different parts of the business, who then become the ones others ask. A whole-team session makes sense once the rules already exist.