“Simple” and “easy” are words that resonate universally. Albert Einstein famously said, “Make everything as simple as possible, but not simpler.” The examples of how designers making complex decisions are everywhere. I like those coming from Seth Godin’s blog – As simple as necessary (but not simpler).This wisdom applies perfectly to PLM processes and software.
Everyone remember that simplicity is the ultimate sophistication (usually credited Leonardo da Vinci). Whether it’s choosing a new app or making a decision about optimizing the product development process, planning product data management, document management, or the entire product lifecycle, everyone gravitates toward these ideals.
If you check PLM vendors’ marketing materials, everyone is advertising an easy and simple PLM system. For years, product lifecycle management (PLM) was associated with being complex and expensive. Thinking about the entire lifecycle of product data, multiple business systems, and business processes can be intimidating. Over the last decade, PLM vendors have changed their attitude to focus on better user experience and a modern PLM software and PLM technology that is easy and simple. You can hear about simple data sharing, easy access to up-to-date information, and the organization of engineering processes.
But are “simple” and “easy” the same? I found that it is important to understand the difference and it can help you to clarify your PLM strategy and selecting PLM software that works for your organization. Let’s break it down.
Simple and Easy: Two Sides of the Coin
At first glance, simplicity and ease might seem interchangeable. But they are not. Here is my take: simple refers to the design or structure of a process or tool, while easy refers to the experience of using or adopting that process or tool.
PLM Strategy
Simplicity:
A simple process eliminates unnecessary complexity while retaining essential functionality. However, simplicity alone is not enough. The process must also be easy for users to adopt and follow. This requires a nuanced understanding of user behavior, organizational culture, and change management.
When designing processes, consider whether steps are intuitive, if redundancies exist, and how to provide clear guidance and support for users. The challenge lies in balancing – a process can be simple on paper but difficult to embrace, or simple to adopt but overly complex, leading to inefficiencies.
Ease:
An easy PLM strategy focuses on communication and adoption using intuitive tools, straightforward workflows, and user-friendly interfaces. With accessible platforms and preconfigured templates, it ensures quick alignment across teams, reducing resistance and accelerating implementation for seamless collaboration and long-term success.
PLM Software
Simplicity:
In software, simplicity often refers to the number of features or the overall design philosophy. Software with fewer features can encourage adoption by reducing the learning curve, but a lack of essential features can limit functionality and create frustration.
Choose software that provides just enough functionality to meet your needs without overwhelming users with unnecessary options. This ensures simplicity serves your goals rather than hindering them.
Ease:
Ease of use is about how complexity is managed within the software. A feature-rich PLM solution can still be easy to use if it’s designed with usability and flexibility in mind. Intuitive interfaces, clear workflows, and minimal administrative overhead make the adoption of complex systems smoother, ensuring users can harness the software’s full potential without frustration.
What is my conclusion?
Simple and easy are not the same, and their roles in PLM implementation must be approached with clarity. For processes, prioritize simplicity to eliminate unnecessary steps while ensuring ease of adoption through proper training and support. For software, choose solutions that strike a balance: simple enough to avoid unnecessary complexity, but easy enough for users to engage with effectively.
Ultimately, the goal is to create a harmonious synergy between process and software – one that aligns with your organizational needs and drives PLM success.
Just my thoughts… what are yours?
Best, Oleg
Disclaimer: I’m the co-founder and CEO of OpenBOM, a digital-thread platform providing cloud-native PDM, PLM, and ERP capabilities. With extensive experience in federated CAD-PDM and PLM architecture, I’m advocates for agile, open product models and cloud technologies in manufacturing. My opinion can be unintentionally biased.
