Re:Every change breaks someone's workflow (2013)
by happytoexplain on Monday October 07, 2024 @11:39AM
(#41767104)
The opposite problem is much more common and shouldn't be downplayed: A developer or designer using the "every change breaks someone's workflow" exaggeration as an excuse to break a workflow.
[ Parent
| on HN ]
Re:Every change breaks someone's workflow (2013)
by JohnFen on Monday October 07, 2024 @11:59AM
(#41767324)
This.
The fact that any change to software people are used to using will bring pain to the users shouldn't mean that devs automatically prefer or avoid breaking workflows. What it should do is encourage actually thinking about the cost/benefit (to the user) of the change.
Users will accept the pain that change brings if the benefits of that change outweigh the cost of it. If the cost/benefit ratio isn't favorable to the user, they will, quite understandably, resent the change.
Re:Every change breaks someone's workflow (2013)
by Netch on Monday October 07, 2024 @12:03PM
(#41767354)
Most cases an initial estimate of change cost is utterly overstated because emotional and reluctant to change.
(And, well, this fact is also abused by wreckers who explain any reasonable objection with this factor;))
Re:Every change breaks someone's workflow (2013)
by maaaaattttt on Monday October 07, 2024 @11:45AM
(#41767153)
or (worse?) to not change anything; but I think this comes usually more from devs (guilty as charged).
Re:Every change breaks someone's workflow (2013)
by BiteCode_dev on Monday October 07, 2024 @12:05PM
(#41767380)
"We don't break userspace"