Posted By Christine Longwell

One of the major objections to implementing a PLM system is that it is going to tie a creative organization into a structured workflow that can slow down their process and ability to react.  If the process is too strictly structured, people start looking for ways around the process when “special situations” arise.  A major deadline, build stoppages on the manufacturing floor, unexpected audits, or irate customers can all be reasons to go around the process and not wait for the standard Friday Morning design review meeting to get designs released.

What if we assume that every design change is driven by a special situation, and allow them to all “flow” naturally?  I believe it’s possible to use tools that facilitate real time, collaborative communication and status on issues to treat each problem differently, and come to the right solution more quickly. 

The argument is that employees are lazy, and no one will do anything unless they are told to do something.  I just don’t think that’s true anymore, and Daniel Pink agrees with me in his book Drive.  Today’s workforce is driven more by pride of creativity and accomplishment than simple financial incentive.  Treat your employees like children, and they will act like children.  Allow them the freedom to accomplish a task in their own way, and they will naturally work harder and do whatever it takes to accomplish their goals. 

The next natural question is that of issue ownership.  Without workflow, how do you know who has ultimate responsibility for an issue?  My thoughts are that an organization can be like a sports team, where responsibilities can be clear, with motivated players.  If you had to constantly tell your outfielder explicitly to catch the ball when it comes towards him, would you really keep him in the game?  Putting the right people in the right jobs and providing the right tools can truly yield a lean, efficient environment for true productivity. 

 
10 Comment(s):
Christine said...
Thanks everyone for your comments. They are all good, thought provoking points. I think this is the start of a great discussion that I hope to revisit soon. I think this discussion easily goes beyond technology, and begins to address some interesting ideas in corporate organizational theory. On one hand, I agree wholeheartedly that all engineering changes follow a “Process”. I’m a true believer that everything is a process, but it just so happens that the frequency that the “process” is unique is fairly high. On the other hand, I think that we have “gut feelings” that drive engineering changes. I’m not saying those are bad, but rather that designers instinctively understand the product criteria that are important, and fight to justify that intuition to the organization through official channels. I think we owe it to our engineers to encourage them to explore these intuitive design changes without the burden of formal justification.
January 1, 2011 05:04:07
 
Carlos Benassi said...
Hi Christine and all, great point. I`d like to add something from south america. I`m implementing PLM systems in Brazil for a reasonable time and my concern is: we do need structured workflows. The reason is, unfortunately in Brazil at least, we don`t have enough skilled people (e.g. organized, pro-activity, responsible). The ISO 9000 quality system shows to kinds of process. The first is a quick release process and the second is a 3 step process (edit, verify, approve) evolving at list 2 people, so I believe that both process can hold the special occurrences and the daily load. You just need some looking for the special is not 80% of the situations
December 10, 2010 05:30:27
 
Nitin said...
@Christine - you brought up a very good point. However having worked on shop floor and in design, honestly speaking it's difficult to digest. The main issue in most of the manufacturing firms still remain the people's issue, except to name few. It's very difficult to deal with them and most of the times you find yourself ego's attached to employees suggestions. Conditions become worse on shop floor and everybody wants to make thing work as they are or they can see production line sloggin! I still believe that you need to have some well defined processes to help management take informed decisions and yes employee who understand freedom of executing things in their own way should be allowed to do so but if they show sense of responsibility. @Scott - I like your comment - "a squirrel by any other name is still a squirrel".
December 9, 2010 12:00:36
 
Vuuch said...
Most if not everything done in a design project CANNOT be accomplished using Workflow. Workflow is reserved for repeatable things and lists are used for innovation. Every design team manages issues, tasks and things that need to be evaluated using lists. Although a workflow maybe used to process a release or a change it will never be used to design a part.
December 7, 2010 05:35:36
 
prashant said...
I agree with you, not all the activities in an organization are structured that doesnt mean they are wrong or right but mostly depends upon how they would like to adress the issue in hand. organizations should have more freedom in desgning and definng their processes. This theory is interpreted in drools flow engine as case management. You could find more information at drools blog. http://blog.athico.com/2010/11/towards-case-management.html
December 6, 2010 09:24:06
 
Christine said...
Chad, I agree that Engineering organizations are more under resourced than ever in this economy. Clear issue tracking in a centralized, visible, and easy-to-use format is a great way for collaborators outside of the engineering organization to realize just how thinly stretched their technical staff is.
November 28, 2010 06:56:06
 
rick holl said...
you propose an interesting theory. i find that it may be true given healthy workforce. too often, society does not prepare people to be responsible for themselves. lack of maturity creates other problems. all create a very negative environment. better, to train for the characteristics of responsibility, maturity and more.....and then let them unfurl their wings, and fly high in creative effort.
November 21, 2010 02:21:05
 
Chad Jackson said...
I like your thoughts here Christine. The only mitigating factor in my mind is that engineering projects are so understaffed and, as a result, there are so many firedrills that engineers aren't acting like children when they can't resolve or take ownership of an issue. They just don't even have time to be aware of every issue. I do think that's where so sort of centralized issue management technology can be helpful. Maybe it's a focus on centralized management to pick up ownership as opposed to driving the process? Good discussion.
November 17, 2010 02:46:45
 
Scott Wertel said...
Very thought provoking post. I agree that there will be tools available for more brain-mapping workflows instead of linear workflows, but a squirrel by any other name is still a squirrel. Implementations have gotten too complacent and accepted the 80/20 rule for so long they think it needs to be that way, and that the remaining 20% is too costly to pursue. If blindly following a rule of thumb, and you can't achieve a workflow that covers 90-99% of your business -- even the special ones, then it is your business that needs to be reviewed, not the workflow.
November 4, 2010 11:03:25
 
Jeff Sweeney said...
If you find your workflow is slow and cumbersome during emergencies maybe it is impeading you too much during normal times too? Another way to look at it...If it isn't adding value even in special times is it ever adding value? I do like your sports analogy, workflows do make it easier to ensure everyone is on the same play.
November 4, 2010 09:58:26
 
Leave a Comment:
Name: * Email: *
Home Page URL:
Comment: *
   char left.

re-generate
Enter the text shown in the image on the left: *
 Remember Me?
* fields are requried
    


 
Google

User Profile
Christine Lo...
christine@lo...
Anderson SC

 
Archives
 
Links
 
Visitors

You have 49251 hits.