It’s Time To Resurrect Concurrent Engineering
I think it’s time to resurrect a long-forgotten way of working called Concurrent Engineering, or CE. We’ve wrung out all the savings from process-centric ways of working (Lean and Six Sigma). The next level of profits will be achieved by opening up the design space to include the customer, the product, the manufacturing processes, the tooling, the assembly process, the quality plan, the supply chain, and the service network. And Concurrent Engineering (CE), which came before Lean and Six Sigma, does just that.
Concurrent, as a word, means done at the same time, done together, done in parallel, done in conjunction with, and done in consideration with. And that’s what makes CE different. It demands that all the elements of bringing a new product to market are done in a connected way and done in parallel. Customer learning flows into a product specification and sales tools. The product specification drives product design, which shapes the manufacturing and assembly processes, which, in turn, guide the quality plan. And the supply chain takes direction from all that upstream work. And the service network makes sure customer problems are addressed, taking CE full circle.
With CE, the natural flow from customer to product to process to quality to supply chain to service network and back to customer makes clear that this circle of life demands that the downstream work takes direction from the upstream work. What that means is that the downstream work is connected to the upstream work and must be designed together, or concurrently. (That’s the concurrent part of CE.) And when they ARE designed together, the upstream work is better because the downstream work does just what’s required by the upstream work. It’s global optimization at the expense of local optimization.
And you’d think that this upstream-to-downstream circle of life is the primary benefit of CE, but it isn’t. There’s a second and lesser-known (and often overlooked) element of CE that’s equally powerful. It’s the counterclockwise circle of life where the downstream work shapes the upstream work. Yes. I said the downstream work shapes the upstream work. And the clearest example of this is when the manufacturing and assembly processes tell the product design how it must change to reduce the cost of making the parts and assembling the product. Downstream and upstream are designed concurrently, where the downstream work is improved (manufacturing and assembly) by reengineering what’s upstream (the product design).
CE is a two-way global optimization where both directions – clockwise (upstream to downstream) and counterclockwise (downstream to upstream) – are engineered concurrently. And the key to both is the organizational ability to communicate effectively across the functional interfaces. For CE to deliver the goods, people within the functions must communicate their needs upstream and downstream. But that’s only half of it because everyone must also receive information from upstream and downstream operations. CE requires give-and-take from all functions. And the most effective way I know to do that is through trust-based relationships that can pass their needs across the interfaces and receive/validate the needs passed to them.
The benefits of CE are staggering – improved quality, improved product performance and robustness, reduced cycle times, reduced cost, faster response times (shorter supply chains), increased profits, increased throughput, and happier customers. But CE requires that we rebuild organizational muscles that have long ago atrophied.
We have the talent within the functions, but we now measure the functions in a way that drives local optimization within each function. And I think we have to rebuild the capability to optimize across the functions. This requires more one-up-one-down knowledge within the functions and a rebuilding of trust-based relationships across the functions.
We’ve done CE before, and we can resurrect it and do it again. Yes, it has been a long time since we pulled it off, and there is little knowledge of how to do CE within our companies. But there are still some “seasoned” individuals out there who remember how to do it. And, before we hang it up, it would bring meaning to our lives to teach the next generation how to do CE.
You are one step away from your journey to resurrect CE. You just have to ask us for help. And we’ll come running.
Image credit — Philip McErlean, Beahgmore Stone Circles
The Global Optimizer
Define your business problem.
Assess the market to make it a commercial problem.
Define how you differ from your competitors.
Define everyone’s lines of improvement.
Project things into the future.
Define what you’ve got to improve to leapfrog your customers and yourself.
Test the new concept with customers.
Once validated, convert your commercial improvement objective into a technical problem.
Define the problem as an interaction between two system elements that touch.
Define the problem in time – before, during, and after the problem occurs.
If possible, solve the problem before it happens.
If you can’t, solve it while it happens.
If you’re in a hurry, solve it after the problem while you solve it during or before.
Make a prototype that demonstrates you solved the technical problem.
Show the prototype to customers to verify it’s still something worth solving.
File the patents.
Create the sales tools and convert them into a product specification.
Create a project plan and define the team to create the new product.
Make the first prototype and test it.
Show it to your suppliers and manufacturing crew and listen to their thoughts on how to reduce cost.
Incorporate the feedback and design out half the parts.
Take a risk and order the parts with long lead times.
Make the alpha units, show them to customers, and define the next improvements.
And while you’re doing that, test them, break them, and fix them until you run out of time.
Create the high-volume manufacturing and assembly processes for the beta build.
Make the beta systems and let customers use them. Listen to their feedback.
Update the sales tools and send the beta systems to customers to validate the offering.
Train the sales team.
Build the production units and fill the shelves.
Sell, sell, sell.
It’s important to execute each of these tasks well. But that’s not enough because they’re not independent. They’re interconnected. The upstream tasks shape the downstream tasks and the downstream tasks shape the upstream tasks. To get that shaping right, you need people who know all elements of the work and who can work across organizational and company interfaces. Those people are few and far between and invaluable.
The design engineer who can work with customers, marketing, and manufacturing. The manufacturing engineer who can work with design engineers, suppliers, and customers. The marketing leader who can speak engineering, manufacturing, customer, and supply chain. And the unicorn who can do every task, speak everyone’s language, empathize with all subject matter experts, accompany the sales team on tricky customer visits, recognize good work and publicly praise it.
All the tasks and deliverables are important. But more important is knitting everything together so upstream inputs feed downstream activities and downstream activities shape upstream inputs. Most important is that special person who can knit, shape, guide, cajole, praise, and actively help with all of the deliverables and all of the work.
When the wheels fall off, you know who to call. When the work is new, you know whose office provides good guidance. When there’s misalignment, you know who can do the realigning. And when local optimization is driving the wrong behavior, you know where to find the global optimizer.
Image credit — Irene Steeves – Boy Monk Meditating
Sometimes it’s best to leave a problem unsolved.
Fixing things is easy. Not fixing things is difficult.
We have a natural inclination to try to fix every problem, but that’s a problem in itself because we have more problems than we have time to solve them.
To fix or not to fix? That is the question.
If you know you can’t solve it, yet you try, I think that’s a bigger problem. You have all the downside of trying to solve it (consumed resources) and all of the downside of not solving.
If you know you can’t solve it, and you don’t try, you get accused of not caring. But, in fact, you do care. You care about preserving your capacity to solve the solvable problems.
When you have the gift of seeing problems, you also have the curse of seeing problems.
You can’t unsee a problem, so sometimes it’s best not to look so you don’t have to see.
Solving a problem that’s not yours to solve creates a bigger problem. The next time the problem arises, it’s yours to solve. The real problem owner gets to go home early, and you get to stay late to fix their problem.
See a problem, solve a problem…. But only if it’s yours to solve.
See a problem, solve a problem…. But only if you can.
See a problem, solve a problem…. But only if it’s the most important problem.
See a problem, solve a problem…. But only if you don’t create a bigger problem by solving it.
Image credit — Mike Keeling (one too many head-on collisions)
DEADLINE – Online Workshop on Cost Reduction Using Product Simplification
DEADLINE — I am holding a workshop tomorrow (October 29 at 11:00 am Eastern Time) on Designing Out Product Cost Using Product Simplification. Over the last two decades, I’ve developed tools and methods to help engineers obsolete their best work. The methods help engineers see their work differently and design new products with radically reduced cost signatures. They also help non-technical leaders reduce risk in new product development projects.
In the workshop, we’ll review real analyses of real products and learn how to create design approaches that simplify products and reduce cost. To register, click this link — REGISTER.
I look forward to seeing you at the workshop.
For those unfamiliar with me and my work, here’s a testimonial from Nick Dewhurst, CEO of Boothroyd Dewhurst, the inventors of Design for Manufacturing and Assembly (DFMA). Nick and his crew are the OGs of product simplification.
I’ve known Mike Shipulski since 2005, and in twenty years of working with engineering leaders, I’ve met very few who get results like he does. At Hypertherm, Mike didn’t just adopt DFMA, he built it into how the company designs products. He tracked the results all the way from the design station to the shipping dock: profit per square foot up 7X, warranty cost per unit down 4X, and part counts cut in half. Mike is a no-nonsense, fact-based decision maker. He starts with the data, and he knows that getting engineers to believe radical simplification is possible is as important as the tools themselves. He is also a true thought leader. Through his writing and his talks at our DFMA Forum, he has shaped how engineers and executives think about product cost, and he has made the case for product simplification to a generation of engineers.
Nicholas P. Dewhurst, President, Boothroyd Dewhurst, Inc.
Workshop On Designing Out Product Cost
This one isn’t a blog post!
After more than sixteen years of blog posts, I’ll host my first live workshop on October 29 at 11:00 am Eastern Time! This marks a new phase for me, and I’m super excited!
In the workshop, I’ll share the tools and approaches for Designing Out Product Cost that I’ve developed over the last 25+ years. Using the methods, I increased profit per square foot by 7X and reduced warranty cost per unit by 4X (see results below), which earned a cover story in IE Magazine. And my results have been published in Design News, ASSEMBLY Magazine, Digital Engineering, IE Magazine, ASME, and I’ve presented them at GE Research and Development, MIT, WPI, and Tuck.

In the workshop, you’ll see real before-and-after examples which will give you a feel for what’s possible; you’ll see real data on part count and cost; you’ll learn how to use data to create a design approach; and you’ll learn the ins and outs of a successful implementation.
And for the first 15 people to register, I am offering a complimentary strategy session after the workshop. To book your 30-minute strategy session, a link will be provided in the registration confirmation email.
Workshop Details
- Topic: Designing Out Product Cost
- Date: 10/29/26 at 11 AM EST
- Price: $100.00
Product simplification is a battle for hearts and minds.
With product simplification, it’s a battle for hearts and minds. You cannot simply ask the engineering community to design out half the parts because they don’t think it’s possible. The first step is to help them believe it’s possible.
Engineering Leadership Development Is Company-Specific
Customers buy products. Manufacturing makes the products. Design engineering designs the products. Engineering leaders guide and grow the engineers. In a “start with the customer” way, engineering leaders are important to growing revenue and profitability.
Engineering leadership requires both technical leadership and people leadership. You need to understand the technology, or you can’t use good professional judgement. And you need to understand people, or you can’t create the conditions for them to do work they thought was impossible. (I call this the almost impossible.)
Is it 90% technical and 10% people? Or is it 90% people and 10% technical? Or is it split down the middle at 50-50? The answer is yes. Sometimes it’s a 90/10 meeting followed by a 50/50 conversation in the hall. Sometimes it’s 10/90 for a whole week. Sometimes it’s 90/10 in the morning and 10/90 in the afternoon. Once in a while it’s 100/0 for a hot minute or 0/100 on rare occasions. (Most of the time, though, it feels like 75/75.) A great engineering leader must know technology and people and must know how to set their balance based on the context.
I think the curriculum for an engineering leadership development program must be context-specific. And because each company’s context is different, I think an engineering leadership development program should be company-specific. The new product development process is unique. The products are unique. The analytical tools and how they’re used are unique. The ins and outs of the design reviews are different. So, when in doubt, I suggest you make your engineering leadership development process more company-specific and use context-specific artifacts and examples.
More specifically, I think the curriculum to teach new product development is the new product development projects themselves. Junior engineering leaders work alongside senior engineering leaders during the actual projects in an apprenticeship way. The senior leader demonstrates an activity, and the junior leader watches. Next time, the senior leader demonstrates less, and the junior leader does more. This responsibility balance shifts over time until the junior leader demonstrates and the senior leader doesn’t have to watch anymore. The junior leader is certified activity by activity under the guidance of a senior leader. And when the junior leader has demonstrated all the necessary activities, they become a senior leader. And the cycle continues.
Companies win when their customers buy their products. And I think one of the best ways to do that is a formal (company-specific) program to develop engineering leaders.
Image credit – Willy Verhulst.
Improvement Goals Are Arbitrary
We do our best, and it’s either good enough or it isn’t. But it IS our best. Some questions: How was the good/not good bar set? Who set it? Was the bar set unreasonably? Were the measurement criteria clear? Was there agreement on the good/not good delineation? Does there need to be agreement? If there’s a disagreement, how is it arbitrated? Can there be disagreement?
Truth is, all goals, including the goals used to decide if you did a good job last year, are arbitrary.
20% improvement over last year. Arbitrary. Why not 21%?
15% faster than last time. Arbitrary. Why not 85%? Or 300%?
80% more “things” than last year. Arbitrary. Why not 9%?
If you do a sh*tty job last year, wouldn’t that set next year’s bar arbitrarily low?
Unless, of course, last year’s bar was set arbitrarily high and you actually did a great job.
If your leader likes what you did last year, you’ll get a good rating. And how do they decide if they like what you did last year? Kinda arbitrary.
If you made your leader look good last year, you’ll get a good review. But someone else arbitrarily set your leader’s good/bad threshold. One step removed from you, but still arbitrary.
If you do what you say you’ll do, that’s not arbitrary.
If you keep your promises, that’s not arbitrary.
If you help people, that’s not arbitrary. (And they will remember you helped them.)
If you tell the truth, that’s not arbitrary.
If you treat people with respect, that’s not arbitrary.
If you see something then say something, that’s not arbitrary.
If you listen to people, that’s not arbitrary.
If you treat people with kindness, that’s not arbitrary.
If you advocate for people, that’s not arbitrary.
If you say what everyone else is afraid to say, that’s not arbitrary.
When you take responsibility, that’s not arbitrary.
When you maintain someone’s confidence, that’s not arbitrary.
When you take action, that’s not arbitrary.
When you care, that’s not arbitrary.
When you help the team laugh, that’s not arbitrary.
When you give guidance, that’s not arbitrary.
When you tell people they did a good job, that’s not arbitrary.
When you ask people what they’re working on, that’s not arbitrary.
When you demonstrate trust, that’s not arbitrary.
Improvement goals are arbitrary.
Demonstrating that you care is not.
Image credit — Marcin Wichary
Working With Someone For A Long Time
When you see others get promoted, what do you do? Do you beat yourself up because you didn’t get promoted? Are you happy for them? A little of both?
When someone you worked with for a long time gets a wonderful new role outside the company, what do you do? Do you hold onto the fact that things will be harder for you because they won’t be there for you? Do you worry about the organizational gap that you’ll be asked to fill? Do you actively celebrate their good fortune and praise them to the sky?
When you work with someone for a long time, you build trust. And trust allows you to have difficult conversations. You can talk about the real deal. You can discuss situations that have strong emotional energy. You can get to the real root cause, however inconvenient. You can share your fears and struggles. You can support each other in bad times and celebrate success in good times. When you have trust, it’s less lonely for both of you.
When the person you work with for a long time is a pro, they teach you because you are willing to learn from them. And you teach them because they’re willing to learn from you. They elevate their pro-ness, and so do you. Sure, it feels good to both of you, but it also feels good to the broader organization.
When you work with someone for a long time, you invest in each other. You don’t keep score; you simply invest. They need some investment, and you give it freely. And when they need some investment, you don’t hesitate. You grow from the giving as much as the receiving. This respectful give-and-take ratchets up performance on both sides of the interaction.
I think working with someone for a long time creates immense value. However, I think it’s difficult to measure and takes time to develop and yield fruit. I don’t think companies can effectively calculate the return on investment of its people working together for a long time, but that’s okay. There is great personal value that comes from working with someone for a long time. And I think that’s reason enough to find someone to invest in for the long haul.
Image credit — Veit (Can I trust you?)
The Most Important Question – What do we do next?
With companies, there are always competing demands and too few resources. Always. Don’t feel special. And there is always noise in the signals. Always. And it always comes down to a single question:
What do we do next?
Don’t believe me? Think about your meetings last week. During the meetings, there was discussion about the current situation followed by discussion on what to do next. And at the end of the meetings, there were lists of things to do next. Those things may not get done, but there were lists of things to do next.
The competing demands create the set of possible problems to address. And the problems are inputs to the critical decision: What do we do next? The demands are not fully defined, which adds noise to the decision process, and there is no agreement on the underlying problem, if the problem is formulated at all. This adds noise to the signal. There are more demands/problems than resources, and they compete with each other for the small pool of unallocated resources and the sea of double-booked resources. This creates emotional stress and also adds noise to the signal.
Situation Normal for all companies: Partially formed (competing) demands, disagreement on the relative priority of the ill-formed demands, incomplete (or missing) problem formulation, limited understanding of the required resources other than everyone knows there are more demands/problems than resources, and immense pressure to violate resource constraints.
I cannot give you a recipe to answer the all-important question (What do we do next?), but I can suggest ways to reduce the noise and better assess the options.
Spend some time formally fleshing out the demands before the meeting. Dig in. Bring data. What is the output required? Who is asking for it? What are the inputs? What happens if we do it? What happens if we don’t? Come to the meeting with your analysis, but call it “a draft”. Let others ask questions and challenge your assumptions. Don’t be defensive. They are not attacking you; they are trying to improve understanding to make a better decision.
The cost of making a bad decision is immense, so it makes sense to spend a lot of time preparing a good description/assessment. The cost of over-preparing is low, so over-prepare. Here’s a rule:
For big decisions, preparation time should be at least ten times longer than your first estimate.
Another type of assessment is often overlooked. It’s the assessment of how well the opportunity fits with what you do well, with how you do things, and with the dispositional state of the larger system. In short, you’re trying to answer: Is it easy?
Here are some things to consider to answer the “Is it easy?” question. If the opportunity requires new knowledge, skills, and abilities, it will not be easy. If it requires you to work in different ways with new partners, it will not be easy. If it cuts against an industry trend, it won’t be easy. This is not an exhaustive list, and you should come up with your own assessment themes. To be clear, though, these lines of assessment are different than “How many people do we need?”
Here’s a rule:
You can’t run a marathon wearing running shoes that are three sizes too small.
There is nothing wrong with having too many good opportunities and too many competing demands. In fact, I think that’s a good sign. I think it says you are in high demand. And there is nothing wrong with having too few resources because, again, it means you’re in high demand. I’ve never met a profitable company that had too few opportunities and too many resources.
Image credit — Mitchell Hirsch
Two Ways To Look At It
See something TO say something.
Say something TO do something.
Gotta get it right TO gotta give it a try.
Progress BEFORE perfection.
I failed TO I learned.
Can’t be done TO here’s how.
It might not work TO I’ll do it anyway.
Progress AT THE EXPENSE OF perfection.
Me TO we.
My way or the highway TO what do you think?
Why BEFORE what.
This will be difficult AND we’ll do it together.
Them TO us.
Condemnation TO best intention.
Don’t do that TO why not try this?
This is what I expect BEFORE this is not good.
You messed up TO how can I help?
What BEFORE how.
Do this TO what should we do?
Finish BEFORE starting.
Quiet criticism TO public praise.
Image credit — Fraser Mummery
Mike Shipulski