Twenty-five common project management mistakes with early warning signs, concrete service-desk examples, corrective actions and evidence that better practice is working.
The guide covers purpose, authority, scope, acceptance, estimates, dependencies, resources, cost, risks, decisions, changes, delivery flow and handover. Use it to select a few practical improvements rather than adding process for its own sake.
Spot the pattern before it spreads
Most project mistakes become easier to correct when the early signal is visible. A delivery activity is easier to justify than an untested outcome. Coordination alone does not establish who may approve a commitment. An untested assumption can become an invisible dependency.
Label the assumption, explain its effect if false and assign a person and date to test it. Add the related risk or issue when appropriate.
04 / Keeping exclusions invisible
A missing boundary invites incompatible expectations. Late criteria can turn completed work into unexpected rework. A busy task list can still omit part of the promised result. A desired target is not evidence of a feasible plan.
Keep the target visible and develop an evidence-based forecast. Explain assumptions, uncertainty and the trade-offs required if the target is tighter than the feasible sequence.
08 / Omitting real dependencies
Unconnected activities can create an impossible completion date. A name on a schedule does not confirm available capacity. A precise number can conceal an unsupported assumption. Money used does not prove that useful work is complete.
Report accepted results and remaining work using a defined progress method. If earned value is used, apply its approved measurement basis rather than substituting spending.
12 / Double-counting commitments
Separate reports can contain the same future cost. A register does not reduce uncertainty merely by existing. Different conditions need different management actions. A technically delivered result may still fail the people using it.
Identify affected groups early and involve representative users in discovery, feedback and acceptance. Ask about real work, exceptions and operating constraints.
16 / Reporting status without a decision
A long update can leave the reader unsure what to do. A shared concern is not yet a reliable commitment. Lack of response can mean absence, confusion or insufficient authority. Small unrecorded additions can accumulate into a different project.
Capture the request, assess combined scope, time, cost, risk and acceptance effects, then route it to the proper authority. Keep urgent delegated decisions traceable.
20 / Rewriting the baseline to hide variance
A moving comparison can make deterioration disappear on paper. High activity can increase waiting and delay completion. An earlier date can transfer unresolved problems into operations. A measure can encourage behaviour that weakens the intended result.
Connect metrics to decisions and outcomes. Show definitions, counts, quality and age where relevant, and investigate the behaviour a target may encourage.
24 / Leaving handover until the end
A finished output still needs people prepared to operate it. A lesson matters when it changes a later decision or practice. Use the twenty-five patterns to select a few useful improvements.
For each selected pattern, record the current evidence, intended change, owner, checkpoint and sign of success. Ask the team whether the response is practical.
Contents
- Spot the pattern before it spreads
- 01 / Starting without a clear purpose
- 02 / Leaving authority ambiguous
- 03 / Treating assumptions as facts
- 04 / Keeping exclusions invisible
- 05 / Defining acceptance at the end
- 06 / Planning tasks without outputs
- 07 / Promising a date before estimating
- 08 / Omitting real dependencies
- 09 / Assuming resources are reserved
- 10 / Hiding the estimate basis
- 11 / Equating spending with progress
- 12 / Double-counting commitments
- 13 / Listing risks without responses
- 14 / Mixing risks with issues
- 15 / Consulting users too late
- 16 / Reporting status without a decision
- 17 / Giving actions no accountable owner
- 18 / Treating silence as approval
- 19 / Accepting changes informally
- 20 / Rewriting the baseline to hide variance
- 21 / Starting too much work
- 22 / Cutting required quality to recover time
- 23 / Rewarding a metric without context
- 24 / Leaving handover until the end
- 25 / Recording lessons without action
- Build a better-practice review
Using the PDF
Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.
Frequently asked questions
Who is this guide for?
Twenty-five common project management mistakes with early warning signs, concrete service-desk examples, corrective actions and evidence that better practice is working.
How can I practise the ideas?
Follow the running case, work through the page actions and use the PDF bookmarks to revisit a topic. The final learning pages help you apply the decisions to your own project.
What does the download contain?
The PDF contains 30 pages, including 27 numbered learning pages, a cover and two linked advertisements. The book is written in English.


