A weekly 1:1 is a conversation. A good one might surface concerns, repair a relationship, unblock a decision. What it cannot do is create accountability. Accountability isn't a conversation — it's a structure. Either the system makes ownership and progress visible without anyone having to ask, or it doesn't.

Managers running 1:1s as their primary accountability mechanism end up in one of two failure modes. Either they trust the conversation and discover six weeks later that "we're on track" meant nothing, or they don't trust it and ask the same questions every week, turning the meeting into a recurring oral exam.

The structural alternative

Accountability shows up in the system before it shows up in the meeting. The owner of an objective can be named in one place, with one click. The work meant to move that objective is attached to it. Progress against it is visible without anyone writing a status update. Drift triggers a signal.

When that is in place, the 1:1 becomes useful again. The conversation is no longer about what's happening — that's already visible. It's about what we should do about what's happening. That's a meeting worth thirty minutes.

Why this is hard

Because the structural version requires the system to be honest. And the system is only honest if the underlying data is connected — goals to work, work to owners, owners to capacity. Most companies don't have that. So they substitute the meeting and call it management.

The Vindaris view

If accountability only exists during the 1:1, it doesn't exist. Build the substrate that makes ownership and progress legible without a manager's prompt. Then the conversation can do what it was meant to do.