SigmaForge
Projects

Run the whole improvement project in one workspace

From the charter to the sign-off page, with every chart and document kept in the record.

5
tollgates
one per phase
14
templates
saved as deliverables
32
analyses
saved to the phase
13
agents
working in the project
An enterprise project workspace in the Improve phase: DMAIC gates across the top, phase tools, the team task board, deliverables, the tollgate and an AI phase summary.
Product screen, demo data

Five phases, five gates

The same method on every project.

Each phase has an objective, the tools that fit it, and a gate that checks three things before the project moves on. This is the guide the team sees inside the workspace.
  1. Phase 01

    Define

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

    Project charter · SIPOC · CTQ tree · Business case

  2. Phase 02

    Measure

    Baseline how the process performs today, on data you can trust.

    Process capability · Gage R&R · Data collection plan · Sample size

  3. Phase 03

    Analyze

    Find the root causes and prove them with evidence, not opinion.

    Pareto · Fishbone and 5 Whys · ANOVA and regression · Hypothesis tests

  4. Phase 04

    Improve

    Design, pilot and prove the fix for the causes you verified.

    Design of experiments · Poka-Yoke and 5S · Impact against effort · Before and after test

  5. Phase 05

    Control

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

    Control chart · Control plan · Realized savings · Standard work

  • Define gate

    • Charter approved by the sponsor
    • Problem and goal are measurable
    • Scope and team agreed
  • Measure gate

    • Measurement system validated
    • Baseline capability established
    • Data plan followed
  • Analyze gate

    • Root causes identified
    • Verified with data
    • Vital few prioritized
  • Improve gate

    • Solution piloted
    • Improvement shown with data
    • Risks and FMEA addressed
  • Control gate

    • Control plan in place
    • Process owner signed off
    • Realized savings recorded

One project, on video · 1:42

Watch a real project run, phase by phase.

Server mainboards failing burn-in at 3.6% against a 1.2% target. The idea is chartered, DataForge finds where the loss sits, DocuForge writes the control plan, ProjectSensei names the one thing blocking the gate, and CollabForge writes the retrospective.

One project record. Enter it once, and every tool knows it.

More videos for project teams
Run a real project1:42 · Captions

The workspace

Everything about the project, on one screen.

The gates run across the top. Under them sit the tools this phase needs, the team’s tasks, the deliverables so far, the tollgate and a written summary of where the phase stands.

  • Charter, phase plan and process steps
  • A shared collection sheet for the team’s measurements
  • A dossier PDF of the whole project, whenever you need one
sigmaforge.ai/projects
An enterprise project workspace in the Improve phase: DMAIC gates across the top, phase tools, the team task board, deliverables, the tollgate and an AI phase summary.
  1. 1The gate stripApproved, in review or upcoming, per phase.
  2. 2Tools for this phaseOne click to open each one.
  3. 3DeliverablesSaved outputs count as gate evidence.
  4. 4Phase summaryWhat happened, what was found, what is still open.
Product screen, demo data

The team

Who is doing what, inside the project.

Every task lives in the project it belongs to, not in a separate tracker. Give it to someone, set a date, and move it across as it progresses. Filter by phase or by lane to see one piece of the work at a time.

  • Tasks by phase and by lane
  • An owner, a status and a due date on each
  • Coaching next steps added as tasks in one click
sigmaforge.ai/projects
The task board inside a project: work filtered by phase and lane, each item assigned to a person with a status and a due date.
Product screen, demo dataThe task board inside a project

The record

Deliverables, the team and the conversation, together.

The phase’s deliverables sit beside the people on the project and the discussion about them. The activity feed records who commented on what and when, so a decision has its reasons next to it.

sigmaforge.ai/projects
Project deliverables beside the team and the activity feed, recording who commented on what and when.
Product screen, demo dataDeliverables beside the team and the activity feed

The tollgate

Nobody approves their own gate

The person who submits a tollgate cannot be the person who approves it. The system refuses, rather than trusting the org chart.

The gate shows the evidence it expects and the artifacts attached against it. When it is approved, the approval is written to the audit log with who made it and when.

  • Evidence expected, and how much is attached
  • Submitted, awaiting review, approved
  • Every approval in the audit log
How governance works
sigmaforge.ai/projects
The Improve tollgate awaiting review with four of four artifacts attached, beside the phase deliverables and the DMAIC gate strip.
  1. 1Improve, in reviewDefine, Measure and Analyze already approved.
  2. 2Four of four artifactsThe evidence the gate asked for.
  3. 3Awaiting reviewBy a manager who did not submit it.
Product screen, demo data

ProjectSensei

A coach that has read the project.

Phase coaching reads the project’s own deliverables and numbers, says how ready the phase is, and names the one thing blocking it. It is advisory: the team decides what to act on.

  • How ready the phase is, as a percentage
  • The one thing blocking the gate
  • Evidence attached and evidence missing
  • What the numbers say today
See ProjectSensei
sigmaforge.ai/projects
Phase coaching for an enterprise project: readiness, the one thing blocking the phase, gate evidence attached and missing, and the numbers that decide it.
Product screen, demo dataPhase coaching on the Improve phase

Sign-off

Closed, with savings somebody else validated.

Estimated, actual and validated are separate fields. Only an owner or admin can validate, only after the project is complete, and never the person who ran it.

  • All five gates approved
  • Estimated, actual and validated savings
  • The deliverables from every phase, kept
sigmaforge.ai/projects
A completed project: all five DMAIC gates approved, savings validated at sign-off, the deliverables from every phase, and the team.
Product screen, demo dataA completed project

DocuForge

The documents each phase asks for.

Start from a short brief and get back a document saved into the project. 14 templates, filed by the phase they belong to; 8 of them produce a diagram as well.

Define

  • Project CharterWhite Belt
  • SIPOCWhite Belt · diagram
  • CTQ TreeWhite Belt · diagram
  • Stakeholder MatrixWhite Belt · diagram

Measure

  • Data Collection PlanYellow Belt
  • Gage R&R PlanGreen Belt

Analyze

  • A3Yellow Belt
  • FMEAGreen Belt · diagram
  • Hypothesis Test PlanGreen Belt

Improve

  • Pilot PlanGreen Belt · diagram
  • DOE PlanBlack Belt · diagram

Control

  • Control PlanGreen Belt
  • Standard Work / SOPGreen Belt · diagram
  • OCAPBlack Belt · diagram
sigmaforge.ai/docuforge
The DocuForge template board: fourteen templates arranged by DMAIC phase, each with its belt level, and the four steps from template to branded PDF.
Product screen, demo dataThe template board, arranged by DMAIC phase

The film · 3:27

One project, from the idea to the sign-off.

The demo company from the screens on this page, end to end: an idea scored in the hopper, worked in the workspace, decided at a tollgate and closed with validated savings.

SigmaForge for Enterprise3:27 · Captions

Thirty minutes

Walk one of your projects through the gates.

Bring a project you are running now. We will set it up in the workspace with you and show where each deliverable lands.