5 ms·
Ah, my sister endured all this sort of thing during 20 years as a VP in corporate America. She successfully deployed new data systems to 120 plants in 50 region
by JoeAltmaier 7y ago
Ah, my sister endured all this sort of thing during 20 years as a VP in corporate America. She successfully deployed new data systems to 120 plants in 50 regions in one year. Didn't cost $25M.
Her method? Ruthlessly purge the region of the old data system and install the new (web-based API to a central, new data system). Investigate every regional difference and consolidate into one model.
Before deployment day, get all the regional Directors in one room and tell them it was going to happen. Tell them there was no going back, no push-back would be permitted, and have the CEO in the room to confirm this.
It all went well, with her team of a dozen professionals that did a surgical strike to each region. IT equipment installers, trainers. Even one lady who's job was to ferret out the hidden PC somebody was squirrelling away in a closet (there was always that person) and rip it out, take it to her car and lock it in the trunk.
All went well, except for one region. That regional Director had missed the big day, and tried (vainly) to push-back for all the familiar reasons: special circumstance, retraining was going to keep them down for too long, and on and on.
100 years of data systems gone in a year (including paper systems) and replaced with a web API.
- keiru 7y agoI was reading the article thinking that I would take an approach just like that. I don't think there is any other way to ensure success.
- brazzy 7y agoIt requires you to have complete and unwavering backing from top management even when some of the guys whose toes you're stepping on haven been golf buddies with said top management for 20 years. Sounds like an unrealistic expectation.
- jandrese 7y agoIt also depends on you having a crack IT team who can get it right the first time. No months of stuff crashing or having a horrible interface that impedes work or being intolerably slow. You have to be confident enough to push back against the exec who says "oh, we'll just hire $massive_consultancy_firm to do it" and takes years to roll out a half baked hackjob on top of their stupidly expensive CMS.
- JoeAltmaier 7y agoShe insisted on a hand-picked team
- crispyambulance 7y ago> ...No months of stuff crashing or having a horrible interface that impedes work or being intolerably slow. Dude, that's the not a temporary transition state. That is normal _all_ _the_ _time_ for much of enterprise systems. The crashing might stop, eventually, but the byzantine intractable complexity maintained by a small army of information-hording corporate battle-axes... that stays forever, regardless of whether you go to a single "web-api" or not.
- otakucode 7y agoThat sort of nepotism can be a problem. It's why Amazon's search sucks so bad. In the book 'The Everything Store', it tells the story of when a team at Amazon responsible for something else saw how bad search was and decided to fix it. So they built a prototype with Elasticsearch and whatnot. It worked great. The dude at the head of the search team, good friends with Bezos, got all territorial and angry. Bezos solution? Have a test between the two solutions to determine which was best. Bezos idiocy? He let the head of the search team decide who won. So, no surprise, the head of the search team said the search team won. So the improved search was shut down and the garbage search we all have to deal with regularly got to stay. Once you've got that kind of thing going on, only retirements and deaths can effect good change at an organization.
- keiru 7y agoIt is, in the sense that I wouldn't expect it to happen, at least to me. But it's not unrealistic that some CEO would actually listen to you about the matter and put his foot down to make it happen. These are not matters difficult to comprenhend, my guess is that people use to take IT stuff for granted and that's it. I've also known guys who didn't give a fuck when they saw upper management screw up tech-wise so as not to get into arguments. That also cripples healthy feedback.
- b_tterc_p 7y agoIt’s impressive that this worked. In my experience this doesn’t work because there’s so much “process” built around the tool to handle tons of undocumented edge cases that deploying the new tool just doesn’t work so it’s extra hard to get it up and running successfully.
- mason55 7y agoThe key to being successful at something like this, whether it's internal LOB software or a B2B enterprise product, is to provide a way for users to handle any exceptions out of band. If you try to code for every process exception you will (a) never go live and (b) create a horrendous monstrosity of a system. But if you can find the right spots to put in manual hooks then the users can be empowered to solve their own process exceptions. An easy example is if you have an application that does a bunch of different calculations based on random rules and data sets. Instead of trying to code every calculation and random exception that the users throw at you, you start with the top 80% (or 50% or whatever) and give them a robust way to add a "manual calculation". Then tell them to handle their own exceptions by doing whatever crazy crap they need to do and just stick the result in the system. It's difficult because if you're not familiar with the industry then you won't even be able to imagine the places where exceptions can occur. And the users will complain about having to do stuff manually. If you automate 80% of what they are doing right now and they still have to do 20% manually, stuff that they are doing manually right now, that manual work suddenly becomes a critical blocker that prevents the whole system from being useful. So you need someone with a strong personality who will not just accept that whatever the users are saying is right.
- slfnflctd 7y agoWhat a great summary, I could not agree harder. Some of the worst turmoil happens when suddenly 'business as usual' for customers/users you didn't recognize the full value of disappears, and the front line people have to say things like "the new system doesn't let us do that any more". You're absolutely right that they'll complain and drag their feet no matter what and that rock-solid leadership is needed to overcome this, but if you at least give them a way to do all the good-for-business stuff they did before in a similar time frame (with an overall faster/better system in the long run, of course), the majority of the sane ones will eventually come around.
- rb808 7y agoAnd then the devs moved on to something greater, the support was offshored and nobody could get the software to work as they wanted any more. 5 years later someone has the great idea to empower each plant by having different versions and the cycle continues.
- ialwaysforgetm 7y agoYes, this! But sometimes all it really takes is some VP who wants to show how they can 'reshape' (or whatever buzzword of the week) the company for major changes to start happening. I feel that stability of good things is impossible in big corps since there will always be people generating unnecessary work to others in order to accomplish their own personal agendas. Also sometimes a great improvement to one team generates a ton of extra work to another team.
- crazygringo 7y agoBut what about training and processes? The tech part is easy, relatively speaking. The hard part is each plant can have hundreds of workers whose entire jobs depend on the way things are set up. It can be hugely expensive, time-consuming and disrupting for months to try to replace processes with new ones, particularly if you expect things to continue running without interruption. It's one of those rebuild-the-airplane-while-flying-it situations. Maybe this was a uniquely lucky situation, because it doesn't sound like a generalizable magic-bullet to me.
- treis 7y agoIt would definitely be interesting to hear the other side of this anecdote. My guess is that there's a lot of workarounds happening at the plant level that are being hidden.
- JoeAltmaier 7y agoThe plant now tracks each individual product, line, customer, contract in realtime with complete transparency to the parent company. They swipe barcodes and use online tools. Their processes were streamlined and paper removed. It wasn't painless for everybody. In each region some good ol boy would resign the week before changeover. When they'd come in to do inventory some room or shed would be locked and nobody would have the key. They'd break the lock and whattaya know, the room would be empty. Supposed to be full of inventory.
- treis 7y ago>The plant now tracks each individual product, line, customer, contract in realtime with complete transparency to the parent company. I'm sure that's what the parent company thinks is happening. Whether that's what actually is happening at the plant level is another question. So is whether the improvement came with a hit to productivity or any other hidden cost. Obviously I know nothing specific about the company but speaking generally I've seen a lot of work arounds and inefficiencies in my day.
- sergiomattei 7y agoThis sounds amazing. How did it turn out?
- JoeAltmaier 7y agoStill running a decade later. Of course, now they've lost the people who designed that system, and are hard up to keep it updated. Like most large corporations, they 'outsourced' IT years ago. Which means, they lost their IP for their business processes to a revolving door of contractors. My sister is retired, but predicts the collapse of the US business sector due to critical process failures within a few years. Its a pretty dismal outlook.
- th0ma5 7y agoCan you go into any more detail about that or have any related resources about such a potential collapse?
- Qwertystop 7y agohttps://www.youtube.com/watch?v=pW-SOdj4Kkk https://www.youtube.com/watch?v=pW-SOdj4Kkk seems similar (somewhat melodramatic title, perhaps)
- brokenmachine 7y agoWhat would the "collapse of the US business sector" look like?
- JoeAltmaier 7y agoCan't sell product; can't manufacture or source parts; schedules start extending out to infinity?
- pjc50 7y ago> Tell them there was no going back, no push-back would be permitted, and have the CEO in the room to confirm this. I'm sure this is great when it works, but it's also reminding me of things like the TSB switchover disaster which lost them hundreds of millions of pounds and a lot of customers when their systems were down for a week. Apparently rollback wasn't planned for. "No pushback" also means "do not tell us how this is going to go wrong, we aren't going to listen".
- JoeAltmaier 7y agoOr, be diligently prepared for it to go right. After one or two regions succeed, you've got a pretty good idea of how the rest will go.
- burnte 7y agoI did the same thing a few years ago in a healthcare place about faxing. I just issued a decree that we were done with paper fax. One my my team had identified a great product, my team ran with integration, we staged everything, tested, did training, then on rollout day we switch over all 45 locations, and terminated analog lines in each location (unplugged them and took the cords if we had to). A few people bitched but most people loved it. Sometimes you have to be the benevolent dictator.
- brokenmachine 7y agoCall me a pessimist, but all went well for a couple of weeks until they all realized they needed reports that don't exist in the new system and all the users individually realized the new system didn't enable the thousands of workflows that people had adapted their old systems to do that the managers didn't know about. By this time your sister had hopefully moved sideways with "another successful migration" added to her resume.
- JoeAltmaier 7y agoNope. Still running after a decade; still selling tires. Still adapting to requests for reports and workflow issues, as is possible with web-based tools. Because they are so much better than the old C-coded static tools and static reports running on a PC (not to mention paper). That's why we use web tools after all.
- brokenmachine 7y agoThat's not at all like any of the "big bang" migrations that I've been involved in unfortunately.