OPERATIONS PRACTICE · FMEA & PROCESS RISK

Imagine your organization is launching a new client intake process.

The workflow looks reasonable.

The form works.

The team has been trained.

Everybody agrees that the process is ready.

Then the first week arrives.

Requests disappear into an inbox.

Two staff members assume the other person is following up.

One client receives conflicting instructions.

A required approval is discovered too late.

None of these problems was impossible to imagine.

They simply were not discussed systematically before launch.

That is the kind of conversation Failure Mode and Effects Analysis (FMEA) is designed to support.

The American Society for Quality describes FMEA as a systematic, step-by-step approach for identifying and prioritizing potential failures in a product, process, or service so teams can reduce or mitigate them.

The Institute for Healthcare Improvement similarly describes FMEA as a proactive method for examining where and how a process might fail and assessing the relative impact of those failures.

The important word is proactive.

Root-cause analysis asks what went wrong. FMEA asks what could go wrong.

After an incident, organizations often investigate causes.

That is useful.

But FMEA points in the other direction.

Before launch, ask:

• Where can this process fail?
• What would happen if it did?
• Why might it fail?
• What controls already exist?
• Which failure modes deserve attention first?

This does not eliminate uncertainty.

It gives the team a structured way to discuss it.

A hypothetical service example

Suppose a professional-development provider creates this process:

1. Client submits request.
2. Coordinator reviews needs.
3. Facilitator is selected.
4. Client confirms scope.
5. Session is scheduled.
6. Workshop is delivered.

Now examine one step:

Step: Facilitator selection

Possible failure mode:
A facilitator is assigned without sufficient experience in the requested topic.

Possible effect:
The session does not address the client's problem adequately.

Possible cause:
The intake form captured the workshop title but not the underlying organizational challenge.

Existing control:
Coordinator reviews facilitator profile.

Possible preventive action:
Add three diagnostic questions to intake and require the coordinator to document why the facilitator matches the stated need.

Notice how much more actionable this is than simply writing:

Risk: Wrong facilitator.

A lightweight FMEA workshop for service teams

Formal FMEA approaches can use structured scoring for severity, occurrence, and detection. ASQ describes these dimensions and also notes limitations, including data quality and the risk of making the method overly cumbersome.

For teams new to the method, a facilitated qualitative version can be a useful starting point before deciding whether formal scoring is appropriate.

Step 1 — Map the process

15 minutes

Write the major process steps in sequence.

Keep the scope narrow enough that the team can discuss it meaningfully.

For example:

Inquiry → qualification → assignment → confirmation → delivery → follow-up

Responsible role: process owner.

Step 2 — Ask what could fail

20 minutes

For each step ask:

“In what specific way could this step fail to perform its intended function?”

Avoid vague answers such as:

“Communication problem.”

Use specific descriptions:

“Client receives no confirmation within two business days.”

Step 3 — Identify the effect

15 minutes

Ask:

“If this happens, what does the client, employee, partner, or next step in the process experience?”

This keeps the discussion grounded in consequences.

Step 4 — Identify likely causes

15 minutes

Ask:

“What conditions could create this failure?”

There may be several.

Avoid assuming the first explanation is the root cause.

FMEA is identifying potential causes; it is not proof that a cause actually produces the failure.

Step 5 — Review controls

10 minutes

Ask:

• What currently prevents this?
• What currently detects this?
• Would we notice before the client does?

This question often reveals that a process relies on memory rather than a control.

Step 6 — Prioritize action

15 minutes

For a lightweight workshop, consider:

• consequence severity,
• likelihood based on available evidence,
• detectability,
• and the organization's tolerance for the risk.

Do not reduce judgment to arithmetic automatically.

A rare but catastrophic failure can deserve attention even when a simple scoring method does not rank it first.

Step 7 — Assign owners

5 minutes

Each selected action should have:

• an owner,
• a due date,
• and a method for verifying completion.

Example action register

Failure mode	Proposed action	Owner	Timeframe	Progress measure
Requests are not acknowledged	Automatic receipt + daily queue review	Operations lead	1 week	% acknowledged within target
Wrong facilitator selected	Add diagnostic fit questions	Program manager	2 weeks	% assignments with documented fit
Scope changes after confirmation	Add scope-confirmation checkpoint	Coordinator	1 week	Number of post-confirmation scope changes

The measures should fit the actual process.

They are not universal benchmarks.

FMEA is especially useful before change

ASQ identifies several situations where FMEA can be useful, including when a process, product, or service is being designed, redesigned, applied in a new way, or targeted for improvement.

That makes it particularly relevant before:

• launching a new service,
• changing an intake workflow,
• implementing a new technology,
• redesigning onboarding,
• transferring responsibilities,
• or scaling a process that previously worked informally.

The limitations matter

FMEA is not a substitute for every form of risk analysis.

Potential limitations include:

• incomplete information,
• subjective scoring,
• blind spots shared by the entire team,
• excessive detail,
• weak follow-through,
• and false confidence because a spreadsheet looks comprehensive.

ASQ specifically notes that lack of data and inefficient one-size-fits-all formats can weaken the method.

Another practical problem is participation.

If only the process designer conducts the analysis, the team may reproduce the same assumptions that created the process.

Cross-functional perspectives are valuable because different people see different failure modes.

One question to use before your next launch

Before approving the process, ask everyone involved:

“If this fails in the first month, what is the most predictable way it will happen?”

Then do not stop at the answer.

Ask:

What could we change now?

That is the practical value of FMEA.

Explore frameworks and facilitation support

Use the Management Framework Selector to compare approaches, or the Organizational Challenge Navigator to clarify the issue. Explore workshop options or request a facilitator when a guided discussion would be useful.