Run

One project, one place

The charter, the plan, the data, the documents and the discussion, kept together and ending in something you can hand to somebody.

Book a demo →
5
tollgates
one per phase
14
templates
available to the project
8
surfaces
charter through dossier
1
dossier PDF
when it closes

What a project holds

Everything the work produced, attached to the work

Improvement projects usually scatter: a charter in a shared drive, data in a spreadsheet, the decision in an email. The workspace exists so the record of a project is the project.

Charter

The problem, the goal, the scope and the business case, approved before data is touched.

Phase plan

Dates per phase, so time in phase can be measured against something rather than described afterwards.

Task board

Who is doing what, and what is blocked, inside the project rather than in a separate tool.

Process steps

The process as the team actually mapped it, kept with the project it belongs to.

Collection sheet

A shared sheet for the data the team is gathering, so the numbers and the analysis stay together.

Deliverables

The documents the phase produced, versioned, with an approved one staying in force until a change is accepted.

Comments

The discussion attached to the artefact it is about, not in a thread somebody has to go and find.

Dossier PDF

The whole project as one document when it closes.

The five phases

Each phase has a job, and a gate at the end of it

The workspace carries the objective for the phase the project is in, so the team is working to a stated purpose rather than to a folder name.

Define

Frame the problem, the goal, the scope, and who the customer is — so everyone agrees on what "done" means before any data is touched.

Measure

Baseline how the process performs today with trustworthy data — you can only improve what you can measure.

Analyze

Find and verify the true root causes of the problem — with evidence, not opinion.

Improve

Design, pilot, and prove solutions that address the verified root causes.

Control

Lock in the gains so the problem stays fixed after the team moves on.

How a project moves

Forward is a decision somebody made

A project does not advance because a date passed. It advances when a gate is approved by someone who did not submit it, and that approval is recorded.

  1. 01

    Chartered

    Scope, goal and sponsor agreed.

  2. 02

    Worked

    Tasks, data and deliverables in the phase.

  3. 03

    Submitted

    The team puts the gate up for review.

  4. 04

    Reviewed

    Approved or sent back, by somebody else.

  5. 05

    Advanced

    The phase clock restarts and the record keeps it.

Document control

A change waits for acceptance

When somebody revises an approved deliverable, the approved version keeps serving until an approver accepts the new one. Nobody finds out their standard work changed by noticing the line is doing something different.

Everything lands in the audit log

Gate approvals, benefit validations and accepted revisions are recorded in a log the customer can read, which is what turns a project record into evidence.

See it run with your own team

Bring the process you use today. Thirty minutes is enough to see it as a governed project with the decisions recorded.

Book a demo →

How SigmaForge governs the work →