
The bus factor reveals work that depends on one unavailable person
A team can depend heavily on one person’s knowledge even when it has many members. Use the bus-factor idea to identify fragile handovers without blaming experts.
Practical notes on leading a team, sharing responsibility and turning a discussion into a decision people can use.
Record the next decision →

A team can depend heavily on one person’s knowledge even when it has many members. Use the bus-factor idea to identify fragile handovers without blaming experts.

A cost-performance index compares the budgeted value of completed work with its actual cost. Use a small example to avoid confusing spending with progress.

A work breakdown structure organises the project’s deliverables and scope. Use it to expose missing work before adding dates and assigning activities.

Rolling-wave planning gives near-term work detail while keeping later stages visible at a higher level. Use clear review points to add detail before it is needed.

Use Little’s Law to connect average work in progress, throughput and time in a process, while keeping boundaries and assumptions clear for your team.

Define a service-level objective with a meaningful indicator, target and time window so an operations team can judge performance consistently.