The people, information, and observations needed to improve a workflow are often already inside the organization. Technicians see where a task becomes awkward or repetitive. Managers see where schedules begin to slip. Customers experience delays and uncertainty from another direction. Data reveals patterns that can be difficult to recognize one job at a time.

The opportunity is to create a disciplined way to see those signals, understand what they mean, and act on them.

That discipline sits at the heart of structured process-improvement approaches such as Lean methodology and Theory of Constraints. The terminology can sound specialized, but the practical objective is straightforward: understand how work actually moves, identify the places that limit flow, involve the people who experience those constraints directly, and improve the system in a way that produces better outcomes.

Fernando Bertrand has spent much of his aviation career working with those ideas. His experience includes approximately a decade with Embraer, senior leadership with Air France, and now his role as CEO of Bonus Tech. At Embraer, his work included continuous-improvement projects using Lean methodology and Theory of Constraints to improve ground operations.

Those principles apply far beyond one company or one segment of aviation.

Improvement Begins With Observation

Every improvement effort needs an accurate starting point.

The most useful place to begin is the work itself: watch how a process moves from one step to the next, who touches it, where decisions occur, where people wait, where information changes hands, and where employees develop workarounds to keep things moving.

This is especially important when entering a new leadership role. An established organization already contains years of habits, knowledge, compromises, successes, and adaptations. Before deciding what should change, spend time watching people work, learning who owns each part of the process, understanding how responsibilities overlap, listening to employees, and talking with customers about what they experience.

That observation period can reveal important differences between the documented process and the working process.

A procedure may show five clean steps while employees routinely use seven because the system requires an extra workaround. A delay that appears to be caused by staffing may actually be caused by incomplete information arriving upstream. A recurring quality problem may look like an employee training issue until a closer look reveals that the instruction itself creates ambiguity.

The objective is to understand the process well enough to diagnose the right problem.

Experienced leaders have an advantage because they recognize familiar patterns. They have seen similar bottlenecks, communication failures, layout problems, staffing issues, or workflow constraints before. That pattern recognition can help narrow the search quickly.

It should still be followed by observation.

Experience tells you where to look. Evidence tells you what deserves to change.

The People Closest to the Work Often See the Constraint First

Frontline employees interact with a process repeatedly. They feel every awkward movement, unclear instruction, missing tool, unnecessary handoff, repeated delay, and frustrating workaround.

That gives them a form of operational knowledge that is difficult to recreate from somewhere else in the organization.

A strong example comes from a C-check operation on an Embraer Legacy 600/EMB-135.

The work required removal of the aft fuel tank and replacement of structural skin. The operation was difficult, safety-sensitive, and consumed roughly 300 labor hours. The documentation was also difficult to manage as one large job.

The mechanics approached the workflow differently. They divided the job into smaller daily job cards, creating visible milestones and making progress easier to manage. On the first operation using that revised approach, the work dropped from approximately 300 hours to 200 hours.

That is roughly a one-third reduction in labor time on the task.

The same job produced another useful lesson.

Engineering saw an opportunity to create a better support structure for the fuel tank and spent several weeks developing a purpose-built tool projected to cost around $15,000.

When the design was brought to the floor, the mechanics had already solved the problem themselves. They modified an existing table, created an opening to support the tank, and produced a workable solution in only a few days for roughly €500.

Both groups were trying to improve the same work. They simply possessed different information.

Engineering brought technical knowledge, design capability, and a broader view of what a formal solution might require. The mechanics brought daily experience with the physical task and immediate knowledge of what would make the job easier.

The strongest improvement process connects those perspectives earlier.

Frontline knowledge should be treated as an input to solution design, alongside engineering, management, data, customer requirements, safety, and cost.

Turn Frontline Knowledge Into a Repeatable Process

Encouraging employees to contribute ideas is useful. Creating a system that can capture and apply those ideas is much more powerful.

A practical improvement system gives employees several things:

• permission to identify a recurring problem,
• a clear way to communicate what they are seeing,
• time to explain how the problem affects the work,
• enough operational context to understand related constraints,
• a method for testing an alternative,
• appropriate authority to make small improvements,
• feedback after an idea is evaluated,
• and a way to document successful changes.

This matters because some of the most valuable operational knowledge initially exists only in someone’s head.

A mechanic knows that one sequence works better than another. A salesperson knows which question customers repeatedly misunderstand. An inspector recognizes the same documentation issue arriving every week. A warehouse employee knows that parts stored in one location create unnecessary travel. A planner sees the same decision getting delayed by the same missing piece of information.

Each observation is useful on its own. The organization gains much more when the lesson can be validated, documented, and shared.

That progression might look like:

Experience → Recognition → Investigation → Validation → Standardized Knowledge

The goal is to preserve useful experience in a form that the organization can repeat.

Visibility Helps Reveal Where Work Is Getting Stuck

Process improvement becomes much easier when the work is visible.

Visibility can take many forms: a physical board on a shop floor, clearly defined job stages, production software, dashboards, work-in-process reporting, CRM data, turnaround metrics, customer portals, or simply better communication between departments.

The tool matters less than the questions it helps answer.

Internally, useful operational visibility should help teams understand:

• What work is currently in process?
• Where is it waiting?
• Which step is consuming the most time?
• Which problems are recurring?
• Where is ownership unclear?
• Which decisions remain unresolved?
• Which constraint is limiting throughput?
• What information is missing?

Bonus Tech is applying Lean methodology to facility layout and operating processes while also developing new software designed to increase visibility across the operation. The company is also building a CRM and customer portal intended to give customers easier access to information about the progress and history of their engines.

Those are two sides of the same principle.

Internal visibility helps the organization decide where to improve. Customer visibility helps the customer decide what to do.

Visibility Becomes Valuable When It Supports a Decision

Information volume alone does not create clarity.

Customers need information that helps them determine what happens next.

An engine moving through teardown or inspection can generate a large amount of technical and operational information: condition, component status, records, inspection findings, repair possibilities, material value, turnaround implications, and potential disposition paths.

Bringing that information together gives the customer a better basis for deciding whether to repair, inspect further, tear down an asset, recover particular components, or pursue another strategy.

Bonus Tech has operated for approximately 25 years and has completed roughly 2,600 engine teardowns. That history creates a substantial base of practical engine knowledge. The continued involvement of experienced founders, managers, engineers, and technicians adds another layer of context that can help turn individual findings into useful recommendations.

The same principle applies inside almost any organization.

A metric earns its place when it informs an action.

A dashboard earns its place when it helps someone identify a priority.

A customer portal earns its place when it reduces uncertainty.

A report earns its place when someone can use it to make a better decision.

Visibility should shorten the distance between evidence and action.

Better Information Can Be More Valuable Than Faster Movement

Speed is important in aviation. Aircraft availability, turnaround time, inventory, maintenance schedules, asset value, and customer commitments all create pressure to keep work moving.

Efficiency requires a broader view.

Consider a fan case sent through an engine-support process. An experienced teardown provider may inspect the part and recognize conditions that affect the economic or technical value of a proposed repair. Sharing that information may add time before the next decision is made.

That additional analysis can still improve the total workflow if it prevents a poor repair decision, unnecessary shipping, avoidable inspection expense, rework, or another delay later.

This is one of the most useful distinctions in process improvement:

Speed measures how quickly work moves. Efficiency measures how effectively it moves toward the desired outcome.

A process can look fast when only one stage is measured.

The full workflow may tell a different story.

A task completed in two hours may create six hours of downstream rework. A purchase order issued immediately may save an hour and create a week-long delay when the wrong item arrives. An asset decision made before all relevant information is available may have to be revisited later.

A better efficiency calculation includes the entire path:

processing time + waiting + handoffs + rework + decision delays + unnecessary movement

That broader view helps organizations optimize flow rather than individual activity.

Constraints Tell You Where Improvement Has the Greatest Value

Every process has something that limits its output.

It may be equipment capacity, technical data, staffing, tooling, floor space, inspection availability, decision authority, documentation, parts supply, customer response time, or another step in the workflow.

Improving the constraint has a disproportionate effect because that constraint is setting the pace for everything around it.

This idea is central to Theory of Constraints and is also useful when deciding how to expand capabilities.

Bonus Tech’s Part 145 development provides a practical example. The company has been expanding around the CFM56 and Pratt & Whitney PW4000 families, where it already has relevant OEM tooling, documentation access, trained employees, existing skills, and customer demand.

That provides a strong foundation for the next step.

When evaluating an expansion or process change, leaders can ask:

• Do we already have the required knowledge?
• Do we have trained people?
• Is the correct tooling available?
• Can we access the required technical documentation?
• Is there sustained customer demand?
• Does the current layout support the work?
• What new inspection or quality requirements will appear?
• Which current resource becomes the next constraint if volume increases?

These questions turn growth into a sequence of manageable capability decisions.

The same logic works on a much smaller scale. If one inspection station limits the output of an entire process, making three upstream stations faster may create a larger queue. Improving the actual constraint creates value throughout the system.

Better Processes Often Reduce Work Before They Accelerate It

Efficiency is frequently associated with doing the same task faster.

Some of the strongest improvements remove work altogether.

Breaking one confusing job card into smaller, clearer stages reduces management effort. Improving visibility can eliminate repeated status requests. Giving customers better information can reduce unnecessary back-and-forth. Fixing a layout can eliminate repeated walking or material movement. Capturing a technician’s solution can prevent every future employee from solving the same problem again.

This is an important way to evaluate a proposed improvement:

What work disappears if this solution succeeds?

The answer may include:

• fewer repeated questions,
• fewer manual handoffs,
• fewer corrections,
• less searching,
• less waiting,
• fewer duplicated entries,
• fewer unnecessary approvals,
• less rework,
• and fewer decisions that have to be revisited.

Those reductions often produce both speed and quality because the process becomes simpler.

New Leadership Should Begin With Understanding

A new leader often arrives with useful experience and immediate ideas.

The most productive first step is understanding where those ideas belong.

For an established operation, that means watching the work, learning who does what, understanding existing processes, listening to employees, and talking directly with customers about what they need.

That may require several months.

The time is an investment in diagnosis.

The organization may already have processes that work extremely well. Employees may have developed practical solutions that never reached management. A frustrating procedure may exist because of a regulatory, technical, or customer requirement that is not immediately visible. A proposed change may solve one problem while creating another somewhere downstream.

Understanding the system first helps distinguish among them.

This is where experienced leadership can be especially valuable. Experience provides a larger library of patterns and solutions, but it also makes disciplined diagnosis possible. The leader can recognize similarities while remaining open to the differences that make this organization unique.

A useful leadership sequence is:

Observe → Understand → Prioritize → Engage → Improve

That approach gives experience somewhere productive to land.

Make Continuous Improvement Part of the Operating Rhythm

The strongest improvement cultures develop a repeatable rhythm rather than waiting for a major project or operational problem.

Teams observe the work. Employees surface issues. Leaders review constraints. Data provides visibility. Solutions are tested. Lessons are captured. Customers provide another perspective. Then the process begins again.

Over time, the organization becomes more skilled at recognizing its own friction.

A simple operating rhythm might include:

1. Observe the work. Spend time where the process actually happens.
2. Identify recurring friction. Look for delays, repeated questions, rework, workarounds, and queues.
3. Ask the people closest to it. Understand what they experience and what they have already tried.
4. Find the constraint. Determine which issue is having the greatest effect on total flow.
5. Test a practical change. Start small enough to learn quickly.
6. Measure the outcome. Evaluate labor, turnaround, quality, rework, customer impact, or another meaningful result.
7. Capture the lesson. Update the process so the improvement becomes repeatable.
8. Make the result visible. Give employees and customers the information they need.
9. Look again. The next constraint may now be somewhere else.

That last step matters.

Improvement changes the system. Once one constraint is removed, another becomes more important. A growing organization constantly creates new combinations of people, information, workload, equipment, customer expectations, and capabilities.

Continuous improvement provides a way to keep learning from those changes.

Better Processes Begin With Seeing the Work More Clearly

The resources required to improve an organization are often closer than they appear.

They exist in the technician who has performed the same difficult task dozens of times. In the customer who keeps asking the same question. In the queue that grows every afternoon. In the data showing the same delay month after month. In an experienced leader who recognizes a familiar pattern. In a new employee who asks why a longstanding step exists.

The work is constantly generating information about itself.

A disciplined improvement process helps the organization notice it, understand it, and turn it into action.

That is how better processes lead to greater efficiency.

And better information, clearer workflows, and stronger visibility create something equally important: better decisions about what to improve next.