Quick 20 on project management:
A project begins much before the first meeting.
It begins in the human imagination—that mysterious place where ambition is unlimited, resources are assumed, deadlines are decorative and other people’s weekends are freely available.
Someone sees an opportunity. Someone else prepares a presentation. A senior leader approves it with confidence. A project manager is then invited into the room and informed that the impossible has already been promised. This is called alignment.
Project management is usually presented as a science of planning, scheduling, budgeting and execution. But beneath the templates, dashboards and risk registers, it is really a philosophical inquiry into human behaviour.
How much truth can an organisation tolerate? How much uncertainty can a leader admit? How quickly does accountability travel downward?
Why do intelligent people repeatedly agree to deadlines that offend both mathematics and common sense?
And why does every project plan, however colourful, eventually encounter the inconvenient existence of reality?
Projects reveal us. They expose our vanity, fear, ambition, evasiveness and remarkable ability to rename failure. They show how institutions behave when desire collides with limitation.
Here are twenty reflections from that collision.
1. Nothing Is Impossible for the Person Not Doing It
The first law of project management is simple: nothing is impossible for the person who has no responsibility for delivering it.
Distance produces courage.
The farther a decision-maker sits from the actual work, the more visionary the deadline becomes. A task that appears technically impossible to the project team may look like a “healthy stretch” from the executive floor.
The sponsor dreams in quarters. The team suffers in hours.
This is why impossible deadlines are rarely called impossible. They are called bold, agile, transformational or strategically necessary. Language performs the first miracle. Labour is expected to perform the second.
2. A Commitment Is Often an Ambush
Your manager may persuade you to commit to an impossible deadline. He cannot persuade time to cooperate.
Most commitments are not freely made. They are extracted in meetings. “Can we all agree?” “Can I take that as a yes?” “Is there any reason we cannot deliver this?”
The wise employee knows that the last question is not an invitation to reason. It is a test of loyalty.
Once you agree, the deadline becomes your moral obligation. The assumptions on which it was based quietly disappear.
Corporate life has perfected this transaction: optimism is owned by leadership; consequences are franchised to execution.
3. Every Large Project Is a Small Problem Wearing Ceremonial Clothing
At the centre of every large project is usually a smaller and more ordinary problem trying to escape.
A “digital transformation initiative” may actually mean that customers cannot find products on the website. A “retail excellence programme” may mean that store inventory is inaccurate. A “cultural transformation” may mean that nobody trusts the senior management.
But small problems do not attract large budgets, prestigious consulting firms or launch events. Therefore, they must be dressed.
The problem receives a new name, a strategic framework, a logo and sometimes its own office.
Organisations often enlarge the language because they are unwilling to simplify the work.
4. People Answer Questions, Not Intentions
Your project team and users will tell you everything you ask—but rarely what you needed to know.
Ask whether a new retail application has been installed, and the answer may be yes. Ask whether it works, and the answer may still be yes.
Ask whether anyone uses it, whether the data is accurate and whether store staff secretly maintain handwritten records behind the counter, and the discussion becomes more spiritual.
People do not always conceal the truth. Often, they merely ration it.
The quality of information depends on the courage of the questioner. Vague questions produce comfortable answers. Precise questions disturb the furniture.
5. What You Do Not Know Is Already Working Against You
Every project contains visible risks and invisible certainties.
The risk register lists what the team has imagined. The real trouble often comes from what nobody considered important enough to mention.
An unavailable approval. An undocumented dependency. An employee who alone understands the old system and has resigned. A vendor who interpreted “customised” differently.
Ignorance is not empty space. It is an active participant in the project.
What you do not know does not wait politely to be discovered. It matures quietly and introduces itself near the deadline.
6. There Is Never Time to Think, but Always Time to Repair
Organisations rarely have time to do things correctly. They possess unlimited time to repair the consequences.
Planning is treated as delay. Rework is treated as commitment.
A manager may reject two additional weeks for testing and later approve six months of emergency correction. The first request appears cautious. The second appears heroic.
This is because prevention is invisible.
Nobody receives applause for a crisis that never occurred. But the person who works through the night fixing a crisis may be celebrated for dedication—even if the crisis was created by refusing to listen to him earlier.
Corporate culture often rewards the firefighter and ignores the person who requested a fire extinguisher.
7. Quality Remembers What Deadlines Forget
The sweetness of meeting a deadline is temporary. The bitterness of poor quality develops institutional memory.
Customers do not admire a product because it was launched on schedule. They expect it to work.
A retailer may open a new store exactly on the promised date, with balloons, music and smiling executives. But if the billing counters fail, the stock is incomplete and the staff are untrained, the customer does not experience punctuality. He experiences incompetence with decorations.
A deadline pleases the organisation for a day.
Quality—or its absence—remains with the customer much longer.
8. Communication Is the Art of Producing Multiple Truths
“I know that you believe you understand what you think I said, but I am not sure you realise that what you heard is not what I meant.”
This sentence is not absurd. It is the official language of project confusion.
Communication does not fail only because people speak poorly. It fails because people listen strategically.
The sponsor hears reassurance. The finance team hears cost. The technology team hears scope. The user hears inconvenience. The project manager hears an approaching migraine.
Everyone attends the same meeting and leaves with a different project.
Later, minutes are circulated to prove that alignment occurred.
9. What Is Not Written Will Be Rewritten
Human memory is flexible in ordinary life. Under pressure, it becomes an accomplished lawyer.
Verbal agreements flourish during optimism and vanish during investigation.
“Yes, we discussed it.” “No, I never approved it.” “That was only a preliminary thought.” “You misunderstood the context.”
The sentence “As discussed” has prevented more organisational amnesia than most knowledge-management systems.
Writing is not bureaucracy when accountability matters. It is protection against retrospective imagination.
In projects, history belongs to the person who has the email.
10. Calmness May Be a Data Problem
If everyone around you is panicking and you remain completely calm, two possibilities exist.
You possess extraordinary wisdom. Or you have not opened the latest project report.
Calmness is praised as leadership, but uninformed calmness is merely ignorance with good posture.
Before congratulating yourself on emotional balance, confirm that you understand the dependencies, costs, delays and unresolved decisions.
Peace of mind is admirable. Peace caused by outdated information is a temporary condition.
11. Failure Must Be Rebranded Before It Is Discussed
A team leader must protect his brand.
Therefore, if at first you do not succeed, never call it failure. Call it learning, experimentation, recalibration or phase-one discovery.
Modern organisations do not bury failure. They promote it into vocabulary. A missed target becomes a “revised strategic ambition.” A failed system becomes a “valuable pilot.” A project cancellation becomes “capital reallocation.”
Nothing has gone wrong. Reality has merely provided feedback.
The language grows more sophisticated as the result becomes more embarrassing.
12. Luck Is Planning Observed from a Distance
Organisations often believe there are no good project managers—only lucky ones.
This is partly because competent project management is mostly invisible. Risks are anticipated, decisions are clarified and problems are resolved before senior leadership notices them.
When nothing dramatic happens, people assume the project was easy. When disaster is avoided, nobody celebrates the absence of disaster.
Good planning therefore appears as luck, while bad planning often appears as heroic crisis management.
The more you prepare, the luckier others believe you are.
Still, including your favourable planetary alignment in the project charter may satisfy those stakeholders who consider data unnecessarily restrictive.
13. A Green Dashboard Can Hide a Red Reality
If everything is progressing exactly according to plan, examine the plan—or the person reporting it.
Projects rarely remain perfectly green. Human beings, however, become highly skilled at selecting the shade of green most acceptable to management.
Dashboards are not always designed to reveal reality. Sometimes they are designed to regulate executive emotion.
At a previous organisation, I observed how incentives encouraged people to improve the appearance of the plan rather than the project itself. The hole in execution became increasingly elegant. Unfortunately, the project manager did not know that the hole existed.
The presentation succeeded. The project merely failed behind it.
14. The Sponsor Takes a Step; the Manager Crosses an Ocean
A project is one small decision for the sponsor and one long migration for the project manager.
The sponsor approves the vision. The project manager inherits the vendors, budgets, disagreements, resource gaps, technical limitations and colleagues who are “fully supportive” but unavailable.
The sponsor requests updates. The project manager becomes the update.
Every ambitious declaration creates someone else’s operational burden. This is why overruns are often as predictable as death and taxes, though taxes generally have clearer rules.
15. Overtime Is an Organisational Myth
New project managers soon learn that overtime is not considered real time.
It is treated as a mystical reserve hidden inside employees.
A project may be under-resourced by thirty percent, but management assumes the gap can be recovered through passion, ownership and food delivered after 9 p.m.
When personal sacrifice becomes routine, poor planning is disguised as commitment.
The employee who objects may be called inflexible.
The organisation that repeatedly depends on exhaustion is still described as agile.
16. Fast, Cheap and Good: Choose Two, Demand Three
The ancient project equation remains undefeated:
Fast. Cheap. Good. Choose any two.
Management will choose all three.
It will then ask the team to challenge traditional thinking.
Metrics will be introduced to prove that the triangle has been overcome. Consultants may rename the corners. A dashboard may show arrows. Yet the universe remains uncooperative.
Quantitative management is valuable, but numbers do not abolish trade-offs. They merely make denial more presentable.
17. Long Projects Eventually Become Belief Systems
A two-year project may take three years. A three-year project may outlive some of its original sponsors.
As projects lengthen, the original purpose becomes increasingly difficult to remember. New people join. Old people leave. Assumptions become traditions. Meetings multiply.
Eventually, managing the project becomes a separate project. A programme office is created. A governance committee is added. A consultant is appointed to explain why the governance committee requires restructuring.
The project no longer moves toward completion. It develops civilisation.
18. A Project Becomes Late One Innocent Day at a Time
Warning: dates in a calendar are closer than they appear.
A project does not wake up one morning and discover that it is a year late. It becomes late gradually, through respectable daily decisions.
One approval is postponed. One issue is deferred. One dependency is assumed. One meeting is rescheduled.
Every delay appears harmless when viewed alone. Together, they become strategy.
The future rarely collapses dramatically. It is usually spent in small instalments.
19. Many Projects Depend on Controlled Disclosure
Some projects would never be approved if the full truth about cost, complexity and time were stated at the beginning.
Therefore, uncertainty must be edited. Estimates become commitments. Risks become manageable concerns. Dependencies become assumptions. Hope becomes methodology.
The project is declared viable because nobody has yet provided sufficient detail to prove otherwise.
If you are six months late on a milestone due next week and still believe you can achieve it, you may be a brilliant project manager.
You may also be suffering from institutional optimism, a condition for which organisations usually prescribe another review meeting.
20. Change Continues Until Time Forbids It
Anything that can be changed will be changed until there is no time left to change anything.
Stakeholders who ignored the project for months will arrive near completion with “one small suggestion.”
The suggestion will affect design, technology, training, inventory, cost and launch. It will still be described as small.
No project is ever completed exactly on time, within budget and perfectly to requirement. The first plan was based on assumptions. The final result is based on survival.
The sooner you fall behind schedule, the more time you have to explain how you will recover.
The Project Beneath the Project
The deepest problem in project management is not scheduling. It is truth.
Can people speak honestly about what is possible? Can leaders distinguish ambition from fantasy? Can teams admit uncertainty without appearing weak? Can organisations accept that every choice has a cost?
Projects fail long before the deadline. They fail when inconvenient information is softened, when silence is mistaken for agreement, when enthusiasm replaces capability and when status becomes more important than reality.
The same behaviour appears outside business.
In families, friendships and society, we make promises before understanding the effort involved. We postpone difficult conversations. We hear what comforts us. We preserve our image long after the facts have changed.
Project management is therefore not only about managing work. It is about managing the human desire to appear certain in an uncertain world.
The project manager stands at the border between aspiration and consequence. His task is not to eliminate chaos. It is to stop everyone else from pretending that chaos does not exist.
Do these twenty reflections feel familiar? Then you are certainly a project-management professional.
Or perhaps you are simply an observant human being who has watched a group of intelligent adults convert an avoidable problem into a steering committee.
