Some questions need a working session

“Got twenty minutes this week?” is a question with a precise meaning. It comes from the sales engineer staring down a technical evaluation, the marketer halfway into a launch narrative that stopped hanging together, the partner engineer holding a topology nobody anticipated. Each of them has something too tangled for a Slack thread — they tried to write it down and the message kept growing — and not weighty enough for a real meeting with an agenda and six attendees. What they need is twenty minutes of somebody who knows, talking it through. Every expert’s calendar carries a strip of these, and every one displaced something.

The tangled question is a distinct species from the lookup. A lookup has an answer; a tangled question has a shape that only emerges in conversation — the asker discovers what they were really asking two exchanges in, when your first answer eliminates a wrong assumption they didn’t know they held. No amount of documentation absorbs these, because the follow-up path is different every time.

The depth problem

Watch the same question arrive from three people and the problem gets clearer. “How does multi-site sync actually work?” needs one sentence for the seller confirming a suspicion, a diagram for the partner engineer wiring into it, and a genuine working session for the customer architect with a weird topology. The words of the question don’t reveal which one you’re in; two exchanges do. A document is stuck answering at one depth, chosen in advance. The expert adjusts in real time — which is the actual reason “quick call?” has survived every wave of documentation tooling: the call is the only interface that could match depth to asker on the fly.

A session on demand

This is the gap Deputy’s live sessions cover. One question becomes a working session — a voice conversation that runs at exactly the depth of the ask. The seller gets the sentence and is gone in ninety seconds. The architect gets the twenty minutes, without waiting for a slot on your calendar, at 11pm before their migration if that’s when the question got urgent.

The part that surprises people watching one for the first time: it sketches while it talks. A diagram materializes as the explanation needs one — then gets amended, live, when the asker says “but where does the gateway sit in that picture?”. A checklist assembles itself out of a “so what do I actually do first” exchange. The artifacts are made on the spot, for this question, in this conversation.

Made for the question

Generated-on-the-spot is a deliberate choice, and it cuts against the instinct to build a library of polished diagrams. The library has the same disease as every other artifact pile: it answers the questions you anticipated, at the resolution you anticipated them, and it started aging the day you exported it. A sketch made for the question at hand is disposable by design — the understanding persists, the drawing doesn’t need to. What keeps improvisation honest is that the underlying claims still come from the briefing, cited like anywhere else; the drawing is a fresh rendering of vouched-for facts, never fresh facts.

What stays human

The twenty-minute strip on your calendar never goes to zero, and it shouldn’t. Sessions where the group is deciding something, negotiating something, or reviewing work — where the conversation produces new judgment rather than transferring existing judgment — are the job you keep. The working sessions worth handing off are the ones running on the tax test: the same knowledge, re-explained at custom depth, gladly delegated if only something could match the depth. Now something can.