Effort justification and automation in outbreak analytics pipelines #121
jamesmbaazam
started this conversation in
General
Replies: 2 comments
-
Thanks @jamesmbaazam - that's an interesting discussion. I'm not sure whether this particularly applies to software usage. Often, the main selling point of a package, GUI, or software is that it reduces a complex wofklow to "just one click". |
Beta Was this translation helpful? Give feedback.
0 replies
-
Or maybe this applies when the selling point is that it gives you more control over what you can do rather than having to deal with a black box 😉. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I read about the effort justification effect today and it got me thinking about automation versus manual tasks in outbreak analytics pipelines. Basically, effect justification is when people feel attached to an output due to the effort put into acquiring/achieving it. It's also referred to as the IKEA effect. Apparently, people are sometimes more attached to IKEA products because they get to build them themselves and I guess this extends to DIY in general.
This same effect raises a lot of debate in many spheres of life, including, how one feels using
git
from the terminal versus GUI,SPSS
versusR
, driving a manual car vs automatic, etc.In outbreak analytics workflow/pipeline design and automation, to what extent can this be applied? For example, do we have any sense of what aspects of outbreak analytics pipelines and workflows users prefer to perform manually rather than through automation? How can we apply this effect in the design of our software?
Beta Was this translation helpful? Give feedback.
All reactions