
Force-field analysis separates pressures for and against a change
Force-field analysis maps the pressures helping and resisting a change. Use a concrete team example to turn the diagram into decisions rather than a popularity vote.

Force-field analysis maps the pressures helping and resisting a change. Use a concrete team example to turn the diagram into decisions rather than a popularity vote.

A decision journal keeps the reasons, uncertainties and expectations behind a choice available for a more useful review later.

Use the ladder of inference to separate an observation from the conclusion you draw about a colleague, then ask a question that can change the picture.

Catchball turns a strategic target into a discussion about feasibility, resources and ownership. Learn how to run a useful exchange without endless consensus.

Consent-based team decisions look for reasoned objections within a defined scope. Explore a practical example with safeguards, explicit responses and a review date.

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.

Prevent two teams from owning the same live queue by agreeing a cutover time, a shared work list and a route for late updates.

Calling a decision reversible is useful only when the team knows how to reverse it. Define the scope, review point and exit cost before experimenting.

Use a premortem to surface specific project risks, then turn the useful concerns into owners, early signals and practical responses.