The Taskmaster Manager
A taskmaster is highly focused on getting work done—quickly, continuously, and according to deadlines. They tend to manage through assignments, follow-ups, status checks, and pressure.
Their management vocabulary often sounds like:
“Is this done?”
“When will you finish it?”
“What’s the status?”
“I need this by EOD.”
“Once you’re done with that, start this.”
The defining characteristic is that they see management primarily as assigning tasks and ensuring execution, rather than developing people or giving them ownership of broader outcomes.
A taskmaster often:
- Keeps employees constantly busy.
- Tracks deadlines closely.
- Frequently asks for progress updates.
- Quickly assigns another task when one is completed.
- Measures productivity through visible output.
- Has little tolerance for delays or excuses.
- May emphasize urgency even when something isn’t genuinely urgent.
- Often gives tasks rather than problems to solve.
For example, a good manager might tell a senior DBA:
“Database performance has deteriorated over the last month. Investigate it and recommend what we should do.”
A taskmaster is more likely to say:
“Check the indexes. Update the statistics. Run this query. Send me the results by 2 PM. Then check these five servers.”
The first gives the employee ownership of an outcome. The second gives the employee a sequence of tasks.
Taskmaster vs. Micromanager
They’re related, but not identical.
A taskmaster controls what and how much you do.
A micromanager controls how you do it.
So a manager can be a taskmaster without micromanaging:
“I don’t care how you accomplish these five things, but I need all five completed by Friday.”
And someone can unfortunately be both:
“Complete these five things by Friday—and show me exactly how you’re doing each one.”
When a Taskmaster Can Be Effective
This style isn’t always bad. It can work well in environments involving repetitive operations, tight deadlines, incident response, inexperienced teams, or clearly defined deliverables.
The problem arises when everything becomes a task and everything becomes urgent.
With experienced knowledge workers—engineers, DBAs, architects, analysts, designers—the style can become counterproductive because highly skilled employees generally provide more value when they’re given problems, responsibility, and decision-making authority, rather than an endless queue of instructions.
At its worst, the taskmaster creates a culture of:
“Tell me what to do next.”
A stronger manager tries to create:
“Here’s the outcome we need. Figure out the best way to achieve it, and come to me when you need support.”
