How long should 1:1 preparation take?

Two minutes if the context is already gathered. The work is in the gathering, not the reading, which is why prep tends to collapse when it depends on your memory and a search box.

Does Emily join or record my meetings?

No. Emily reads your calendar to know a meeting is coming and works from the notes and follow-ups you capture. She does not join calls, record audio, or transcribe conversations.

Do I need to write notes for this to work?

Some, yes. Meetings arrive from your calendar automatically, but the substance of a conversation only exists if you capture a line about it. Emily can only help with context she has. The capture is deliberately short: one line from Slack or the app is enough to be useful later.

Preparing for 1:1 meetings

Good 1:1 preparation means arriving with three things in hand: what you discussed last time, what either of you committed to, and what has changed for that person since. The point is not the time it saves: it is that a prepared 1:1 continues a relationship while an unprepared one restarts it, and nobody develops through a series of first meetings. Most managers know this and still walk in cold, because assembling those three things by hand takes attention they do not have between two meetings. Emily assembles them instead, into a prep brief waiting the morning of the conversation.

What should you actually review before a 1:1?

Three things, in this order: the last conversation, the open commitments, and anything that has changed for that person since you last spoke. Everything else is optional.

Reviewing the last conversation stops you from re-asking questions you already asked, which is the fastest way to signal you were not really listening. Reviewing open commitments: yours and theirs: is what turns a 1:1 into a thread instead of a series of disconnected chats. And knowing what has changed, whether that is a new project, a reorg, or something they told you they were worried about, is what lets you ask a second question rather than a first one.

The notes from your last 1:1 with this person
Commitments you made to them that are still open
Commitments they made to you that are still open
What has changed in their work or circumstances since
One thing you want to ask that is not about status

Why do managers skip 1:1 prep?

Because the cost of preparing is paid in the two minutes before the call, and the information needed is scattered across four places.

Your notes are in a document, or a notebook, or nowhere. The commitment you made is in a Slack thread from three weeks ago. The context about their project is in a meeting you attended but did not write down. Reconstructing all of that takes fifteen minutes you do not have between back-to-back meetings, so the rational choice is to skip it, and then apologise for forgetting.

This is not a discipline problem. It is a retrieval problem. Managers with eight direct reports are holding eight parallel narratives, each updating weekly, none of them written down in one place.

How does Emily prepare you for a 1:1?

Emily follows your calendar, and before a 1:1 she assembles a prep brief from the context she already holds: notes from your last conversation with that person, follow-ups that are still open, and what has changed on their profile since.

You did not have to file any of it. Notes you captured during the week, including ones you saved straight from Slack: are already attached to the right person. Commitments you logged are already tracked. Emily pulls the relevant pieces together and suggests what is worth asking, so the preparation happens whether or not you had ten minutes to do it yourself.

The result is that preparing stops being a task you schedule and becomes something you read for ninety seconds before you join the call.

What makes a prep brief useful rather than noise?

It has to be short, specific to the person, and current. A brief that summarises everything is as useless as no brief at all.

The test is whether it changes the first question you ask. If your brief reminds you that they mentioned being stretched thin two weeks ago and you open with "how did that resourcing thing land?", the brief earned its place. If it produces a wall of text you skim and forget, it did not.

How does preparation help someone actually grow?

Because development is cumulative, and a conversation that starts from zero cannot be cumulative.

Someone tells you in March that they want to move toward architecture work. If that is in front of you in April, May and June, you notice the design review they were not invited to, the project that would stretch them, the feedback that would help. If it is not, you have six pleasant conversations about this sprint and the year passes without them getting closer to anything. Same manager, same care, different outcome, and the only variable is what you were holding when you walked in.

It works at the harder end too. Feedback you gave once and never returned to did not land; it evaporated. Knowing that you gave it, and when, is what makes the second conversation possible instead of feeling like an ambush.