Six Myths About Waiting-For Lists in a DevOps Career

Six Myths About Waiting-For Lists in a DevOps Career

Ask a room of DevOps practitioners how they keep track of what other people owe them and you will collect confident answers that crumble under inspection. “The tracker handles it.” “Good engineers remember.” “Chasing people is rude.” Each belief sounds reasonable, yet each hides a flaw that costs real delivery time. Below are five myths about the waiting-for list, a simple record of requests you have made to others with a named responder and a chase date, tested against how engineering work actually flows.

Myth 1: “Our ticketing system already tracks everything”

The claim: If a dependency matters, it is already in the tracker, so a separate list is redundant.

What the evidence suggests: Trackers record work items and their states. They rarely record the informal requests that surround the work: a question to a platform engineer in chat, a certificate you asked a vendor for, a favour from another team’s on-call. Even where a ticket exists, “blocked” says nothing about who owes the next move and when anyone will look again. A ticket can sit untouched for weeks with a perfectly accurate status.

The better view: The tracker holds shared work; your list holds your personal follow-ups. Keep ticket numbers in your list’s notes so the two connect, and let each do what it does well.

Myth 2: “Good engineers just remember”

The claim: Competence means holding all open threads in your head.

What the evidence suggests: Human working memory handles a handful of items at once. A busy engineer might have a dozen outstanding requests spread across reviews, approvals, access grants and vendor questions, plus the actual job. Experienced practitioners tend to externalise memory, not rely on it. Checklists, runbooks and automation exist in this field precisely because recall under pressure is unreliable, a lesson the discipline has applied to deployments and incident response for years. Applying it to personal follow-ups is consistent.

The better view: Reliability comes from systems, not from superhuman recall. Learning to build a small system of your own is a skill worth showing in your career, much like the analytical habits described in a guide to developing sharper reasoning when solving DevOps problems.

Myth 3: “Following up is nagging, and nagging damages relationships”

The claim: If you chase people, you will be seen as pushy, so it is better to wait patiently.

What the evidence suggests: Most people do not hold a reminder against you; many are relieved by it, since they forgot too. What irritates colleagues is vague, repeated, emotional chasing: “any update???” three times a day. A single dated, specific, friendly nudge that explains why the timing matters is easy to act on. The waiting-for list helps here, because the nudge date is set when you ask, so follow-ups arrive at predictable, reasonable intervals rather than at moments of frustration.

The better view: Silence is not politeness; it just moves the cost onto the project. A courteous reminder is a service to both sides.

Myth 4: “A waiting-for list is only for managers”

The claim: Individual contributors do not depend on many people, so tracking is a management concern.

What the evidence suggests: Individual contributors often depend on more outside parties than managers do, simply because they are doing the work that requires access, reviews and approvals. A site reliability engineer waits for capacity from a cloud provider. A build engineer waits for licence keys. A junior developer waits for repository access and a mentor’s review. Each of these is a dependency that a manager may never see.

The better view: Whoever does the asking benefits from tracking. In fact, careers often accelerate for people who handle this well, because colleagues notice the person whose requests never go missing. A practical overview of skills for stepping up, such as a roadmap of practical DevOps skills for IT transformation, rarely lists this habit explicitly, yet it underlies much of what is described.

Myth 5: “It takes too much time”

The claim: Adding a line for every request and reviewing the list daily is overhead that busy teams cannot afford.

What the evidence suggests: Adding a line takes under half a minute. A daily review of a short list takes a couple of minutes. Compare that with the cost of one stalled change request: a day or two of lost progress, an awkward status update, perhaps a missed window. Simple arithmetic favours the list even if it prevents only one such incident per month. The overhead objection usually comes from people who have imagined a complicated system rather than a plain page with four fields.

The better view: Keep it minimal. One line per request, four fields, one daily glance. The time you save from not hunting for lost threads more than repays the effort.

Myth 6: “It only matters at work”

The claim: The habit belongs in the office and has no place in personal life.

What the evidence suggests: Long personal projects have the same structure: many people, each holding a piece, each replying at their own speed. A person weighing up a home purchase in India may read around on Propraahi, a site that positions itself as a property research destination for buyers, and would then be waiting on several answers from different directions. A private list of questions asked and replies pending fits that situation as neatly as it fits a release.

The better view: The method is neutral. It is the shape of the problem, dependency on others, that calls for it.

The pattern behind all six myths

Look closely and each myth shares a root: the assumption that someone or something else is already watching. The tracker is watching, memory is watching, the other person will surely volunteer an update. In distributed work, that assumption is the most expensive one available, because every party makes it at the same time. The waiting-for list is a small act of taking ownership of the follow-up, and it asks nothing of anyone else.

What to do on a team that disagrees

You do not need consensus to benefit. Keep your own list quietly for a month and let the results speak. If colleagues notice that your requests never get lost and ask how you manage it, share the template. If your team lead wants a team-level view, offer to merge a few lines into the standup agenda. Adoption that starts from demonstrated usefulness lasts longer than adoption mandated in a meeting, and it keeps the format light.

What a sensible setup looks like

  1. Pick a plain format that you will open every day: a text file, a spreadsheet, a notebook.
  2. Write a line for every request that another person must answer, in the moment you send it.
  3. Fill four fields: what, who owes it, date asked and nudge date.
  4. Read the list at the start of the day and send whatever is due.
  5. Close lines as items arrive, and keep a short archive of reply times.

How to test the claims yourself

Do not take any of the above on faith. Run a two-week trial. Before you start, count how many requests you remember having to chase late in the last month. During the trial, record every request and every nudge. At the end, compare. If late chases fall and surprises shrink, the myths were costing you. If not, adjust your intervals or your review habit and run it again. The point of treating the list as an experiment is that you replace opinions with observations drawn from your own work.

Myths persist because they flatter our self-image: we like to believe we are organised enough, trusting enough or busy enough to skip a small discipline. The data from everyday practice says otherwise. A short, dated record of what others owe you is among the cheapest reliability measures available, and it fits comfortably into any engineering routine.