> I think this is looking at the problem wrong. The problem is that implementing positive change in these systems is impossible for reasons far outside the control of any product designer or developer currently on the team.
A developer working on something is different from a product designer. For product designer I don't mean a UI/UX developer. I mean someone empowered to design the thing. This is often a leader or product manager.
Product design isn't something taught well in most schools. It's often out of sight and mind. An engineer who was good at building hardware or writing code didn't learn the skills needed for product design through that. Product design requires looking at the whole system differently.
> It probably takes 3 months to move a button around, and instead of moving that button executives are having them push a feature that earns a few more million, or a feature that the customers want more then a UX improvement.
A better UX would reduce the amount of time nurses spend using these systems. That productivity could be used to do more other work (like taking on more patients). I don't like this argument but it's easy to make in terms of cost effectiveness.
I don't think the cost effective conversations are happening. I expect there isn't that level of depth to these. It's hard to do when a purchasing organization (like a hospital) only have a few options and they are all bad.
This is an opportunity. To build software that is both compliant and has a good UX. There's an opportunity to disrupt all the crap software here.
