Simple Solution, Low Maintenance
Practical Project Management for PMs & PMOs
Practical Project Management for PMs & PMOs
Start your first project
Guidance, templates & governance in one place
A short set of practical tools that make the fundamentals work in the real world — deciding under pressure, managing the people around a project, writing so people actually read you, and growing as a project manager.
You make dozens of calls a day with incomplete information and no time to model each one. Heuristics — practical rules of thumb built from experience — are how you decide quickly and sensibly anyway. Here is a working set worth knowing, with the SSLM principle each one leans on. Apply them with judgement, not as laws.
Shortcuts for the calls you make every day. Most are already baked into an SSLM tool.
| Heuristic | What it means in practice | Aligns to |
|---|---|---|
| 80/20 (Pareto) | A small share of causes drives most results. Find the vital few and put your effort there first — fix the handful of risks behind most of the schedule threat. | Prioritise |
| Add a contingency buffer | First-cut estimates are optimistic. Add a margin — often 15–25% — before you commit to a date or budget. | Report the real colour |
| Analogous estimating | Use a similar past project as your starting yardstick, then adjust for what's genuinely different this time. | Learn and improve |
| Three-point estimate | Blend best, most likely and worst case — (O + 4M + P) ÷ 6 — instead of a single hopeful number. | Report the real colour |
| Focus on the critical path | Watch the chain of tasks that sets the finish date; a slip there slips the whole project. | Plan to the critical path |
| MoSCoW | Sort scope into Must, Should, Could and Won't so the essentials are protected when time runs short. | Prioritise |
| Escalate early | Bad news doesn't improve with age. Raise issues while they're small and cheap to fix. | Report the real colour |
| Under-promise, over-deliver | Commit to what you're confident of and aim to beat it. Trust compounds. | Report the real colour |
| One-way vs two-way doors | Decide reversible choices fast; slow down only for the ones you can't undo. | Right-size governance |
| Ignore sunk costs | Money and effort already spent are gone. Judge only on the value still ahead. | Willingness to stop |
| Run a pre-mortem | Before you commit, ask the team to imagine the project has failed and say why. It surfaces the quiet risks. | Report the real colour |
| Timebox the work (Parkinson's Law) | Work expands to fill the time allowed, so set a deadline or a timebox and hold it. | Plan to the critical path |
| Brooks's Law | Adding people to a late project usually makes it later. Protect the plan; don't just throw bodies at a slip. | Capable to deliver |
Bent Flyvbjerg — who has spent his career studying why big projects succeed or fail — distilled eleven rules of thumb from expert “masterbuilders.” They scale down to a first project as neatly as they scale up to a mega-project. (the research)
| Heuristic | What it means in practice | Aligns to |
|---|---|---|
| Think slow, act fast | Plan slowly and carefully, then deliver fast. A long, cheap planning phase is the safest place to make your mistakes. | Plan to the critical path |
| Take the outside view | Forecast from how comparable past projects actually turned out, not from your own plan. Your project is less unique than it feels. | Learn and improve |
| Hire a masterbuilder | Put someone with a proven track record in this kind of project in charge. Relevant experience is the best predictor of success. | Capable to deliver |
| Get your team right | A tried and tested team beats a group of talented strangers. Bring people who have delivered together before. | Capable to deliver |
| Ask “why?” | Fix the real purpose and the outcome before you touch the how. Build to the goal, not the assumed solution. | Anchor to purpose |
| Build with Lego | Assemble big things from small, repeatable modules you can build and test one at a time. | Compose from standard blocks |
| Watch your downside | Give the risks as much attention as the benefits. Protect against the few failures that could sink the whole project. | Willingness to stop |
| Say no and walk away | Decline projects and changes when the risk is too high or the resources aren't there. | Clear accountability & authority |
| Make friends and keep them friendly | Build and hold good relationships with the people who could help — or derail — the project. | Clear accountability & authority |
| Build climate mitigation in | Design for the long term and the project's wider footprint, not only today's deliverable. | Anchor to purpose |
| Know that your biggest risk is you | Your own optimism and bias are the most common cause of failure. Plan against yourself. | Report the real colour |
The flip side of good judgement is knowing how it goes wrong. Flyvbjerg also catalogued the ten biases that most distort project decisions. Each maps to the SSLM principle that guards against it. (the research)
| Bias | What it does | SSLM principle | The guard in practice |
|---|---|---|---|
| Strategic misrepresentation | Costs and timelines are understated on purpose to get a project approved — the most damaging bias because it's deliberate. | Report the real colour | A transparent Business Case and independent assurance; every number traces to a named owner. |
| Optimism bias | Genuine belief that things will go better than the evidence says they usually do. | Report the real colour | Contingency buffers, the outside view, and an assurance re-test before commitment. |
| Uniqueness bias | “Our project is different” — so relevant lessons from similar projects get ignored. | Learn and improve | Take the outside view — compare to comparable past projects, not the inside story. |
| Planning fallacy | Underestimating how long tasks take, even when you know similar work ran longer. | Plan to the critical path | Analogous and three-point estimating, with a buffer, on a critical-path plan. |
| Overconfidence bias | Too much faith in your team's ability to predict and control outcomes. | Report the real colour | The pre-mortem and an independent assurance challenge at each stage gate. |
| Hindsight bias | After the fact, failures look as if they were obvious — so the wrong lessons get drawn. | Learn and improve | Lessons Learned logged as you go, not rationalised at closure. |
| Availability bias | Recent or vivid events feel more likely than they are. | Learn and improve | Base rates and the outside view, not the last thing that went wrong. |
| Base rate fallacy | Ignoring how the whole class of similar projects turned out, in favour of your own case detail. | Learn and improve | Reference-class forecasting — start from the base rates of comparable projects. |
| Anchoring | The first number mentioned drags every later estimate toward it. | Report the real colour | Estimate from the analogous basis first, then debate the gap. |
| Escalation of commitment | Pouring more into a failing project because of what's already been spent. | Willingness to stop | Stage-gate re-tests judge on the value still ahead, not the sunk cost. |
SSLM is itself a heuristic: least-sufficient governance, depth only on a real trigger, good enough over gold-plated. The framework sets the stance; these rules of thumb make the countless in-the-moment calls the templates never decide.
You'll be accountable for outcomes long before you have authority over everyone who delivers them. Relationship management is how you get things done anyway: authority gets compliance; relationships get commitment — and only commitment makes a change stick. It is the human skill behind SSLM's stakeholder and communication tools.
SSLM gives you one accountable owner per project (Principle 1) — but rarely full command over the people doing the work. They usually report elsewhere. So you lead by influence, evidence and trust, not by position. It's not “being nice” or networking, and it's never manipulation: it's purposeful, honest, two-way work that only holds if it's genuine.
Know your subject (credibility), do what you said (reliability), make people feel safe to be honest (closeness) — and visibly serve the purpose over yourself (low self-interest). In SSLM: credibility is “report the real colour”; reliability is keeping the reporting cadence and small promises; low self-interest is “anchor to purpose”.
The human side of SSLM's Stakeholder & Communication Plan: decide who needs how much attention, then set the rhythm.
The ten relationship-management principles and SSLM's own principles come from the same place — serve the purpose, tell the truth, earn trust.
| Relationship principle | Aligning SSLM principle | How they reinforce |
|---|---|---|
| Trust is the foundation | Clear accountability & authority · Capable to deliver | SSLM names one owner but rarely gives authority over the people; trust is what lets that owner move work they cannot command. |
| Influence without authority | Clear accountability & authority · Plan to the critical path | Accountability without command means you persuade with evidence — the plan and critical path are the neutral, factual case. |
| Seek mutual value (win–win) | Anchor to purpose · Prioritise | Framing every ask so the other function also gains ties it to the shared purpose, not to one party's turf. |
| Be transparent and honest | Report the real colour | Both demand the real picture including bad news — “an amber that's really red” is exactly the behaviour transparency requires. |
| Listen with empathy | Fit for purpose · Right-size governance | Understanding each function's real pressures is how you judge what's genuinely “good enough” and how much process they need. |
| Be reliable — keep small promises | Capable to deliver · Learn and improve | Reliability compounds like a delivery track record; small promises kept and lessons fed back are proven capability, day to day. |
| Predictable cadence | Narrative flow & roll-up | SSLM's single weekly report sets the rhythm; predictable, expected contact keeps relationships warm on that same beat. |
| Respect each perspective | Prioritise · Anchor to purpose | Every function sees the work differently; respecting those views lets priorities be set on purpose and capacity, not territory. |
| Manage conflict constructively | Willingness to stop · Plan to the critical path | Surfacing disagreement early and making it about the process, not the person, uses the plan as neutral ground. |
| Stay customer-centric | Anchor to purpose | The end customer's value is the shared, neutral goal that outranks turf — the human form of SSLM's umbrella principle. |
SSLM's tools give you the structure — who to involve, what to report, the cadence and the forums. Relationship management is what turns that structure into commitment.
| SSLM instrument | What it provides (the structure) | The behaviour it supports |
|---|---|---|
| Stakeholder & Comms Plan | Places each stakeholder on the grid; records who hears what, how often, in what format. | Map stakeholders, set a rhythm, invest before you withdraw |
| RACI (Responsible, Accountable, Consulted, Informed) | Names who is Responsible, Accountable, Consulted, Informed — one accountable per activity. | Role clarity that defuses conflict; clear hand-offs |
| Meeting Playbook | Fit-for-purpose meetings — the right people, prepared, on a predictable cadence. | Warm, expected contact; “go and see” the work |
| Weekly Update & RAG (Red, Amber, Green)-Trend | An honest status on a fixed cadence — report red early, no surprises. | Be transparent; reliability that builds the trust balance |
| RAID — Issues & Dependencies | Every issue and dependency logged and linked to a milestone. | Surface and resolve conflict early — about the process, not the person |
| Anchor to purpose | Every step and meeting must serve the purpose and the customer. | Stay customer-centric — the neutral goal that outranks turf |
The practical detail, in SSLM terms.
The Board / SteerCo and sponsor (keep satisfied), the function heads whose people do the work (manage closely), frontline operators (keep informed — their input is gold), support functions, and customers & suppliers. Prioritise them with the power / interest grid.
Expectations, trust and goodwill, communication, dependencies and hand-offs, and competing priorities — each held by an SSLM artefact (the Stakeholder & Comms Plan, RACI, and the RAID log). Your job is keeping each one truthful and current.
Map stakeholders, learn each one's goals and pressures, build the relationship in good times, set a rhythm, make every request win–win, follow through visibly, and handle conflict early through the RAID log — never as blame.
Before you need anything, and on SSLM's fixed cadence (weekly, monthly, SteerCo) so contact is predictable — not a scramble at the point of need. Especially before change, at moments of tension, and at milestones.
At the work itself — “go and see” surfaces real issues far better than a meeting room — plus SSLM's formal forums (SteerCo, planning), the informal settings where trust builds fastest, and deliberately across sites and remotely.
Blockers clear faster, change sticks, you get early warning, silos break, and improvement compounds. In SSLM terms, honest roll-up reporting only works if each layer trusts the one below — and that trust is built by relationships, not the template.
Most project communication buries the point. The Pyramid Principle — set out by Barbara Minto at McKinsey — flips that: lead with the answer, then group the reasons that support it. For a project manager writing to busy sponsors and steering committees, it is the single fastest way to be understood.
Start with the conclusion. Then give the handful of reasons that support it, grouped so they don't overlap and together cover the point. Each reason can, if it needs to, be backed by its own facts one level down. The reader gets your message in the first sentence and reads on only for the detail they actually want.
A sponsor reads the first line of your update and often no further. If that line is “we remain on track for the March go-live, with one risk being managed”, they have what they need. If it is three paragraphs of activity that slowly build to the point, they have to do the work you should have done for them — and busy people simply stop reading.
Buried: “The vendor was late returning the test environment, and two testers were on leave, and the integration defect took longer than expected, so testing has slipped by a week.”
Pyramid: “Testing has slipped one week; go-live is unaffected. Three things caused it: a late test environment, two testers on leave, and one integration defect. I have reordered the plan to protect the go-live date.”
SSLM already reports this way. The Weekly Update leads with a RAG status and trend, not a narrative; the SteerCo pack opens with the decisions needed, not the background. Write every update, email and paper answer first, and your reporting and your framework pull in the same direction.
The Dunning-Kruger effect is the popular name for a simple, uncomfortable idea: when you know little about something, you often can't see how much you're missing, so you feel more certain than you should. The more you learn, the more you notice what you don't know, and the more measured you become.
Every project asks you to be confident in two areas at once: project management itself, and the domain of the project. You can be strong in one and a beginner in the other. The skill is knowing which is which — where you can trust your own judgement, and where you should ask, listen and check before you commit.
A team wants a project manager who is calm and decisive, so a degree of “act confident and learn the rest as you go” is part of the job. It works only with a matching dose of honesty: back yourself, but stay aware there is more to learn, invite feedback, and find a mentor. Confidence without that awareness is how projects walk off cliffs.
A fair caution on the science: the size of the effect is debated, and some of it is a statistical artefact rather than a real bias. The practical point — match your confidence to your actual knowledge on this project — holds either way.
SSLM builds this in. “Question the Green”: when a status looks fine but a risk or issue says otherwise, distrust the comfortable reading. The framework's honesty checks exist precisely because confident but wrong is the most expensive place a project manager can be.
You don't need any of this yet — but it helps to see where a first project leads. Two things grow together: what you can do, and the scope you can lead.
Think of learning to ride a bike — from a child's first bike to racing the Tour de France. The mechanics of riding never change; both are simply riding a bike. But the context between them is a paradigm shift of skill, discipline and thinking. At first every movement is a conscious effort; with repetition it turns instinctive. At the top, the equipment, training, support teams and competition add a whole new dimension. Project work is the same: the fundamentals become second nature — and leading at scale is a different race.
The fundamentals and principles. A risk is still a risk; a baseline still a baseline. You deepen them until they're instinctive — you don't discard them.
Accountability, power and influence — and the skill mix. The weight moves from tangible, technical skills toward relational, soft ones: influence over control, judgment over process, people and strategy over tasks.
The trap. Under pressure we ride the new race the old way — leading a transformation like a bigger project, reaching for control where only influence works. Growing from visible technical skills to harder-to-see soft skills is the real work of the climb. The idea, and the phrase, come from Marshall Goldsmith's What Got You Here Won't Get You There.
So learn the fundamentals well now — they become the instinct everything above is built on.