Really great article on the importance of UX to software development.
Digitization genuinely can be amazing. It means that (with proper practices) nothing critical is ever lost, key information can easily be accessed and communicated without risk of loss or duplication errors, and additional analysis can be quickly and easily done (minimal cost per extra set of data analyzed; it does take appropriate design and investment to design the algorithm), and a variety of other benefits.
But if you don’t have a very clear picture of how the data will actually be used in the real world, none of those benefits matter because the whole thing is a pile of shit.
Consumers of the software want one thing. C-Suite doesn’t know what they want, but want to be involved in every step dictating terms. Designers are caught in the cross-fire (if they even get a chance to get consumer input). C-Suite pulls the paycheck trump card to get what they want then cry, “Why do they hate our software?”
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Really great article on the importance of UX to software development.
Digitization genuinely can be amazing. It means that (with proper practices) nothing critical is ever lost, key information can easily be accessed and communicated without risk of loss or duplication errors, and additional analysis can be quickly and easily done (minimal cost per extra set of data analyzed; it does take appropriate design and investment to design the algorithm), and a variety of other benefits.
But if you don’t have a very clear picture of how the data will actually be used in the real world, none of those benefits matter because the whole thing is a pile of shit.
Consumers of the software want one thing. C-Suite doesn’t know what they want, but want to be involved in every step dictating terms. Designers are caught in the cross-fire (if they even get a chance to get consumer input). C-Suite pulls the paycheck trump card to get what they want then cry, “Why do they hate our software?”