What to Track About Your Team in Your First 90 Days

In your first 90 days as a new manager, track context about each person, not a project status board. For every report, capture five things and keep them per person and dated: what they own and care about, how they want to work, where they want their career to go, what is on their mind right now, and the commitments you have made to them. Do that and by day 90 you have a real timeline for each report instead of a blur of first impressions. The 90-day-plan genre is full of frameworks, but the habit underneath all of them is the same: write down what people tell you, the day they tell you, filed under their name.

This matters more at the start than at any other point in the job. You are meeting an entire team at once, learning a dozen names and a dozen histories, and you have nothing to lean on yet. Memory is a terrible filing system on a normal week; in a firehose first month it is hopeless. The detail @Maya shared in your first 1:1 about wanting to move into architecture work is gone by week six, buried under everything else, unless you wrote it down. A record does not make you a more careful manager. It makes you a more accurate one, because by review season you have the whole period and not just the last few weeks.

What to track about each report

You do not need a complicated system. You need five buckets, kept per person, each entry dated and specific. Copy the layout below and fill one out for every direct report as you get to know them.

FIRST-90-DAYS PROFILE - @[Name]

ROLE & SCOPE (what they own; what they care about)
-
-

HOW THEY WORK (communication, feedback, working style)
-
-

CAREER (where they want to go; what they're building toward)
-
-

ON THEIR MIND NOW (current frustrations, blockers, wins)
-
-

MY COMMITMENTS (what I said I'd do; by when)
-
-

Here is what each bucket looks like once it has real entries in it. Specific and dated beats tidy and vague every time, especially early, when you cannot yet tell which detail will turn out to matter.

• Role & scope. "Mar 3 - Maya owns the billing service and the on-call rotation. Cares most about reliability; visibly proud of the zero-incident quarter." This is the work as the person sees it, which is not always the work on the org chart.
• How they work. "Mar 4 - Prefers written feedback she can sit with, not hallway comments. Goes quiet in big meetings, sharp in writing." A line like this saves you from giving good feedback in a way that lands badly.
• Career. "Mar 5 - Wants to move toward architecture in the next year. Building toward it with the platform cleanup. Watch for a stretch project." So you can show progress against where they actually want to go, not where you assumed.
• On their mind now. "Mar 9 - Frustrated that releases are still manual. Three late nights this sprint because of it. Real, not a complaint." Capturing the concern the day you hear it is what lets you act before it becomes resentment.
• My commitments. "Mar 9 - I said I would push for a CI budget by end of Q2. Follow up at next 1:1." Nothing erodes a new manager’s trust faster than promising something in week two and quietly forgetting it by week five.

Start with one conversation per person

The fastest way to fill those buckets is the same move every good new manager makes: a first-week 1:1 with every report, built around the same handful of questions. You are not there to set direction yet. You are there to listen and to write down what you hear. Ask what they own, what is working, what is frustrating, and where they want to grow. Then, and this is the part most people skip, write the answers down the same day, before the next three conversations blur them together.

A few questions worth asking in those early 1:1s, and worth capturing the answers to:

• "What does a good week look like for you?" Tells you what they value and what quietly drains them. Write the answer under how they work.
• "What should I keep doing, and what should I change?" You inherited a team with habits and grievances. This surfaces both. Capture the patterns, not just the one-offs.
• "Where do you want to be in a year?" The single most useful thing to know early, because almost every later decision (projects, feedback, promotion support) is easier when you know the direction. Write it under career.
• "What is getting in your way right now?" Gives you something concrete to act on in your first month, which is how trust gets built. Whatever you commit to, capture it under my commitments.

If you want a fuller bank of questions to draw from, the 1:1 meeting questions resource has a set organized by what you are trying to learn. The principle is the same either way: the questions only pay off if you keep the answers.

What not to track (and why)

A first-90-days log is a tool for understanding people, and it stays healthy when you are clear about what it is and is not. The point is accurate memory, not a case file.

• Not a surveillance log. You are not timing logins or counting keystrokes. You are remembering what people told you so you can be a fair manager to them. If a note reads like evidence against someone, step back and write what you actually observed.
• Not character labels. "Difficult," "lazy," "not a team player" are verdicts, not observations. Early on you have the least context you will ever have, so a snap label is most likely to be wrong. Write the behavior and the date, not the verdict.
• Not an HR record. Your private notes do not live in your organization’s system of record and do not carry its weight. If something belongs in an official record, put it there through the proper process.
• Not a decision. The log gives you accurate input. The judgment, and the accountability for it, stays with you and your organization under your own policies and applicable law.

Keep the entries factual and behavior-based and you stay on the right side of all of it. Write "shipped the migration with zero downtime on Mar 9," not "rockstar." Write "missed two committed dates this sprint, both from late scoping," not "unreliable." The first is something you observed and can talk about. The second is a label you would not want recorded about yourself in your first month under a new boss.

The one habit that makes the rest easy

You can read every 90-day-plan article ever written, and they will all tell you to build relationships, learn the systems, and find some early wins. That is good advice. But the habit that actually makes it stick is smaller and easier to miss: capture per-person context the day you learn it. Not at the end of the week. Not "when things calm down," because in a new job they do not. The day it happens, in one dated line, filed under the person.

The reason this compounds is timing. Everything hard about management arrives later: feedback you have to give, a review you have to write, a case you have to make for someone who deserves it. Each of those is dramatically easier if you have a record of the whole period instead of a fading memory of your first weeks. The work of remembering is cheap if you do a little each day and expensive if you try to do it all at once in November. Managers who forget important context are almost never careless; they are just relying on memory for a job memory was never built to do.

For deeper detail on how the per-person log holds up across a full year, the manager notes resource walks through the five buckets a more experienced log settles into. Your first-90-days profile is the same idea, started at the moment it is hardest and most valuable to begin.

How Notivo fits the first 90 days

This is exactly the thing Notivo exists to make effortless: a private, per-person running log you keep for yourself. Most options force a bad trade in your first weeks, when you have the least time. A scattered pile of notes is private but useless, because you can never find the line you need. A shared doc is one wrong tab away from being read by the team you just met. And keeping it all in your head simply does not survive a firehose first month.

With Notivo you write a quick note and tag the person with @ and their name, and it files into that person’s timeline. You can tag a topic with # to thread a theme across people. Type @Maya later and the whole history is there, dated and searchable, so before your day-90 1:1 you read the timeline instead of reconstructing it from memory. An AI assistant can draft a recap or answer a question from your own notes only, and it never trains on your data, so "what did Maya say she wanted to work toward?" gets answered from what you actually wrote, not invented. You capture the same way wherever you are: on the web, by WhatsApp on your phone between meetings, or in the ChatGPT and Claude connectors.

On storage, the honest answer: your notes are private by default and scoped to your own account, and they are stored on secured infrastructure. That is platform-level security, the protections that come with reputable cloud storage. It is not a claim that your note content is encrypted end-to-end, and we are not going to pretend otherwise. If you do have something especially sensitive about a person, the Black Box vault (triggered with @bb or #bb) is PIN-locked and end-to-end encrypted for exactly that. So use the same judgment you would use with any cloud notes app: this is the right home for your working memory of who does what, with a locked vault for the rare note that needs more.

Frequently asked questions

Keep reading

• A private employee journal, organized by person
• 1:1 meeting questions worth asking
• Why managers forget important context
• Notivo for private, per-person notes
• Notivo for managers