You are currently browsing the tag archive for the ‘Bussines change’ tag.

Last week I shared my thoughts related to my observation that the ROI of PLM is not directly visible or measurable, and I explained why. Also, I explained that the alignment of an organization requires a myth to make it happen. A majority of readers agreed with these observations. Some others either misinterpreted the headlines or twisted the story in favor of their opinion.

A few came from Oleg Shilovitsky and as Oleg is quite open in his discussions, it allows me to follow-up on his statements. Other people might share similar thoughts but they haven’t had the time or opportunity to be vocal. Feel free to share your thoughts/experiences too.

Some misinterpretations from Oleg’s post: PLM circa 2020 – How to stop selling Myths

  • The title “How to stop selling Myths” is the first misinterpretation.
    We are not selling myths – more below.
  • “Jos Voskuil’s recommendation is to create a myth. In his PLM ROI Myths article, he suggests that you should not work on a business case, value, or even technology” is the second misinterpretation, you still need a business case, you need value and you need technology.

And I got some feedback from Lionel Grealou, who’s post was a catalyst for me to write the PLM ROI Myth post. I agree I took some shortcuts based on his blog post. You can read his comments here. The misinterpretation is:

  • “Good luck getting your CFO approve the business change or PLM investment based on some “myth” propaganda :-)” as it is the opposite, make your plan, support your plan with a business case and then use the myth to align

I am glad about these statements as they allow me to be more precise, avoiding misperceptions/myth-perceptions.

A Myth is bad

Some people might think that a myth is bad, as the myth is most of the time abstract.  I think these people do not realize that there a lot of myths that they are following; it is a typical social human behavior to respond to myths. Some myths:

  • How can you be religious without believing in myths?
  • In this country/world, you can become anything if you want?
  • In the past, life was better
  • I make this country great again

The reason human beings need myths is that without them, it is impossible to align people around abstract themes. Try for each of the myths above to create an end-to-end logical story based on factual and concrete information. Impossible!

Read Yuval Harari’s book Sapiens about the power of myths. Read Steven Pinker’s book Enlightenment Now to understand that statistics show a lot of current myths are false. However, this does not mean a myth is bad. Human beings are driven by social influences and myths – it is our brain.

Unless you have no social interaction, you might be immune to myths. With brings me to quoting Oleg once more time:

“A long time ago when I was too naive and too technical, I thought that the best product (or technology) always wins. Well… I was wrong. “

I went through the same experience, having studied physics and mathematics makes you think extremely logical. Something I enjoyed while developing software. Later, when I started my journey as the virtualdutchman mediating in PLM implementations, I discovered logical alone does not work in businesses. The majority of decisions are done based on “gut feelings” still presented as reasonable cases.

Unless you have an audience of Vulcans, like Mr. Spock, you need to deal with the human brain. Consider the myth as the envelope to pass the PLM-project to the management. C-level acts by myths as so far I haven’t seen C-level management spending serious time on understanding PLM. I will end with a quote from Paul Empringham:

I sometimes wish companies would spend 6 months+ to educate themselves on what it takes to deliver incremental PLM success BEFORE engaging with software providers

You don’t need a business case

Lionel is also skeptical about some “Myth-propaganda” and I agree with him. The Myth is the envelope, inside needs to be something valuable, the strategy, the plan, and the business case. Here I want to stress one more time that most business cases for PLM are focusing on tool and collaboration efficiency. And from there projecting benefits. However, how well can we predict the future?

If you implement a process, let’s assume BOM-collaboration done with Excel by BOM-collaboration based on an Excel-on-the-cloud-like solution, you can measure the differences, assuming you can measure people’s efficiency. I guess this is what Oleg means when he explains OpenBOM has a real business case.

However, if you change the intent for people to work differently, for example, consult your supplier or manufacturing earlier in the design process, you touch human behavior. Why should I consult someone before I finish my job, I am measured on output not on collaboration or proactive response? Here is the real ROI challenge.

I have participated in dozens of business cases and at the end, they all look like the graph below:

The ROI is fantastic – after a little more than 2 years, we have a positive ROI, and the ROI only gets bigger. So if you trust the numbers, you would be a fool not to approve this project. Right?

And here comes the C-level gut-feeling. If I have a positive feeling (I follow the myth), then I will approve. If I do not like it, I will say I do not trust the numbers.

Needless to say that if there was a business case without ROI, we do not need to meet the C-level. Unless, and it happens incidental, at C-level, there was already a decision we need PLM from Vendor X because we played golf together, we are condemned together or we believe the same myths.

In reality, the old Gartner graph from realized benefits says it all. The impact of culture, processes, and people can make or break a plan.

You do not need an abstract story for PLM

Some people believe PLM on its own is a myth. You just need the right technology and people will start using it, spreading it out and see how we have improved business. Sometimes email is used as an example. Email is popular because you can with limited effort, collaborate with people, no matter where they are. Now twenty years later, companies are complaining about the lack of traceability, the lack of knowledge and understanding related to their products and processes.

PLM will always have the complexity of supporting traceability combined with real-time collaboration. If you focus only on traceability, people will complain that they are not a counter clerk. If you focus solely on collaboration, you miss the knowledge build-up and traceability.

That’s why PLM is a mix of governance, optimized processes to guarantee quality and collaboration, combined with a methodology to tune the existing processes implemented in tools that allow people to be confident and efficient. You cannot translate a business strategy into a function-feature list for a tool.

Conclusion

Myths are part of the human social alignment of large groups of people. If a Myth is true or false, I will not judge. You can use the Myth as an envelope to package your business case. The business case should always be a combination of new ways of working (organizational change), optimized processes and finally, the best tools. A PLM tool-only business case is to my opinion far from realistic

 

Now preparing for PI PLMx London on 3-4 February – discussing Myths, Single BOMs and the PLM Green Alliance

 

  1. It does not make sense to define the future of PLM
  2. PLM is not an engineering solution anymore
  3. Linearity of business is faster becoming a holdback
  4. The Product in PLM is no longer a mechanical Product
  5. Planet Lifecycle Management has made a next major step

 

It does not make sense to define the future of PLM

future exitAt the beginning of this year, there was an initiative to define the future of PLM for 2025 to give companies, vendors, implementors a guidance to what is critical and needed for PLM in 2015. Have a read here: The future of PLM resides in Brussels.
I believe it is already hard to agree what has been the recognized scope of PLM in the past 10 years, how can we define the future of PLM for the next 10 years. There are several trends currently happening (see the top 5 above) that all can either be in or out of scope for PLM. It is no longer about the definition of PLM; it is dynamically looking towards how businesses adapt their product strategy to new approaches.

Therefore, I am more curious how Product Innovation platforms or Business Innovation platforms will evolve instead of focusing on a definition of what should be PLM in 2025. Have a further look here, such as, The Next Step in PLM’s Evolution: Its Platformization a CIMdata positioning paper.

Conclusion: The future is bright and challenging, let´s not fence it in by definitions.

PLM is not an engineering solution anymore

plmMore and more in all the discussions I had this year with companies looking into PLM, most of them see now PLM as a product information backbone throughout the lifecycle, providing a closed-loop of information flow and visibility across all discipline.

End-to-end visibility, End-to-end tractability, Real-time visibility were some of the buzz-words dropped in many meetings.

These words really express the change happening. PLM is no longer an engineering front-end towards ERP; PLM interacts at each stage of the product lifecycle with other enterprise systems.

End-to-end means when products are manufactured we still follow them through the manufacturing process (serialization) and their behavior in the field (service lifecycle management/field analytics).

All these concepts require companies to align in a horizontal manner, instead of investing in optimizing their silos. Platformization, as discussed above, is a logic step for extending PLM.

Conclusion: If you implement PLM now, start thinking first about the end-to-end flow of information. Or to be more concrete: Don´t be tempted to start with engineering first. It will lock your new PLM again in an extended PDM silo.

 

Linearity of business is faster becoming a holdback

changeTwo years ago I started talking about: Did you notice PLM is changing ? This topic was not in the mainstream of PLM discussions two years ago. Now with the introduction of more and more software in products (products become systems), the linear process of bringing a product to the market has become a holdback.

The market /your customers expect faster and incremental innovations/ upgrades preferably without having to invest again in a new product. If you look back, the linear product development approach has not changed since the Second World War. We automated more and more the linear process. Remember the New Product Introduction hype around 2004 -2006, where companies started to extend the engineering process with a governance process to follow a product´s introduction from its early concept phase toward a globally available product. This process is totally linear. I wrote about it in my post: from a linear world to fast and circular, where the word circular is also addressing the change of delivering products as a service instead of deliver once and scrap them.

One of my favorite presentations is from Chris Armbruster: Rethinking Business for Exponential Times – enjoy if you haven´t seen this one.

Conclusion: The past two years the discussion related to modern, data-driven dynamic products and services has increased rapidly. Now with IoT, it has become a hype to be formalized soon as life goes faster and faster.

 

The Product in Product Lifecycle Management is no longer a mechanical Product

imageI have mentioned it already in the previous point, the traditional way of working, designed and targeting a linear product development process, is no longer enough to support the product lifecycle.

When I started to implement PDM systems in the nineties, we tried to keep electrical engineering outside the scope as we had no clue how to manage their information in the context of a mechanical design. It was very rudimentary. Now PLM best practices exist to collaborate and synchronize around the EBOM in an integrated manner.

The upcoming challenge now is due to the software used in products, which turn them into systems. And not only that, software can be upgraded in a minute. So the classical ECR / ECO processes designed for hardware are creating too much overhead. Agile is the motto for software development processes. Now, we (PLM consultants/vendors) are all working on concepts and implementations where these worlds come together. PLM (Product Lifecycle Management), ALM (Asset Lifecycle Management) and SysLM (System Lifecycle Management as introduced by Prof. Martin Eigner – have a read here) are all abbreviations representing particular domains that need to flow together.

Conclusion: For most companies their products become systems with electronics and software. This requires new management and governance concepts. The challenge for all vendors & implementors.

 

Planet Lifecycle Management has made a next major step

imageFinally good news came in the beginning of December, where for the first time all countries agreed that our planet needs to have a sustainable lifecycle. Instead of the classical lifecycle from cradle to grave we want to apply a sustainable lifecycle to this planet, when it is still possible. This decision is a major breakthrough pushing us all to leave the unsustainable past behind and to innovate and work on the future. The decisions taken in Paris should be considered as a call for innovative thinking. PLM can learn from that as I wrote earlier this year in my post PLM and Global Warming

Conclusion: 2015 was a year where some new trends became clear. Trends will become commodity faster and faster. A challenge for all of us to stay connected and understand what is happening. Never has the human brain challenged before to adapt to change with such an impact.


 

thinkClosing 2015 means for me a week of quietness and stepping out of the fast lane. I wish you all a healthy 2016 with a lot of respect, compromises and changing viewpoints. The current world is too complex to solve issues by one-liners.
Take your time to think and reflect – it works!

SEE AND HEAR YOU BACK IN 2016


Topics discussed in 2014-2015

PLM Basics

PLM and Business Change

From a linear world to a circular and fast-blog

PLM and Business

Conferences

tacit_logoThe brain has become popular in the Netherlands in the past two years. Brain scientists have been publishing books sharing their interpretations on various topics of human behavior and the brain. Common theme of all: The brain is influencing your perceptions, thoughts and decisions without you even being aware of it.

Some even go that far by claiming certain patterns in the brain can be a proof if you have a certain disorder. It can be for better or for worse.

“It was not me that committed this crime; it was my brain and more…”

Anyway this post will be full of quotes as I am not the  brain expert, still giving the brain an important role (even in PLM)

“My brain? That´s my second favorite organ” – Woody Allen

It is good to be aware of the influence of the brain. I wrote about this several times in the past, when discussing PLM vendor / implementer selection or when even deciding for PLM. Many of my posts are related to the human side of justifying and implementing PLM.

As implementing PLM for me primary is a business change instead of a combination of IT-tools to implement, it might be clear that understanding the inhibitors for PLM change are important to me.

In the PLM communities, we still have a hard job to agree between each other what is the meaning of PLM and where it differs from ERP. See for example this post and in particular the comments on LinkedIn (if you are a member of this group): PLM is a business process, not a (software) tool

And why it is difficult for companies to implement PLM beside ERP (and not as an extension of ERP) – search for PLM and ERP and you find zillions of thoughts and answers (mine too).

Charles_RoxburghThe brain plays a major role in the Why PLM we have ERP battle (blame the brain). A week ago I read an older publication from Charles Roxburgh (published in May 2003 for McKinsey) called: Hidden flaws in strategy subtitle: Can insights from behavioral economics explain why good executives back bad strategies. You can read, hear and download the full article here if you are a registered user.

The article has been written long before the financial and global crises were on the agenda and Mr. Roxburgh describes 8 hidden flaws that influence our strategic decision making (and PLM is a strategy). I recommend all of you to read the full article, so the quotes I will be making below will be framed in the bigger picture as described by Mr. Roxburgh. Note all quotes below are from his publication.

Flaw 1: Overconfidence

We often make decisions with too much confidence and optimism as the brain makes us feel overconfident and over optimistic about our own capabilities.

Flaw 2: Mental accounting

Avoiding mental accounting traps should be easier if you adhere to a basic rule: that every pound (or dollar or euro) is worth exactly that, whatever the category. In this way, you will make sure that all investments are judged on consistent criteria and be wary of spending that has been reclassified. Be particularly skeptical of any investment labeled “strategic.”

Here I would relate to the difference in IT-spending and budget when you compare ERP and PLM. ERP spending is normal (or strategic) where PLM spending is not understood.

Flaw 3: The status quo bias

People would rather leave things as they are. One explanation for the status quo bias is aversion to loss—people are more concerned about the risk of loss than they are excited by the prospect of gain.

Another reason why adapting and implementing PLM in an organization is more difficult than for example just automating what we already do.

Flaw 4: Anchoring

Anchoring can be dangerous—particularly when it is a question of becoming anchored to the past

PLM has been anchored with being complex and expensive. Autodesk is trying to change the anchoring. Other PLM-like companies stop talking about PLM due to the anchoring and name what they do different: 3DExperience, Business Process Automation, …..

Flaw 5: The sunk-cost effect

A familiar problem with investments is called the sunk-cost effect, otherwise known as “throwing good money after bad.” When large projects overrun their schedules and budgets, the original economic case no longer holds, but companies still keep investing to complete them.

I have described several cases in the past anonymously; where companies kept on investing and customizing their ERP environment in order to achieve PLM goals. Although it never reached the level of acceptance and quality a PLM system could offer, stopping these projects was impossible.

Flaw 6: The herding instinct

This desire to conform to the behavior and opinions of others is a fundamental human trait and an accepted principle of psychology.

Warren Buffett put his finger on this flaw when he wrote, “Failing conventionally is the route to go; as a group, lemmings may have a rotten image, but no individual lemming has ever received bad press.”

A quote in a quote but so true. Innovative thinking, introducing PLM in a company requires a change. Who needs to be convinced? If you do not have consensus (which usually happens as PLM is vague) you battle against the other lemmings.

Flaw 7: Misestimating future hedonic states

Social scientists have shown that when people undergo major changes in circumstances, their lives typically are neither as bad nor as good as they had expected—another case of how bad we are at estimating. People adjust surprisingly quickly, and their level of pleasure (hedonic state) ends up, broadly, where it was before

A typical situation every PLM implementation faces: users complaining they cannot work as efficient anymore due to the new system and their work will be a mess if we continue like this. Implementers start to customize quickly and we are trapped. Let these people ‘suffer’ with the right guidance and motivation for some months (but this is sometimes not the business model the PLM implementer pushes as they need services as income)

Flaw 8: False consensus

People tend to overestimate the extent to which others share their views, beliefs, and experiences—the false-consensus effect. Research shows many causes, including these:

  • confirmation bias, the tendency to seek out opinions and facts that support our own beliefs and hypotheses
  • selective recall, the habit of remembering only facts and experiences that reinforce our assumptions
  • biased evaluation, the quick acceptance of evidence that supports our hypotheses, while contradictory evidence is subjected to rigorous evaluation and almost certain rejection; we often, for example, impute hostile motives to critics or question their competence
  • groupthink, the pressure to agree with others in team-based cultures

Although positioned as number 8 by Mr. Roxburgh, I would almost put it as the top when referring to PLM and PLM selection processes. So often a PLM decision has not been made in an objective manner and PLM selection paths are driven to come to the conclusion we already knew. (Or is this my confirmation bias too Smile)

Conclusion

As scientists describe, and as Mr. Roxburgh describes (read the full article !!!) our strategic thinking is influenced by the brain and you should be aware of that. PLM is a business strategy and when rethinking your PLM strategy tomorrow, be prepared to avoid these flaws mentioned in this post today.

tornado_butterfly You might have heard about the chaos theory and the butterfly effect ? In general, the theory promoted by Edward Lorentz and others, claims that the flapping of the wings of a butterfly, somewhere in South America may influence ultimately the path of a tornado, either preventing or accelerating that a tornado may hit at a certain place in North America.

WOW, if a butterfly can do this, can you imagine the impact of all of us, flapping our notes and plans around PLM in an organization ?  What a chaos we can create ?

I came to this association, looking back on my activities the past three weeks. Talking with implementers and companies, who all had a tornado of wishes and activities,  trying to create order through a PLM implementation – the anti-chaos theory.

Most of the discussions were based on a typical mid-market approach.

What do I mean by a typical mid-market approach – and I am generalizing here. None of the people I have been talking to in the past weeks match the exact characteristics, however all contributed to the picture in my mind.

shout_left

 

Typical mid-market approach (my generalization):

 

  • (Power) User Driven / Do It yourself approach – inside the organization there are people who have the dream to improve the company with PDM / PLM and the energy to prove it. They build the plan and define the solutions. External resources are only hired to do specialized services, fitting in the thought process of the power users. They believe that everyone will see the benefits of the implementation and join their approach step-by-step enthusiastically.
  • Focus on technical details– often the wishes are based on implementing technical capabilities close to the understanding of users, usually requiring a minimum of change in the daily processes. For example the focus might be on a technical capability how to connect the PLM system to the ERP system (Middleware / XML /Web Services / …..)  instead of discussing how it will work from the process point of view – how is the process impacted ?
  • Task solving – much in combination with the previous point, the focus is on optimizing and/or automating tasks of a certain user. The end-user’s daily tasks/pains are the focus for solving, which means trying to automate as much as possible, providing as much as possible single system / single screen solutions. 
  • Risk Avoidance – often these companies do not have the capabilities (people / time / budget) to experiment with new directions. Approaches from other similar companies are followed (looking for references). For sure not a bad approach, however the result is it will be harder to be differentiate from your competitors. And of course risk avoidance should always be considered in the scope of manageable risks.
  • Lack of top-management investment / push – although the top management in these companies subscribe to the needs for PLM, the focus of the investment is usually mainly on the external costs (software and services), where internal resources are forced to do the PLM activities beside daily tasks. Later the management will wonder why things are going slow, as they did their job (they approved the investment– waiting for the results now)
  • Focus on business skills – the people in the project team are often well educated in their daily business and practices, but lack project management, risk management and change management skills. These ‘soft’ skills are often acquired by buying a book to be placed on the desk.

observation

 

After writing these generalizations, I had the feeling that instead of characteristics, i was writing about risks . As this was not the intention, let see the how to manage these risks:

 

  • The power users should realize that they are sent on a difficult mission which requires a lot of creativity to implement changes in the context of the PLM project. And strange as it seems the PLM software might not be the biggest challenge.
    The biggest challenge will be on choosing the right best practices and to implement them with acceptance of the users. This is change management combined with implementation knowledge / experience. They point for the power users should be to have an implementation partner with experience, who can explain why best practices work and explain how other companies address this issue. Without practical guidance the power users have become pioneers, which is something the management for sure wants to avoid.
    Often to avoid user objections, the project team decides on heavy customizations or ‘weird’ compromises – nice to keep the user community quiet, but bad for the future, as benefits will not be the same.
    This mainly happens as there is too much focus the ‘hard’ side of the project ( hardware /software /IT /Services ) , and no or limited attention to the human / change management side.
    Power Users – be aware !
  • The management should realize that it is a company’s decision and vision. So from their side a steering committee with a clear vision is required. Their job is to keep the vision, prioritize the activities and make sure the power users are not creating an isolated solution based on their dreams.
    The most important role of the management is to take continues responsibility for the project – it does not end by giving the approval for the project and budget. Where users might reluctantly accept changes, it is the job of the management to enforce the changes and support them.
    This can be done in a harsh way by imposing the changes, however this will cause resistance and the end users will demonstrate the management was wrong. This leads at the end to a situation where the company as a whole will be in a worse position as before.
    So managing by motivation should be the approach, as after all the power lies in motivated users, who understand the benefits of the changes and benefits for their future job.
    Management – be aware !
  • Make sure the focus and priority is on business not on IT. Sell and explain the business benefits internally all the time.
    All be aware !

To conclude:

  • The mid-market characteristics look like risks for a successful PLM implementation, if not addressed and taken seriously
  • There is significant management support and control needed to monitor, guide and sell the PLM project.
    To make sure the company benefits are targeted and not the individual users or departments demands only.
  • Implement bottom up but control and direct top-down
  • Your implementation partner should have resources with skills for both levels – so not only programmers who can do miracles, but also consultants that can explain, validate best practices based on other experiences

 

Understanding chaos – enjoy:

Translate

Categories

%d bloggers like this: