
The Delphi method gives a forecast more than one quiet round
The Delphi method uses repeated, structured rounds of expert input. Learn how anonymity and feedback help, and why agreement alone does not make a forecast true.

The Delphi method uses repeated, structured rounds of expert input. Learn how anonymity and feedback help, and why agreement alone does not make a forecast true.

Pooled, sequential and reciprocal dependencies call for different coordination. Map how work moves before adding another meeting.

More tasks and more decision-making are different job-design changes. Use a concrete example to compare enlargement with enrichment.

Find business-critical responsibilities before naming successors. Build a practical development plan around knowledge, access and decision-making.

Resource levelling can move a finish date because people cannot perform overlapping assignments indefinitely. Read the schedule assumptions first.

Run an after-action review that separates expectations from events, invites different perspectives and turns observations into a small set of owned improvements.

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.