Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Systems theory
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
====User-centered design process==== Systems thinking is a crucial part of [[user-centered design]] processes and is necessary to understand the whole impact of a new [[human computer interaction]] (HCI) [[Information System|information system]].<ref>{{cite web |last1=Söderström |first1=Jonas |title=Algoritmiska larm belastar sjukvården |url=http://javlaskitsystem.se/2020/02/algoritmiska-larm-belastar-sjukvarden/ |website=Jävla skitsystem |access-date=12 September 2020 |archive-date=6 August 2020 |archive-url=https://web.archive.org/web/20200806011103/http://javlaskitsystem.se/2020/02/algoritmiska-larm-belastar-sjukvarden/ |url-status=live }}</ref> Overlooking this and developing software without insights input from the future users (mediated by user experience designers) is a serious design flaw that can lead to complete failure of information systems, increased stress and mental illness for users of information systems leading to increased costs and a huge waste of resources.<ref>{{cite book |last1=Söderström |first1=Jonas |title=Jävla skitsystem! |date=2010 |publisher=Karnaval Förlag |location=Stockholm |page=16,17}}</ref> It is currently surprisingly uncommon for organizations and governments to investigate the project management decisions leading to serious design flaws and lack of usability.{{citation needed|date=September 2020}} The [[Institute of Electrical and Electronics Engineers]] estimates that roughly 15% of the estimated $1 trillion used to develop information systems every year is completely wasted and the produced systems are discarded before implementation by entirely preventable mistakes.<ref>{{cite web |last1=Charette |first1=Robert N. |title=Why Software Fails |url=https://spectrum.ieee.org/why-software-fails |website=IEEE Spectrum |date=2 September 2005 |access-date=12 September 2020 |archive-date=9 September 2020 |archive-url=https://web.archive.org/web/20200909063905/https://spectrum.ieee.org/computing/software/why-software-fails |url-status=live }}</ref> According to the CHAOS report published in 2018 by the Standish Group, a vast majority of information systems fail or partly fail according to their survey: {{Blockquote|Pure success is the combination of high customer satisfaction with high return on value to the organization. Related figures for the year 2017 are: successful: 14%, challenged: 67%, failed 19%.<ref>{{cite web |last1=Portman |first1=Henny |title=Review CHAOS Report 2018 |url=https://hennyportman.wordpress.com/2020/01/03/review-chaos-report-2018/ |website=Henny Portman's Blog |date=3 January 2020 |access-date=11 September 2020 |archive-date=29 September 2020 |archive-url=https://web.archive.org/web/20200929194449/https://hennyportman.wordpress.com/2020/01/03/review-chaos-report-2018/ |url-status=live }}</ref>}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)