How the Kaizen approach to business process, systems analysis and designing a new Sample ERP System promotes creative solutions.
How would you design a Sample ERP System for your company? The notion that everything is broken, suggesting a rip and replace tactic for an all-in-one shiny solution, is offensive to most any established organization. In the same way that sample products become your bestselling designs, a new system is a similar mix of new materials across a proven template.
How can we solve today’s pain while also promoting tomorrow’s creativity? To answer the big questions, we must start with the smaller, more realistic ones. Similar to creating new sample items, we consider the templates that are proven; iteratively revising business processes and tweaking existing technology. We approach each department with simple questions, in search of realistic problems and creative answers!
The Kaizen method of continuous improvement focuses on the smaller steps toward incremental change. Instead of starting with big picture questions, we look at the smaller things. Examining inter-departmental process flows, optimizing existing underused resources (employees, partners, technology, etc.) and possibly implementing additional infrastructure. Sound familiar? Established brands don’t fabricate samples purely from scratch, but instead reuse portions of their current success. While searching for the perfect system, we must maintain the integrity of your company’s culture, business partner relationships, account management techniques and product development that give your brand a competitive edge. These are the consistent, repeatable elements of your template to build a sample system.
Once our template is established, we must inspire creativity. We ask seemingly small (and easy!) questions of every department. Similar to recognizing bad materials or batches across product, we look for patterns across applications, integrations and departmental activities. Recommendations to upgrade dated technology and/or redesign workflows now become a strategy. The process creates a journey that your brand knows from early development stages, revisited for internal organization needs. The goal is to better utilize in-house talent, leverage key business partners and ultimately, take your brand to another level. By testing some of these new materials across a proven template, we can develop a system blueprint that has a supporting vision.
Should decisions to change your technical infrastructure derive from eminent pain or be driven by unfounded creativity? digad’s System Blueprint Process uses Kaizen techniques to map the current infrastructure, highlight places of improvement and recommend opportunities to change. New technology recommendations take into account quality, costs and implementation timeline.
Next blog: Is your technical footprint small, medium or large?