A project management course rebuilt around decisions

A project management course moves through budgeting, resourcing, scheduling, and closing. Each module ends with a knowledge check. People complete the course.

Now give one of those people a project where the budget is fixed, a deadline has moved, and the only experienced engineer is needed elsewhere. The categories no longer arrive one at a time.

This is an illustrative redesign of that course. It can run online or in a room. The delivery format does not decide how much thinking it demands.

Begin with the collision

The project must ship in six weeks. Another team needs the engineer for two of them. Keeping the engineer protects your schedule but puts the other team's customer commitment at risk. Moving the engineer may expose a dependency your team has not documented.

Ask the learner to recommend a plan. Supply the relevant project information and access to the tools a person would normally use. Require them to explain what they would protect, what they would give up, and what they would verify first.

That explanation is the first piece of evidence. A choice alone gives too little insight into its basis.

Make the consequences connected

Suppose the learner chooses to compress testing. Later, reveal a defect that requires rework. Do not imply that every compressed test schedule causes this outcome. Ask whether the original plan accounted for the possibility, and how the new evidence changes the plan.

Or suppose they negotiate a smaller release. Introduce a customer whose needs depend on a deferred feature. The exercise should make them reconsider a real trade-off, not discover which button the designer wanted them to press.

Keep instruction close to the need

A learner who does not understand a dependency map needs help. Provide a worked example, let them use it, and later ask them to interpret a different map. Requiring a person to struggle without enough knowledge is not a shortcut to higher-order thinking.

An experienced learner may instead need a more ambiguous constraint. Match the support to the learner, then record it when interpreting the performance.

Debrief the reasoning

Ask what the person expected when they made the first decision. Compare that prediction with what followed. Which relationship did they overlook? What would they check earlier? What would they do the same way, and why?

Then give them another attempt with different conditions. A persuasive debrief is not sufficient evidence that they can use the insight.

Capture two useful outputs

For the individual, identify a concrete next practice: “Before reallocating a shared person, trace the effect on both delivery plans.”

For the organization, preserve an observation and its limits: “In this exercise, the participant identified the cross-team dependency after a prompt. Independent recognition remains to be observed.”

The course still teaches project management knowledge. Its practice now asks people to use that knowledge where the demands conflict.

Try the redesign: Choose one module in a current course. Write a decision in which that module's topic conflicts with another. What would the learner need to explain?