Most answers to this question are weak in the same way: they describe a tool rather than a system. "I use Notion" or "I keep a to-do list" tells the interviewer nothing about how you make decisions about your work. The question is really asking: how do you ensure the right things get done, in the right order, without things falling through the gaps?
What interviewers are actually asking
This question comes up most often in roles where self-management matters: fast-paced environments, roles with multiple stakeholders, jobs where you're expected to handle several workstreams without constant supervision.
What the interviewer wants to know:
- Do you have a deliberate approach, or do you just react?
- Can you manage your own workload without being chased?
- Do you have strategies for when things pile up or go wrong?
- Will you be reliable in a role with real demands?
System vs tool: why the distinction matters
A tool is software or a method (Notion, a spreadsheet, a physical diary). A system is the logic behind how you use it. Two people can both use Trello and produce completely different results — one thoughtfully and one chaotically.
What makes an answer strong is explaining the decisions behind your system:
- How do you capture incoming work? (immediately, or in batches?)
- How do you decide what to work on first?
- How do you track things that aren't your task but are waiting on others?
- How do you review and adjust when priorities shift?
If you can describe the logic, the tool becomes a detail.
How to structure your answer
Three-part structure: how you capture work → how you prioritise → how you review and adjust. Mention a tool only as an example of how you implement the system, not as the answer itself.
Sample answers
Individual contributor role
"I have a pretty simple system that I've refined over the years. I keep a running list — currently in Notion — of everything I have on. Every morning I take five minutes to review it and decide what the two or three things are that must happen today, and what order they go in. I don't try to plan the full day because things change, but I anchor my day around those two or three so that even a disrupted day moves the needle.
For things that aren't my task but are waiting on someone else, I track those separately with a follow-up date so they don't fall off my radar. And on Friday afternoon I do a quick weekly review — what's outstanding, what's coming next week, is anything at risk. That fifteen-minute habit has probably saved me from missing things more times than I can count."
Manager or multi-stakeholder role
"At a team level, I use a shared project tracker for visibility — everyone can see what's in flight and what's blocked. For my own work I use a daily planning habit: first thing in the morning, I look at what's due this week, what's at risk, and what decisions I need to make today. I'm quite deliberate about protecting blocks for focus work — otherwise the day gets consumed by reactive communication and the important things don't progress.
I've also learned to build slack into plans rather than assuming everything will go perfectly. A project where every task runs perfectly on time is a project with no buffer when something inevitably shifts. I try to flag capacity risks to stakeholders early rather than hoping things will sort themselves out."