Big Y
The Big Y is the main result a Six Sigma project is trying to improve — the customer-facing outcome written as Y in Y = f(X). The X’s are the inputs and process factors that drive it, and the project works on those.
Teams often break a Big Y into a few operational “little y” measures so daily work has targets that actually move the customer result, instead of a vague goal like “improve quality.”
How a Big Y is chosen
Start with the voice of the customer and the business case, not with a favorite tool. A usable Big Y is:
- Important to a real customer or to a clear business need (delivery, quality, cost, safety).
- Measurable with a defined unit, source, and frequency.
- Movable by the process in scope — if the team cannot change the X’s, it is not a project Y.
- Stated as an outcome, not as a tool (“reduce promise-date misses,” not “implement a new scheduler”).
On a project charter this is the primary metric. Critical-to-quality (CTQ) trees do the same job: they turn a customer statement into measurable little y’s. The Y = f(X) problem-solving strategy is the same idea in equation form. The Define phase is where you write it down and agree the scope.
Little y’s and X’s
A restaurant that wants higher guest satisfaction (Big Y) might track seating wait, order accuracy, and meal cycle time as little y’s — the original example on this page still holds. At Northriver, “customers get complete hinge kits on the promised date” is a stronger Big Y than “run Six Sigma.” Little y’s might be hole-position yield, pack completeness, and missed promise dates. The X’s are the process knobs: drill wear, fixture setup, pick-list accuracy, WIP in front of pack, and how sales promises dates.
Do not collect twenty X’s and hope. In Measure and Analyze you confirm which X’s actually move the y, then change those. A map such as a SIPOC keeps the scope honest: suppliers and inputs on the left, the Big Y on the right.
A simple test
If two people on the team cannot name the Big Y in one sentence, and name the data that will show it improved, the project is still in Define. If they can name the Y but not a single controllable X, the work is still a wish, not a transfer function.
Exam notes
BoK items describe the Big Y as the primary customer or business outcome of a project, often cascaded into operational little y’s, and they expect you to recognize Y = f(X) as the model that links outcomes to process inputs. Distinguish the Big Y from a secondary metric you merely watch, and from a solution you have already decided to install.
Frequently asked questions
Can a project have more than one Big Y?
It can have supporting metrics, but one primary Y keeps the team from optimizing one result at the expense of another. If two outcomes both matter, name the trade-off in the charter rather than pretending both can be “the” Big Y.
Is the Big Y the same as a CTQ?
Often they line up. A CTQ is a measurable requirement that is critical to quality. The Big Y is the project’s chosen outcome. Many charters use a CTQ as the Big Y, then list related CTQs as little y’s or constraints.
See also: Y = f(X), voice of the customer, Define, and SIPOC diagrams.
See also: Correlation and regression
Related guides
Last updated: · Published by Lean Six Sigma Training Guide (sixsigmatrainingfree.com) · How this guide is written