by eos consulting | Aug 11, 2020 | Manufacturing, Homepage Featured, Uncategorized
We’ve been talking about challenges for incumbent manufacturers, and suggested in our last post that for manufacturers to thrive, they need to command privileged positions in at least some of the business ecosystems in which they participate.
A privileged position means:
- Being core to or at the center of the ecosystem; or
- Owning vital elements of the ecosystem (standards, technology, proprietary software, etc.)
We suggested some ways to achieve that, among them:
- Ensuring that if there’s value in making your product ‘smart’, you play an important role in doing that — controlling or influencing the development of software, APIs, capabilities, standards, etc.
- If your product has software in it, owning its design and development as much as possible, especially for controls.
But designing and developing software poses distinct challenges for incumbent manufacturers — even if they don’t try to do it themselves.
In particular, incumbents’ existing development processes for many industrial products (such as electro-mechanical devices ranging from valves to combine harvesters) are likely much slower than for software & electronics — and for good reason. Such products (especially large ones) often comprise multiple integrated systems and components. Changing one affects others, and can have unpredictable effects on the performance of the entire machine. Moreover, a design change means changing manufactured parts and/or their fabrication — which, especially if it involves suppliers, can be slow, risky, and costly. Accordingly, incumbent manufacturers have learned how to update their products carefully and with manageable pacing.
Software development cycles, on the other hand, are much shorter. Software is easier to edit, test and replicate (even if the consequences are just as unpredictable, if not more so). But precisely because it is easier to edit, software development processes have come to be dominated by modularity, agile methodology, and rapid development and deployment.
Harmonizing these differing development processes across a set of design projects for a specific product is not easy, even (or especially) if the software development is outsourced. Except in cases of an entirely new product form, the physical product exists already, and the software project is about adding or upgrading sensors; adding communications in or out (from those sensors, for example); or automating (and/or optimizing) controls. Hardware engineers do not generally write software, so the first challenge is setting and maintaining execution schedules between hardware and software engineering teams (coordination only between individual engineers is often insufficient). A technical surprise or a shift in funding priorities can disrupt timelines, leading (in the worst case) to product delays or even incomplete (or buggy) solutions coming to market. In addition, design changes to the physical product and the software can get out of sync, again requiring time and often-scarce resources to reconcile. (Your software people may be spread thinner than you realize — especially if they must work with several product families.)
But there’s a deeper issue which may produce or exacerbate execution challenges: it’s not uncommon for requirements to change (or to be too vague), leading to misalignment between hardware and software teams. This especially plagues projects where the software component is outsourced or developed by a different unit of the company. It may even be unclear who owns the user experience, or the entire solution’s architecture and requirements.
In addition to adding cost, time delays are a frequent outcome of these challenges; yet for a large industrial product, missing a competitive product upgrade cycle (or two!) can be fatal to market share and/or profit margin.
So, what can be done?
- Start upstream from execution, with a shared vision across hardware and software of the value proposition for what you’re doing. Are you adding software-enabled features because the competition has them, and you must keep up? Ask yourself what the new capabilities will do for the customer, and whether/how that fits into your value proposition. If you must catch up, you might as well leapfrog — but only so far as you are meeting a real customer need, and not just trying to “out spec” the competition. (Yet leapfrogging can be a dangerous temptation — you are likely to take on additional technical risk, as well as marketing / channel challenges. And you had better be confident about profitability.)
- Ensure the product requirements are specific, measurable, and deliver the value proposition. Work together and be willing to listen to each other — often, the software team can suggest capabilities the hardware team didn’t realize were feasible. Most important, when requirements change (as they often will over the course of a project), don’t assume everybody is aware. Revisit the timeline and collaboratively make any needed adjustments.
- Consider developing a realistic, actionable product roadmap, incorporating some high-probability variants (e.g., funding cuts). This can align expectations and enable planning for contingencies. Perhaps most important, it enables you to be proactive — not re And the roadmap needs to reflect — and reconcile — the differing challenges of hardware and software development (e.g., seasonal product testing).
- Establish program governance across all the participating organizations for the set of projects together delivering the product update. This doesn’t have to be extensive or bureaucratic, but it does need to include:
-
- A joint repository of the project documents, including staffing, leadership, schedules, and requirements.
- Who decides what, and how conflicts are managed (“decision rights” — especially over product architecture, standards, and shared systems). And not just in theory — the organization must honor the process and “walk the talk,” especially when it comes to balancing the interests of not only hardware and software, but of design, manufacturing, and sales & marketing. (For example, who owns the specifications of the CAN bus on a vehicle? Especially if it is the factory which must carry the cost of a better one?)
- How communications between software and hardware teams will happen (e.g., when software teams change delivery dates for product features, how they will ensure the hardware teams know about it so they can plan).
Incorporating intelligence and connectivity into industrial products and components can be challenging, but it also opens new opportunities (as well as challenges) for incumbent manufacturers. Failing to do so can mean eventual relegation to commodity status. The manufacturing companies that will thrive in the future are likely to be “smart industrials.”
For more about operational governance, please see here.
by eos consulting | Feb 22, 2021 | Homepage Featured, Manufacturing Strategy, Uncategorized
If you Google manufacturing strategy, one of the top results is a Harvard Business Review article — from 1994. How can it rank so high given its vintage? The reason: it gets clicked on a lot — not only because it was written by two authorities on the subject, but because its insights remain on-point and highly useful (even after twenty-five years).
Let’s start with what they say about manufacturing strategy and strategic flexibility. Hayes & Pisano argue that:
In a stable environment, competitive strategy is about staking out a position, and manufacturing strategy focuses on getting better at the things necessary to defend that position. In turbulent environments, however, the goal of strategy becomes strategic flexibility. Being world-class is not enough; a company also has to have the capability to switch gears—from, for example, rapid product development to low cost—relatively quickly and with minimal resources. The job of manufacturing is to provide that capability.
That seems like kind of a big ask, doesn’t it? Perhaps it’s less daunting if we break it down into manufacturing capabilities that can deliver strategic flexibility to the business, such as:
- Agility & Responsiveness — the ability to handle changes in production volumes or product mixes; and to react quickly and effectively to product design changes, raw material changes, or customer order and delivery requirements (product options, order changes, delivery modes / timing / locations)
- Resilience — the ability to withstand shocks or rapid changes in exchange rates, labor or input costs, trade conditions, shipping rates, pandemics, and other operational disruptions
- Integration — the ability to incorporate new processes, products, or product architectures into the manufacturing operation
- Innovation — the ability to develop and deploy new or unique manufacturing processes to dramatically improve manufacturing performance
- Control & Improvement — the ability to direct and regulate operating processes, correct errors or inefficiencies, and to improve manufacturing performance
Such capabilities depend on much more than manufacturing sites, equipment and technology. As Hayes and Pisano point out, “a company’s capabilities are more than its physical assets. In fact, they are largely embodied in the collective skills and knowledge of its people and the organizational procedures that shape the way employees interact.”
Assembling the right combinations of assets, people, and process to deliver a desired capability — such as resilience to trade disruptions or global pandemics — takes time, commitment, and judgment.
And of course there are tradeoffs: low-cost production which relies on offshore suppliers can be brittle, subject to supply shocks (as many learned during the pandemic); yet steps to increase resilience can also increase costs. Production agility, if achieved with highly flexible lines, can also be expensive (but there are other ways to do it…).
These choices should be made in view of the business strategy — particularly the “how to win” elements. And good decisions about how to win can’t be made in ignorance of the actual or potential capabilities of the manufacturing organization. In fact, by “expanding the range of their manufacturing capabilities, [manufacturing leaders] increase their strategic options” for the business.
Which is why manufacturing leadership should be engaged in the business strategy.
by eos consulting | Oct 14, 2020 | Manufacturing, Uncategorized
Consumer and medical goods shortages during the global pandemic have inspired some media backlash against Lean Manufacturing practices; the Wall Street Journal even published an article saying we should “blame lean manufacturing” for paper towel shortages. Yet most manufacturing leaders have been taught (or learned the hard way) to “buffer or suffer” — that is, carry some inventory of key parts or materials, lest production halt for a simple stock-out. But inventory buffers are costly, and more than just the cost of capital: there’s also storage space and the risk of damage or obsolescence.
Demand or supply shocks are particularly challenging to process manufacturing (paper, paint, etc.), because winning in such products generally requires scale — often huge scale, expensive and time-consuming to build. But discrete manufacturing is vulnerable as well, especially if capacity (robots, material handling automation, assembly lines) is expensive.
This WSJ article provoked responses from Lean experts and practitioners, chiefly that:
- Lean practices work best with steady (or predictable, or controllable) demand, and that the pandemic created surges in demand that predictably created shortages; and
- Over the full cycle, Lean Practices (as demonstrated by Toyota) save much more than they cost.
The critics complain that producers are unwilling (or unable) to quickly add capacity when demand surges, and the rest of the supply chain is insufficiently buffered against demand (or supply) shocks. This restraint is attributed to the high cost and time required to add capacity (especially in process industries), but it also reflects managers having learned their lessons while playing the “Beer Game” in business school. The Beer Game is an exercise wherein teams of four (representing the factory, distributor, wholesaler, and retailer) compete to deliver beer to their customers at the lowest total cost over the course of the game (both stockouts and excess inventory incur penalties). End consumer demand is steady throughout the first part of the game, then doubles for the remainder. Inevitably, that single step change in demand generates a huge over-response in the system. Players learn that the best way to avoid “whiplash” in the Beer Game is to be slow to react to demand shocks.
So it is not surprising that many goods (including medical PPE and more) are still in short supply, even nine months into the pandemic. So, is there anything to be done, any adjustments that can be made? How should business leaders decide whether to stay (or become) lean, or instead build in more buffers to cushion against shocks? And how far should you go? The answer lies in your business strategy, which should drive your manufacturing strategy.
It starts with your value proposition — why your customers buy from you instead of your competitors. This is a key element of any business strategy. Generically, firms compete on the basis of price, differentiation, or customer intimacy.
Price includes not just cost to the customer, but also terms and transaction costs. To be sustainable, competing on price requires a secure cost advantage. Differentiation can include product quality (such as materials, durability, reliability), features, and performance. The value of the brand (where it means something to buyers) is also an element of differentiation, as is local production – really anything that a customer values and sets you apart from the competition. Customer intimacy is about the relationship, support, and responsiveness; it can include product scope, range, and customization; as well as order windows and delivery policies. (Customer intimacy can also be thought of as a dimension of differentiation.)
Customers don’t select one or another so much as they make tradeoffs between them: e.g., “good enough” quality at a “low enough” price, with adequate delivery performance. Moreover, not all customers make the same tradeoffs — although customers in particular segments may make similar tradeoffs.
If your most important customer segments will trade off the lowest possible price in return for product availability and reliability of delivery, then you should consider taking on the added costs of buffering finished goods and/or critical inputs. But if your targeted customer segments instead value the lowest price more than product availability (perhaps they prefer to hold their own inventory), then it’s worth risking occasional shortages to keep your operations as lean and efficient as possible. (In either case, you need to consider what your competitors can do for those customers — if they can accommodate those customer needs better than you, you’ll need to shift the basis of competition.)
Another way of handling these tradeoffs is to build flexibility into your sourcing and manufacturing, not by buffering but by configuring your operations to flex with supply or demand shocks. In the simplest case, lean methodology has always insisted on the need to identify and qualify additional suppliers — and many firms always source from one or two alternate suppliers as well as their primary, to ensure additional supply is available. But some disruptions (like hurricanes or pandemics) affect all regional suppliers, not just one.
You can also build flexibility into your manufacturing network, especially if you have modularized product designs (products consisting of assemblies of interchangeable modules), by:
- Manufacturing modules in more than one location, so production in one location can cover for outages or cost surges in another
- Ensuring those manufacturing capabilities are in differing trade zones and supply bases
- Carrying some additional production capacity in those locations
Modular product designs enable you to offer more product variety, by offering different permutations of modules — which can also help limit the size and scope of inventory buffers.
Lastly, it need not be entirely up to manufacturing to respond to demand shifts: demand can be shaped to better fit manufacturing capacity. Makers of large capital equipment, for example, often offer discounts for early orders, or price options consistent with the availability of parts to make them.
Lean practices have attracted scrutiny as a result of the disruptions caused by the global pandemic. But whether you should modify what you are doing — and how — depends not just on costs, but on your business strategy.
Read more: Manufacturing Strategy
Read more: Manufacturing Strategy in Today’s Volatile Trade Environment
Read more: Hitting RESTART After the Pandemic
by eos consulting | Apr 6, 2018 | Uncategorized
In today’s constantly evolving and increasingly competitive business landscape, many companies are urgently developing new products/services and exploring new revenue streams. However, their traditionally developed business strategies are either outdated or not as directly applicable. Over time, strategy comes unmoored from competitive reality, leading to misalignment of the company’s offerings, target markets, development priorities, marketing messages, and so on.
Sometimes it’s appropriate to do a full strategic overhaul, committing to a lengthy and far-reaching conventional strategy project. But some companies are beginning to “think different” (Apple’s classic mantra) about strategy. They realize that a clear, concise and timely strategy coupled with the right offerings and capabilities is the way they are going to win in the marketplace. And large, long, expensive strategy efforts may not get them there soon enough (if at all). Increasingly, companies are looking for ways to update their business strategies in a more rapid, focused way.
What is Rapid Cycle Strategy?
Rapid Cycle Strategy is a methodology for compressing and focusing the strategy development cycle to more effectively align with the realities of changing internal and external environments. Rapid Cycle Strategies operate over shorter time horizons and are quicker to develop and test – and thus are more responsive to your (and your competitors’) innovation cycles. They require fewer resources to develop and are significantly less costly than traditional strategy programs.
A Rapid Cycle Strategy project includes these elements:
- Identify the key mismatches between current strategy-in-practice, demonstrated capabilities, and the competitive landscape — good candidates for these mismatches are almost always known or suspected among the executive team, and it doesn’t necessarily require time-consuming, deep study to reveal them.
- For each mismatch, specify “what you would have to believe” to think that relieving the mismatch would make a real difference; and then test that (where possible) quickly and economically.
- For each mismatch, decide “what you would have to do” to fix it, and how hard that would be: would you need new products / services? Different capabilities? Different business models? Different organizational structure? Different people? Different customers? Different markets?
- Select one or two to work on first, prioritizing more highly those with a better combination of potential payoff and the work required to fix the mismatch.
- Craft a set of actions (assigning accountability) to fix the selected mismatches, and test (where possible) with pilot programs and test markets. Make adjustments on the basis of the testing.
- Develop and communicate a strategy statement which clearly describes what you are changing and why.
Many strategy efforts eventually address these items, but often take a long time to get there — and many times the organization feels “disconnected” from the work and the resulting choices. Our experience has shown that there is a better way. A few focused, multi-disciplinary workshops comprised of subject matter experts enables the harvesting of tribal knowledge. This knowledge is of better quality and is much more rapidly developed than by traditional means.
“Cutting to the chase” in this manner not only enables a more accurate, timely and cost effective strategy, but it engenders “buy-in” for subsequent execution. Many strategy efforts are wasted as there is not alignment and buy-in from those responsible for its ultimate success. The Rapid Cycle Strategy process significantly increases the chance of success.
Will the senior executive teams of major corporations move away from large corporate strategy efforts in the near future? Possibly not, but increasingly the business units/divisions of these companies are — and you should be too!
by eos consulting | Jul 2, 2020 | Uncategorized
In the 2007 movie There Will Be Blood, a character explains how directional drilling can drain the oil reservoir under someone else’s land. “I drink your milkshake!” he proclaims, to the dismay of the character whose oil profits have vanished. With similar dismay, many manufacturers have seen their profits drained away by other companies.
Many of the great American manufacturing companies of the 20th century have fallen on hard times. GM, US Steel, General Electric and more are now shadows of their former glory. Those that have thrived in this century (such as Apple, Intel, Honeywell, John Deere, or Rockwell Automation) tend to either lead or play major roles in one or more of the business ecosystems in which they participate.
Consider Apple, now one of the world’s most valuable companies as measured by market capitalization. Apple makes the lion’s share of profits earned in the smartphone industry, and they are the most profitable large-scale OEM in the world. Especially for a manufacturer, Apple is very profitable.
But is Apple really a manufacturer? They outsource nearly all their production and assembly — Apple does not actually build their phones, pods, computers, or much of anything else in their product suite.
If they are not, how then do they manage to drain the profit pools of most of the manufacturers in the smartphone industry? Why can’t most of the companies who actually build all those chips, iPhones and iPads extract more value from Apple?
Only by holding the commanding heights (privileged positions) in a thriving ecosystem, including a manufacturing ecosystem, is Apple able to collect most of the profits in the smartphone business.
The famed Apple product and services ecosystem consists of devices (mostly iPhones, iPads, Mac desktops & laptops, and wearables (Apple Watch, AirPods)) and their key components (especially chips); operating systems, standards, & APIs; software applications and services; and a software development community. The attraction of the ecosystem is the interoperability and ease of use of its elements — “it just works.”
Apple’s manufacturing ecosystem is also extensive. Apple designs its products, sets standards for and governs much of the supply chain several layers deep, and has other companies in the ecosystem manufacture components and assemble most products. Key hardware and manufacturing members of the ecosystem include Foxconn, TSMC, ARM, Intel, AMD, Samsung, LG, NVIDIA, Broadcomm, and many more.
Apple governs this ecosystem by occupying the key roles: As the OEM (and direct seller of many devices), Apple controls access to the customer. As developer of the operating systems and core applications, Apple sets the standards, defines the APIs, and controls the platforms on which Apple products and services operate. As designer of the products and the systems-on-chips (SOCs), Apple optimizes both hardware and software to achieve better performance for cost. As system integrator, at both the device and ecosystem levels, Apple is able to ensure that participation in the Apple ecosystem is always on Apple’s terms.
Because Apple controls both the software and hardware, they are able to sell software embedded in proprietary hardware — and realize the profits on either the hardware or the software (depending on what is tax-advantageous).
Apple did not start off controlling their own smartphone ecosystem. Indeed, they were late entrants to smartphones, with relatively low volumes — at first. But Apple crafted its smartphone ecosystem, then over time merged the rest of its offerings into it. This demonstrates one doesn’t have to be the market leader (at the time, that was Nokia— remember them?) to begin building a viable ecosystem.
Apple’s example has important implications for other manufacturers: if you want to earn sustainable returns, you too need to figure out how to define and control key roles in viable ecosystems. This is especially urgent in the age of the Internet of Things (IoT) — as more physical products are imbued with networking capabilities, “dumb” (no computational or networking capabilities) products are likely to be increasingly commoditized.
Manufacturers should consider:
- Ensuring that if there’s value in making your product ‘smart’, you play an important role in doing that — controlling or influencing the development of software, APIs, capabilities, standards, etc. (Note this doesn’t mean “make your product ‘smart’” if there’s not a customer segment willing to pay for such capabilities; internet-connected washers come to mind). But industrial valves, for example, can usefully be enhanced to be both sensors and digital controls.
- If your product has software in it, owning its design and development as much as possible, especially for controls. Any performance-enhancing integration of your product’s controls with others in the ecosystem strengthens your position.
- Commanding the integration nodes to and around your products. Proprietary physical interfaces and proprietary APIs can both deliver great leverage, even in an ecosystem not your own. (They must deliver real value to your customers, though.)
- Ensuring that it’s your hardware and/or software used at the points in the system that most drive performance. In an engine, for example, the fuel controls, emissions aftertreatment, and turbocharging are important drivers of an engine’s performance — and there is an entire frontier of optimization opportunities. Finally, to the extent that an important platform is part of the ecosystem (operating software, an order fulfillment system, a particular piece of hardware), try to move up from connection and compliance with it to influence on it.
These are fundamental issues strategically: Where to Compete, and How to Win. “Where” is not only which products, for which customers, in what markets and geographies; it’s also where in the value chain and where in the ecosystem. “How” includes all the strategic actions described above, but especially regarding ways to be a more important player in the ecosystems in which you participate. It’s not going to be enough to be “the low cost producer.” Not for long, anyway.
by eos consulting | Apr 6, 2018 | Uncategorized
Is your R&D portfolio producing the right balance of incremental improvements and innovative projects necessary to stay ahead of the competition? Are you funding too many incremental improvements over potential breakthrough innovations? Is focusing on ROI providing you the right portfolio mix?
These are the types of questions that many of our clients are facing as they strive to outpace the competition. This competition is advancing from all sides, including traditional competitors as well as upstarts coming seemingly out of “left field.” In order to win in the marketplace, product development and manufacturing companies need a robust R&D portfolio, one that provides a well-rounded pipeline of future products.
Companies typically don’t lack for interesting potential projects or programs vying to be included in the portfolio — they lack the appropriate mechanisms and strategic rigor to determine what projects should “make the cut” (and receive the needed funding and personnel). What can be done to address this? Our experience points to 4 key elements:
Align Strategically — specify whether and how a project explicitly furthers strategic goals. Many companies fund projects in the portfolio by focusing primarily on what we call “value to the company”, such as ROI. Including value to the company is necessary, but not sufficient in portfolio optimization — overreliance on it results in an unbalanced portfolio. Strategic alignment focuses on how well the candidate project advances strategic goals, ideally by market segment. The prerequisite here is clarity regarding the competitive goals of the company (by product line) in each segment and geography, as well as a clear understanding of “how you’ll win” in each.
Tie to Value to the Customer — identify the specific value that the project brings to the customer. This value is defined by the factors that are most important to the customer. This is not easily determined, but is critical to an optimized portfolio and provides the added benefit of focusing on a deeper understanding of customer needs and how your products are used by customers to create value. For one customer, we created a graphic representation — based on analytics established by Marketing & Engineering — that clearly depicts this value across a few key criteria versus both the competitive product and the closest internal product.
Categorize – another key to attaining (and maintaining) an appropriately balanced product portfolio is to assess and categorize types of projects flowing into R&D — are they breakthroughs, differentiators, followers? When we did this at one of our large manufacturing clients, they realized that their R&D portfolio was too heavily weighted toward incremental improvement (“me too”) projects and not enough truly innovative potential “game changers.” A rigorous set of criteria and assessment to determine the category in which a project resides enables proper allocation and encourages development teams to focus on the ways to create value that matter most to customers.
Simplify – new product proposals/justifications typically rely on lengthy documents, spreadsheets, presentations, etc. in an effort to display rigor and provide proposal gravitas. Yet the executive team making R&D portfolio decisions can rarely read (much less digest) all this documentation. If the elements outlined above are rigorously and consistently developed, then it’s possible to concisely pull all of the information together into a short (even single page!) document highlighting the key elements required for decision-makers to make an informed R&D portfolio decision, or inquire more deeply into the issues that really matter.
Incorporating these keys into your company’s process for shaping the R&D portfolio will not only focus your decision-making, but it will result in a strategically optimized product portfolio to stave off (and gain market share) from competitors.
