Month: February 2014
What comes to your mind when you hear that word? Are you jubilant in the comfort of knowing exactly what the next step is, or are you feeling claustrophobic because your creativity just got hog tied? Lean evangelists live by process because what can be identified can be measured, therefore evaluated and improved. Creative types reject process because you can’t schedule innovation, you can’t track and improve original thought. A good Product Developer can meet in the middle, or swim in both lanes when needed.
I would consider myself a lean advocate, not a lean evangelist.
Back to process. Process is a step by step instruction to accomplish a task. Processes can include steps taken by one person or a group of people or resources in a defined sequence. Line a number of processes up and you get a workflow, or a scenario that starts with a certain input and produces a packaged outcome. In a manufacturing sense, think about assembling a pair of scissors. The processes may include steps to procure the raw materials, steps to deliver the materials to the assembly line, steps to assemble the scissor halves together with a rivet, then steps to test the scissors for form and function, then steps to package the finished scissors for shipping. This is very linear, very repeatable, very consistent.
The beauty of this process is that each step is measurable, you may know exactly how long it takes to attach the 2 halves together with a rivet. This allows you to match the processes before and after the assembly steps to maintain a steady flow of goods. It takes 30 seconds to assemble, but 1 minute to pick the parts, then you need 2 resources picking parts, it’s that simple. Once the steps are measurable, you can adjust the steps and see how they affect the process, then adjust the other processes to match.
Some might think, “This process stuff is great!” but in the world of Product Development and Design things get grey. The benefit of process is repeatability and predictability of the workflow, but the downfall is the loss of flexibility to deal with variation. Lean principles offer a quiver full of Six Sigma tools to eliminate variation, but variation is what the design cycle is all about. On the flip side, those who refuse to accept process can tent to get lost in the weeds, particularly creative types who can’t be bothered, and should not be bothered by the details.
My take on process in design cycle? A good process should have minimal steps to accomplish the task. An effective process should clearly set the inputs, provide milestones and allow deviation between those steps for personal creativity and experimentation, and define the final expectations. “This is where you are, these are things you need to hit, there is where you need to end up. Figure out the rest. Have fun along the way, keep me posted.” One key from Lean principles that I am a fan of is the revision of process as requirements change, or as innovations occur.
What steps within the design cycle are process-able? I will leave that for another day.
What I do know is that I struggle with process on a daily basis. What are your thoughts?
How often have you heard that and thought it was just lip service? How often are you given a tight deadline, only to have the delivery date get moved up? How did you feel about your boss, your team, your organization and the quality of your work product when you got pushed to delivery early? Irritated I assume, along with a variety of other emotions. In the product development field I feel these emotions almost daily, and I hear these emotions verbalized from my team all the time.
Why are we in such a hurry all the time in business? Competition of course, doing things better than the next guy.
The reality of Product Development is that the products of today are the Ideas of yesterday. Good product concept guys are thinking 5-10 years out. Good Product Management guys are looking 1-3 years out to commercialize products. Good Product Development teams have design cycles in the 6 month to 2 year range to release products to market. Operations now require time to ramp up the supply chain to get the product to the end user; this may take 3-6 months or more depending on the product. In today’s world this is not a linear process, which means every stage of the product life cycle overlaps in order to crash the overall schedule. Supply Chain starts working before the product gets released; Product Development teams begin foundation work before Product Management gives the green light for development, and so on. AT the end of the day this means that innovative product ideas are old news by the time they hit the market.
What’s the problem then, every organization has to deal with the same cycle right? Wrong. Larger organizations may have the engineering might to overcome problems quickly, but have too much process to react quickly. Smaller organizations may have more flexibility to react quickly, but may have limited resources to overcome obstacles outside of their core competency. The key is that the first one to market has the advantage, either as the product leader if it is successful, or as a product killer if the product is rushed and fails to wow the consumer.
The old adage, “Loose lips sink ships” is a huge issue in the design cycle. As time goes on, information gets out. Through employee interactions within their community conversations, through vendor interaction, through supplier co-development, or a number of other innocent or nefarious means. A simple example of this is in prototype development. Most firms use outside companies to fabricate prototypes and fixtures for products in development. Guess what, other firms also use these outside companies, it’s not hard to walk through a fabrication shop and peek at other firms products in fabrication. It’s a reality that good ideas are discovered by competing firms, and if the idea is good enough it is almost guaranteed to be integrated into their next product.
Back to speed here, the best defense is a good offense. The risk of a product being copied, beat to market or missing the market timing gets significantly greater the longer the product is in the development cycle. Unfortunately this big-picture message can get lost to the troop on the ground, the engineer in the cube or the tester in the lab who is only hearing the whip get cracked. Hopefully this helps put a little bit of rhyme to the reason.
Remember, the first one to the finish line wins!
Did you find this conversation helpful? Please leave a comment.
Here I am sitting in a hotel room in Bandon, Oregon, overlooking the beach and crashing waves. I’m pretty excited this morning, because low tide is in 20 minutes and I’m ready to go tide-pooling with my dog. Problem is that there have been gale force winds all night and the rain is horizontal. I can hardly see the beach, but can sure hear the breaking waves. I guess beach combing is not on the docket for today.
Yesterday went a little more like plan on our little holiday, my wife and I visited the Evergreen Museum in McMinnville, which was an impressive collection of aircraft, space vehicles and a water park. The water park seems a bit random, but hey, it works. The claim to fame for the Evergreen Museum, besides the Boeing 747 parked on its front lawn, is that the main building was constructed around the Spruce Goose, the largest all-wood airplane ever built, and briefly flew in 1947.
If you are not familiar with the Spruce Goose, you can read about it here. The Dime Store description is that it was the largest airplane built for its time, and remains one of the largest built to date. The scale of the project is amazing, and standing underneath the wingspan is impressive. The brainchild of Howard Hughes, it was built in 1943-1947, it is an aquatic plane that weighs 300,000 pounds, the wingspan is more than a football field, 8 propeller engines and was intended to carry 750 wartime troops. Most unique is that it was built entirely from wood due to war-time material shortages, using construction techniques developed for the project.
I am fascinated by this undertaking, given the scale and the timeline that was achieved at this time is history. The typical design cycle that I drive towards for a new slot machine product is 14 months, which historically gets compressed to the 8-10 month time frame from concept to production. This is today, using today’s technology of solid modeling, rapid prototyping and electronic simulations. All of these tools have evolved over the years specifically aimed at reducing the time to market. How were Hughes and company able to pull off the Spruce Goose in 4 years, napkin sketch to first flight?
I understand it’s a matter of resources, larger projects need larger resource pools. Of course the more people you throw into the kitchen the greater level of coordination and bureaucracy are required.
How is all of this relevant? For me it is a wake-up call when faced with deadlines and design specs that seem unrealistic. No matter how large the task seems, look back at history and see what was accomplished. Another take-away for me is that better tools are not the only answer, we often fall into the ‘if I only had XXX, I could meet the challenge’ trap. Hughes carved he largest plane in history from a pile of lumber for crying out loud. Hughes also did not get wrapped up by roadblocks, instead he innovated solutions to work through, or work around the challenges.
I’d like to think all challenges are overcome-able, although it may take a little work.
What are your thoughts? love to hear them, please leave a comment.
Products. Every put much thought into them? Sure, if the gizmo you just purchased is fantastic you might tell a friend. If the widget you are playing with is a piece of crap, breaks or does not perform you might tell the world. Beyond the user experience, have you ever thought about how that product was conceived, designed, developed, manufactured, packaged, shipped, presented or installed and made available for the ultimate durability test—–meaning you the consumer?
Before I got into the industry of product development I had a pretty naive view of things. I took for granted the development effort and extensive supply chain that sat behind that new GI Joe figure that was hanging on the store rack. Funny how we form our early views, I recall watching the Tom Hanks film Big when I was 13. The film was really not my cup of tea at that age, heck, I don’t remember much about it at all except for a little snippet when Hanks and his young costar were in FAO Schwarz critiquing toys. The younger star declared that this little toy robot only cost a dollar to make in China and it was selling for a lot more than that, how is that fair? Funny how a 30 second clip can form a long-term splinter in your mind, all I know is that I was pissed the next time I went to the store and that GI Joe was $8.
A few years down the road I have realized that every product, either on the shelf or in your home, or even dispensing soda at your favorite junk food place has an entire history book of product design behind it. It’s not magic, it took work! Now I flip my mind to the dimension of supply chain and backtrack the transportation, packaging, assembly, etc, etc all the way back to the minerals being dug from the earth or grown from seed. Wow.
Contrary to 12 year old logic of Hanks and his little costar, I am not just paying for the manufacturing cost. I am paying for the history, the effort, the labor, the whole chain. Now when I look at the GI Joe (and I still do look at toys, BTW), I wonder how it’s possible that they are so cheap!
What’s your gut feel when you are out shopping around? Do you see an overpriced piece of plastic or do you see the momentous effort it took for it to get there?
Let me know what you think.
Continuous Process Improvement (CPI), what is it and why should you care?
Aside from what can be gleaned from it’s super-sexy namesake, the term CPI is probably fairly foreign to those outside of the Supply Chain field. In everyday life though, I’d like to think most folks practice some facets of CPI in their normal routine. Look back into your own habits, actions or activities from the past, can you pinpoint something you tried and it turned out right, correct and perfect the first time? Balancing your checkbook? Creating a recipe? Riding a bike? Studying for that big exam?
CPI, at a personal level is embedded in the learning process. Activities that a person engages in, specifically repetitive activities seem to get easier over time. This is most likely explained by trial and error, persistence and experience; building on what works and abandoning what did not. I watched my daughter teach herself how to bake, it took quite a few batches of cookies until she nailed a consistent recipe for success, now she sells her cookies for $.25 a piece at her high school, go figure. Other activities can have more direct learning curves, such as riding a bike. Falling down hurts, and pain happens to be a pretty powerful and effective teacher, the rider learns quick what works and what does not. Jumping forward a little bit, the cues and challenges of activities will evolve over time. Once the rider masters the ‘survival skills’ to prevent skinned knees, he is off to work on curb-hopping and skids.
Again I pose, why should you care? This seems so obvious.
In the business world there can tend to be a certain level of stagnation of progress in many fields, particularly repetitive plug-and-chug type disciplines. Operations, Manufacturing, Accounting, even some portions of the Product Development Cycle can tend to follow a prescribed routine that has been trained in, passed down and maintained across organizations and across disciplines. New Product Design tends to be exciting and innovative, think iPhone, think Corvette, but after the initial ‘wow’ of the concept, Engineers skilled in the trade work to grind that concept into a commercially viable product. We Engineers have learned how not to skin our knees, but taking it to the next level is the key to increasing the company’s value.
CPI was born in manufacturing as a method to identify and measure steps in the process, so that logical decisions on those steps could be made to make the whole system work better. Why not use CPI concepts in the Product Design Cycle, where they fit, before products hit the manufacturing line?