Article 1: How to Write an Operational Problem Statement
Define the current condition, desired condition, measurable gap, population, timeframe, impact, and scope.
Domain 1. Article 1.
By Edwin Angulo | Co-Founder, Angulo & Morsa Legacy Consulting LLC
Published July 27, 2026 | Last reviewed July 27, 2026
EXECUTIVE TAKEAWAY
An operational problem statement should define the measurable difference between what is happening and what the organization requires.
It should identify the current condition, desired condition, size of the gap, affected process, affected population, time period, business impact, and deliberate scope boundaries.
It should not assume the cause, assign blame, or prescribe the solution.
Article 1 examined why recurring operational problems should be approached through competing, testable hypotheses rather than accepted explanations.
That work depends on an earlier requirement: the organization must first define the performance gap those hypotheses are intended to explain.
This article addresses that foundation.
“We need a better CRM.”
“Employees need more training.”
“Communication needs to improve.”
“We should automate the process.”
“The scheduling system is broken.”
These statements may reflect legitimate concerns. They may even point toward changes the organization eventually needs to make.
But they do not clearly define an operational problem.
Some describe a preferred solution. Others express dissatisfaction, assign blame, or describe a broad condition without establishing what is actually happening.
A useful operational problem statement does something more disciplined.
It identifies the difference between current performance and the level of performance the organization needs.
The operating principle is simple:
A problem should be stated as a measurable gap before it is investigated as a cause or addressed with a solution.
This does not require every operating concern to become a complex research project.
It requires leadership to establish:
What is happening
What should be happening
How large the difference is
Who or what is affected
When the condition occurred
Why the gap matters
Where the initial investigation begins and ends
The American Society for Quality describes gap analysis as a comparison between a current condition and a desired state.
Lean A3 problem-solving similarly begins by defining the difference between current and expected performance before causes and countermeasures are developed.
The Institute for Healthcare Improvement emphasizes clear, specific, measurable, population-focused, and time-bound improvement aims.
These frameworks share the same underlying logic: improvement requires a defined performance gap.
Figure 1. Anatomy of an Operational Problem Statement.
Eight elements connect the observed current condition to the required condition, measurable gap, affected process, affected population, timeframe, business impact, and deliberate scope boundaries.
A Problem Is a Gap, Not a General Complaint
A general complaint identifies dissatisfaction.
A problem statement identifies a performance difference.
Consider the statement:
Customer follow-up is inconsistent.
The word “inconsistent” indicates that performance varies, but it does not establish:
What qualifies as follow-up
Which customers or inquiries are affected
How performance is measured
What percentage currently receives follow-up
How quickly follow-up should occur
What level of performance is expected
When the problem occurred
Whether the gap is operationally significant
A measurable statement might begin:
During the 90 days ending June 30, 2026, 69% of qualified inquiries received a documented follow-up within one business day, compared with the company’s target of 95%.
The second statement gives leadership something that can be examined.
It identifies:
An observable current condition
A required condition
A defined population
A performance requirement
A measurement period
It also creates the basis for calculating the size of the performance gap.
Current performance compared with required performance creates the defined operational gap.
That gap is the problem to be investigated.
The explanation for the gap remains a separate question.
Do Not State the Preferred Solution as the Problem
One of the most common problem-framing errors is embedding a proposed solution inside the problem statement.
Examples include:
We need a better CRM.
We need to hire another employee.
We need more accountability.
We need to automate scheduling.
We need additional training.
We need to replace the current software.
We need a new policy.
We need an AI system.
Each statement moves directly to an intervention without first establishing the performance condition the intervention is intended to change.
The organization may ultimately need a new CRM.
It may also discover that the existing system is functioning correctly while:
Employees use inconsistent procedures
Assignment rules are unclear
Records are duplicated
Notifications are ignored
Required fields are bypassed
Managers do not review overdue work
Employees use communication channels outside the system
Service capacity is unavailable
Similarly, training may be appropriate when employees lack the required knowledge or skill.
Training will not correct:
Insufficient staffing capacity
Contradictory procedures
Unavailable information
Unclear authority
Poor system design
Conflicting priorities
A process that cannot meet the target under expected demand
A solution-led statement narrows the investigation before the evidence has earned that conclusion.
Figure 2. Problem, Cause, and Solution Are Different Decisions.
The operational gap describes what is happening, the causal hypothesis proposes why it may be happening, and the countermeasure defines what the organization may change.
DIAGNOSTIC PRINCIPLE
Do not define the problem by naming what management wants to purchase, install, enforce, automate, replace, or teach.
Define the performance gap the proposed change is supposed to correct.
The Eight Components of an Operational Problem Statement
A sufficiently developed operational problem statement should address eight elements.
The statement may not always place every element in a single sentence. Complex situations may require a short paragraph followed by a separate scope note.
The objective is not grammatical compression.
It is decision clarity.
1. Current Condition
The current condition describes what is happening during the defined period.
It should be based on an observable measure rather than a general impression.
Weak descriptions include:
Follow-up is inconsistent.
Customers are waiting too long.
Employees make too many errors.
Scheduling is inefficient.
The owner is involved in everything.
Communication is poor.
Words such as “inconsistent,” “slow,” “excessive,” “inefficient,” and “poor” may identify areas of concern, but they do not establish the actual level of performance.
A measurable current condition might state:
Sixty-nine percent of qualified inquiries received a documented follow-up within one business day.
Depending on the problem, the current condition may be expressed as:
A percentage or proportion
A transaction count
A completion rate
An error or defect rate
A cycle time
A response time
A backlog
A frequency
A customer rating
A labor-hour requirement
A cost
A contribution-margin amount
A number of management interventions
A percentage of work completed within a requirement
The selected measure should describe the performance issue directly enough that the organization can later determine whether the condition changed.
2. Desired Condition
The desired condition defines the level of performance the organization expects or requires.
It may come from:
A customer commitment
A service-level standard
A contractual requirement
A regulatory requirement
A documented procedure
A capacity requirement
A management target
An approved operating standard
A historically demonstrated performance level
For example:
The company’s target is for 95% of qualified inquiries to receive documented follow-up within one business day.
The current and desired conditions must use the same basic measure.
The original concern could be expressed as either:
Thirty-one percent of qualified inquiries did not receive documented follow-up within one business day.
or:
Sixty-nine percent of qualified inquiries received documented follow-up within one business day.
Both describe the same current condition.
However, comparing a 31% failure rate directly with a 95% success target makes the gap less immediately understandable.
The measures should first be expressed in the same direction.
Using the success rate:
Current success rate: 69%
Target success rate: 95%
Gap: 26 percentage points
Using the failure rate:
Current failure rate: 31%
Maximum acceptable failure rate: 5%
Gap: 26 percentage points
The desired condition must also have a defensible basis.
A target should not be accepted merely because it is ambitious, convenient, or visually appealing on a dashboard.
Leadership should understand whether the target reflects:
Customer requirements
Contractual obligations
Historical capability
Risk tolerance
Available staffing
Approved resources
A documented management standard
Another legitimate operating need
3. Measurable Gap
The measurable gap is the mathematical difference between the current and desired conditions.
If current performance is 69% and the required level is 95%, the gap is:
26 percentage points
The difference between two percentages should ordinarily be expressed in percentage points rather than simply as a percentage.
A change from 69% to 95% represents:
A 26-percentage-point increase
Approximately a 37.7% increase relative to the original 69% level
Those are different statements.
For operational problem framing, the percentage-point difference is generally more direct because it identifies the distance between the current condition and the target using the same scale.
The gap may also be expressed in operational units.
Suppose the organization reviewed 420 qualified inquiries:
Current timely follow-up: 290 inquiries
Required timely follow-up at 95%: 399 inquiries
Operational shortfall: 109 inquiries
The rate and count provide complementary information.
The rate supports comparison across periods with different transaction volumes.
The count communicates the number of affected transactions.
4. Affected Process
The problem statement should identify the process or process segment in which the performance gap appears.
Examples include:
Inquiry intake
Lead qualification
Initial customer follow-up
Appointment scheduling
Customer onboarding
Work assignment
Order fulfillment
Service delivery
Billing and collections
Complaint resolution
Employee onboarding
Work-order closeout
Management review
Broad functions such as “sales,” “operations,” “marketing,” or “customer service” may contain several connected processes and may be too general to guide an investigation.
For the inquiry example, the initial process boundary might include:
Inquiry receipt, qualification, assignment, and first documented follow-up.
The process named in the statement is where the performance problem is observed.
It is not necessarily where the underlying cause will be found.
A delayed follow-up problem could originate in:
The intake channel
Qualification criteria
Assignment rules
Staffing
System configuration
Notification design
Employee workload
Unclear responsibility
Management review
Incomplete customer information
Unavailable service capacity
The statement should define where the gap appears without prematurely deciding where the cause must exist.
5. Affected Population
The affected population identifies which customers, transactions, inquiries, employees, orders, appointments, locations, or cases are included.
Examples include:
Qualified website inquiries
New customers
Returning customers
Appointments scheduled at one location
Orders received through a particular channel
Work orders assigned to field employees
Invoices older than 45 days
Employees hired during the review period
Service requests received during operating hours
Population definitions matter because unlike transactions may enter the same workflow.
A shared inbox may receive:
Qualified customer inquiries
Existing-customer service requests
Vendor messages
Job applications
Spam
Duplicate submissions
Sales solicitations
Messages outside the company’s service area
Treating every message as an equivalent qualified inquiry would distort the follow-up rate.
The statement or supporting measurement definition should establish the relevant inclusion and exclusion rules.
For example:
Qualified inquiries include prospective customers requesting an offered service within the company’s approved service area and providing sufficient contact information. Duplicate messages, spam, vendor solicitations, job inquiries, and requests outside the service area are excluded.
Without a stable population definition, performance can appear to improve or decline merely because the denominator changed.
6. Time Period
The problem statement should identify the period during which the current condition was measured.
Examples include:
During the 90 days ending June 30, 2026
From April 1 through June 30, 2026
During the second quarter of 2026
Over the most recent six complete months
During weekday operating hours in June 2026
A defined period establishes an analytical boundary.
Without one, managers may rely on recent incidents, memorable complaints, or isolated examples that do not represent normal process performance.
The period should be long enough to produce useful evidence but specific enough to investigate.
Leadership should also consider whether the selected period contains unusual conditions such as:
Seasonal demand
A major promotion
Temporary staffing changes
A software implementation
A system outage
A location closure
A pricing change
A new service launch
An unusual customer mix
When possible, use exact dates rather than terms such as “recently,” “lately,” or “over the last few months.”
7. Financial, Customer, or Operational Impact
A measurable gap becomes a management priority because it affects something the organization values.
Possible consequences include:
Lost or delayed revenue
Avoidable labor expense
Rework
Overtime
Excess capacity consumption
Customer waiting
Missed appointments
Customer confusion
Service inconsistency
Complaints
Refunds
Employee frustration
Management intervention
Compliance exposure
Reduced conversion
Customer attrition
Damage to trust
The impact should be quantified when reliable evidence is available.
However, management should not manufacture financial precision simply to make the problem appear more important.
Suppose 109 more inquiries missed the one-business-day target than the company’s standard would permit.
The organization can accurately state:
The gap exposed 109 additional qualified inquiries to delayed or undocumented follow-up during the review period.
It cannot automatically state:
The company lost 109 customers.
Not every delayed inquiry would have converted.
Some customers may also have received follow-up through channels that were not recorded.
A credible problem statement distinguishes among:
Observed impact
Estimated exposure
Suspected impact
Impact that remains to be quantified
For example:
The gap affected 109 qualified inquiries. The related effect on conversion and contribution margin has not yet been established because timely and delayed inquiries have not been compared using consistent population and outcome definitions.
That statement is less dramatic than a fabricated revenue-loss claim.
It is also more defensible.
8. Deliberate Exclusions From Scope
A useful problem statement defines what the initial investigation will not address.
For the inquiry-follow-up example, exclusions might include:
Advertising performance
Lead-generation volume
Pricing
Product-market fit
Full CRM replacement
Later-stage sales conversion
Customer retention after purchase
Employee compensation
Processes at other locations
Transactions outside the defined period
Scope exclusions prevent one focused operating problem from becoming an unrestricted review of the entire company.
They also clarify what conclusions the investigation can and cannot support.
An exclusion does not mean the subject is unimportant.
Evidence may later show that an upstream or downstream factor must be examined.
For example, an apparent follow-up problem may actually reflect unavailable appointment capacity, causing employees to delay contacting customers they cannot serve.
When evidence justifies revising the scope, the boundary should be changed deliberately and documented.
It should not expand informally whenever a new concern is raised.
Figure 3. Scope Boundary for the Inquiry-to-Follow-Up Process.
Included steps are separated from related but initially excluded areas such as marketing volume, pricing, CRM replacement, later-stage conversion, and customer retention.
The Measurement Must Be Operationally Defined
A statement can contain numbers and still remain ambiguous.
Consider:
Sixty-nine percent of inquiries received follow-up within one business day.
Leadership still needs to define:
What qualifies as an inquiry?
What counts as follow-up?
Which timestamp starts the clock?
What is one business day?
Are weekends and holidays excluded?
Does an automated acknowledgment count?
Must the activity be documented in the CRM?
How are duplicate inquiries treated?
How are incomplete or invalid contact records treated?
What happens when the customer submits through multiple channels?
Without these definitions, two managers can calculate different performance rates from the same underlying activity.
A more operationally complete definition might state:
A qualified inquiry is a nonduplicate request from a prospective customer seeking an offered service within the approved service area and containing a valid telephone number or email address. Timely follow-up means a personalized telephone call, voicemail, text message, or email completed within eight defined business hours after receipt and documented in the approved customer record.
The exact definition should fit the organization’s actual process.
The purpose is consistency, not complexity.
MEASUREMENT PRINCIPLE
A precise number attached to an unstable definition creates false confidence.
Define the event, population, unit, timing rule, data source, and exclusions before treating the baseline as reliable.
A Target Is Not Automatically a Valid Desired Condition
Some organizations have no documented performance standard.
Others have targets that were selected years ago, inherited from a different operating model, or created without considering customer need or process capability.
In those situations, the desired condition may need to be validated.
Leadership should ask:
Who established the target?
What customer or business requirement does it support?
Is the target documented?
Has the process ever achieved it?
Is the target operationally possible under expected demand?
Does meeting it require resources the organization has not approved?
Would achieving the target create a new problem elsewhere?
Does the target apply equally across all transaction or customer types?
For example, a 95% one-business-day follow-up standard may be reasonable.
A requirement that every inquiry receive a personalized response within five minutes, 24 hours per day, may be impossible without dedicated staffing, automation, or an external service.
A desired condition should represent an actual operating requirement, not an unsupported aspiration.
If the target is provisional, the problem statement should say so.
Bad, Better, and Fully Scoped Statements
BAD STATEMENT
We need a better CRM.
This statement assumes that technology is the problem and that replacing or modifying the CRM is the solution.
It does not identify:
Current performance
Required performance
The measurable gap
The affected process
The affected population
The review period
The operational or financial impact
The scope boundaries
Evidence that the CRM caused the condition
BETTER STATEMENT
During the past 90 days, 69% of qualified inquiries received a documented follow-up within one business day, compared with the company’s target of 95%, creating a gap of 26 percentage points.
This statement identifies:
The current condition
The desired condition
The measurable gap
The affected population
The performance requirement
The time period
It still does not fully define the process boundary, impact, measurement rules, or exclusions.
FULLY SCOPED STATEMENT
During the 90 days ending June 30, 2026, 290 of 420 qualified website, telephone, and referral inquiries—69%—received a documented personalized follow-up within one business day, compared with the company’s target of 95%, creating a gap of 26 percentage points and an operational shortfall of 109 timely follow-ups. The initial scope includes inquiry receipt, qualification, assignment, and first documented follow-up. It excludes advertising performance, total lead volume, pricing, full CRM replacement, sales activity after the first response, and customer retention. The effect on conversion and contribution margin remains to be quantified.
The fully scoped statement provides a defensible starting point.
It identifies:
What the organization currently knows
The standard being missed
The scale of the gap
The operating boundary
What remains unknown
It does not claim that the CRM, employees, training, workload, or management caused the problem.
Figure 4. From Preferred Solution to Defined Operational Gap.
The statement “We need a better CRM” is progressively reframed into current performance, required performance, measurable shortfall, process boundary, impact, and exclusions.
Keep the Problem Separate From the Cause
A problem statement describes what is happening.
A causal hypothesis proposes why it may be happening.
A countermeasure describes what the organization may change.
Consider:
Employees are failing to follow up because they have not been properly trained.
This combines the observed condition with an unverified causal explanation.
Training may be relevant, but other explanations could include:
Inquiries are not consistently assigned
Assignment responsibility is unclear
Employees cannot identify overdue inquiries
Notifications are unreliable
Required information is missing
Duplicate records create confusion
Staffing is insufficient during peak periods
Employees use communication channels that are not documented
Managers do not review overdue inquiries
Service capacity is unavailable
The one-business-day requirement was never communicated
The underlying data are incomplete
Once the operational gap has been defined, Article 1’s hypothesis-testing framework provides the next step: develop competing explanations for the gap and determine what evidence would support or contradict each one.
The sequence is:
Define the measurable operational gap.
Develop competing hypotheses that could explain the gap.
Identify evidence that would support or contradict each hypothesis.
Determine which causes are sufficiently supported.
Select countermeasures that directly address the supported causes.
Measure whether the change improves the original performance gap.
Establish ownership and controls to prevent regression.
A problem statement defines what must be explained.
The hypotheses propose possible explanations.
The evidence determines which explanations remain credible.
Do Not Combine Several Problems Into One Statement
A broad statement such as the following is difficult to investigate:
Leads are not followed up, scheduling is inefficient, employees need training, customers are confused, managers cannot see what is happening, and the CRM is outdated.
This combines:
Multiple symptoms
Several processes
Possible causes
A proposed solution
Several different performance measures
The concerns may be connected, but they should not automatically be treated as one problem.
A more disciplined approach would separate the suspected gaps:
Percentage of qualified inquiries receiving timely first follow-up
Time from customer response to appointment scheduling
Percentage of appointments requiring manual correction
Percentage of customer records missing required information
Percentage of overdue inquiries reviewed by management
Number of inquiries requiring owner intervention
Leadership can then determine:
Which gap is most material
Which should be investigated first
Whether the conditions belong to the same process
Whether one gap is causing or contributing to another
Whether different measures and scopes are required
Narrow scope is not the same as narrow thinking.
A focused problem statement makes it easier to determine where evidence should be collected and whether a countermeasure changed the intended result.
What to Do When the Baseline Is Unknown
Many organizations cannot immediately produce a reliable current-condition measure.
Follow-up may be recorded across:
Email
Telephone logs
Text messages
Personal notes
Shared spreadsheets
CRM records
Individual employee inboxes
The absence of a reliable baseline does not justify inventing one.
The initial statement should distinguish between what is known, what is suspected, and what must still be measured.
For example:
Management has identified repeated cases in which qualified inquiries appear not to receive timely follow-up. The current completion rate is not reliably known because follow-up activity is recorded inconsistently across email, telephone, text messaging, and the CRM. The initial diagnostic scope will define the qualified-inquiry population, validate available records, and establish a 90-day baseline for documented first follow-up.
This is a legitimate preliminary problem statement.
It does not yet prove the size of the follow-up problem.
It defines the measurement problem that must be resolved before management can reliably assess performance.
Missing data may itself indicate a management-control weakness.
However, incomplete records should not automatically be treated as proof that the underlying operating performance is poor.
The organization may have:
A performance problem
A documentation problem
A measurement problem
A combination of all three
The initial evidence must distinguish among them.
Worked Example: A Clear Gap With an Unverified Financial Effect
Assume a company reviews 420 qualified inquiries received during the 90 days ending June 30, 2026.
The initial evidence shows:
290 received documented follow-up within one business day.
130 did not receive documented follow-up within one business day.
Current timely-follow-up rate: 69%.
Company target: 95%.
Target number of timely follow-ups: 399.
Operational shortfall: 109 inquiries.
Performance gap: 26 percentage points.
The organization can accurately state that 109 more inquiries missed the timely-follow-up requirement than the approved target would permit.
It cannot yet conclude that all 109 inquiries were lost.
Suppose management also observes:
Timely inquiries converted at 24%.
Delayed or undocumented inquiries converted at 14%.
Average contribution margin per converted customer was approximately $650.
A preliminary screening estimate could be calculated as:
109 affected inquiries × 10-percentage-point observed conversion difference × $650 average contribution margin
Estimated 90-day contribution-margin exposure:
Approximately $7,085
A simple annualized estimate would be:
Approximately $28,340
This calculation may help leadership determine whether the issue deserves further investigation.
It does not establish that delayed follow-up caused the entire conversion difference.
Timely and delayed inquiries may differ in:
Lead source
Customer urgency
Service requested
Time of receipt
Geographic area
Appointment availability
Qualification quality
Employee assignment
Customer responsiveness
The financial estimate should therefore be labeled as preliminary exposure rather than verified loss or guaranteed recoverable value.
The problem statement can acknowledge this limitation:
The observed conversion difference produces a preliminary annualized contribution-margin exposure estimate of approximately $28,340. The estimate has not been adjusted for differences in lead source, service type, customer urgency, appointment capacity, or other potential confounding factors.
A credible problem statement communicates what the evidence supports and what it does not.
State the Scope in Operational Terms
“Review customer service” is not a usable scope.
“Review the process from receipt of a qualified inquiry through first documented follow-up” is more specific.
A practical scope statement should identify:
The starting event
The ending event
Included channels
Included locations
Included roles
Included systems
Included transaction types
The review period
Deliberate exclusions
For example:
The initial scope begins when a qualified inquiry enters the website form, telephone line, or approved referral channel and ends when the first personalized follow-up is documented. It includes the intake coordinator, assigned sales personnel, the shared email inbox, telephone records, and CRM activity. It excludes marketing campaign design, advertising spend, pricing, later-stage sales conversion, and customer retention.
Figure 5. Operational Scope Boundary.
The process is defined by a starting event, ending event, included roles, systems, channels, and transactions, with adjacent business issues explicitly excluded from the initial investigation.
A Problem Statement Should Be Revised When Evidence Changes
A precise problem statement should not become a permanent conclusion.
It reflects what the organization knows at the beginning of the investigation.
As evidence is collected, leadership may discover that:
The original baseline was inaccurate
The population definition was too broad
The target was unsupported
The issue occurs only through one channel
One location accounts for most of the gap
Recorded follow-up understates actual activity
The problem is concentrated during peak demand
The apparent customer problem is actually a capacity problem
The financial impact is larger or smaller than estimated
The initial scope must be narrowed or expanded
Revising the statement in response to evidence is not a failure.
It indicates that the organization is learning.
A problem statement should be stable enough to guide the investigation but flexible enough to be corrected when the evidence contradicts the original framing.
The Eight-Question Management Test
Before authorizing root-cause analysis, software evaluation, staffing changes, training, automation, or process redesign, leadership should be able to answer these questions in writing:
What is the current condition, and what evidence supports the measure?
What desired condition or performance standard is the organization comparing it with?
Are the current and desired conditions calculated using the same definition, population, unit, and direction?
What is the size of the gap in both rate and operational volume when applicable?
Which process, starting event, ending event, roles, channels, and systems are included?
Which customers, transactions, employees, locations, and time period are represented?
What financial, customer, employee, capacity, compliance, or management consequence is observed or reasonably estimated?
What is deliberately excluded from the initial scope, and what important information remains unknown?
If leadership cannot answer these questions, the organization may not yet have a sufficiently defined problem.
It may have a concern, complaint, symptom, management belief, or preferred solution.
Those can justify preliminary investigation.
They do not yet justify assuming the cause or approving a major change.
Conclusion: Precision Prevents Expensive Misdiagnosis
Operational problems create pressure to act.
Customers may be waiting.
Employees may be frustrated.
Managers may lack visibility.
Revenue may be at risk.
The owner may be repeatedly pulled into routine coordination.
That urgency is real.
But urgency does not turn a general complaint into a defined problem or a preferred solution into a verified need.
“We need a better CRM” may eventually prove correct.
Before approving the change, leadership should be able to state:
What the process currently produces
What the organization requires
How large the performance gap is
Who or what is affected
When the condition occurred
Why the gap matters
What the initial investigation includes
What it deliberately excludes
A well-written operational problem statement does not solve the problem by itself.
It creates a problem that can be investigated.
It prevents the organization from beginning with blame, technology, staffing, training, automation, or policy treated as the answer.
It establishes a defensible bridge:
Observation → measurable gap → competing hypotheses → evidence → supported causes → countermeasures → results → control
Article 2 defines the gap.
Article 1 explains how to test the possible reasons for that gap.
Together, they establish the foundation for disciplined operational diagnosis.
OPERATING RULE
No major process, staffing, software, AI, training, pricing, or policy change should be approved until leadership can state the current condition, desired condition, measurable gap, affected process, affected population, time period, business impact, and deliberate scope exclusions.
When Structured Diagnosis Becomes Appropriate
When an established organization has a recurring operational problem with a meaningful customer, financial, employee, capacity, service-delivery, or management impact—and leadership cannot reliably define the gap, validate the available information, or establish the cause—Angulo & Morsa’s Operations Diagnostic examines how the work currently happens, the available evidence, measurement limitations, constraints, and competing explanations before recommendations are made.
[Learn about the Angulo & Morsa Operations Diagnostic]
Related Reading
[Read Article 1: Problem Framing and Scientific Reasoning]
[Return to The Legacy Perspective Knowledge Library]
Educational and Professional Disclaimer
This article is provided for general educational and informational purposes.
It does not constitute legal, tax, accounting, financial, investment, human-resources, cybersecurity, regulatory, engineering, statistical, or other professional advice.
Examples and calculations are illustrative and may not apply to a specific organization.
Operational measures and estimates depend on data quality, definitions, assumptions, process conditions, and organizational context. Qualified professional review may be appropriate for material decisions.
Use of this article does not create a consultant-client or other professional relationship with Angulo & Morsa Legacy Consulting LLC.
References
American Society for Quality. (n.d.). DMAIC process: Define, measure, analyze, improve, control.https://asq.org/quality-resources/dmaic
American Society for Quality. (n.d.). Quality glossary of terms, acronyms, and definitions.https://asq.org/quality-resources/quality-glossary
Institute for Healthcare Improvement. (n.d.). Aim statement worksheet.https://www.ihi.org/library/tools/aim-statement-worksheet
LaHote, D. (2015, January 7). Why effective problem solving begins with a good problem statement. Lean Enterprise Institute. https://www.lean.org/the-lean-post/articles/why-effective-problem-solving-begins-with-a-good-problem-statement/
Lean Enterprise Institute. (n.d.). A3 problem-solving: A resource guide.https://www.lean.org/lexicon-terms/a3-report/
Verble, D. (2021, February 11). Why A3 thinking is the ideal problem-solving method. Lean Enterprise Institute. https://www.lean.org/the-lean-post/articles/why-a3-thinking-is-the-ideal-problem-solving-method/
© 2026 Angulo & Morsa Legacy Consulting LLC. All rights reserved.