Something is already getting dropped from your week. Make sure it is not the 1:1

A manager's job keeps quietly expanding. Ship faster with AI. Stay close enough to the technical decisions to still have an opinion. Coach people through more ambiguity than before. Influence teams you do not run. Operate more strategically than last year's version of the role required. Each of those asks is reasonable on its own ^source. None of them come with more hours in the week. Something is already being traded away to make room, whether or not you have named it, and the honest question is not whether that is happening. It is what you are letting it be.

The trade-off is already happening, named or not

LeadDev's Diego Quiroga put a sentence on this that is worth sitting with: "You cut a one-to-one short because a cross-team fire is waiting." ^source That is one example among several he gives of a manager quietly absorbing a widening job description, and it lands because it is so ordinary. Nobody schedules the cut. It just happens, in a week that also brings more proposals, longer specs, and half-formed options to judge than before. Quiroga's broader point is about interpretation load, not just output. AI does not just hand a manager more finished work; it hands them more half-finished options to judge, which is a different kind of tax on the same fixed attention ^source. Yassine Kachchani restated the same argument in his own newsletter, framing the whole set of new demands as expanding against a limit that does not move ^source.

The remedy both writers point to is visibility, not more capacity. Make the trade-off explicit, so your team and your own manager have something concrete to react to, instead of you privately absorbing the shortfall and hoping nobody notices.

The instinct to add a tool can make the problem worse, not better

Here is where most advice goes sideways. The visible response to "I am stretched thin and things are slipping" is usually to add something: a dashboard, a check-in bot, a fuller platform with modules for reviews, surveys, and goals sitting next to the 1:1 feature you actually wanted. This is our editorial position, not a claim from either article above: a tool that has to be configured, checked, and read on its own is a new claimant on the same finite attention, and that can make the trade-off worse instead of better. You do not fix a zero-sum problem by adding a new claimant to the sum without also removing work somewhere else.

The thing most likely to get quietly cut under this pressure is the 1:1, because unlike a missed deliverable, a shortened or skipped 1:1 does not set off an alarm. Nobody escalates a 1:1 that ran twelve minutes instead of thirty. The cost can show up later, in a form that does not obviously trace back to the week it started slipping.

What actually helps: remove reconstruction work, not add monitoring work

If the scarce resource is attention, the useful move is to spend less of it rebuilding context you already had, not to spend more of it watching a new screen. A manager walking into a 1:1 cold has to reconstruct what was open, what was said last time, and what the pattern has been, before the conversation about this week can even start. That reconstruction is where a rushed 1:1 gets worse than a shorter one: less time and more setup cost at once.

That is the gap 1on1 is built to close: recurring history so last session is in front of you instead of in your memory, action items with an assignee and a visible open-or-closed state instead of a note that evaporates, and a session rating read as a trend across the series instead of a single number. It is designed to cut the reconstruction work, not to add a separate monitoring routine on top of it, so the fixed attention you do have goes into the conversation instead of the setup for it. This is our own answer to the trade-off Quiroga and Kachchani describe, not something either of them prescribes.

A test that costs one pair, not a rollout

You do not need to decide any of this in the abstract. Pick one manager and one direct report, and run four sessions with the history and open action items sitting in front of you each time instead of pieced together from memory. Then notice, honestly, whether prep gets easier or harder by the third or fourth session. That is an observation worth making for yourself, not a result we are promising you will get.

The pair and the session history you need to run this are already on the Free plan, one manager and one direct report, no rollout required ^source. The AI-assisted summary and trend read described above sit on Pro; the test itself does not need to wait for that. If the trade-off eases, you have found something worth widening. If it does not, you found that out for the cost of one pair and four sessions, not a platform.