Simple Solution, Low Maintenance
Practical Project Management for PMs & PMOs
Start your first project
Guidance, templates & governance in one place
hello@sslmproject.com · 🌐 sslmproject.com
How it works

How a lightweight project management process works

A 60-second animated walkthrough of how a project moves through SSLM — stages, management and governance on one timeline.

The whole model at a glance

The same model, seen all at once

The animation above plays the journey out step by step. This static view shows the same three layers, stages, project management, and reporting and governance, on one timeline. Use it to take in the whole shape at a glance and as a quick reference to come back to.

The SSLM ModelOne project · three connected views on a single timelineStages of a projectPre-approvalGreen LightDeliveryGo-LivePost Go-LiveProject managementPlan · RAID (Risks, Assumptions, Issues, Dependencies) · Change control · SteerCo (Steering Committee)Reporting & governanceWeekly → Monthly → Portfolio roll-up
Understanding the model

How the SSLM model works

The SSLM model is one project seen through three connected views on a single timeline (shown above). The views run together as the project moves left to right, and two threads hold them together. Here is each part, the principle behind it, and the templates you use.

1 · Stages of a project

The lifecycle spine: Pre-approval → Green Light → Delivery → Go-Live → Post Go-Live. The two stage gates (Green Light, Go-Live) are go / hold / stop decisions, not just milestones.

Principle Anchor to purpose; Right-size governance
Templates Idea on a Page, Business Case
2 · Project management

How the work is run: the Plan sets the critical path, the RAID logs are its working memory, a Change Request protects the baseline, and the SteerCo resolves what is beyond the PM.

Principle Plan to the critical path; Clear accountability
Templates Project Plan, RAID & Tracker Logs, Change Request, SteerCo Pack
3 · Reporting & governance

How status flows up: the Weekly Update rolls into the Monthly Report, which rolls up to portfolio or board. Each level synthesises the one below, never repeats it.

Principle Report the real colour; Narrative flow & roll-up
Templates Weekly Update, Monthly Report to BoM
The thread

One Project Reference (an ID like YYYY-NNN) is carried by every document, so the whole story stays traceable end to end. It is what turns a pile of documents into one narrative.

The spine

The Project Plan is the centre. Every other document either informs the Plan (the Business Case) or is informed by it (RAID, Change Requests, reporting). Get the Plan right and the rest follows.

A worked example

Take a customer returns portal. At Green Light the Business Case is approved (Anchor to purpose) and the project is baselined. In Delivery the Project Plan sets the critical path, the RAID log tracks a risky vendor integration, and a Change Request is raised only when scope moves. Each week the PM reports the real colour on a Weekly Update, which rolls into the Monthly Report; the SteerCo clears the blocker at the gate. At Go-Live the deliverables are accepted; at closure the Project Reference retires. Three views, one timeline, one thread.

See the Templates & Guides for every document in the model, and the Principles behind it.

Next: the Templates & Guides give you every document in this flow, or revisit the Principles behind it.

Why SSLM