AI Guides › Playbooks
By Nigel Guy · 7 min read
Most people assume quality of work travels on its own. You do the job well, you wait, and you treat the lack of recognition as a verdict on your talent. It feels fine while it is failing you, because the work really is good; what is missing is a second system that carries that work into rooms you are not in.
The rule: your manager can only argue for what they can state in one sentence with a number in it, so build the sentence yourself, every month, before you are asked.
This is a playbook, not a guarantee. It will not manufacture a promotion, and it will not rescue a workplace that does not reward anyone. It makes your work easier to repeat accurately by people who have a vote.
Decisions about pay, promotion and who leads the interesting project are usually made in meetings you do not attend. Your manager, or someone above them, speaks for you in those meetings from whatever they can remember and summarise quickly. If your contribution is "she's reliable and gets things done", that is what gets said, and it does not move anyone.
The distinction that matters is between a mentor and a sponsor. A mentor advises you; a sponsor, in the usual definition, is someone senior who puts your name forward when you are absent. Writing on the subject (the Fortune piece below is one example) argues that people tend to have more of the first than the second. You may not have a sponsor today. This playbook assumes you do not, and treats your own manager as the first person to equip.
One-to-ones are the natural place to do it. Public-sector and university guidance on them describes their purpose as checking progress against objectives, recognising achievements, discussing development and career aspirations, and avoiding surprises at the formal appraisal. Notice the word "recognising": the meeting exists for this, and most people use it only to report status.
A ledger is a running record you keep in one place. This one has four columns and one monthly habit.
| Column | What goes in it | Test it must pass |
|---|---|---|
| Outcome | What changed because of your work, not what you did | Could someone who has never seen your task understand why it mattered? |
| Number | One figure: time saved, money, error count, people affected, turnaround | Can you point to where the figure came from? |
| Who noticed | Names of people outside your immediate team who used or saw the result | Would they confirm it if asked? |
| Next ask | The bigger thing this earns you the right to request | Is it a specific request, not a general wish for "more responsibility"? |
Imagine Priya, an operations coordinator at a mid-sized firm. All of this is invented for illustration.
| Outcome | Number | Who noticed | Next ask |
|---|---|---|---|
| Rebuilt the weekly supplier-chase process so late deliveries are flagged on Monday, not Thursday | Average chase time per late order down from three working days to one, from her own tracker | Warehouse lead and finance both use the Monday list | Lead the same fix for the returns process |
Her sentence for the meeting: "The Monday supplier list now cuts chase time on late orders from about three days to one, warehouse and finance both use it, and I'd like to run the same approach on returns." That is specific, checkable and ends in a request.
Use this with an AI assistant to turn raw notes into ledger lines. Check every figure against your own sources afterwards; the assistant does not know your facts and must not supply any.
Role: You are a plain-speaking career coach who has sat in many pay and promotion discussions. You help people state their contribution accurately and without exaggeration.
Context: I have a one-to-one with my manager on [MEETING_DATE]. My role is [YOUR_ROLE] at [TYPE_OF_ORGANISATION]. My notes on the past [TIME_PERIOD] are below, including any figures and where each figure came from.
[PASTE_YOUR_NOTES_AND_SOURCES]
Goal: Produce a short evidence sheet I can use in the meeting. A good result is one my manager could repeat to a senior colleague in one breath.
Steps:
1. Pick the three to five items that most changed something for the organisation.
2. For each, rewrite the entry as an outcome with one figure, and show the figure's source from my notes.
3. Mark any item where I described activity instead of result, and propose the outcome version.
4. Write one spoken sentence per item, in everyday language, with no CV phrasing.
5. For each item, suggest one specific next request it supports: [THE_KIND_OF_STEP_UP_I_WANT].
6. Name the item with the thinnest evidence and list what I could collect before [NEXT_REVIEW_DATE] to firm it up.
Rules:
- Use only facts and numbers I gave you. Never invent or estimate a figure.
- If a number or source is missing, ask me for it before writing that item.
- Do not inflate: if my contribution was shared, say so and describe my part only.
Output format: a table with columns Outcome, Number and source, Spoken sentence, Next request, followed by the thinnest-evidence note.
Self-check before answering: confirm every figure appears in my notes, and that no sentence claims credit for work I did not describe.
Fill in the meeting date, your role and organisation type, your pasted notes with sources, the step you want, and the next review date.
It will not fix a manager who will not listen, a budget that is frozen, or a culture where recognition goes by seniority regardless of results. It also does not replace building relationships; it gives those relationships something concrete to carry.