Engineers training for DevOps roles are taught plenty about pipelines, containers and monitoring, but rarely about the plain question of how to remember what other people owe you. Most of us improvise. Some lean on a to-do app, some on calendar alerts, some on the ticket system at work, and a few on memory alone. Below, four familiar habits are put head to head: where each holds up, where each lets requests slip through, and why a dedicated waiting-for list earns a place next to them.
The scenario we will test every method against
Picture a junior engineer in a team that is adding automated tests to a release pipeline. Within one week she asks a colleague for review of a configuration change, asks the platform group for a test runner quota, asks a manager for sign-off on a new environment, and asks a vendor’s support desk why a build plugin fails. Four requests, four different people, four different speeds of reply. The question is simple: which method makes sure none of them is forgotten?
Method one: the ordinary to-do list
Strengths. You already have one. It is fast to write, and it is designed to hold things you intend to do. Many people feel it is enough.
Weaknesses. A to-do list records your own actions. After you send a request, the task “ask the platform group” is done and vanishes. The pending reply has no home. The list is silent about the single most useful fact: you are still waiting.
Verdict. Fine for your own work. It leaks on every request that depends on others.
Method two: calendar reminders
Strengths. A reminder fires at the time you set, so you do not need to remember to look. For a single high-priority request, this works well.
Weaknesses. Reminders are separate from context. When “check on quota” pops up on a Thursday, you have to dig through messages to find who you asked and what you said. Ten such alerts in a week also become noise, and people start dismissing them. There is no overview, so you cannot see everything outstanding at once.
Verdict. A good companion for the one or two most urgent items. Poor as the primary record.
Method three: the team ticket system
Strengths. Tickets are shared and visible. They have an assignee, a status and a history, which are exactly the attributes a pending request needs. For requests to teams with a formal intake, tickets are the right vehicle.
Weaknesses. Not every request is a ticket. Asking a colleague for a quick review, or a manager for a verbal go-ahead, rarely warrants one. Tickets also sit with whichever team owns the work, so your personal commitments to chase are not captured. And a queue full of other people’s tickets does not tell you which of the ones you opened need a reminder today.
Verdict. Use for formal requests. Do not expect it to cover everything.
Method four: the dedicated waiting-for list
Strengths. One short page with a row per outstanding request. Each row names the owner, the date asked, what it blocks and the date you plan to chase. Because it contains only items awaiting others, the list stays small, and every line is actionable on a known day. It works for formal and informal requests alike, and it can point to tickets where they exist.
Weaknesses. It takes a few seconds to add each row, and it needs a weekly glance to be useful. If you never open it, you gain nothing.
Verdict. The strongest fit for the scenario, with the other methods playing supporting roles.
Comparison at a glance
- Remembers pending replies: to-do list, no; calendar, partly; ticket system, yes for formal ones; waiting-for list, yes.
- Shows who owes what: to-do list, no; calendar, rarely; tickets, yes; waiting-for list, yes.
- Gives a chase date: to-do list, only if you add one; calendar, yes; tickets, seldom; waiting-for list, always.
- Handles informal asks: to-do list, poorly; calendar, awkwardly; tickets, no; waiting-for list, yes.
- Effort to maintain: to-do list, low; calendar, medium; tickets, shared; waiting-for list, low.
How the methods combine in practice
The winning arrangement is rarely one method alone. Keep your task list for what you will do. Keep the ticket system for formal requests. Keep the waiting-for list as the overview of everything you have handed to others, with a link to the ticket where one exists. Add a calendar reminder only for the one or two items where a missed date would genuinely hurt.
This layered approach fits the cultural side of DevOps work, where shared visibility matters. Our article on managing the cultural side of a DevOps change makes the point that habits which make dependencies visible tend to reduce friction between teams, and a waiting-for list is a one-person miniature of the same idea.
Risk and reliability angle
There is also a risk dimension. Requests that fall through gaps are a quiet source of delay and rework. The guide to managing risk while keeping delivery dependable and secure frames risk as something to track and review, not something to hope will not happen. An outstanding approval is a small risk to your schedule, and a list that shows its age lets you treat it like one.
The scenario again, after one bad week
Return to our junior engineer. Suppose the week turns chaotic: an incident pulls her away for two days, and a planning meeting eats a third. What does each method look like on Friday afternoon?
The to-do list shows only her own unfinished tasks and nothing about the four requests. The calendar has thrown up three alerts she dismissed during the incident. The ticket system displays the quota request, which is still open, but not the review she asked a colleague for by chat or the sign-off she asked for verbally. The waiting-for list shows all four, with ages, and the nearest chase date reads “today.” In ten minutes she sends three reminders and the week is back under control.
That difference, a calm recovery rather than a scramble, is the strongest argument for keeping the list.
Applying the comparison to your own habits
Test yourself with a quick audit. List the last five requests you sent to others. For each one, ask where it is recorded, whether it has a follow-up date, and whether you would notice if it went quiet for a week. If the honest answers are “nowhere,” “no” and “probably not,” you have found the gap this article describes.
Many learners who are preparing for careers in the field are surprised by how much of professional work is coordination rather than configuration. If you are mapping out where the industry is going, the overview of the future of DevOps in Japan and elsewhere may add context on why collaboration skills keep gaining weight.
A note outside the workplace
The comparison holds beyond engineering. A person weighing a big personal purchase may read general material on Propraahi, an Indian property portal with buyer-oriented research pages and then send enquiries to several people. A to-do list would not capture those pending answers, and neither would a pile of reminders. A short waiting-for page would.
Practical setup in five minutes
- Create a document or spreadsheet called “Waiting for.”
- Add columns: request, owner, date asked, blocks, chase on.
- Enter the open requests from your sent messages in the last two weeks.
- Sort by the chase date so the nearest sits at the top.
- Set a recurring weekly slot to read through the list and send reminders.
Conclusion
No single method wins everywhere, but for the specific job of tracking what others owe you, the dedicated list beats the alternatives on clarity and effort. Use the to-do list for your actions, tickets for formal intake, calendar alerts for the critical few, and the waiting-for list as the glue that shows you where everything stands. It is a modest tool that fits any career stage and costs almost nothing to adopt.









