LetEmily compared with keeping 1:1 notes in a document
A running document per direct report is the default system most managers build, and for a small team it is genuinely hard to beat: free, flexible, and shareable with the person. It breaks down on attention: a document is only useful when you have the time and the presence of mind to open it, and those are the first two things a management week takes away. Nothing in a file notices that a commitment is still open or that someone has gone quiet for a month. That noticing is what Emily adds.
What does the document approach do well?
It is free, it works everywhere, and it can be shared with the person so you both add to the same agenda before each 1:1. For a manager with three or four reports it is often sufficient.
It also has a real advantage LetEmily does not replicate: because the document is shared, the person you manage can add their own items during the week. If that shared-agenda habit is working for your team, it is worth keeping regardless of what else you use.
Where does it break down?
At the point where it starts depending on your attention rather than adding to it, and it degrades gradually enough that most managers do not notice until they are already relying on memory again.
Notes in a document are only useful if you remember to open it, remember roughly when something was discussed, and can find it by scrolling or searching a phrase you may not recall. Nothing prompts you. Nothing tells you a commitment from six weeks ago is still open, or that you have not written anything about someone since March.
- Nothing surfaces before a meeting unless you go looking
- Commitments live in prose, so nothing tracks whether they closed
- Cross-team patterns are invisible: one document per person by design
- Capture during the day means finding and opening the right file
- Coverage gaps are silent; no document tells you it has gone stale
What does LetEmily do differently?
It inverts the direction. A document waits for you to have a spare moment and the presence of mind to look. Emily brings the context to you before the conversation, without being asked.
Concretely: notes and follow-ups are attached to a person as you capture them (including from Slack, without opening the app), commitments are tracked as items rather than sentences, prep briefs are assembled before 1:1s from your calendar, and a weekly reflection looks across the whole team rather than one person at a time.
The difference that matters is not really tidiness. A document is a record you consult when you happen to think of it, which means someone's stated goal survives only as long as your attention keeps returning to it. Delivered context means the thing they told you in March is in front of you in June whether or not you remembered it existed, and that is the difference between a note about someone and actually helping them get somewhere.
The trade is that it is a product with a plan attached rather than a free file, and it is a manager's workspace rather than a shared agenda.
When is a document still the right answer?
When you manage a small number of people, your shared-agenda habit is working, or your organisation restricts what tools can hold employee information.
It is also the right answer if the honest problem is that you are not writing anything down at all. No tool fixes that. Start with a document and a two-minute habit after each 1:1; the retrieval problem is a good problem to graduate into.