Interesting. I wonder if we are talking about different things.
To me unclear boundaries imply a degree of exploration and boundary-setting activity, and that is rarely plain subtractive.
True, in a bigger picture this boundary-setting activity still works towards completing some solution—but then in an even bigger picture, I would put forward that in the real world projects are never actually complete.
As a maybe far-fetched example, say there is such and such real-world user problem that was usually addressed via use of spreadsheet- or CRUD website based solutions; now a teammate delivers an Electron-based app prototype which shifts the constraints of what we can do or what level of effort it takes, and even prompts a reformulation of user’s true needs as possibilities previously not even thought about are suddenly on the radar.
To me unclear boundaries imply a degree of exploration and boundary-setting activity, and that is rarely plain subtractive.
True, in a bigger picture this boundary-setting activity still works towards completing some solution—but then in an even bigger picture, I would put forward that in the real world projects are never actually complete.
As a maybe far-fetched example, say there is such and such real-world user problem that was usually addressed via use of spreadsheet- or CRUD website based solutions; now a teammate delivers an Electron-based app prototype which shifts the constraints of what we can do or what level of effort it takes, and even prompts a reformulation of user’s true needs as possibilities previously not even thought about are suddenly on the radar.