I liked the way another comment here phrased it of subtractive in the sense that you are working to subtract risks from your project.
That is something we run into all the time. "We need to deliver X, we think the biggest risk is Y, so we will spend some time there trying to quantify what needs to happen and how big the box is"
My daughter got a plaster mold thing with prizes hidden inside it for Christmas and we were working on it just a few minutes ago. You use a hammer and chisel to bust chunks off until you find pieces. I feel like a lot of project development is like that. You know the thing you want is somewhere in there, and the real work is making strategic decisions on what to hit at next in order to make the biggest gains towards finding what you want.
Nice analogy. Would you qualify assessing what needs to happen (which may include R&D or PoC work) as subtractive activity? Probably not, since it takes place before you start hitting the mold so to speak?
Yea I really don't know I guess. I think the subtractive / additive distinction is kind of leading people off on a tangent away from what the author was trying to say, or at least what I was took from what the author said.
Really I think what the author was getting at is there are some things that if you don't do them, it's easy for someone else to do them. And there are other things that if you don't do them, no one else is realistically going to come back and take care of them for you. And the whole "shape" analogy is just pointing out that some shapes are easier to fill around than others.
Regarding the whole subtractive vs additive thing, you could build a statue either way. You could carve away at a block of stone, or you could build it up with clay. Both get you a statue at the end. I think some of it just depends on how your mind works.
The thing the article talks about is more of a strategic vs procedural type of distinction I think. Part of being more effective is knowing where to put your effort, and it's a difficult thing to point out to people that their view of what is productive doesn't align with the actual needs of the project.
I liked the way another comment here phrased it of subtractive in the sense that you are working to subtract risks from your project.
That is something we run into all the time. "We need to deliver X, we think the biggest risk is Y, so we will spend some time there trying to quantify what needs to happen and how big the box is"
My daughter got a plaster mold thing with prizes hidden inside it for Christmas and we were working on it just a few minutes ago. You use a hammer and chisel to bust chunks off until you find pieces. I feel like a lot of project development is like that. You know the thing you want is somewhere in there, and the real work is making strategic decisions on what to hit at next in order to make the biggest gains towards finding what you want.