Cost of Solution vs. Cost of Problem
Post from September 20, 2007 (↻ August 24, 2017), filed under Everything Else.
This and many other posts are also available as a pretty, well-behaved e-book: On Web Development.
Problems cost money, and problems require solutions that also cost money. This is known in all industries, but in many cases, there is focus on only one side: What does the solution of the problem cost? This ignores the other side, the cost of the problem.
Evaluating cost of solution is simple: You determine the time and money you need to develop and implement it. You’re looking at the resources needed. Cost of problem, however, equals the price of doing nothing. That is, for what I know, an important economic principle known from cost-benefit analyses.
I recently wrote more on the matter for Germany’s Dr. Web mag, including some detail and examples. Unfortunately, that prevents me from providing more information in this place. The point is this: Always consider the cost of the problem in order to prioritize appropriately. Some changes are unnecessary and expensive, others are critical and must not be delayed.
If you cannot wait until I share any more detail: Jeff Thull’s been on the same page.
About the Author
Jens Oliver Meiert is a tech lead and author (sum.cumo, W3C, O’Reilly). He loves to try things, particularly in the realms of philosophy, art, and adventure. Here on meiert.com he shares and generalizes and exaggerates some of his thoughts and experiences.
If you have any thoughts or questions (or recommendations) about what he writes, leave a comment or a message.
Have a look at the most popular posts, possibly including:
Looking for a way to comment? Comments have been disabled, unfortunately.