Running Several Live Processes at Once

For weeks the problem is that nothing is happening. Then, usually all at once, four things are happening, and it turns out the search you built for volume is badly shaped for this.

Live processes are not a bigger version of applications. An application is fire-and-forget: ninety seconds of admin and then you wait. A live process is an ongoing obligation with scheduled events, preparation debt, people whose names you need to remember, and a timeline that interacts with three other timelines. Four of them at once is a coordination job.

Here’s the operational layer for it. Not how to perform in the conversations — how to not drop anything.

Promote the row to a page

A row in a spreadsheet was the right unit for an application. It stops being enough the moment a real process starts, because the volume of detail jumps.

When something moves to Screening, create a short document for it and put the link in the row. One page, appended to after every contact:

NORTHWIND — Senior Analyst
Tracker row: #38    Applied: 12 June    Source: referral (Priya)

PEOPLE
  Dana Okoye — recruiter, dana@...
  Marc Lefevre — hiring manager, would be my manager
  Sam — second-round panel, mentioned they own the reporting pipeline

TIMELINE
  24 Jun  screen w/ Dana, 30 min. Said: 2nd round w/in 2 weeks,
          process usually 4-5 weeks end to end.
  01 Jul  panel scheduled, 14:00, 90 min, video
  ~11 Jul their stated decision date

FACTS THEY GAVE ME
  Team of 6, splitting off from central data next quarter
  Role exists because the previous holder moved internally
  Hybrid, 2 days in office, not negotiable per Dana
  Resume version sent: ops-tailored-v2

OWED
  Me: send Dana the availability for w/c 7 Jul (by Fri)
  Them: panel confirmation email

Five minutes per contact, and it removes the failure that costs most: turning up to a third conversation having forgotten what you were told in the first. With one process you’d remember. With four you won’t, and the person on the other end experiences that as disinterest.

The per-conversation habit that feeds this page is worth its own treatment — see the notes you take after every conversation.

Calendar hygiene

Three rules, all boring, all learned the hard way.

Everything scheduled goes in one calendar, the one you actually look at. Not in an email thread you’ll search for later.

Block the preparation, not just the event. A 90-minute panel on Tuesday afternoon needs a block on Monday evening. If preparation isn’t on the calendar it becomes something you do in the twenty minutes before, and with several processes running there’s a genuine risk of preparing for the wrong one.

Leave buffers. Two calls back to back means you arrive at the second one still thinking about the first, and if the first overruns — they do — you’re late. Thirty minutes between, minimum.

The logistics of fitting all this around an existing job are their own problem; that’s scheduling interviews around a job you still have.

The priority order, decided in advance

When the week is short — and with several processes live it always is — work down this list:

Anything with a scheduled date. Preparation for a booked conversation outranks everything.
Anything where someone is waiting on you. A recruiter who asked for availability two days ago is watching how long you take, and it’s cheap to fix.
Follow-ups that are due.
New applications.
Sourcing.

New applications go fourth, but they don’t go to zero. Dropping the input entirely while processes run is the mistake described in how much should be in flight at once — reduce the rate, don’t stop it.

Don’t level-fund your attention

Four live processes rarely deserve equal effort. They differ in how much you want them, how far along they are, and how likely they look.

Once a week, tag each one:

A — want it, going well, worth real preparation hours.
B — plausible, keep it warm, do the minimum properly.
C — you’ve realised you don’t want it, or it’s clearly stalled.

Then act on the tags. The C ones deserve an honest decision: either withdraw politely, which frees your time and theirs, or let them run with no preparation investment. What’s expensive is leaving a C process in the same mental compartment as an A process, where it consumes worry without consuming effort.

Withdrawing is under-used. If you know you won’t take the job, saying so is a small professional kindness that costs you nothing and takes two lines. It also means the row leaves your live view, and your coverage number stops being inflated by a process that was never going to produce anything.

Diverging timelines

The coordination problem with real teeth: process A is about to make you an offer and process B, which you’d prefer, has two rounds to go.

There is no clean solution, but there are honest moves.

Ask for the timeline early and explicitly. At the end of every conversation: “what’s the process from here, and roughly when?” Do this at the first screen of every process, not when it becomes urgent. It costs nothing and it’s the only input that lets you plan at all.

Tell the slower process the truth, once. A short message saying you have another process reaching a decision by a specific date, that you’d rather not decide without hearing from them, and asking whether they can indicate anything by then. Sometimes it accelerates things. Sometimes it doesn’t. Either way you’ve given them accurate information and they can act on it or not.

Never invent the pressure. A deadline that doesn’t exist, or an offer you haven’t received, is a bluff with a real chance of being called — recruiters in the same city talk to each other — and being caught in it ends the process instantly. It is also just a lie about your situation, which is not something this site will help you do.

Accept that you may have to decide with incomplete information. Some timelines don’t align, and no amount of process design fixes that. When it happens, it isn’t a failure of your system; it’s the actual condition.

The weekly five minutes that holds it together

In your admin block, open the live-processes view and go through each one:

What’s the next scheduled event, and is preparation blocked out?
Is anything owed by me? Send it now.
Is anything owed by them, past the date they gave? That’s a follow-up.
Any change to the A/B/C tag?
Is the notes page up to date, or am I about to forget something?

Five processes, five minutes. That’s the whole overhead, and it’s what stands between a busy fortnight and the specific, avoidable embarrassment of missing an interview you’d have been good at.