# people.md

Who is around this work. Use the right name, the right register, the right channel.

| Person | Role | How to write to them |
| --- | --- | --- |
| Chris Robb | Runs the accelerator programme | Direct, short, outcome first. Slack. |
| The People Ops lead | Owns employee-data policy | Formal, written, always in email so there is a record. |
| The guild | ~30 accelerators across BUs | Demo-first. Show the artifact, then the how. Slack `#ai-accelerators`. |
| A BU team adopting a skill | Non-technical, busy | No jargon. One install line. One example. One place to ask. |

## Standing constraints

- Never quote someone's Slack message in a doc without asking them first.
- Never name a colleague in anything that leaves Prosus.
- If a title is not in this file, write the name without a title.

## Register per surface

- Slack: lowercase is fine, under 60 words, one link.
- Email: full sentences, subject line states the ask.
- A deck: one claim per slide, no bullets under 6 words.