Peter Drucker, the recognized management guru of the 21st century, talked about Knowledge Workers in his final work. Specifically he addressed the requirements for increasing productivity among knowledge workers; which ultimately is EAC’s goal – increasing productivity within product development.
To increase product development productivity there needs to be a focus on quality of output. Drucker contends that the quality of output is as important, and perhaps more important, than the quantity of output. If you find a mismatch between informational needs of somebody doing work and the information that arrives with them, then you have a problem. If that’s the case then the thing to do is take this problem, raise a flag, and move into the Continuous Improvement subsystem, which we will discuss separately. It is a critically important one of the three subsystems of The Product Development Operating System.
Also, please reach out to us if you are finding a wide gap between information needs and availability. We offer the tools and services you may need to close that gap and move to a better position.
Contact us to learn more about how Systems Thinking and the application of our Product Development Operating System can help your organization become more efficient, productive, innovative, and competitive.
Follow Bill at http://www.twitter.com/systhinking
In previous videos we talked about a framework we’ve developed for looking at product development as a system. In the last two videos and posts we talked about two of the subsystems, both of them flow systems, one being information flow and one being workflow. The third subsystem of the Product Development Operating System is the system of Continuous Improvement. This subsystem is often missing when we begin to work with an organization, and in organizations that are “committed” to continuous improvement; in many cases the efforts are ad-hoc and underwhelming
If you’re familiar with the works of Stephen Covey, author of The Seven Habits of Highly Effective People, you are probably familiar with his thesis about the tension between our urgent work and important work, and how our urgent work tends to overwhelm our important work. We see this in product development where we see continuous improvement as the important work. Often times it gets pushed aside and overwhelmed by the urgent work of completing projects.
Patrick Lencioni, an author whose work I enjoy reading, talks about the metrics of organizations. He talks about the ultimate metric of an organization as being the health of the organization. In our Product Development Operating System we see the health of your product development system as the ultimate metric of your productivity and effectiveness. It brings to mind the aphorism from Chinese medicine that says, “There is only one disease; congestion. There is only one cure; circulation.” The circulation in product development is the flow systems. The Continuous Improvement subsystem is the system for increasing the overall health of those flows, of the system, and the effectiveness and productivity of the product development system.
The Continuous Improvement subsystem of the product development system has three constituent parts. Each one aligns with a different tier of the organization. There is Strategy. This aligns with the executive tier. The executive tier looks to build a shared vision; a vision of the future of the organization that, collectively, we’re all working to realize. Another element of the continuous improvement subsystem centers on subject mater experts and the increasing their expertise, their development, and the deepening of their expertise and the expansion of competency within the organization. The third element in the continuous improvement subsystem is the importation and development of a root cause problem-solving methodology, specifically one that is appropriate for knowledge workers — the workers that populate product development.
If you bring improvement energies to your product development system, you need to bring a certain threshold of energy just to maintain your current state. If you will, to counter balance the destructive work of entropy. To make significant and continuous improvement you need to invest more energy into the subsystem. You need to invest significant energies into a continuous improvement subsystem that will eventually lead to increased productivity and increased effectiveness of your overall product development operating system.
Contact us to learn more about how Systems Thinking and the application of our Product Development Operating System can help your organization become more efficient, productive, innovative, and competitive.
Follow Bill at http://www.twitter.com/systhinking
Imagine getting a text from your equipment in the field telling you there’s been a problem. Not too far of a stretch, right? Well, let’s take the situation a bit further. What if you get an unsolicited thank-you email from your customer who was excited about how fast their last service call went since the service rep had the right parts for the particular problem on the machine. That’s because the cloud-based machine monitoring system had automated communications between the equipment, the supply chain, the service reps truck inventory and the recent training the rep had completed for just this situation. Even further, once on site, the rep pointed an iPad at the equipment and the video displayed an augmented reality video of the machine with overlaid graphics showing both the internal geometry and streaming sensor data indicating the problem and highlighting failing parts. Here’s the kicker — when the rep clicked on the screen to see the details of the issue, a ‘how-to’ video popped up on the screen to step the rep through the repair. By the way, did I mention that the issue was predicted by a different cloud computer monitoring huge stores of data and ‘learning’ while it’s predicting issues?
Ok, so I’m not much of a science writer, but it doesn’t matter because this isn’t ‘the sci-fi of the future.’ This is today. This is what the Internet of Things looks like, and it’s both growing and accelerating. Last week, I attended LiveWorx ’15 with 2500 other like-minded professionals. This PTC Internet of Things conference had another 5000 in attendance virtually as the Boston venue had sold out locally. It was pretty obvious that the buzz continues to grow around this topic and that we’re all interested in growing and accelerating business and product development leveraging these technologies.
While some of the technology and science behind cloud computing is ground-breaking and game-changing, it’s not just about the technology. That’s why having both a business and product development strategy are just as important as integrating the technology into the products. At EAC, we’ve been developing products and helping others do the same for the last 20 years. We’re especially excited about helping companies build and execute their IoT strategy since the opportunity and impact are only limited by the imagination. We’re talking about deeper engagement with customers, reducing operating and service cost, new revenue streams, even products that tell product managers and engineers what customers want in additional functionality or how they’re using your product today. If you’re considering developing or leveraging smart and connected products as a part of your product development and business strategy, we’d love to hear from you and partner with you along the way. If you’re not planning out an IoT strategy, we should talk.
EAC Product Development Solutions is a Minnesota based company providing engineering and product development software, service and consulting to the discrete manufacturing industry. Rob is currently leading the EAC business effort related to product development for the Internet of Things. You can reach out to us here!
Recent posts have talked about Systems thinking and introduced the concept of The Product Development Operating System framework.
I’d like to present one subsystem of The Product Development Operating System, that being the Workflow subsystem. In a previous video in this series we talked about how companies evolve into The Product Development Operating System. I’d like to use the workflow subsystem to demonstrate that.
When a company is founded an entrepreneur will have an idea that fills a market need. He or she will hire some engineers to work on this idea. The engineers will develop the design and work directly with the entrepreneur to bring the product to market. This exercise of product development is raw innovation — just bringing a new idea to market through the innovation that is usually done within the product development process.
If the organization is successful and survives, it will grow. As it grows in size and complexity there becomes a need to organize the members of product development into functional groups. Simultaneously there arises a need to provide coherent management and leadership for the engineers. This is the second element of the workflow subsystem – Leadership. As it evolves, you now have a Workflow subsystem for Innovation and a subsystem for Leadership.
As an organization is more successful it will have more opportunity for market penetration, but it will have limited resources. So, it needs to make careful investment decisions about which projects it will develop and which opportunities it will forego. These Investment Decisions are the third step in the evolution in the workflow of product development.
When all three Workflow subsystems have been created, you will have a part of the organization making Investment Decisions, which then triggers work to be done by the Leadership of product development to organize efforts that will generate Innovation within a project that will deliver a product to the market.
Investment Decisions, Leadership, and Innovation. Those are the three parts of the Workflow of The Product Development Operating System.
Contact us to learn more about how Systems Thinking and the application of our Product Development Operating System can help your organization become more efficient, productive, innovative, and competitive.
Follow Bill at http://www.twitter.com/systhinking
Today we’re going to talk about the Information Flow subsystem of EAC’s Product Development Operating System.
Pre-1980 there were no IT groups and there were no great numbers of knowledge workers. With the emergence of the computer and the dawning of the information age there was an explosion of IT tools that transformed business systems. In the product development business system these tools initially focused on helping the individual. We had CAD and CAM tools for helping mechanical and electrical engineers. We had tools that applied synthetic annealing to optimize optic design. And we had tools that helped simulate or analyze the designs that came forward.
More recently there’s been an emergence of more complex tools that facilitate product development — Product Data Management, tools for collecting and archiving project information, and a variety of tools that help support decision making in product development.
Product development is a knowledge centric function of the organization, but the topic of knowledge management itself is one that spreads in a lot of directions. If we look at the IT backbone that supports knowledge management; that topic converges on a small number of complex, connectable, but functionally focused IT systems.
We’re all interested in making informed decisions. That being decisions that are supported and influenced by accurate real-time information. This requires the ability to get the appropriate information to the decision maker at the right place, at the right time. This is the goal of the Information Flow subsystem.
This Information Flow subsystem is also a subsystem of your IT system. In both of these systems there are two critical jobs for the subsystem. The first is to support the goals of that system itself. The second is to look at the interaction between this subsystem and the other subsystems within its parent system; those being the IT System and The Product Development Operating System.
Here at EAC we’ve been devising a visual model to help you remember The Product Development Operating System. In this model the Information Flow subsystem is the foundation. It’s so critical that it supports the rest of the system. In knowledge centric product development a strong information flow is critical to inform the decisions that are made in both the Workflow subsystem and the Continuous Improvement subsystem. Without it, we have nothing.
Contact EAC to learn more about how Systems Thinking and the application of our Product Development Operating System can help your organization become more efficient, productive, innovative, and competitive.
There’s a lot of buzz these days about leveraging the internet and the ‘cloud’ for business — especially in the realms of product development. Phrases like Internet of Things (IoT), Machine 2 Machine, Product as a Service, Internet of Everything, Cloud Things, Connected Products and others get thrown around daily. Regardless of the term you use, the real intent of any of these IoT projects is to generate some additional value. That could be from more capability, deeper customer interaction, predictive maintenance, new revenue streams, market share, knowledge of how the product is being used or many other scenarios. I thought it would be fun to leverage it for gardening!
This time of year, there are a lot of northern gardeners are doing a dance with garden plants they’ve started from seed while winter was still rolling along. Now the seedlings want to be outside in the sun, but its too cold at night. The plants are getting crowded and too big to park in a window in the living room. Build a plastic tent outside as a make-shift greenhouse and it’s too hot during the day. So you’re left with shuffling the plants inside and outside to follow the spring sun and avoid a late frost. But how do you balance this while keeping your day job?
Enter the IoT and a little project in our parking lot… With a little creativity, some parts we had around and a few extra parts from the thrift store, we built an ‘almost’ free greenhouse we can monitor through any web-browser. Our interest at first is simply to monitor the temperature, relative humidity and light level both inside and outside the greenhouse. It’s fun to see the values ebb and flow with the day and with the weather. This was achieved through an Ethernet connected Arduino wired to a photoresistor and a pair of DHT11 Digital Humidity and Temperature sensors. Currently the system feeds into ThingSpeak for graphical representation with plans to port it over to ThingWorx in upcoming days.
Since the sun is hot this time of year but the cold weather isn’t over, we’ll likely experience some high temperature spikes and some cold nights that could damage the tomatoes. This brings up phase 2 — ‘control.’ Our near term plans are to have powered ventilation and heating to kick in either by reaching through the internet or with the internal controller. Eventually we’ll get to a fully autonomous greenhouse that manage temperature, have sensors in the soil monitoring moisture and turning on/off soaker hoses and misting fans all the while keeping us informed on a smart phone. Those are going to be happy tomatoes with their own twitter account…
Maybe all this tech and automation will take some of the fun out of gardening and fiddling with the plants to get it ‘just right’. What’s more likely is that it will just encourage the acquisition of more plants and the need for a bigger garden and a bigger greenhouse with more automation — but that would be fun too…
EAC Product Development Solutions is a Minnesota based company providing engineering and product development software, service and consulting to the discrete manufacturing industry. With 20 years of product development experience, EAC is seeking to help companies that desire to get more from their products through the IoT. We engage in all aspects of product strategy, product design and enabling technology to achieve those goals. Please contact Rob at rmiller@eacpds.com to find out more.
