AWS plants more tombstones in the application graveyard On Tuesday in San Francisco at an event called "What's Next with AWS," CEO Matt Garman took the stage to announce that AWS is (for what, depending on how you count, is the seventh, eighth, or ninth time) moving up the stack and entering the applications business. The batting lineup: Amazon Quick, formerly known as QuickSight, …
First of all, basing an application on the AWS UI, which has changed three times since I started using it, and each time its gotten less useful was not a very smart idea.
Altman had somewhere to be that required his physical presence, and it wasn't scheduled by his AI assistant, it was scheduled by a judge.
Best of luck replacing Epic. I used to work on a healthcare cost accounting system, and epic data was just one source we ingesting into our platform. MASSIVE amounts of data, everything that happens in a hospital is tracked and coded. In the US, hospitals are notorious for (among other things) being extremely slow to upgrade systems for day-to-day operations.
Once my wife was in for a routing procedure, and as the nurse was entering info into the computer by her bed, she paused, then raised her hand. Someone came over with clipboard and then called someone else on a radio. In a couple of minutes a 'runner' came over, and showed her how to do what she needed to do in the system.
"But I always do that over in this other screen"
"Well, it's not there anymore. Did you do the training?"
I asked the nurse what was going on, and she said they had upgraded their Epic system several days ago, and "everything changed".
The problem was that they use it day in and day out, so any kinds of changes massively alters their workflow. To the point that to keep operating, they had to have many runners with radios for about a week (to cover all shifts) to help people get used to the changes after a release upgrade.
I have an app I use for my hospital (I go there for everything like regular checkups and so forth since it is a very large one that's in town) and everytime the app updates the release notes talk about new features but none of them are applicable for me because my hospital's Epic software is several versions behind.
Anyone working in IT knows why that sort of thing is the case, of course. Someday they'll upgrade (probably forced by Epic due to a cutoff of support for older versions) to the latest or near latest version and a lot of new features will appear in the app, then they'll wait years before they are forced to do another upgrade because it is so disruptive to operations.
What happens to the Product Managers of these cancelled apps? Its likely those PM's have or had monthly or quarterly performance review meetings with a Product Director. Its probably obvious when things start to go south for your app, its in the numbers vs. projections. "We think you'd be a better fit somewhere else" may or may not be common at AWS.
A Zoom wannabe so bad, that even Amazonians refused to use it. It made Teams look good. No, really! During the time I was there, they made a half-hearted attempt at making us "eat our own dog-food" but only the most brain-dead cheerleaders tried to enforce it for team meetings and stand ups (this was during 100% wfh lockdowns) and people just rebelled.
