For managers: 1:1 notes and debates that stop repeating

Your work is mostly invisible: the context you hold, the decisions you keep straight, the reasons behind them. Meet Sam, who leads a small engineering team.

The mess

You leave a 1:1 with three things to follow up on. You write two in your head and forget the third. And every quarter, the same process debate comes back - why did we stop doing X? - because the reasoning never got written down anywhere findable.

Your desk, in a manager's terms

• Inbox - the after-1:1 dump: a concern to follow up on, a name to remember, a rough idea.
• Work - not a personal kanban. The few things that unblock the team.
• Ideas - team experiments and process changes you're weighing.
• Memory - why you hired this way, why you changed that process, what you promised whom. The context that usually only lives in your head.
• Ship - what the team shipped, and how it landed.

Four moments from Sam's week

"Capture the 1:1, don't file it." Straight out of a 1:1, Sam captures "Priya wants more backend ownership - revisit in Q2." No form, no folder. It lands in the Inbox, ready to turn into a task when the time comes.

"Write the reason, not just the rule." Sam changes how the team does on-call and records it as a decision in Memory - with the why: "rotating weekly, because the monthly cadence burned people out." When someone questions it later, there's an answer.

"Unblock, don't micromanage." Sam's Work → Today isn't every ticket - it's the two things only a manager can clear: an approval and a cross-team intro.

"We've had this debate before." Before reopening the estimation argument, Sam asks Memory "why did we drop story points?" and gets the earlier reasoning, with sources. The meeting is five minutes, not fifty.

A manager's week

• After 1:1s and meetings: capture the follow-ups and context immediately.
• When you change how the team works: write it in Memory with the reason, that day.
• Weekly: turn the important captures into a few unblock-the-team tasks.
• Before repeating a debate: ask Memory first.

FAQ

Will this replace my 1:1 doc? It does not have to. Capture the follow-ups and the decision while they are fresh. Ask Memory before the same debate starts again.

Is this team knowledge-base software? No. It is a desk with a memory. Useful when the “why we stopped doing X” lives in your head.

Next

The habit is the same as everyone else's: Just capture, then Make something of it. Recurring debates belong in a decision log. Start here is the two-minute orientation.