This is a sample report for a fictional organisation (Fictional regional bank). Your report is written from your own answers.
Take the assessmentLean Six Sigma Programme Health Check
Sample report: Lean Six Sigma Programme Health Check
Completed 21 November 2026
Overall score
Emerging
Your Lean Six Sigma programme is currently an expensive hobby for belts that fails to deliver credible financial impact, requiring immediate pivot from ad-hoc projects to business-integrated value delivery.
Scorecard
Your score by area
Each area is scored from your answers. A weakness in one area holds back the others.
Red flags
Answers that need urgent attention (3)
These answers sit at the weakest level.
Executive summary
What this means for your organisation
The programme is stagnating at a 37% health score, functioning more as a training initiative than a strategic business lever. While formal structures like steering groups exist, the lack of active executive sponsorship and absence of dedicated capacity for practitioners means the organisation is not capitalising on its existing investment in belts. The current operation produces sporadic results that are disconnected from the bank's core business planning and financial targets.
The core diagnosis is a lack of rigorous, enterprise-wide integration. The absence of a project pipeline means that improvement efforts are reactive rather than proactive, and the lack of independent benefits validation undermines the credibility of the entire initiative with senior management. Because Belts treat projects as an additional burden to their day jobs, progress is slow and the sustainment of improvements is left to chance rather than robust control systems.
To rescue this programme, the bank must first link the improvement agenda to the annual budget and resource allocation. Immediate steps must be taken to formalise benefits validation, transition from a 'belt-led hobby' to a 'business-owned transformation' model, and secure dedicated capacity for top-tier practitioners. Without these changes, the programme will continue to generate local optimisations that fail to move the firm's bottom-line performance.
Key strengths
- Presence of a steering group with established terms of reference
- Formalised project governance through defined tollgates
- Effective foundational training that incorporates live project requirements
- Clear role definitions for the programme infrastructure
Risk register
Critical risks
Ranked by severity, with the business consequence and the recommended mitigation.
Total loss of executive sponsorship and business alignment
Impact
Programme defunding and loss of organisational mandate
Mitigation
Establish a mandatory quarterly review where sponsors must report on value delivered by their specific projects
Financial credibility deficit due to self-reported benefits
Impact
Loss of trust from the Finance department and leadership
Mitigation
Appoint a finance business partner to act as an independent validator for all project savings
Burnout and attrition of skilled practitioners
Impact
Loss of institutional knowledge and ability to execute complex improvements
Mitigation
Negotiate a minimum 20 percent time allocation for Black Belts with their line managers
Sustainability failure leading to process regression
Impact
Reversal of gains and waste of previous transformation effort
Mitigation
Integrate control plan compliance into existing operational audit schedules
Dependencies
How the areas affect each other
- The lack of a project pipeline is directly caused by the absence of active sponsorship, as leaders are not identifying the business problems that need solving.
- Without independent benefits validation, the programme cannot secure the resource allocation required to solve the capacity issue for belts.
- The 'belt-only' culture is a symptom of poor communication from leadership; when the business does not own the project, it remains a peripheral activity for the belt.
Benchmark
Maturity benchmark
Maturity for each area on a five-level scale, compared with typical organisations.
Level 2, Emerging. In typical regional banks, sponsors are actively involved in tollgate reviews rather than just attending steering meetings.
Level 1, Ad hoc. Successful banks maintain a rolling pipeline of 12-18 months of projects aligned to strategic cost-reduction targets.
Level 1, Ad hoc. Top-tier organisations require 50 to 100 percent of a Black Belt's time to be dedicated to improvement work.
Level 3, Defined. Most banks operate at this level, but they often struggle with the transition from data collection to rigorous root cause verification.
Level 1, Ad hoc. Financial validation must involve Finance as a gatekeeper to ensure that project benefits translate to actual budget or capacity releases.
Level 2, Emerging. Mature organisations treat CI as part of the daily management system, not as a project-based intervention.
Momentum
Quick wins
Actions you can take in the next two to four weeks.
Implement a mandatory finance sign-off on all project charters
Improvement Lead · 2 weeks
Increased credibility of reported project savings
Audit current projects and terminate those without clear link to business goals
Steering Group · 3 weeks
Free up capacity for high-value strategic work
Publish a list of 'Stalled Projects' to force sponsorship intervention
Improvement Lead · 4 weeks
Increased visibility of roadblocks and resource constraints
Standardise the project documentation repository
Programme Manager · 4 weeks
Improved knowledge sharing and easier project handover
Diagnosis
Area-by-area diagnosis
01Sponsorship and governance
The governance framework is technically present but functionally inert. While the steering group meets, the absence of active senior leadership turns these meetings into reporting sessions rather than decision-making forums. The programme operates in a silo, disconnected from the broader business strategy and resource planning cycle. This structural weakness prevents the programme from addressing enterprise-level pain points.
Root causes
- • Inadequate definition of 'active sponsorship'
- • Poor alignment between CI and the annual budget cycle
Evidence from your answers
“A senior leader is named but rarely involved”
“It is mentioned in plans but not resourced”
Strengths
- • Formal steering group meeting cadence
- • Clear definition of programme roles
Gaps
- • Lack of executive engagement in project outcomes
- • No resourcing tied to the improvement plan
Actions
- • Re-contract sponsors on their specific accountability for project outcomes
- • Embed CI targets into the senior leadership performance scorecards
- • Integrate project demand into the annual budgeting cycle
02Project selection and pipeline
The programme lacks a deliberate strategy for selection, resulting in opportunistic rather than value-driven work. There is no active pipeline, which means belts often search for problems rather than solving the most urgent business issues. Projects are often scoped well individually, but they fail to cumulatively impact the bank's bottom line because they are not prioritised strategically.
Root causes
- • Absence of a strategic alignment framework for project selection
- • Lack of senior management input into the priority list
Evidence from your answers
“From a list, with little screening”
“There is no pipeline”
Strengths
- • Clear project charter format
Gaps
- • No proactive pipeline management
- • Low-rigour screening process for incoming projects
Actions
- • Establish a quarterly project prioritisation session with senior leadership
- • Develop a strategic alignment matrix to score project proposals
- • Create a visual pipeline dashboard to track project health and timing
03Belt capability and roles
Practitioners are currently set up to fail. Requiring belts to balance transformation work on top of a full-time job ensures that projects will always be slow and quality will suffer. The lack of formal, protected time indicates that the organisation views Lean Six Sigma as a secondary skill rather than a primary vehicle for transformation.
Root causes
- • Line management pressure to prioritise core operational tasks over improvement
- • Lack of clear career pathing for certified practitioners
Evidence from your answers
“None; projects sit on top of the day job”
“Informal help from colleagues”
Strengths
- • Training includes practical application on live projects
Gaps
- • No dedicated project time
- • Weak support system for belt development post-certification
Actions
- • Define and enforce minimum time allocations for belts based on certification level
- • Formalise a coaching rhythm between senior belts and practitioners
- • Link project success to professional development goals for belts
04Method and project quality
The method is correctly taught and applied, but the rigour is often lost in execution. Projects follow the DMAIC structure, yet they often fail to move beyond data observation into verifiable root cause analysis. While tollgates are formal, they appear to be a check-box exercise rather than a meaningful barrier to poor-quality work.
Root causes
- • Over-reliance on qualitative observations rather than statistical verification
- • Fragmented documentation hindering peer review
Evidence from your answers
“On most projects”
“With some data, but rarely verified”
“Each belt keeps it in their own files”
Strengths
- • Consistency in tollgate execution
- • General adherence to the DMAIC framework
Gaps
- • Lack of formalised root cause verification
- • Decentralised project documentation
Actions
- • Mandate statistical verification of root causes in the 'Analyse' phase
- • Implement a shared project management and document repository
- • Introduce a 'peer review' step before formal tollgate meetings
05Benefits and financial validation
This is the most critical failure point in the programme. When belts report their own benefits without external validation, the credibility of the entire programme is compromised. The failure to track results post-project means that the organisation is unable to confirm if the gains are real or if they have dissipated after closure.
Root causes
- • Lack of collaboration between the improvement office and Finance
- • Absence of a standardised benefits tracking tool
Evidence from your answers
“With rough guesses at the start”
“The belt reports their own benefits”
“No”
Strengths
- • None
- • Occasional success stories used for visibility
Gaps
- • Self-reported benefits bias
- • Zero post-closure benefit tracking
Actions
- • Create a finance-approved benefit calculation template
- • Require a sign-off from the budget holder for all claimed benefits
- • Establish a post-project review process at 3, 6, and 12 months
06Sustainment and culture
The programme is perceived as a niche activity for specialists, which limits its cultural impact. Improvements are not locked into the management system, leading to a high rate of regression. Because the programme has not evolved in years, it is viewed as stagnant rather than a dynamic source of innovation for the bank.
Root causes
- • Lack of engagement with operational leaders to integrate control plans into business-as-usual
- • Failure to communicate success beyond project completion
Evidence from your answers
“As something only belts do”
“It runs, but has not changed in years”
Strengths
- • Occasional reuse of solutions through informal networks
Gaps
- • Weak sustainment mechanisms
- • Lack of programme evolution
Actions
- • Build standard work audit routines for process owners
- • Develop an annual programme improvement roadmap
- • Create a 'Community of Practice' to share solutions formally
Measures
KPIs to track
Measures that show whether things are improving.
Realised financial savings vs. initial estimates
Benefits and financial validationDetermines the accuracy of project forecasting and budget impact.
Target: Within 10% of forecast by end of next quarter
Percentage of projects with Finance-validated benefits
Benefits and financial validationRestores the credibility of the programme with leadership.
Target: 100% within 2 months
Belt utilisation rate (hours on projects vs. BAU)
Belt capability and rolesTracks whether belts are being given the time to succeed.
Target: 20% minimum
Project cycle time variance
Method and project qualityIndicates whether projects are being adequately resourced and managed.
Target: Reduction by 20% in 90 days
Percentage of projects sustaining gains at 6 months
Sustainment and cultureProves the efficacy of control plans.
Target: 80% success rate
Roadmap
Your 90-day plan
Sequenced to fix the weakest foundations first.
Days 0 to 30
Stabilise
- Finalise finance-approved benefit calculation templates.
- Audit all active projects for strategic alignment and kill non-performers.
- Formally brief sponsors on their required accountability levels.
- Establish a central digital documentation repository.
Days 31 to 60
Build
- Implement the 20% capacity rule for Black Belts with line managers.
- Roll out the new Finance-led validation process for all project charters.
- Launch a quarterly pipeline review session with the leadership team.
Days 61 to 90
Embed
- Conduct post-project audits on completed work from the last 12 months.
- Integrate control plan audits into line management standard work.
- Launch the CI Community of Practice for formal knowledge sharing.
For leadership
Questions your leadership team must answer
- 01Are you prepared to link project outcomes to your own performance bonus?
- 02Will you hold your direct reports accountable for participating in improvement projects?
- 03Are you willing to release capacity from your team for these projects, or is this just another 'off-the-side-of-the-desk' activity?
- 04How will you measure the success of this programme in terms of profit or efficiency rather than just the number of belts trained?
- 05What specific business problem will this programme solve for you in the next quarter?
Next steps
How Lean 6 Sigma Hub can help
The services that best fit the gaps in your results.
Operational excellence maturity assessment
This will provide an independent baseline and high-level buy-in for the necessary transformation of the current programme.
Learn moreCI Flow implementation
This will address the lack of project pipeline visibility and the weak benefits tracking by implementing a formal portfolio platform.
Learn moreWant to talk through your results?
Book a free discovery conversation. We will walk through your report and agree the best next step.
This report is generated from your own answers with the help of AI. It is a starting point for discussion, not a formal audit or professional advice.
