Team management: the four things a manager actually owns

Team management is the work of making a group of people collectively more effective than they would be individually. Written down like that it sounds abstract, and most advice keeps it there — leadership styles, personality types, trust exercises. The job is more concrete: a manager owns four things, and almost every team problem traces back to one of them being unowned.

Those four are direction, workload, feedback, and obstacles. Direction is knowing what we are doing and why. Workload is who is doing what and whether it is survivable. Feedback is the loop that lets people correct. Obstacles are the things a manager can remove and the team cannot. Nothing else on a manager's calendar matters as much, and most of what fills it belongs to none of the four.

The four, and how each one fails

• Direction fails quietly. The team is busy, everyone is working, and nobody can state what would make this quarter a success. The symptom is effort spread evenly across everything.
• Workload fails visibly, then invisibly. First people say they are stretched; then they stop saying it and quality drops instead. By the time the second stage arrives, the manager has usually stopped asking.
• Feedback fails by delay. Something is noticed in March and mentioned in the November review, by which point it is neither useful nor fair.
• Obstacles fail by escalation, or the lack of it. A team blocked by another department for three weeks is not a performance problem; it is a manager who has not made the call.

A working rhythm

1. Weekly one-to-ones, thirty minutes, owned by the person not the manager. This is where feedback and obstacles surface early enough to be cheap.
2. One weekly team meeting with a fixed shape: what changed, what is blocked, what is next. Not a status round-robin where seven people wait to speak.
3. A visible list of what the team is working on, with owners. Ambiguity about ownership is the most common source of both duplicated work and dropped work.
4. A monthly look at workload distribution. Not who is busy — everyone reports busy — but who is carrying the interrupts, the on-call, and the unglamorous maintenance nobody counts.
5. A quarterly restatement of direction, in writing, including what the team is deliberately not doing.

The most underrated management act is deciding what the team will stop doing. Adding priorities is free and feels like leadership; removing them costs a conversation with whoever asked, which is why it does not happen — and why teams end up with nine priorities, which is the same as none.

Managing people you cannot see

Distributed teams change the failure modes rather than adding new duties. Direction has to be written down, because there is no corridor in which it gets absorbed. Obstacles surface later, so they have to be asked for explicitly rather than noticed. Workload becomes harder to read, because the visible cue of someone looking exhausted is gone. The four jobs are the same; the manager just cannot rely on the building to do part of them, and the policy side of that is covered in remote work policy.

Where the work is visible

Ettex Teams holds who is on the team, what they own and how the group is structured, which is the substrate the other three jobs run on. What people are actually working on belongs on a board with owners and dates, and one-to-ones tend to work better with a running document — the format is covered in one-on-one meeting, and the workload half in workload management.

To be direct about the limits: no tool manages a team. There is no productivity scoring, no activity monitoring, and nothing that will tell you a person is struggling — deliberately, because software that measures keystrokes and calls it management produces exactly the behaviour it deserves. What tooling can do is make ownership and workload visible enough that a manager doing the four jobs can see what is happening.