Post #1457402
2025-11-14 17:41 UTC
@patmikemid Yeah, if you don't want to waste time working on the wrong problem, you should first think through what the problem even is, what its boundaries are, what you want to specify as in scope and what as out of scope, and how success would look like.
Replies (2)
-
@patmikemid@sfba.social 2025-11-14 17:46
@davidculley Back in the time of the dinosaur (the '80s), I took an Introduction to System Analysis course taught by Jack Gibson at UVA. One of his tenets was "The client does not understand their own problem." The problem definition section in that link is pretty similar. Define the system as is (descriptive scenario) Document how it should be (normative scenario) Define objectives to get from descriptive to normative Define measures (indices of performance) to evaluate your solution alternatives Model
-
@chewie@mammut.gogreenit.net 2025-11-15 09:20
@davidculley @patmikemid https://i.pinimg.com/originals/58/dd/1c/58dd1cd6957dc487c960c4d51aef300b.jpg