A company has certified a large group of Green Belts and Black Belts, printed the certificates and held a launch event, and twelve months later has closed almost no projects. Nobody was careless. The belts were trained; the programme around them was never built. A Six Sigma deployment succeeds or fails on six elements that have little to do with statistics: how projects are chosen, who owns them, how much time belts really get, who validates the savings, how projects are reviewed, and what keeps the gains in place.

This article walks through those six elements in the order a deployment meets them, then lists the early signs that a programme is drifting towards the stalled pattern above. It stays on the company-wide view. The project-level methods, DMAIC and DMADV, are covered in other guides on this blog, and the exam itself gets one short block near the end.
Which six elements decide whether a Six Sigma deployment works?
A deployment is a management system, and the technical tools are the smallest part of it. Wikipedia's overview of Six Sigma traces the method back to a manufacturing programme, but what carried it into banks, hospitals and software companies was the governance wrapped around the tools: sponsors, a defined belt structure, project reviews and a link to financial results. Those are the six elements, and each one fails in a recognisable way.