Many years ago, one of my mentors told me that “the worst pencil is better than the best memory”. I liked it. Since than, I have no trust in remembering things. I started to take notes. I switched to be completely paperless 4-5 years ago. The biggest problem on my way to become completely paperless was the ability to capture information at the time you need it coming from multiple sources. Finally, iPhone and combination of apps allowed me to create an environment where I can keep track of my activities and get access to this at any time.
Engineering people are bad organized (please, don’t take it personally). Processes and work planning are not going well with engineers designing and creating new products. Companies tried to create innovation process management software, but in my view it was very unsuccessful. At the same time, I can see a need of engineers to capture information alongside their everyday activities.
One of the products I’m using to capture the information on a daily basis is Evernote. It supports many ways to capture notes using web and mobile versions including capturing of videos, pictures, website links and many others. Combined with search function, it helps to keep things organized. Evernote is not alone in this market. Two additional notable companies in this space – Clipboard and Snip.it. The last one was snatched by Yahoo few days ago. Watch the following two videos if you are not using similar products in your life.
From Personal to Collective Memory
I found a total absence of tools that can help engineers to capture their everyday working activities. Of course, engineers are not prohibited from usage of Evernote, Google and many other tools. At the same time, one of the key elements in capturing the activity is contextual relationships to information. In case of Evernote, it is photo, voice memos, videos, etc. To make engineering and design context capturing can be an interesting opportunity, in my view. They key element is efficiency. Engineers won’t tolerate even additional 30 secs of their working time. However, to memorize design idea, concept or decision can be extremely powerful.
The next interesting step can come with the ability to provide information around a particular item, drawing, product, customer, etc. collected by different people in organization. Such type of clipboards can become a sort of collective memories. The potential value can be significant – lost ideas, forgotten decisions, potential customer problems and many others.
What is my conclusion? Our memory is not efficient. To be able to capture information around engineering and design activity is still very untapped place. Usability is a key. Vendors can learn from tools like Evernote and others how to create a tool you can use in your everyday life in any environment. Just my thoughts…
Best, Oleg
Image courtesy of [keattikorn] / FreeDigitalPhotos.net
PLM is all about process management. This statement comes to the play when people explain the value of PLM in the organization. Usually, when you think about process management, your mind is switching to some kind of “workflow thinking” mode, which assumes you need to follow the process from state to state by accomplishing tasks and activities. In every PLM implementation, this is a moment of time, people ask – how do we manage engineering processes? What toolset we need to have to make it happen?
Enterprise software is a complicated beast. PLM is not an exclusion from the list. Despite demands to be simplified and become user friendly, the majority of PLM implementations require long preparation, planning and implementation phases. However, this is only a visible part of the iceberg. The invisible part (and probably mostly important) that many people are rejecting to use data-management software. If you speak to engineers, they can tell you how they hate everything that makes their lives very complicated. Here is the question I can hear many times in industry discussions, conferences, dispute and blogs – how to get engineers to use PLM software?
). This is my favorite passage:
