Behaviour Owner

Purpose Give key people clear responsibility for making the behaviour work
Intervention type Behavioural stewardship & embedded accountability
Audience Team leads, product managers, delivery owners, or ops leads responsible for day-to-day AI performance
Time 1 hour setup, 1 hour fortnightly check-in, optional 60-min monthly review ≈ 4h/month

Expected outcomes

• Users: Know who to go to when the AI behaviour breaks, drifts, or needs adjusting

• Teams: Build a clear review rhythm and behavioural playbook, led by a trusted peer

• Business: Avoid costly drop-offs post-rollout with visible accountability and reduced friction

• Organisation: Behavioural adoption becomes owned and managed at team level.

What to bring to the session

• Behaviour Steward Brief Sheet. (Within the steps)

• Ownership Network Map. (Within the steps)

Steps

1 | Spot the Right Behaviour Owner

Step 1: Look for these signals

Choose someone who is:

• Close. Has access to where the behaviour happens day-to-day

• Reliable. Already seen as a go-to person for “how we get things done”

• Trust. Trusted by their peers, their advice is acted on

• Influential. Able to adjust or influence small levers: prompts, processes, hand-offs

• Results-oriented. They care about what works, not just what was planned

• Pragmatic. Spot friction early and fix it fast.

• Empathetic. Has either behavioural training or an intuitive sense about people.

If you're stuck, ask:

“Who does the team already go to when the task is blocked, skipped, or unclear?”

This might by you AI Champion. Or someone entirely different.
Common places to find them: product leads, ops managers, delivery leads, team supervisors.

2 | Outline the Role

Step 2: Scope the Behaviour Owner’s role using 6 pillars

Use the following six pillars to shape the Behaviour Owner’s scope:

Step 3: Define success & KPIs

Outline 3 things:

1. What’s the specific and observable behaviour?
   e.g. “We want everyone to run one AI-generated version before finalising their weekly report.”

2. What’s the shift we’re aiming for?
   e.g. “From skipping the AI tool to using it as the first draft helper.”

3. How will we track it?
   Offer concrete examples:

• % of team using AI in the defined task

• Number of support/friction requests raised

• Time saved per use or error reduction

• Feedback signals: “I forgot”, “It’s too slow”, “Doesn’t help me”

Step 4: Map the Behaviour Support Network

The Behaviour Owner owns the outcome, not the specific tasks.
So they know who to involve, when and for what.

Use the Ownership Network Map to log:

Step 5: Announce their role to the team

Use this sample message:

“Hey team, [Name] is now our Behaviour Owner for [task].
Their job is to help this AI behaviour stick, adapt, and improve over time.
If you’re stuck, have feedback, or notice friction, go to them first.
They’ll run check-ins and help us make this part of how we work.”

Step 6: Run a Behaviour Health Check every 2 weeks

Block a 20-min slot in the Behaviour Owner’s calendar.
Use the Behaviour Health Tracker to guide the review.

Check:

• Is the behaviour happening?

• What’s working well?

• What’s getting skipped or blocked?

• What team signals are showing up? (hesitation, confusion, workarounds)

Optional: Run a monthly Behaviour Sync with key stakeholders if changes are needed across teams, prompts, or incentives.

Resources

Responsibilities of a Behaviour Owner

Behaviour Tracking

• Check in weekly or fortnightly on how the behaviour is playing out in real work

• Use real signals (metrics, comments, task logs), not just guesses

Friction Spotting

• Gather feedback on blockers, confusion, or drop-off

• Run small tests to reduce friction (e.g. prompt tweaks, reminders, flow nudges)

Adaptation & Maintenance

• Update workflows or rituals when the behaviour starts slipping

• Flag upstream issues (tools, incentives, training gaps) to the right person

Peer Support & Communication

• Be a sounding board for teammates

• Share tips, spotlights, or insights during stand-ups, retro, or async channels

Other methods within the adapt block