KajoData / Career & business
Too much work: discuss scope and priorities
I show how to explain work and its constraints, offer realistic options and check whether the discussion changed the plan.

You have too much work, but every new request looks like another opportunity to prove yourself. You accept a report, a correction, an urgent question and one last small task before leaving. Eventually the excess becomes invisible. Everyone sees completed outputs while extra hours become your private method for keeping the queue moving. It is worth naming that arrangement before it becomes the ordinary plan for every week.
I would start by showing the scope, available time and decision I need. You can explain the value of your work while also saying that the current task list does not fit the agreed conditions. I would not assume that presenting overload well will secure a pay rise. The goal here is a concrete change in what gets delivered, when it happens and who takes responsibility for the work.
Establish what fills the day
For a few ordinary days, record categories of work: recurring reports, new analysis, meetings, maintenance, corrections and unplanned questions. A simple record is enough. The purpose is not to track every minute or build a case against colleagues. I want to understand the actual scope, because memory tends to focus on the most recent urgent request. Repeated small interruptions may occupy a substantial part of the week without looking like a single large assignment.
Separate working time from waiting. An analysis might require several hours of effort while taking three days to complete because the source data has not arrived. Those are different constraints. Presenting them as one number makes the deadline conversation harder to understand. Also distinguish tasks you start voluntarily from commitments already agreed. Your own ideas for improvements use time too, even when nobody formally requested them and the result would be useful.
This allows a more specific statement than “I am busy”. For example: “Recurring reports and meetings use most of the available time, and this week we added two analyses and a source repair.” You do not need to prove that you work harder than everyone else. You need enough visibility to decide together what is achievable. Comparing one person’s tiredness with another’s rarely helps establish a workable delivery sequence or a shared understanding of current commitments.
Show the output and its maintenance cost
Name what you deliver. “I prepare the weekly sales report and maintain its refresh process” says more than “I handle Excel”. Explain what the result supports and what makes it reliable. Checking sources, investigating a difference and repairing an incorrect lookup may be invisible in the final chart. Without that work, however, the chart can lose its meaning. The conversation needs to include the less visible responsibilities behind an apparently simple output.
Describe time savings only when there is evidence for them. If the earlier process was never measured, do not attach a convenient number of hours to the improvement. You can name the mechanism: one repeatable import replaced manual file merging, or recipients now use one agreed set of metrics. Those are worthwhile outcomes. Explaining the actual change is more credible than producing an impressive saving that nobody can reconstruct or compare with a clear baseline.
For automation, include ongoing maintenance. Who notices a missing input file? What happens when a column changes name? Who answers the report user’s questions? If all of that comes to one person, building the automation may free less time than the initial demonstration suggests. Include normal operation in the workload discussion. Otherwise every successful project quietly creates another permanent responsibility while its original delivery is treated as evidence that you now have more capacity.
Ask for a priority decision
Bring the task list and a choice. “Within the current deadline I can finish the returns analysis or prepare the new sales view. Which output matters more?” That gives the manager a concrete decision. If both are essential, discuss changes to scope, timing or staffing. Calling everything a priority does not create more time. A sequence or a different delivery arrangement is still required before the list becomes a realistic plan.
I would also propose a recommendation rather than simply handing back responsibility. “I suggest repairing the recurring report first because the current total needs investigation. I will start the dashboard afterwards. If the dashboard must come first, somebody needs to take over the repair.” This exposes the dependency and reasoning. The person authorised to make that trade-off can then decide with an understanding of what the choice will delay or require from others.
When several people assign work independently, ask for a shared point where the order is agreed. Otherwise each requester sees one small task and nobody sees the complete list. The HSE standard on role addresses clear responsibilities and compatible demands. In practice, I would translate that into an explicit answer: who resolves a conflict between two urgent requests sent to the same person, and how do the requesters learn about that decision?
A synthetic example of the conversation
Imagine an analyst who needs to prepare a recurring report, investigate a data difference and begin a dashboard. The report is needed for the next meeting. The difference may affect its result, while the dashboard’s definition has not been agreed. Instead of promising to manage everything somehow, she explains these dependencies. First she needs to establish whether the report can be published, then plan the new view on a clear basis.
A message might read: “The report is prepared, but the total needs investigation before publication. I need the data owner to confirm the returns rule. I suggest using the available time to resolve that issue. I will start the dashboard after we agree its definition and estimate delivery following that discussion.” This provides a state, risk, recommendation and next step. It avoids a precise promise whose essential conditions are still unknown.
If the manager chooses another option, record the consequences too. Perhaps the meeting will use the previous correct report with its date clearly shown. Perhaps another colleague will obtain the returns definition. Do not quietly repair every version of the plan with extra hours so all options appear achievable simultaneously. That prevents anyone from seeing whether the new allocation works. This fictional example illustrates a conversation, not a guaranteed response from a particular manager or organisation.
Limit how many tasks are active
When everything has started, movement can be mistaken for progress. Every task has an open file, a recent message and part of an investigation to reconstruct. I would make the queue visible and distinguish active work, waiting and completion. This does not require elaborate software. It requires agreement about what the states mean and who can change the order, especially when a new request arrives while several older commitments remain unresolved.
Atlassian describes work-in-progress limits as limits on the number of tasks in a process stage. I would use that idea to discuss how many subjects the team can reasonably handle at once. The limit needs to suit the work. It does not remove incoming requests or guarantee a particular productivity increase. It helps expose the moment when accepting another task requires a decision about the ones already underway.
Work waiting for data should remain visible. If it disappears from the board, it will return as a surprise when the file arrives. Record the dependency and next review point. Starting another task during the wait may be reasonable, but remember that both can require attention again on the same day. The queue should represent commitments, not simply whichever application happens to contain the cursor at this particular moment.

Define completion before endless polishing begins
Before starting a report, agree what makes it usable. Which question should it answer? Who accepts the result? How will correctness be checked? Which views belong in this scope? Without a boundary, layout adjustments, extra breakdowns and longer commentary can continue indefinitely. Ambition can become entangled with work that nobody requested and that has no obvious finishing point. A clear acceptance condition gives both the analyst and the recipient something concrete to evaluate.
The first scope might include one period, two stores and an agreed sales measure. Forecasting and comparison with a target can enter a separate queue. If the recipient changes the definition halfway through, update the estimate and priorities. A request is not necessarily small because it fits into one sentence. It may require a substantial change to sources or the model. Make that implication visible before silently absorbing it into the existing deadline.
Completion includes handing the solution over. Where is the source? How is the report refreshed? What do missing values mean? Who should investigate a difference? If only I know the answers, every return to the report consumes my time again. A short instruction can reduce dependence on one person. It still does not replace agreement on ownership and maintenance time, particularly when the output becomes a regular part of how the company works.
Extra hours should not be an invisible plan
If the normal scope regularly fits only by extending the day, say so explicitly. You do not need to establish that you are exceptional before reporting overload. The HSE standard on demands refers to achievable demands within agreed hours. I use that as an organisational reference point. Detailed arrangements for working time and compensation depend on the situation; this article does not derive those rules from a general planning guide.
Distinguish a temporary exception from a recurring pattern. A one-off disruption during an incident and weeks of ordinary work beyond the plan need different responses. Repeated overload requires a change to scope, process or resources. Moving one meeting may be insufficient. Agree what will change next week instead of only discussing how to survive the current one. Then examine whether that change has actually reduced the conflict or merely shifted it to another day.
If the workload is already unacceptable, do not postpone raising it until the measurements or presentation are perfect. A clear statement that the current scope is unachievable matters on its own. Details can be gathered together. Good communication helps a decision, but it does not guarantee a sensible response from every organisation. Nor does it transfer all responsibility for working conditions to the person who first reports that the arrangement is causing a problem.
Separate visibility from the pay conversation
Regularly show results, especially the less visible ones. Explain which question a report helps answer, what improved and which responsibilities you took on. This is useful material for a development or compensation discussion. I would not promise that a particular way of describing your contribution leads to promotion. Decisions also depend on the organisation, budget, role and other conditions. Presenting good evidence supports a conversation without determining its outcome in advance.
Discuss reducing workload separately from asking for a pay rise. Higher pay does not make two conflicting deadlines achievable. A better queue does not necessarily settle whether the responsibility is compensated appropriately. You may need both changes. Keeping the decisions distinct helps avoid a conversation that ends with praise while the actual work plan remains exactly the same. A positive reaction can be encouraging, but it needs to be connected to a concrete decision if the workload is to change.
For development, ask about criteria and the next step. Which responsibility should you take on? What can you stop doing? How will the result be assessed, and when will you revisit the discussion? If development means only adding duties, name that pattern. More started tasks are not automatically evidence of a better role. I want to understand which responsibility is increasing and what support will make it possible to perform it well.
Record the agreed plan afterwards
A short follow-up should identify the sequence, scope, dependency owners and next review date. For example: “This week I will finish the report repair. The new analysis starts after the lookup arrives. Additional requests go into the shared queue.” The purpose is a common understanding rather than proving bad intentions. If another person understood the agreement differently, discovering that now is easier than discovering it on the morning both outputs are expected.
Then check the effect. Are tasks still arriving without priority changes? Do requests bypass the agreed queue? Did someone take over the responsibility they agreed to accept? If the plan fails, return with a specific observation. Establish which condition did not hold and what must change for another attempt to work. A useful review moves beyond whether the meeting felt positive to whether the actual pattern of work became more manageable.
Recovered time can also be filled immediately by new requests. When improving a process, agree what the released capacity is for: maintenance, quality, a new priority or reducing overload. Otherwise the improvement may simply become a higher expected task count. Keep returning to available time instead of treating it as an unlimited source of future commitments. An automation can be successful while the overall workload remains excessive; both facts can be true and need attention.
An exercise before your next discussion
Choose three current tasks. For each, record the recipient, expected output, deadline, dependencies and remaining effort. Mark existing commitments separately from new requests. Prepare two realistic sequences. Do not quietly add extra hours as a hidden reserve in both. If neither sequence fits current conditions, that is the decision to discuss. The exercise is meant to expose the conflict, not manufacture a plan that looks achievable only because its main assumption is left unstated.
Write one recommendation and one question. For example: “I suggest fixing the report error first because it affects a result already in use. Should we postpone the new view or give it to someone else?” That starts a concrete discussion. If the problem is getting stuck within a single task rather than the overall queue, see my article on working through a blocker. Identifying the kind of difficulty helps you request the right support.
Finally, set a time to inspect the effect. A workload conversation should lead to a change you can observe. Praise can be welcome, but you also need to know what to do tomorrow morning, what waits and who resolves the next conflict. That is where I would begin organising the situation. The resulting plan gives you a basis for deciding whether the workload has become more reasonable instead of simply hoping that the next week will feel different.
When the answer is that everything is needed tomorrow
Walk through the conditions of each task. Does the deadline come from a specific event or habit? Does the recipient need the whole report or one answer? Are the data available, and can somebody take over part of the work? These questions may reveal an option that was previously hidden. They do not guarantee that all expectations can fit together. Name the remaining conflict rather than ending the meeting with an apparent agreement that cannot be carried out.
If no decision follows, state the risk and proposed order in writing according to the team’s process. Avoid promising contradictory outcomes to separate requesters. If you cannot set priorities, ask who can. You need an organisational decision rather than another private technique for clicking faster. That boundary matters particularly for a beginner who may not yet know which deadlines are negotiable or who is responsible for accepting a new commitment on the team’s behalf.
Key takeaways
How do I tell my manager I have too much work?
Show the current scope, available time and conflict between tasks. Recommend an order and ask for a decision about scope, timing or allocation.
Must I prove my value before reporting overload?
You can report that the scope is unachievable without first presenting a list of successes. Evidence about results can help the conversation but is not a condition for raising the issue.
Does greater effort guarantee a pay rise?
There is no such guarantee. Compensation and a workable workload are separate decisions, even when both need attention.
AI was used in an automated way while working on this article. If you want to learn how to do it too, check out this project.
