Knowing where each person is trying to go
Knowing your people is not a filing exercise. It is holding a living picture of each one: where they have been, what they are working toward, what they told you was hard, and what you have already discussed, because that picture is what lets you spot the opportunity that fits them rather than the one that happens to be free. It decays fast, usually within weeks, and it decays quietest for the people who need the least managing, because important details about a person should not have to compete for space in your working memory. Emily maintains that picture from the notes, meetings, and introductions you already have.
What is worth remembering about each person you manage?
Less than you think, but more consistently than you currently do. Four categories cover most of it: current work, stated goals, known constraints, and open threads between the two of you.
The mistake is trying to remember everything, which produces nothing. A single accurate line: "wants to move toward architecture work, blocked on getting exposure to design reviews": is worth more than a page of meeting minutes, because it changes what you do next quarter.
Notice what that line is for. It is not a record of a person; it is a description of a direction, which is the only kind of note that helps someone get anywhere. "Quiet in meetings" is a label. "Wants to be the one presenting by the autumn, asked how to get there" is a plan you can act on.
- What they are working on right now, and how it is going
- What they have said they want next in their career
- Constraints they have told you about, at work or outside it
- Feedback you have given, and whether it landed
- Threads still open between you
Why does context about your team fade?
Because it arrives in fragments, spread across weeks, in places that are not designed to be read back.
Someone mentions something in the last two minutes of a 1:1. You hear something else secondhand. A third thing comes up in a hallway conversation. Individually each fragment is memorable; collectively, across eight people and three months, they are not. And nothing prompts you to notice the fade, because forgetting is silent.
It fades fastest for your steadiest people. The person in crisis stays vivid. The person quietly doing good work for eight months is the one you are most likely to be caught out on.
How does Emily build a picture of each person?
It assembles a profile from the things you already produce: notes you capture, meetings from your connected calendar, follow-ups you log, and: for new joiners, a short introduction form the person fills in themselves.
You are not maintaining a CRM record for each report. The profile is a by-product of working normally. When you open it before a 1:1, or when Emily builds a prep brief, the history is already assembled: what you discussed, what is outstanding, and what has shifted.
The introduction form is worth calling out separately. Sending one when someone joins your team gets you their own words on how they like to work, what they want, and what they need from you, which is a much better starting point than three months of inference. It is also the difference between a picture of someone and a picture of your impression of them.
How does this help someone progress?
It makes progress visible, and it makes opportunity matching possible.
Growth over months is genuinely hard to see week to week: for you and for them. A record of where someone was in the spring is what lets you say, specifically, what is different now. That is worth more to most people than any amount of general encouragement, because it is checkable.
The other half is quieter. Most development happens through what someone gets to work on, and most of those decisions are made quickly, under time pressure, by a manager recalling who is available. Having what each person is working toward in view at that moment is how the stretch project goes to the person it would actually stretch.
Is this monitoring your team?
No, and the distinction matters. Emily works from what you as a manager chose to write down about your own conversations. She does not read your team's messages, track their activity, score them, or rank them.
The test we hold the product to is whether you would be comfortable showing someone their own profile. Notes a manager keeps in order to be a better manager pass that test. Surveillance does not, which is why LetEmily does not do it.