JMA Blogs - Quality Is Not Just a Department
- Jul 27
- 4 min read

What Planning a Vacation to Italy Taught Me About Quality and the PDCA Cycle
Last year, my husband and I traveled to Italy for what we hoped would be a memorable vacation filled with beautiful scenery, great food, and unforgettable experiences. While much of the trip delivered exactly that, there were also moments of confusion, frustration, and unnecessary stress that, in hindsight, reflected many of the same challenges organizations face within their business processes every day.
When people hear the word “quality,” they often think of audits, inspections, compliance reports, or a dedicated Quality department. But true quality is not confined to one team or function. It is built into how processes are planned, executed, evaluated, and improved across an entire organization.
In today’s environment, organizations rely on increasingly interconnected processes, suppliers, technologies, and teams. As complexity grows, quality can no longer be viewed as the responsibility of a single department. Successful outcomes depend on communication, planning, accountability, and continual improvement across the entire business.
Ironically, our vacation became a real-world example of the PDCA (Plan-Do-Check-Act) cycle in action.
W. Edwards Deming, the father of modern quality management, taught that quality is achieved not through inspection alone, but through improving the systems that produce outcomes. The PDCA cycle, one of the foundational concepts associated with Deming’s philosophy, emphasizes continual improvement through four stages: planning, execution, evaluation, and corrective action.
Plan
Like many travelers, we relied heavily on a travel agent to coordinate hotels, transportation, and excursions. On the surface, the itinerary looked comprehensive and well organized. However, several important details were either overlooked or insufficiently validated during the planning phase.
For example, we were booked into an electric rental car without fully considering the realities of charging infrastructure in unfamiliar areas. Once in Italy, we discovered that all of the charging stations would not accept our credit cards, creating unnecessary delays and stress while traveling between destinations.
In addition, our reservation information was spread across two separate systems, making it difficult to quickly access confirmations, schedules, and booking details while on the move. Even an excursion that sounded enjoyable on paper..a pizza-making class in Naples, became uncomfortable because the location and surrounding environment did not align with our expectations for safety and convenience.
None of these issues were catastrophic, but together they demonstrated an important quality lesson: even well-intentioned plans can create poor outcomes when risks, dependencies, and customer expectations are not fully understood.
Do
Once the trip began, the execution phase exposed weaknesses in the planning process. Valuable vacation time was spent troubleshooting logistics rather than enjoying the experience itself. Communication gaps, fragmented information, and unverified assumptions all impacted the overall customer experience.
This mirrors what often happens within organizations. A process may appear effective during planning meetings or in documented procedures, but problems surface during execution when teams encounter unclear requirements, disconnected systems, supplier issues, or lack of contingency planning.
Quality is ultimately experienced during execution — not just during planning.
Check
As we reflected on the trip afterward, it became clear that many of the frustrations were preventable. The problem was not a lack of effort, but rather the absence of a cohesive process that aligned planning decisions with operational realities and customer expectations.
Organizations conduct audits, management reviews, performance evaluations, and customer feedback analysis for the same reason families reflect on travel experiences after returning home: to understand what worked well, what did not, and where improvements are needed.
Continual improvement only happens when organizations are willing to honestly evaluate outcomes rather than simply complete the process and move on.
This experience raised an important question that applies equally to business operations: how can organizations create consistent, reliable outcomes when processes involve multiple stakeholders, suppliers, systems, and decision points?
More importantly, who truly owns quality within those processes?
Act
As we plan this year’s travels, we are intentionally applying lessons learned from last year’s experience. Rather than relying entirely on a third party, I am taking a more active role in the planning process by consolidating reservations into a single itinerary application, independently verifying hotels and excursions, and reviewing customer feedback before decisions are made.
These changes may seem simple, but they reflect the same principles organizations use to improve business processes every day:
stronger planning,
better process visibility,
supplier evaluation,
risk reduction,
improved communication,
and continual improvement.
Key Takeaways
Organizations can strengthen quality outcomes by:
Centralizing critical process information to improve visibility and reduce confusion
Verifying supplier capabilities and customer expectations early in the planning process
Building contingency planning into complex processes
Encouraging cross-functional ownership rather than relying solely on a Quality department
Applying continual improvement principles such as PDCA to everyday operations
Quality failures rarely originate from a single mistake. They occur when processes are disconnected, requirements are not fully understood, risks are not evaluated, and ownership of the overall experience becomes fragmented.
That is why quality is not just a department.
Quality exists in every handoff, every decision, every supplier interaction, and every customer experience. Whether managing international travel or complex business operations, successful outcomes depend on well-designed systems supported by people who are committed to continual improvement.
At JMA, our Quality Management System is designed around these same principles. Quality is not treated as a standalone function, but as an integrated part of how we plan, execute, evaluate, and improve our operations in support of our customers and their missions.
By emphasizing collaboration, process ownership, risk-based thinking, and continual improvement, JMA’s quality program helps ensure that quality remains embedded throughout the organization rather than isolated within a single department.
Organizations looking to strengthen operational quality should begin by evaluating where communication gaps, disconnected systems, or unclear ownership may be creating unnecessary risk within the customer experience.


