Workload management is the weekly practice of seeing who has too much and doing something about it. It fails mostly because nobody can see the load in the first place.
Workload management is how work is distributed across a team so that nobody is quietly drowning and nothing important is unstaffed. It differs from capacity planning, which asks whether the team as a whole can take on more; workload management asks who specifically is carrying what, this week, and whether that is sustainable.
The reason it fails is rarely bad intent. It is that load is invisible: a manager sees the tasks assigned, not the ones absorbed informally, not the support requests, not the person who is the unofficial reviewer for everyone else. The first job is making the real distribution visible, and the second is being willing to change it.
Work-in-progress limits do more for workload than any amount of prioritisation. A person with three open items finishes them; a person with eight switches between them, finishes none this week, and reports being extremely busy — which is true and also the problem. Cap the in-progress column and the queue becomes visible instead of hidden inside individuals.
When one person is consistently overloaded, the instinct is to help them prioritise. Sometimes that is right. More often it means the work is not distributed because only they can do it — a skills concentration — or because the team has taken on more than it can carry and the overflow lands on whoever is least able to refuse. Both are decisions for the manager rather than problems for the individual, and treating them as time-management coaching is how good people leave.
Ettex Board makes the distribution visible: columns and cards with drag-and-drop, assignees and avatars so a per-person view is a filter rather than an exercise, colour labels and priority flags, due dates, checklists inside cards, lists and swimlanes for larger boards, and WIP limits to keep flow honest — the single most useful feature here. Every move and edit is logged per card and the board updates live for everyone. Effort estimates and the trend over weeks fit Ettex Sheets, recurring commitments like support rotas belong in Ettex Calendar so they stop being invisible, and the one-to-one where overload is actually raised is best kept in Ettex Notes.
Said plainly: Ettex has no workload analytics. There is no automatic capacity calculation per person, no burndown or velocity, no time tracking to measure real load, no alerts when someone is over a threshold, and no resource-levelling. The board shows what is assigned; whether that is too much is a judgement made in a weekly conversation. For a small team that conversation beats the metric anyway.
The practice of distributing work across a team so that no one is overloaded and nothing critical is unstaffed — usually a weekly review of who is carrying what.
Capacity planning asks whether the team can take on more work overall; workload management asks how the work already accepted is distributed among specific people right now.
A cap on how many items one person has in progress simultaneously — typically around three. It converts hidden overload into a visible queue and increases how much actually finishes.
Support, reviews, interviews and mentoring often consume a third of someone's week and appear on no board. Excluding them makes every workload assessment wrong in the same direction.
Treat it as a system signal. Usually it means skills are concentrated in one person or the team has accepted more than it can carry — both are management decisions, not time-management problems.
Weekly, looking at the board by person rather than by project. Project views reliably hide individual overload.
Workload management needs one board, a WIP limit, sizes rather than counts, and a weekly look by person. When the same name is at the limit every week, that is a staffing decision — not a prioritisation lesson.
A SWOT ends with four lists. A TOWS matrix pairs them — strength with opportunity, weakness with threat — and each pair produces a candidate action. That pairing step is the part almost every workshop skips.
Most go-to-market documents are positioning statements with a launch date stapled on. The version that works names one buyer, one problem, one channel to test first, and the number that decides whether to keep going.
The balanced scorecard measures a business from four angles rather than one. Its enduring value is the argument it forces about what actually drives the financial result.