The reason for working in the virtual realm in manufacturing has always been dreadfully obvious to anyone who looked at what kinds of analysis were possible by running computer simulations … of course, continual back-and-forth interaction with the physical realm is dreadfully important to validate the models used, but NOW that computing processing power and storage have become so incredibly scalable and affordable, it is really time to BE IMMERSED in the virtual realm for anything in the mfg sector.
If you are not there, the time has come to emigrate to the virtual realm … actually, the time was probably a couple decades ago, but GET GOING … especially, now the rest of the world has finally caught on … it’s too costly to drive to ALL of those meetings AND the people who demand a physical meeting are the ones who don’t care about anyone else’s time, so those physical meetings really need to be avoided now… regardless of where you are based geographically at least 99.999% of your potential customers or clients are farther away than your computer [and they don’t really want a daily or hourly personal visit from you either] … the time emigrate to the virtual realm is OVERDUE.
There are some principles to remember:
- DISTRIBUTED version control means GIT … figure out a plan for MASTERING Git and then work every single day at making better use of distributed version control and working in the realm of open source repositories and code libraries. Git Deep!
- Do NOT overinvest for capacity/equipment you think that you’ll need … use JIT infrastructure.
- Test systems at production scale using a production-scale test environment … the key thing to do is to overcome your own path dependent thinking and get out of the ruts that you’ve created, especially if you have stayed in the same old comfortable track or comfort zone. Develop your own Disruptive Engine …
- Demand rapidly evolutionary architectures — encourage agility and rapid evolution. Fail in protected sandboxes and then analyze tear down your failures and rebuild … if you don’t have broken pieces, you are not trying. Plan forward without commiting but your will REQUIRE readiness in terms of your system’s ability to deliver changing business requirements
- Regularly schedule dress-rehearsal scrimmages with real people who CARE, ideally these “game days” are with people who might have some “skin in the game” such as beta customers who have asked for a new feature … continually do HEAVILY-SUPPORTED launch events with REAL customers [and “real” means the PAYING kind who won’t settle for crap] to simulate function in production@scale. If you don’t have a showtime big event, then pretend until you do with chaos monkey simulations.