This week I realized that, although I believe the benefits of PLM are more and more accepted in mid-market companies, the decision how to start and where to start with PLM is often not clear. I recognize several approaches which I will describe in this and some upcoming posts.
All persons in this post are fiction and in case you recognize these persons in your company, it is pure coincidence. Instead of talking about approaches,I was tempted to call it strategies, but when you read my observation you will realize the word strategy would not fit.
Approach 1: The silent PLM
Inside our company, often there is an engineer or an engineering manager, who got caught by the PxM virus. The PxM virus is a modern virus, which makes you a believer that PDM or PLM will bring your company a lot of benefits. Documents and proof points of the severe impact exist all around the world. However nobody has gotten infected so far in this company. Everyone is working the way they worked since many years and life is secure and predictable.
Now this infected engineer is getting exited and dreams about the introduction of PLM in his company and how he will become the hero of the company and gets a big promotion. Unfortunate for him in this kind of business there are no big bonuses to collect, so the honor of promotion is already a big achievement.
So the first thing this engineer does is chatting with his peers and friends to find out where PxM has been implemented successful and he studies some success stories which he learned from his network.
Now the challenge starts.
He goes to the management and shows a nice PowerPoint, explaining why the company needs PxM and what are the expected benefits, based on reference stories. The management has no real clue what he is talking about, but it looks promising and they allow him to select a PxM system for his department and to start a pilot.
The engineer already knows which PxM system to choose. The one, recommended by the friendly reseller, who sold them their 3D CAD system (which is a success) and worked hard with him to finalize the slides. As requested by the management he had to invite two other PxM vendors to make an objective selection and at the end an impressive comparison matrix is shown to the management why system A has been chosen.
Now the implementation starts and step 1 is very successful. The document management part around the CAD system goes smoothly and everyone in the engineering department starts to be happy.
Following this successful implementation there are two options:
- the engineer does not get promoted and the implementation ends. It will remain a silent document management implementation and the dream is put aside.
- the engineer gets promoted and continues to push his vision as now he has a broader audience to spread the PxM virus. We will follow this story line…….
The engineer gets promoted and continues to push his vision
This is the best that can happen and the engineer, who now became the head of engineering, starts to express his vision to his fellow managers, explaining the advantages of PLM. Notice, he is now talking about PLM as the scope has been extended beyond product data management, involving other disciplines in the organization.
And here the head of engineering discovers that his fellow managers are also infected by a virus. Not the PxM virus, but one of them has already for many years the ERP virus. And as the ERP virus addresses the operational and financial tasks in the organization, the management trusts him. The sales and marketing department seems to be infected by CRM, but currently they caught a social disease, which made them push for all kind of communities. The management either likes it (as their kids are also on Facebook) or dislikes it, because they believe work is a serious business and being on internet all day is considered gaming.
So the head of engineering realizes that he has some freedom within his department, but the other departments and the management have their own priorities. And PLM is not on their list. Together with the friendly CAD reseller, who meanwhile was promoted to be Senior PLM Consultant, they work on a perfect PLM environment within the engineering department and they believe their success will show off in the upcoming years.
And then the crisis came and the company had to cut budgets. To be continued in (hopefully) 1 or 2 years
Conclusion: The silent PLM approach has a huge chance to fail as there is no corporate vision and management push to get PLM implemented. PLM should be addressed top-down. As in many mid-market companies there was also no strategically partner, who could assist the management to build a vision and to set priorities.
Next week:
2 comments
Comments feed for this article
September 22, 2009 at 8:14 am
Oleg Shilovitsky
Hi Jos, I’m looking forward approach #2, but one question before. Why do you think the situation is unique for SMB? Don’t you think, with some application of scale, it will be the same for bigger companies too?
Best, Oleg
Oleg hi, I believe especially in SMB there is no strategy layer or cross-departmental analysis / vision which you often would find in bigger companies. But of course also bigger companies can lack this layer
best regards
Jos
LikeLike
September 25, 2009 at 2:37 pm
Joy Garon
Oleg/Jos,
I agree that a lack of strategy and commitment from the top can lead to failure. In my opinion, it would be easier to sell a solution to the management teams of small companies if you could guarantee fixed costs (both initial and recurring) and minimal, predictable impact to current resources. That’s a pretty tall order today…
Joy
Joy thanks for your comment. Indeed I assume this is what small companies expect. And a PLM project should be done in these small packaged steps – rule of thumb 3 months impact – max 30 services days. The challenge remains to orchestrate these PLM steps when they become cross departmental
best regards
Jos
LikeLike