Projects

All projects04 / 05A team with several projects

The manager sees where work
stalls, before the deadline slips

A workspace for a team that runs several projects: the manager sees overload, dependencies and budget, and the employee sees their own work without other people's noise.

Operation
Several projects run by one team
Roles
Manager, employee
Data sources
Task tracker, workload spreadsheet, budget
Main screen
Team workload map

Workload mapPeople by week: overload and idle time are visible before the status meeting.

Context

The team runs several projects at once. The manager is responsible for deadlines and budget, the employee for their own tasks. Tasks live in a tracker, workload in a spreadsheet, and agreements in chats.

Constraint

Overload and blocking tasks became visible at the weekly meeting, when the deadline had already moved.

The plan was recalculated by hand after the meeting, and the decision to reassign work came a week late.

How it was

Each source was accurate in its own way, but the point where work stalls appeared only when they were brought together at the meeting.

Hypothesis

If the manager sees not a list of tasks but the point where a constraint is arising right now — a person, a dependency or the budget — the decision to reassign work is made before the deadline slips.

Operation model

Two levels of one product: the manager sees the whole system, and the employee sees their own work and those waiting for its result.

Task trackerstatuses by project
Load spreadsheetupdated on Fridays
Team chat“who is doing this?”
Status meetingonce a week
Plan recalculationby hand
overload shows up a week laterManager and employee workspace
01Planprojects and milestones
02Workloadpeople by week
03Constraintperson, dependency, budget
04Scenariosimpact on deadline and budget
05Decisionthe manager decides
06Recalculationthe team sees the changes

Interface

Manager and employee workspace

  1. People by week: overload and idle time are visible before the status meeting.

    1. 1Overload by week
    2. 2The task that holds up others
    3. 3Constraints as a list, by importance
  2. The employee sees today's work and who is waiting for its result.

    1. 1Only their own work
    2. 2Who is waiting for the result
  3. The dependency chain, budget and risks explain why the project is at risk.

    1. 1Dependency chain up to the milestone
    2. 2Budget and risks next to the deadline
  4. The manager compares scenarios by deadline, budget and workload and chooses one; the plan is recalculated.

    1. 1Impact on deadline, budget and workload
    2. 2The manager makes the decision
    3. 3The plan is recalculated for the whole team

Specification for the technical team

The product side: entities, roles, events and data sources.

Data sourcesTask trackerLoad spreadsheetProject budgets
Operations layerWorkload by weekDependencies and milestonesScenarios
Roles and devicesManagerEmployee
Entities
Projects, milestones, tasks and dependencies, people and workload by week, budget.
Roles
The manager sees the overview and scenarios; the employee sees their own tasks and what they are waiting for from others.
Plan recalculation
After the manager's decision the plan is recalculated, and the changes appear in “My tasks”.
Data sources
Task tracker, workload spreadsheet, project budgets.

What changed in how the operation runs

The changes are described qualitatively. Figures are published once the client approves them.

  • 01Before the meetingOverload is visible during the week, not at the status meeting.
  • 02Decision before the slipThe reassignment is chosen from scenarios with a clear impact on deadline and budget.
  • 03Less noiseThe employee sees their own work and those waiting for its result.

Metrics

  • Milestones on timetracked
  • Time from overload to decisiontracked
  • Deadline shifts by projecttracked