Transforming Operational Efficiency with Outcome by Design™

Let’s start with an uncomfortable truth: most large-scale transformation efforts fail. McKinsey has reported for years that roughly 70% of transformations don’t achieve their intended outcomes. PMI’s research shows that a significant percentage of projects still miss their original goals and business intent, even in organizations that consider themselves mature.

This failure isn’t due to a lack of effort or care from leaders and teams. Instead, it stems from organizations trying to improve pieces of a system that was never designed to produce consistent outcomes in the first place.

The Real Problem Isn’t Execution

Walk into almost any organization, and you’ll find:

• Agile teams working hard

• Improvement initiatives underway

• Governance structures in place

• Customer metrics being tracked

• Leadership pushing for results

  
  

On paper, everything looks reasonable. But here’s what’s usually happening beneath the surface:

• Strategy is defined separately from delivery.

• Improvement runs as a side initiative.

• Incentives reward local performance, not system performance.

• Governance slows flow without meaning to.

  
  

No one designed those misalignments on purpose. Yet, they exist and compound over time. When that happens, outcomes become unpredictable.

This Is a Design Issue, Not a Performance Issue

Most organizations don’t fail because people execute poorly. They struggle because the way work flows, improves, and is governed was never intentionally designed as a coherent system.

When strategy, delivery, improvement, and leadership behaviors are designed separately, you get:

• Fragmented execution

• Initiative fatigue

• Inconsistent results

• Heroics instead of systems

  
  

And no amount of pushing harder fixes that.

What Outcome by Design™ Actually Does

Outcome by Design™ isn’t just another program layered on top of what you already have. It’s a proprietary operating system built on a simple premise: If you want predictable outcomes, you have to design the system that produces them.

That means aligning:

• Strategy to daily execution

• Delivery to value flow

• Improvement to live operations

• Leadership incentives to system performance

  
  

When those elements reinforce each other, results stabilize. Improvement sticks. Delivery becomes more predictable. Leaders stop fighting friction they unintentionally created.

“Eighty-five percent of the reasons for failure are deficiencies in the systems and process rather than the employee. The role of management is to change the process rather than badgering individuals to do better.”

W. Edwards Deming

The Importance of System Design

Designing a system that works requires a shift in mindset. It’s not just about managing tasks or projects; it’s about creating an environment where those tasks can thrive. This involves understanding the interconnectedness of various functions within the organization.

Understanding Interconnectedness

Every part of an organization affects the others. When one area struggles, it can create a ripple effect. For instance, if the delivery team faces challenges, it impacts customer satisfaction. If leadership isn’t aligned with operational goals, it can lead to confusion and frustration among employees.

Creating a Cohesive Strategy

To truly transform, organizations must create a cohesive strategy that integrates all aspects of the business. This means involving all stakeholders in the design process. When everyone has a voice, the system becomes more robust and adaptable.

The Role of Leadership in System Design

Leadership plays a crucial role in this transformation. Leaders must champion the design of a cohesive system. They need to model the behaviors they want to see throughout the organization. This includes being open to feedback and willing to make changes based on that feedback.

Encouraging a Culture of Continuous Improvement

A culture of continuous improvement is essential. Leaders should encourage teams to experiment and innovate. This doesn’t mean abandoning structure; rather, it means allowing flexibility within that structure. When teams feel empowered to make changes, they are more likely to engage with the system positively.

Conclusion: Designing for Success

The bottom line is clear: you don’t need more initiatives; you need a system intentionally designed to produce the outcomes you expect. Most organizations try to optimize parts. Outcome by Design™ optimizes the system.

By focusing on the system as a whole, organizations can achieve sustainable growth and efficiency. This approach changes everything!

Let’s embrace the challenge of designing systems that work. Together, we can create environments where operational efficiency thrives and transformation becomes a reality.

Why Conventional Training So Often Fails to Produce Real Outcomes...and What to Do Instead

Organizations are spending more on training than ever, and still hearing a familiar complaint from leaders: “We trained them… so why isn’t anything changing?”

That frustration isn’t just anecdotal. Corporate training spend in the U.S. has been reported at roughly $102.8B in the 2024–2025 period, continuing an upward trend. And yet, decades of research and practice show a stubborn pattern: most training doesn’t translate into sustained behavior change or measurable performance improvement.

This article lays out why conventional training programs often struggle to deliver tangible outcomes aligned to what people and organizations actually need, and it proposes a more cutting-edge alternative: Integrated Delivery Design. An approach that treats learning as a delivery system for measurable improvement, not a standalone event. It’s less about “which methodology” and more about building leadership capability + execution muscle so improvements stick.

The uncomfortable truth: training is optimized for “delivery,” not results

Most corporate training is designed to be:

• Efficient to schedule

• Consistent with rolling out

• Easy to complete

• Simple to evaluate

That’s not the same as being effective.

A large portion of training effort never becomes day-to-day practice. One widely-cited synthesis of impact evaluation work notes that only about 20% of training results in improved job performance for managers and leaders, meaning most investment ends up as good intentions without operational change.

Even when people enjoy a course, that’s a weak predictor of outcomes. In leadership development specifically, the measurement gap is striking. The 2024 LEADx Leadership Development Benchmark Report found that while nearly 90% measure learner reaction, only 39% measure behavior change, and just 22% measure business impact.

In other words, many organizations are still “grading the class,” not validating that anything improved.

Why conventional training programs struggle (even when the content is good)

1) Training transfer is treated as an afterthought

The science of training transfer is clear: learning doesn’t “move into the workplace” automatically.

A foundational research model (Baldwin & Ford) highlights that transfer depends on three categories of inputs:

• Trainee characteristics (readiness, motivation, self-efficacy)

• Training design (practice, relevance, feedback)

• Work environment (manager support, opportunity to apply, reinforcement)

Most training programs focus heavily on the middle item, design, and underinvest in the work environment conditions that make transfer likely.

If the system people return to is unchanged, same pressures, same incentives, same leadership behaviors, same overloaded calendars, the training becomes aspirational, not operational.

2) “Knowing” is mistaken for “being able to do.”

A lot of modern training still behaves like school: content first, practice later (if ever).

But adults retain far more when learning is embedded in action. McKinsey summarized a key insight: adults may retain only about 10% of what they hear in a lecture format, versus much higher retention when they learn by doing.

The problem isn’t that people are unmotivated. It’s that training often produces conceptual familiarity, not performance capability.

3) The program isn’t aligned to real work, real constraints, and real tradeoffs

Conventional training frequently fails in one of these ways:

• It teaches an “ideal-state” process that doesn’t fit reality.

• It ignores the hidden constraints (approvals, tools, legacy systems, staffing, politics).

• It’s not built around the actual decisions people make under pressure.

So learners leave thinking, “That makes sense… but it won’t work here.”

4) Leadership behavior is assumed, not built

Training is often aimed at employees, while leadership capability is treated as “context.” But context is created by leaders.

If leaders don’t:

• remove barriers,

• create time and permission to practice,

• reinforce new behaviors,

• measure what matters …then training becomes a short-lived burst of enthusiasm followed by reversion to old habits.

5) Measurement is too shallow to guide improvement

When the primary metric is completion rate or satisfaction score, programs can look “successful” while producing little business value.

LEADx’s benchmark data highlights that leadership development functions often aren’t measuring the two levels that matter most: behavior change and business impact.

Without those measures, organizations can’t learn what’s working, can’t course-correct, and can’t credibly connect training to outcomes.

The core mismatch: conventional training is an event, performance change is a system.

Here’s the simplest way to frame it:

• Training is often delivered like a product.

• Capability and results emerge like a system.

A system produces exactly what it is designed to produce.

If the organizational system is designed (intentionally or not) to reward speed over quality, firefighting over prevention, activity over outcomes, then training can’t “override” that design for long.

That’s why so many organizations experience:

• a burst of new language (“We should do a retrospective!”),

• a few early experiments,

• and then a return to the default operating model.

What does work: when learning is designed as a delivery engine.

Training can work powerfully when it is tied to real performance goals and designed for application.

For example, Harvard Business School Working Knowledge reported evidence that training interventions (in the studied context) were associated with measurable performance improvements, including roughly 10% higher goal achievement among frontline workers and positive spillover effects for supervisors.

The lesson isn’t “training always works.” The lesson is: training works when it’s engineered to produce transfer, adoption, and reinforcement, not just attendance.

A better approach: Integrated Delivery Design (IDD). Integrated Delivery Design is not a new “methodology” competing with Lean, Agile, Six Sigma, Design Thinking, or any specific methodology. It’s a higher-level operating approach that answers a different question:

“How do we build leaders and teams who can repeatedly deliver measurable improvements and make those improvements stick?”

IDD treats learning as one part of a complete delivery system that includes:

• leadership behaviors,

• operating cadence,

• measurement,

• workflow design,

• coaching,

• and real-world application.

It’s “cutting edge” in the sense that it moves past tool-centric training and builds capability as infrastructure.

IDD principles (the shift from training-as-event to training-as-delivery):

1. Start with outcomes, not content.

   Define a small set of business outcomes that matter (cycle time, defects, rework, on-time delivery, customer friction, employee burden).

2. Teach just enough, then apply immediately.

   Learning is modular, timed, and attached to real work, not an information dump.

3. Build leader capability as the main multiplier.

   Leaders aren’t sponsors; they are designers of the conditions for performance.

4. Integrate coaching and reinforcement into the operating rhythm.

   The application doesn’t rely on willpower. It’s designed into how teams work.

5. Measure behavior change and business impact as a default.

   Close the loop. If the change isn’t showing up in behaviors and outcomes, redesign.

6. Design for sustainability from day one.

   Transfer mechanisms are not an add-on; they are part of the architecture.

What IDD looks like in practice: a practical, repeatable model.

Below is a field-tested structure you can apply in many environments (operations, tech, service delivery, PMOs, shared services, customer experience teams, etc.).

Phase 1: Outcome & system diagnosis (2–4 weeks)

Deliverable: a shared definition of “improvement” grounded in business reality.

• Identify 3–5 measurable outcomes (lagging + leading indicators).

• Map the system that produces today’s outcomes (handoffs, constraints, queues, incentives).

• Identify the few “leverage points” where new capability will create results.

• Establish baseline metrics.

This isn’t a long assessment. It’s focused: what must improve, and why isn’t it improving today?

Phase 2: Co-design the capability-to-results pathway (1–2 weeks)

Deliverable: a clear “line of sight” from learning → behavior → metrics.

• Define the critical behaviors needed (e.g., leader coaching, standard work, decision cadence).

• Define the practice loops (weekly routines where people apply skills).

• Define reinforcement mechanisms (manager check-ins, peer review, dashboards).

• Define how impact will be measured at Level 3 and Level 4 (behavior + results).

  
  

  (This directly addresses the measurement gap highlighted in leadership development benchmarking.)

Phase 3: Build leaders first (and build them for the real environment) (4–8 weeks)

Deliverable: leaders who can create the conditions for transfer.

Core leader capabilities typically include:

• coaching for performance (not just accountability),

• removing barriers and protecting time for improvement,

• creating psychological safety for experimentation,

• reinforcing through metrics and storytelling,

• designing team routines that sustain the change.

This phase is where many programs fail by omission. Yet the transfer research emphasizes the importance of the work environment.

Phase 4: Execute “learning in the flow of work” improvement sprints (6–12 weeks)

Deliverable: measurable improvements delivered while learning.

Teams run short cycles with:

• a real operational problem,

• a small set of tools,

• rapid experiments,

• review of metrics weekly,

• leader coaching embedded into the cadence.

The point is not “perfect methodology.” It’s building the habit and infrastructure of delivery.

Phase 5: Lock in sustainability (4–8 weeks, then ongoing)

Deliverable: improvements that persist after the program ends.

You institutionalize:

• standard work where appropriate,

• dashboards and leading indicators,

• quarterly health checks,

• internal coaches or champions,

• onboarding pathways for new leaders and team members.

This is where “lasting and sustainable” becomes real, not a slogan.

Why this works: IDD aligns with what we know about transfer and performance change.

Let’s connect the dots:

• Transfer research emphasizes the work environment and reinforcement heavily influences whether training becomes performance.

• Many leadership programs don’t even measure the outcomes needed to improve them (behavior + business impact).

• Passive learning formats have much lower retention than learning-by-doing.

• Yet, when training is tied to execution and measured properly, it can drive measurable performance improvements.

IDD isn’t “more training.” It’s training redesigned as a delivery system, with leadership capability as the central engine.

The business case: stop buying training and start building an improvement operating system.

When organizations invest heavily in training (again: over $100B annually in the U.S. by some estimates) and still struggle to see measurable, sustained outcomes, the correct conclusion is not “people don’t want to learn.”

The correct conclusion is:

We’ve been treating capability like content when it’s actually infrastructure.

Conventional approach:

• “Send people to training.”

• “Teach the tools.”

• “Hope it shows up.”

Integrated Delivery Design:

• “Define outcomes.”

• “Design the system for transfer.”

• “Build leaders as multipliers.”

• “Practice in real work.”

• “Measure behavior + impact.”

• “Sustain through cadence.”

A simple litmus test: how to tell if your program is built for outcomes.

If you’re designing (or buying) a program, ask these questions:

1. What business outcomes will change, and by how much?

2. What behaviors must change for those outcomes to change?

3. What work routines will force practice and reinforcement?

4. What will leaders do differently starting next week?

5. How will we measure behavior change and business impact?

6. What barriers in the system will we remove to make transfer possible?

7. What happens after the workshop ends?

If the program can’t answer these clearly, it’s probably optimized for delivery, not outcomes.

The future of training is not “better courses”, it’s better delivery design. The next generation of capability building won’t be won by the organization with the most training hours, the slickest LMS, or the most fashionable methodology. It will be won by the organizations that treat learning as a performance system, engineered to produce measurable results, reinforced through leadership, and sustained through operating rhythms.

Integrated Delivery Design is that shift:

• from tools to outcomes,

• from events to systems,

• from participation to performance,

• from “learning” to lasting improvement.

If you want training that actually changes the business, stop asking:“What course should we run?”

Start asking: “What delivery design will build leaders and teams who can produce measurable improvement, repeatedly in the reality we operate in?”

Solving the Skilled Technician Shortage

Across the automotive, transportation, and heavy-equipment sectors, leaders are grappling with a workforce shortage that is as structural as it is severe. The accelerating pace of vehicle technology, the growing complexity of diagnostics, and the expansion of commercial and industrial fleets are driving demand for highly skilled technicians faster than labor markets can supply them.

In the United States alone, the TechForce Foundation estimates a cumulative shortage of over 500,000 automotive, diesel, and collision technicians by 2027. Canadian projections mirror the trend, forecasting a 15–20% supply gap in transport and heavy-equipment mechanics through the end of the decade. Ford's CEO, Jim Farley, has highlighted a critical shortage of skilled technicians within the company and the broader automotive industry. As of now, Ford has around 5,000 unfilled mechanic positions, despite offering competitive salaries of up to $120,000 annually. While these numbers are well-known, the impact is felt most acutely by organizations struggling with downtime, extended backlogs, declining customer satisfaction, and mounting pressure on their remaining technical staff.

The typical response, raising wages, expanding signing bonuses, and competing through incentives, is understandable. But it is also increasingly ineffective. When every employer escalates compensation, the labor pool does not grow; it simply redistributes. Without systemic solutions, financial competition becomes a race few can afford to win.

Having worked with organizations facing similar shortages across industries, I have found that meaningful improvement only comes when leaders stop viewing this as a recruiting challenge and start treating it as a workforce ecosystem challenge. Below, I outline how the Integrated Delivery Discipline (IDD) framework offers a practical, structured, and creative way to respond to the technician crisis without relying solely on wage escalation.

Reframing the Problem: The Limitation of Traditional Responses

Increasing compensation does address a small part of the challenge, but rarely the root cause. Organizations often overlook deeper systemic factors:

• Inefficient workflows that erode technician productivity

• Outdated equipment or diagnostic tools

• Supervisors untrained in coaching or people leadership

• Early-career technicians overwhelmed by onboarding demands

• Limited exposure to the trade in high school and early career pathways

• A workplace culture that doesn’t differentiate itself in meaningful ways

Addressing these constraints requires a different approach, one built on insight, not reflex.

The IDD Roadmap for Sustainable Technician Workforce Solutions

The Integrated Delivery Discipline combines systems thinking, human-centered design, Lean Six Sigma methods, and continuous improvement. Applied to the technician shortage, it becomes a powerful roadmap for redesigning how organizations attract, develop, and retain talent.

1. Diagnose the Workforce System Holistically

Most organizations underestimate the factors driving turnover and limiting productivity. A structured discovery process, including interviews, workflow analysis, skills mapping, and data review, often reveals:

• High fatigue and burnout from outdated shift structures

• Excessive non-wrench activities reducing effective utilization

• Career progression that feels stagnant or opaque

• Barriers in the first 90 days, where most early attrition occurs

• Cultural issues that quietly push people toward competitors

This diagnostic step reframes the challenge: the shortage is not only external, it’s also shaped by internal systems.

2. Re-Imagine the Technician Experience Using Human-Centered Design

Technicians today want more than a paycheck. They want an environment where they can grow, use modern tools, and feel part of something meaningful.

Human-centered design workshops often surface opportunities such as:

• Micro-progression models – small, frequent skill-based advancements every 60–90 days

• Tech-enabled workflows – tablets, guided diagnostics, digital work orders

• Modern apprenticeship pathways – modular, flexible, and focused on rapid competency building

• Improved shop ergonomics – lighting, tool access, and workspace layout

• “Experience redesign” – adjustments to shift flow, onboarding, and professional development

Small improvements in these areas often generate disproportionate gains in satisfaction and retention.

3. Build a Multi-Channel Talent Pipeline Strategy

Rather than relying on traditional recruiting alone, IDD encourages organizations to diversify their talent acquisition channels:

• High-School and Technical Institute Partnerships

  Early exposure dramatically increases entry to the trades.

• Veteran-to-Technician Conversion Models

  Many military occupational specialties align closely with diagnostics, electrical systems, and equipment repair.

• Second-Career Technicians

  Individuals transitioning from aviation, manufacturing, marine, or energy sectors often bring exceptional aptitude.

• International Talent Programs

  With proper credential support, global technicians can meaningfully supplement domestic labor shortages.

• Region-Based Recruiting + Quality-of-Life Incentives

  Lifestyle often outweighs wage differences when positioned properly.

This multi-channel approach expands the talent pool rather than competing for the same shrinking one.

4. Optimize Workflows to Increase Effective Capacity

The fastest way to feel “less short-staffed” is to remove friction.

Technicians frequently lose 30–40% of their time to tasks unrelated to actual repair work, searching for parts, documenting manually, walking between stations, or resolving unclear work orders.

Lean workflow redesign can yield the equivalent of adding several technicians’ worth of capacity without hiring a single person.

5. Leverage Technology to Amplify Talent

Technology does not replace technicians; it multiplies their impact.

• AI-supported diagnostics accelerate troubleshooting

• Telematics and predictive maintenance reduce emergency workloads

• VR/AR training labs accelerate skill development

• Remote expert support models allow one senior technician to assist multiple shops simultaneously

Organizations that modernize their technical environment stand out immediately to candidates, especially younger entrants.

6. Build a Technician Value Proposition That Goes Beyond Compensation

Compensation matters, but value is multidimensional.

Technicians consistently cite:

• Clear, structured career growth

• Access to modern tools and equipment

• Supportive supervisors

• Stability and pride in their work environment

• Work-life balance options

• Paid training and certifications

• Recognition for excellence

These are not expensive; they require intentionality. When organizations build a differentiated value proposition, they often become “destination employers” in their region, not by paying the most, but by offering the best experience.

7. Implement, Measure, and Continuously Improve

The final stage of the IDD roadmap ensures results are sustained.

Recommended metrics include:

• Recruitment cycle time

• Engagement and satisfaction scores

• Technician productivity

• First-time fix rate

• Retention at 90 days, 6 months, and 1 year

• Financial impact of improved uptime or reduced backlog

Feedback loops allow organizations to refine their approach and stay ahead of market changes.

Practical Tips for Leaders Addressing Technician Shortages

Tip 1 – Audit the first 90 days.

Most preventable turnover happens early. A structured and positive onboarding experience pays immediate dividends.

Tip 2 – Train supervisors as your first priority.

A technician’s relationship with their supervisor is the strongest predictor of tenure.

Tip 3 – Modernize the shop environment.

A clean, organized, and technologically current workspace is one of the best recruiting tools you already control.

Tip 4 – Build your employer reputation intentionally.

Technicians talk within communities, schools, and online forums. An authentic reputation is earned through daily experience.

Tip 5 – Treat recruitment like brand marketing.

You are selling a career, not a job posting.

Closing Perspective

The skilled technician shortage is not going away. Organizations that address it systemically, treating it as a design, workflow, culture, and experience challenge, are finding sustainable pathways forward.

The most successful leaders I work with share a common perspective; they see the shortage not as a constraint, but as an opportunity to rethink how they develop and support the next generation of technical professionals.

When approached with creativity, discipline, and a willingness to re-engineer the technician experience, the results can be transformative for organizations, for teams, and for the individuals who choose to build their careers there.