---
name: changed
description: "Put two months side by side and show what shifted in what my First Team works on and talks about. Use before writing a plan, an update or a request to the leadership team."
---

# First Team: what changed

## What this skill does

It compares an earlier stretch of time with now and shows what moved in my First Team's priorities, as two columns I can read across. Priorities drift quietly, and the person whose plan still leads with last quarter's is the last to find out. Run it before I write anything the leadership team will read.

## What it reads first

Work these out before step 1, then tell me what you found in one line so I can correct you.

1. **Who is on my First Team.** Read the files from where the Settings line in the project instructions says they are kept. If there are none, ask me who is on it.
2. **What you can actually reach.** Name the sources you can see and the dates they cover. If you can reach none, say so and ask me to paste in the two periods instead of guessing.

## Steps

1. **Pick the two windows and make them comparable.** Two months ago against this month unless I name others. Say the exact dates, how many leadership meetings fall in each, and whether the current window is still part way through. If one window is much smaller, say so first, because a short window makes everything look like a change.

2. **Search both windows** across calendar, email, shared channels and meeting notes. Do not search the web.

3. **Measure two things:**
   - **What the team talks about:** which topics come up in the leadership meeting and shared threads, as a share of what you can see in each window.
   - **What each person works on:** the areas each peer's meetings and threads went to, as a share of what you can see. Meetings and threads are activity you could see, never a measure of their time.

4. **Lay it out as two columns,** the earlier window on the left and now on the right, one row per shift. Label each row **new**, **more often**, **less often** or **stopped appearing**, with the count behind it.

5. **End every row with one line on what to do:** what to lead my next plan or update with, or a question to take to that peer. Say it as a change I can see in the material, never as a conclusion about what anyone now believes.

## Rules

- Read only meetings and threads where at least one person on my First Team takes part: in a channel or an email, a message they wrote or a thread they replied in (in the shared channels named in the project instructions, my own posts count too, even when nobody replied); in a meeting, they are on the invite or the notes show them speaking. Posts from bots and apps do not count. Leave out everything else in my sources: client calls, other jobs, interviews, personal meetings and classes, even when they are the most recent thing there. A peer's work outside this company (their own business, other clients, a job search) stays out too, even when it comes up in a meeting we share.
- Measure what was said and done. Never score anyone's tone, mood, attitude or how engaged they seem.
- A shift resting on a single meeting is a maybe, and the row should say so.
- A change in a peer's work is a question I take to them, never a judgement about them.
- Shared channels, shared documents, email threads I am on and meetings I was in only. Leave out private messages between other people, anything said in confidence, health or family details, anything my company's AI policy rules out, and passwords or logins.
- Never quote any of it into something I send, and never copy it into another project.
- Write the way I would: plain words, no dashes used as punctuation, and no term I have not used myself without explaining it in the same line.