Three ways to examine a difficult decision

A project is late. The obvious response is to add people.

Before approving that response, three kinds of thinking can change the conversation. In this illustrative example, each makes a different contribution.

Critical thinking: check the explanation

What makes us think staffing is the constraint? A missed milestone is evidence of a delay. It is not, by itself, evidence of its cause.

Ask for the work waiting in the queue, the decisions that remain unresolved, and the points where tasks return for rework. Separate what the team has observed from what it has inferred. If the project is waiting for one approval, adding people may increase the queue without increasing output.

A useful record would include the initial explanation, the evidence used to test it, and any change in the diagnosis.

Creative thinking: produce an option worth examining

The choices may not be limited to adding staff or accepting the delay. Could the team reduce scope, sequence a release differently, test one uncertainty earlier, or change who can approve work?

More ideas are not automatically better. Ask which alternative changes a meaningful constraint, and how you would test it cheaply enough to learn before committing.

Record an alternative the person generated, the constraint it addresses, and the reason for pursuing or rejecting it.

Systems thinking: trace what moves elsewhere

Borrowing an experienced person may help this project and delay another. Releasing a partial product may reduce development work while creating support work. A local gain can shift a cost to someone who was absent from the decision.

Ask what happens next, who experiences it, and whether the proposed fix changes the recurring pattern. Draw the dependencies if words keep hiding them.

Record a consequence outside the immediate team and the action taken in response. A diagram is useful only if it helps explain or improve a decision.

Use the abilities together

Critical thinking tests an explanation. Creative thinking expands the options. Systems thinking examines their consequences and relationships. They are useful ways to describe the work, rather than labels for three types of person or three parts of the brain.

Their use also depends on knowledge of the situation. A thoughtful newcomer and an experienced project manager do not bring the same understanding of the dependencies. Practice across varied situations can help people investigate where their approach applies; transfer should be checked rather than assumed.

Design a task that needs them

Give learners enough context to reason, but leave a consequential decision unresolved. Ask for an explanation before showing an expert response. Change one condition and see whether the reasoning changes with it.

For individual feedback, point to one move in the record: “You tested the staffing explanation, but did not check the effect on the other project.” For an organizational judgment, specify the task and the missing evidence. One good explanation does not establish general readiness to lead projects.

Try it: Take a decision on your desk. Write one question that tests your explanation, one that opens another option, and one that follows the consequences.