Skip to main content
Image coming soon

Process Capability and Defect Reduction Evidence & Implementation Kit

$249.00
Adding to cart… The item has been added
Process Capability and Defect Reduction · charter before data, qualify the measurement system, baseline the real variation, choose the chart from the data, keep control and specification limits apart, compute capability honestly, count opportunities, test the cause, confirm the experiment, hold the gain · Evidence & Implementation Kit
Take a live process problem from charter to a held gain without a problem statement that is really a solution, a capability index computed on a gauge that cannot tell good parts from marginal ones, a subgroup that mixes two shifts and widens the limits until nothing shows, a sigma level quoted without saying which shift convention it uses, or an improvement that quietly reverts because nobody owned the chart after the report was written.
Every control handed to you adopt-ready, from a charter approved before any data are collected with a problem statement that names an observed effect, its magnitude, its time window and the requirement it breaches and no cause or remedy, a baseline quantified from a named source across every shift, operator group, machine and supplier lot the process genuinely runs through, and frozen so closure is judged against one number, a supplier to customer map with every critical-to-quality measure carrying an operational definition that two people would apply the same way and a specification traced to a named customer requirement rather than to a number chosen because it is round, a measurement plan that fixes the data type, the sampling method, the sample size and the analysis before the first observation so the test cannot be chosen after the answers are visible, a gauge repeatability and reproducibility study on every continuous measure read against the conventional bands of under 10 percent generally acceptable, 10 to 30 percent conditionally acceptable and over 30 percent unacceptable with 5 or more distinct categories, an attribute agreement analysis on every inspection whose defect counts feed a chart, a chart chosen from the data type and the subgroup rather than from the tool default across individuals and moving range, Xbar and R, Xbar and S, p, np, c and u, a written subgroup rule that keeps common cause variation inside the subgroup so a shift difference is detected as a difference, signal rules and a reaction plan fixed in advance with a point beyond three sigma and a run on one side of the centre line at the minimum, control limits computed from the process and specification limits left with the customer, stability and distribution shape demonstrated before any index is quoted, Cp and Cpk reported from within-subgroup variation beside Pp and Ppk from overall variation with the gap between them interpreted as evidence about movement between subgroups, defects per million opportunities counted against a frozen opportunity definition with the sigma level convention named because the 1.5 sigma shift is an allowance for drift rather than a measurement, causes established with pre-listed stratification variables and the strata that showed no difference kept in the record, hypothesis tests matched to the data type and the study design with assumptions checked and effect sizes reported beside p values, designed experiments with a stated resolution for any fractional design, a randomised run order, replication, blocking and confirmation runs against the predicted optimum, sampling plans that state producer and consumer risk with the operating characteristic curve beside them, and a control plan with a named owner, a named reaction and limits recalculated only after a documented process change.
Ready in a weekend, not a quarter.

Here is the honest situation. Here is the honest situation. Improvement projects rarely fail because the statistics are hard. The arithmetic of a control chart and a capability index is well established and the software will compute it correctly. They fail before the data and after the result. The first failure is the charter. The problem statement arrives as a solution, because somebody has already bought the machine or booked the software change, and the project becomes a justification. No baseline was captured before the change, so at the end there is no number from before to compare against, and the gain is asserted rather than shown. The second failure is the measurement system. A capability figure divides the specification width by the observed variation, and the observed variation contains the gauge. A measurement system that consumes a third of the tolerance makes a competent process look incapable, and the team then spends weeks improving a process that was adequate while the gauge goes unexamined. Attribute inspection is worse because the error arrives disguised as a clean pass or fail, and disagreement between inspectors is quietly counted as process behaviour. The third failure is the chart. A chart chosen by habit or by the software default computes limits under assumptions the data do not meet, and a subgroup drawn across two shifts absorbs the difference the chart was built to find, so the process looks calm. The fourth is the index. A capability figure quoted without a stable process behind it moves with whichever upset fell inside the window, and one quoted from within-subgroup variation alone hides a process that drifts between subgroups every week. The fifth is the sigma level, which is compared across sites under different opportunity definitions and different shift conventions as though the number were a property of the process rather than a property of the arithmetic. The sixth is the close. The report states that the average moved, nobody asks whether the process is stable now or whether it can meet the specification, the chart stops being plotted, and six months later the process has returned and nobody can say when. This Kit is built for the parts that actually decide the outcome: the charter, the baseline, the measurement system, the subgroup, the limits, the pair of capability indices, the opportunity definition, the evidence behind the cause, and the owner who holds the gain afterwards.

This Kit removes the guesswork. It is process capability and defect reduction written as adopt-ready controls you personalize in a weekend, with the evidence a quality manager, an operations lead, an internal auditor or a customer actually examines.

What you get, the moment you buy

18
Controls, adopt-ready. Every control, written so you personalize and apply it.
18
Evidence-they-examine checklists. For each control, exactly what a reviewer examines, plus where teams fall short, so you close the gap first.
1
Control Matrix, pre-built. Every control in a working spreadsheet, ready to record status, owner and evidence location.
1
Gap & Readiness Assessment. Score each control and the workbook returns your readiness as a single percentage, and exactly what to fix next.

Grounded in quality engineering and process improvement practice as it is actually run on production and service processes with real data, real shift patterns and real Monday mornings. Editable Word and Excel files. This is a practitioner method and it is honest about what a project can and cannot prove from the data it was able to collect.

A gain that is evidenced and held, or a report that says the average moved
Improvement projects are not judged on the chart they drew. They are judged a quarter later: whether the process is still where the project left it, whether anybody owns the chart, and whether the number that justified the work can be reproduced from the data. This Kit builds the charter, measurement, charting, capability, cause, experiment, sampling and control-plan controls that keep those answers available before somebody asks.

What one control looks like

This is the opening control, where the project either starts from an observed effect and a real number or from a solution somebody has already bought. All 18 are built to this depth.

DEFN-1 Write the project charter around an observed problem and a quantified baseline, not around the solution somebody has already chosen CHARTER, SCOPE AND A DEFINED BASELINE BEFORE ANY DATA IS COLLECTED
Put this control in place

Require [your organization name] to approve a written charter before any data are collected for an improvement project, and to return any charter whose problem statement names a cause or a remedy instead of an observed effect. Require the problem statement to state the effect, the process step where it occurs, the population affected, its magnitude, the time window it was observed over and the requirement it breaches. Require a baseline that is quantified from a named data source over a stated window, with the observation count, the unit and the method of calculation recorded beside it. Require the charter to state the scope in and out with the process start and end boundaries, a named process owner who is accountable for the process rather than for the project, a named sponsor, and the team. Require the goal to be expressed as a change in the baseline measure with a target value and a written completion definition, and require the measure used at closure to be the same measure and the same operational definition as the baseline. Require every charter revision to be recorded with the reason and the date, and require the approved version and its revision history to be retained with the project record.

Control note.

Ask the sponsor to describe the problem without naming the fix. Most cannot on the first attempt, and the second attempt is usually the real project.

Evidence a reviewer examines
  • The signed charter, showing the problem statement, scope, process owner, sponsor and goal
  • The review record demonstrating that the problem statement names an observed effect and no cause or remedy
  • The baseline dataset with its source, time window, observation count, unit and calculation method
  • The in and out of scope statement with the process start and end boundaries marked
  • The goal with its target value and written completion definition
  • The revision record for every change to the charter, with reason and date
Common finding they raise: The project opens with a chosen remedy and no number from before the change, so at the end nobody can show whether the process moved or whether the movement was the process's own ordinary variation.

Why this is not another template pack

  • The evidence is the point. A control chart and a capability report are not evidence on their own. This tells you what a quality manager, an operations lead, an internal auditor or a customer examines and where teams fall short, for every control.
  • The hard specifics built in. A charter that rejects a problem statement naming a remedy, a baseline frozen across shifts, operators, machines and supplier lots, operational definitions that two inspectors would apply the same way, limits traced to a named customer requirement, a measurement plan that fixes the chart and the test before the first observation, a gauge study read against the under 10, 10 to 30 and over 30 percent bands with 5 or more distinct categories, an attribute agreement analysis with appraiser against standard, against themselves and against each other separated, chart selection across individuals and moving range, Xbar and R, Xbar and S, p, np, c and u with 10 or more as the common boundary between the middle two, rational subgrouping with the conditions held constant written down, signal rules and a reaction plan fixed in advance, control limits from the process against specification limits from the customer, stability and distribution shape demonstrated before any index, Cp and Cpk from within-subgroup variation beside Pp and Ppk from overall variation with the gap interpreted, 1.33 named as the common starting point for an existing process, defects per million opportunities with a frozen opportunity definition, sigma level with the 1.5 sigma shift named as the convention that places six sigma at 3.4 defects per million opportunities, causes established through pre-listed strata with the negative results kept, tests matched to design with assumptions checked and effect sizes reported, factorial designs with resolution stated, randomisation, replication, blocking and confirmation runs, sampling plans with producer and consumer risk and the operating characteristic curve, and a control plan with a named owner and limits recalculated only after a documented change.
  • Built on real practice, not one person's opinion, grounded in how capability studies and improvement projects actually hold together on a production floor or in a service operation, and where that discipline usually breaks down.
  • It compounds. This work shares its shape with supplier quality, quality management review, internal audit and operational risk reporting, so it feeds your wider quality system rather than ending with one project.

Who buys this

Quality engineers, process improvement specialists, operations supervisors and the managers accountable for a production or service process, who have to say what the customer actually requires, how much of the observed variation is the gauge, which chart the data call for, whether the process is stable enough to quote an index at all, what the gap between within-subgroup and overall capability is telling them, how many opportunities a defect rate was counted against, which sigma convention is in use, what evidence establishes the cause, and who owns the chart after the project closes. Whether you are running a first capability study that has to be defensible to a customer or formalising a programme that has closed projects and evidenced none of the gains, you save weeks and walk in with your charter, measurement, charting, capability, cause and control-plan controls structured.

By the end of the weekend you will have
✓  An adopt-ready control for all 18 areas
✓  A completed control matrix
✓  The evidence a reviewer examines
✓  A charter with a real baseline and a qualified measurement system
✓  A readiness percentage and a fix list
✓  The highest-risk gaps closed

Common questions

Is it really editable? Yes. Word and Excel files you own and adapt. No portal, no subscription.

Does it cover the whole practice? Yes. Charter, scope and a defined baseline, measurement system validation and a defensible baseline, control chart selection and process stability, capability indices and defect metrics, root cause analysis and designed experiments, and sampling plans and holding the gain each have their own controls with their own evidence.

Is this tied to one software package or one industry? No. The controls are principle-level, the charter and baseline discipline, the measurement system study, the chart and subgroup rules, the capability reporting, the opportunity definition, the cause and experiment method and the control plan, so they apply to a production line, a laboratory, a service desk or a finance process, and whatever tool you use to compute the figures.

Does it tell me what thresholds to use? Only where a convention exists and naming it prevents an argument. The Kit states the 10 and 30 percent bands for a gauge study, 5 or more distinct categories, 1.33 as a common starting point for an existing process, and the 1.5 sigma shift behind a sigma level. Each is a convention your organization adopts or departs from on the record. Every other tolerance, sample size, run length and threshold in the Kit is a number you set and record.

What if it is not for me? A 30-day money-back guarantee.

Do not let the next review be a capability figure with no chart behind it, a sigma level with no opportunity definition, or a gain that nobody has agreed to own.
Every control is fast to adopt with the Kit. It is instant, and it is guaranteed.
Add it to your cart and be ready this weekend.

Instant digital download · 30-day money-back guarantee · The Art of Service Pty Ltd, GPO Box 2673, Brisbane QLD 4001 · support@theartofservice.com