A manager's life memory, not employee monitoring

It is Friday, calibration is Monday, and you have six reviews to write.

Five of them are fine. The sixth is an engineer who had a genuinely strong first half and a quiet July, and what you can actually recall is July. You know she unblocked the migration in March, because you remember the relief. You cannot remember what she did, who she convinced, or what the blocker had been. Your 1:1 notes for her are three lines from January and a link to a doc that has since been rewritten. So you open Slack and start scrolling, and what you end up writing is a review of the last three weeks with a sentence about the first six months bolted on.

Recency bias is not a character flaw. It is what happens when the only record of eight months of management is your memory plus whatever you had time to type.

Say the monitoring thing first

Every product in this space gets read as surveillance, so let me be direct about what LUCI is.

LUCI runs on your computer and records your day. Not your team's computers. There is no admin console, no fleet deployment, no dashboard showing you what your reports did this afternoon. Nobody installs it on anyone. It is the manager's own memory of their own workday, which is the day you spent in 1:1s, in review threads, in planning docs, and in calls where decisions got made and then immediately forgotten.

That distinction is the whole design, and it is worth holding onto when you use it. If you cite something in a review, you are citing a conversation you were in, the same as you always did. The change is that you can now remember all of your conversations instead of the recent ones.

What it actually keeps

Your whole day on the computer: meetings, email, code, everything in between. Both sides of the audio on calls, what was on screen, the docs you opened, the tickets you moved, the spec you read twice on a Tuesday. Everything is understood on your machine and stored encrypted there, with no cloud processing of your memory. Cards, keys, and passwords are blacked out before anything is saved, and private windows can be excluded.

Then your agent distills each day and writes your Life: a folder of ordinary dated files on your disk, readable in any text editor, that outlives any app including this one. For a manager that folder is closer to a work journal you never had to keep.

Meetings are part of it, not the point of it. A manager's job is mostly the connective tissue between meetings, and that tissue is where context normally evaporates.

Four things this changes

1:1 continuity

The failure mode of 1:1s is that both people half remember the last one. Ask your agent, which reaches your memory through the Agent Bridge and connects itself with nothing to set up: "what did we agree to in my last three 1:1s with Priya, and what is still open." You walk in having actually closed the loop, which is roughly ninety percent of what people mean when they say a manager is good at 1:1s.

Decision provenance

Six weeks later someone asks why the team cut the offline mode from the release. You know there was a reason. Ask: "when did we decide to drop offline mode and what was the argument." The answer turns out to be a planning call where the concern was a specific API rate limit, which nobody wrote down because everyone present understood it. That is the class of context that costs a team a month when it goes missing.

Review evidence, from the whole period

Instead of scrollback, you ask what a person worked on between February and August and what you personally observed about it. You get March back, with the migration, and the thread where she talked two skeptical people into an approach. Writing a fair review is much easier when the evidence is not weighted by what happened most recently.

Coming back from a week off

Nine hundred unread messages is not a summary. "What decisions were made while I was out that touch my team's roadmap" is a question your memory can answer, because your inbox and the docs and the recorded calls all passed through the same machine.

The honest limits

Some of what a manager holds is genuinely sensitive: comp discussions, performance conversations, a report telling you something in confidence. Your memory stays on your machine, but what an agent reads reaches that model's vendor. LUCI hands over only what a query needs, you choose the agent, and your Life folder survives whichever one you choose. For the most sensitive material, the sensible thing is to search it yourself and keep agents out of it.

The rest of the caveats are the boring kind, and they are real. LUCI is not open source, so you verify its behavior by watching your machine rather than by reading its source. It needs the computer on and capturing, so a week of offsites is a thin week. A 1:1 you take as a walk is not in the record at all, and honestly some 1:1s should stay that way. And your team should know you run it, because a manager with a perfect memory and a secret is a worse manager than one with neither.

Try it on one review cycle

Let it run through a month of normal 1:1s and planning. Then, next time someone says "we talked about this in April," find out whether you did.

Download LUCI for Mac or Windows, free. There is more on LUCI for managers.