Every business has a list of the areas it recognises as responsibilities in their own right: sales, operations, finance, perhaps safety, purchasing or customer service. Each has someone who owns it, some kind of budget and a place in the management meeting. Everything else is a side task. Side tasks live inside those areas, are done by people whose job title names something else, and compete for attention with whatever they happen to be filed under.
The distinction looks administrative. Its effect is real. Being a recognised area brings three scarce things: an owner, a budget and a place on the agenda. Being a side task brings none of them. Cyber security filed under “the person who is good with computers”, complaints filed under whoever answers the phone, quoting accuracy filed under sales, data quality filed under nobody: each may matter a great deal while being funded from someone else’s budget, defended by someone with different priorities and discussed only when it goes wrong.
This article explains why the way a business classifies its work quietly decides what gets attention, how to spot side tasks that have outgrown their filing, how to tell whether promoting one would actually change anything, and what it really costs to do. It is general information for owners of growing businesses.
Classification is a standing decision
The list of recognised areas is rarely written down in one place, and most of it was inherited rather than chosen. Yet it acts as a standing allocation: every recognised area has someone who will defend its time and money, and every side task has no one.
Three misreadings keep important work in the wrong place:
- Classification is just description. It is not. It decides who owns something, where its money comes from and whether it reaches the agenda.
- If it matters, it will get attention. Businesses often agree that something matters and keep filing it as a side task, seeing no contradiction. Importance is a judgement; classification is a structure. Where they disagree, the structure wins every allocation decision.
- Promoting something is a matter of renaming it. Declaring a new area takes a meeting. Making it real takes months, and the remnants of the old arrangement linger long after.
A worked case from project management
Professional disciplines go through the same shift, and one example is instructive. For many years, the most widely used project management guidance treated stakeholder work mainly as part of communication. In its 2013 edition, the Project Management Institute’s guide made stakeholder management a knowledge area in its own right, with its own processes running from the start of a project through planning, delivery and control.
The lesson is not about stakeholders. It is that a profession concluded that treating this work as part of something else had not been working well enough, and restructured around it. When a discipline reorganises in that way, it has in effect published a finding: doing this work late, or as an afterthought, produced failures often enough to justify change. That finding is available to any business before it learns the same lesson from its own failures.
Three signs a side task has outgrown its filing
Each can be checked in an afternoon:
- Effort without recognition. Where is significant time being spent on work filed under a heading that names something else? A manager spending a day a week on IT security while their job is “office manager” is a sign. The key person dependence article covers a related risk: important work that depends on one person’s goodwill rather than a defined role.
- The same failure across unrelated work. A problem that recurs within one job is a delivery issue. A problem that recurs across jobs, teams or customers with nothing else in common is usually a missing responsibility.
- Nobody to ask. For each significant category of work, name the person who would be asked to explain a failure. Where no name comes to mind, the work is being done by whoever happens to notice.
The sequence test: will promotion change anything?
Not every promotion is worthwhile. The useful test is whether giving the work an owner would move its first activity earlier.
Work done at the end of a process, as a check or a clean-up, can only catch problems after they have happened. Work done at the start can change what happens. If making something a recognised responsibility means it is considered before a job is quoted, before a system is chosen or before a customer is onboarded, the change is real. If it simply gains a title while still happening at the same late point, the business has added a reporting line and changed nothing.
Some examples:
| Side task | Late version | Earlier version after promotion |
|---|---|---|
| Quoting accuracy | Discovered when jobs lose money | Owner reviews estimates on large quotes before they go out |
| Cyber security | Addressed after an incident | Owner signs off new systems, suppliers and access before they start |
| Customer complaints | Handled by whoever answers | Owner tracks causes and feeds them into quoting and design |
| Data quality | Fixed when a report is wrong | Owner sets rules for how data is entered at the start |
| Supplier risk | Noticed when a supplier fails | Owner checks critical suppliers before orders are placed |
Count the cost before declaring it
Promotion is usually presented as a tidy-up. It is an investment with a long tail:
- An owner, with enough standing to be heard, usually taken from somewhere else.
- Time and money, which come from areas that may resist.
- A place on the agenda, which displaces something.
- Redrawn boundaries, because a new responsibility is carved out of existing ones, and people losing territory rarely concede it neatly.
None of this argues against promoting important work. It argues for counting the cost honestly and tracking completion, not just the announcement. A half-finished promotion costs the disruption without delivering the benefit. Signs of an unfinished change include old forms still in use, job descriptions never updated, decisions still routed to the old owner and reports that still file the work under its old heading.
What ownership must include
Naming an owner is only the first step. For the change to be real, the owner needs a short written description covering:
- Scope: what the responsibility includes and, just as importantly, what it does not.
- Decisions owned: what the owner can decide without asking, and what must go higher.
- Time: how many hours a week or month are formally allocated, and what the owner stops doing to make room.
- Budget: what they can spend, and on what.
- Reporting: what they report, to whom and how often.
- A deputy: who covers when the owner is away, so the responsibility does not lapse during holidays.
Without these, the new area is a title attached to a busy person, and the work will drift back into being a side task.
Sometimes the right move is the reverse
The same review can show that a recognised area no longer needs to be one. A role created for a past expansion, a committee formed after an incident long since resolved or a report produced for a manager who has left can all outlive their purpose. Apply the same tests in reverse: is there still effort and failure to justify a separate owner, and would merging it back move any work later? If not, fold it into another role, update the decision routes and free the time for responsibilities that need it more.
A five-step review
- Write the list of areas the business formally recognises: those with an owner, a budget and a regular agenda item. The act of writing it often produces disagreement about what is on it, which is useful.
- Name the owner of each, and the person who would answer for a failure. Where those differ or are missing, the area is nominal.
- Apply the three signs to find side tasks that may have outgrown their filing.
- Apply the sequence test to each candidate. If promotion would not move its first activity earlier, describe the change honestly as a reporting change.
- Count the cost and set a completion measure. Name the owner, the time and budget, what the agenda displaces and whose boundaries change, then decide what “done” looks like.
Review the list every two or three years. Businesses that never do end up with a structure built around problems they solved long ago. The decision rights before meetings article covers making ownership mean something once it is assigned.
A worked example
This is an illustration. A garden services and landscaping business with 50 staff recognises five areas: sales, operations, fleet, finance and safety. Over two years, three problems keep recurring across unrelated jobs: jobs priced from incomplete site information, client data in three different systems that never agree, and a growing number of phishing emails reaching staff, one of which nearly led to a fraudulent payment.
The owner applies the three signs. The office manager spends about a day a week dealing with IT problems and security, a role nowhere in her job description. Pricing problems recur across different estimators and types of work. When the owner asks who would answer for a data breach, nobody can say.
The sequence test separates the candidates. Information and security passes: an owner would review new systems, suppliers and staff access before they begin, rather than responding after incidents. Site information for quoting passes: an owner would set a minimum site checklist before any quote over a set value goes out. Data consistency fails on its own; it is really part of the information and security responsibility.
The owner counts the cost. Information and security becomes a recognised area owned by the office manager, with one day a week formally allocated, an annual budget for tools and an external review, and a standing item at the monthly meeting. Quoting quality becomes part of the operations manager’s role, with a checklist and a monthly review of jobs that lost money. Completion is measured: within six months, every system has a named owner, staff access is reviewed quarterly, and the old shared passwords are gone. The office manager’s other duties are reduced to make room, and that change is written into her role.
How this applies to a small Australian business
- Write down the areas your business recognises, with owners.
- Look for effort without recognition, recurring failures and unowned work.
- Use the sequence test before promoting anything.
- Count the real cost: owner, time, money, agenda and boundaries.
- Track completion, not just the announcement.
- Update job descriptions and decision routes so the change sticks.
- Review the list every two or three years.
- Learn from your industry: when professional bodies or regulators restructure around a topic, ask what failure prompted it.
Signals worth watching
- Significant time spent on work no job description mentions.
- The same problem appearing in unrelated parts of the business.
- Nobody able to say who would answer for a failure.
- New responsibilities announced but old forms and routes still in use.
- Important topics discussed only after something goes wrong.
- A structure that has not changed while the business has.
Common mistakes
- Assuming important work will get attention without an owner.
- Promoting work in name only.
- Ignoring the cost of creating a new responsibility.
- Declaring a change and never checking it is complete.
- Copying another organisation’s structure without asking why it changed.
- Never revisiting the list of recognised areas.
Frequently asked questions
Does every important task need its own manager? No. Many can sit within an existing role, as long as ownership, time and agenda space are explicit.
How do we know a side task has become important enough? Look for recurring failures across unrelated work, significant hidden effort and nobody to ask when it goes wrong.
What if no one has capacity to own it? Then the business must decide what else gives way, or accept the risk knowingly. Leaving it unowned is also a decision.
How long does a promotion take to complete? Often months. Set a measure of completion and check it.
Should we follow industry frameworks? Use them as evidence of what others learned, not as templates to copy.
Can one person own several side tasks? Yes, if the time is genuinely allocated and the responsibilities fit together, such as information systems and data, or quality and customer complaints.
Questions to ask
- Which areas does our business formally recognise, and who owns each?
- Where is significant effort going that no role description mentions?
- Which problems keep recurring across unrelated parts of the business?
- Who would answer for a failure in our most important side tasks?
- If we gave a side task an owner, would its work start earlier?
- Which past changes did we announce but never finish?
Bringing it together
The way a business classifies its work quietly decides what gets an owner, a budget and a place on the agenda. Important work filed as a side task competes for attention it rarely wins. Look for effort without recognition, recurring failures across unrelated work and tasks nobody answers for. Use the sequence test to check whether promotion would move the work earlier, where it can change outcomes. Count the real cost, track completion rather than the announcement, and review the list as the business grows.
Source: KEVOS notes, drawing on teaching material on project management knowledge areas and the Project Management Institute’s 2013 addition of stakeholder management as a separate knowledge area. Examples in this article are illustrations. This article is general information.
