Where lean product development experts and practitioners share their stories

Disruptions are happening every time a new technology, a new service, or a new business model provides a ten-time improvement of the present solution. According to Tony Seba (author and co-founder of RethinkX) this is valid all since Johannes Gutenberg invented the printing press in the 15th century. Providing the new solution at ten-times lower cost or being ten-times faster. Digitalization is adding to that trend.

The pandemic dramatically redefined our ideas about community and what being part of a community meant. Some communities were strengthened, new ones were created and some atrophied or ceased to exist. Professional organizations, religious organizations, schools, and businesses were forced to rethink how their community would connect and stay a community often without being able to meet face-to-face. Being part of a community that prospered during this time had a significant impact on how, and how well, people coped with the overall pandemic. That said, some aspects were lost without even recognizing them.

In the article “Unlearning What Toyota Taught Us,”1 author John McElroy lauds Tesla’s success with electric vehicles and wonders where Toyota has been. He specifically quotes the book The Toyota Product Development System2 when describing the Toyota product development standard, which he contrasts with the process used by Tesla: much more rapid improvements, no spec freeze, changes after the launch, etc. McElroy also remarks how forgiving Tesla customers are with small quality problems.

3D solid modeling. Integrated product simulation. Digital twins. Multi-disciplinary Analysis and Optimization (MDAO). Computerized tools for product design and development are proliferating and advancing in capabilities at an ever-increasing pace. The capabilities of today’s software tools are far advanced from what they were just a couple of years ago becoming more and more realistic, accurate, and speedy with better UX, connectivity, and integration.

We are breaking this blog into parts, the first will focus on defining what we believe would further VM and where we believe most VM implementations stop. The following blog(s) will discuss recommended requirements for taking VM further. In all cases, we will hopefully trigger a dialogue with our fellow practitioners on what is realistic and feasible.

Measure twice, cut once. It is this adage that can help us learn through the development process towards maximizing the value delivered with a product or service. However, when our efforts do not turn out the way we expect we have the opportunity to develop the skills and methods to effectively work more methodically and efficiently.