Pitch Your Own Role Change

When to use it

Someone likes where they work but wants their job to change. More time on work they are good at, a new area the business needs, less of the work that drains them. They do not want a new employer, a promotion round or a pay talk. They want a different shape of job, and a manager who says yes.

Most of these asks fail for one reason. The manager hears "I want to do more interesting work" and thinks "then who does your current work". This Move answers that question first. One input (the user's notes on their job and what they want), one output (a one-page proposal and the task map behind it), in one sitting.

Not for: asking for a pay rise or a promotion (different conversation, different evidence), applying for an advertised internal job, negotiating a reduction in hours or flexible working (that has its own process and often its own rules), or leaving.

What it asks you

Ask for everything in one numbered message.

1. Your current role in one line, and who you report to.
2. Your recurring tasks, as a rough list, with hours per week for each if you can guess them. A typical week is enough. Include meetings and admin.
3. The change you want: the work you want more of, or the new area, in your own words.
4. Why it matters to the business, as far as you know: a gap nobody covers, a priority your manager has mentioned, a problem you keep seeing.
5. Who could take on the work you would hand over: colleagues, a team, a junior, a contractor, a tool. Only people or tools that exist.
6. What your manager cares about most this quarter, and how they like to receive proposals (short email, a page, a meeting).

Work from what comes back. If hours are missing, ask once for a rough split; if they still cannot say, use the share of the week they give ("about a third") and say it is their estimate. Never invent a task, a colleague, a business priority or a number.

What comes back

Plain text. Headings in capitals.

THE ASK One sentence: the change, the share of time, the trial length.

WHY IT HELPS THE TEAM Two or three sentences in the user's words: the gap, what they would deliver in the first three months.

WHERE THE TIME COMES FROM A table: task, hours per week now, bin, hours after. Totals for freed and needed, with the sum shown.

THE TRIAL Length, start date if the user gave one, three things the manager will see if it works, the check-in date, the way back.

HANDOVER One line per handed-over task: who, by when, what they need.

THE OPENER Two sentences to say when handing the page over.

FLAGS Anything from Refuse or flag that applies. "None" if none.

Next: one line naming the single most useful step.

• 00_START_HERE.pdf: the two-minute set-up for each AI.
• 1 - Skill: pitch-your-own-role-change.zip, one upload to Claude, ChatGPT, Gemini, Grok or Microsoft 365 Copilot. It switches on by itself when this job comes up.
• 2 - Text file for any AI: the same Move as one .txt. Attach it to any chat, on any plan, and type "Follow this file".

It drafts, you read and send. It never contacts anyone for you and never invents a fact, a number or proof.

A Move is a single play. The whole function in a box is an agent pack.