You’re speaking to my struggle and thank you for writing this to confirm them. I fight this with IT and leadership. I end up having to silo what I can control to avoid the spaghetti. This allows my team to scale over and deliver quickly.
It is even an organizational problem. On many different levels. Too much for a comment, but this much already: I think it cannot be healed by individual leaders alone, you have to widen the view even further. Who needs to work more closely with whom, what should be worked on and what not, how do we find out what is worth it and what is not. In my view, you have to turn several screws so that it doesn't even get to the point where you have to work through a huge mountain of tickets. That is, in my view, a symptom of doing too many things and above all of operating too granularly, which leads to that the view of the big picture is lost. Sure, somehow you have to decompose work, but in a different way in my opinion. I will write my next article about that. What you describe is a big problem and we will not solve it through individual leaders alone.
I really hope that this current situation will lead to a wider adoption of systems engineering. As this is exactly the scope that is adressed by the domain. Not buidling locally and deriving components, but synthesis into the larger scope. It feels like this is a major challenge, as usually we try to apply“divide et impera“ mindset, however now we need a more ecosystem focused approach.
Good post and quite a real problem... Using AI systems to memorize or remember the various siloed solutions will result in increasing the contextual load (token, cognitive or otherwise).
You’re speaking to my struggle and thank you for writing this to confirm them. I fight this with IT and leadership. I end up having to silo what I can control to avoid the spaghetti. This allows my team to scale over and deliver quickly.
It is even an organizational problem. On many different levels. Too much for a comment, but this much already: I think it cannot be healed by individual leaders alone, you have to widen the view even further. Who needs to work more closely with whom, what should be worked on and what not, how do we find out what is worth it and what is not. In my view, you have to turn several screws so that it doesn't even get to the point where you have to work through a huge mountain of tickets. That is, in my view, a symptom of doing too many things and above all of operating too granularly, which leads to that the view of the big picture is lost. Sure, somehow you have to decompose work, but in a different way in my opinion. I will write my next article about that. What you describe is a big problem and we will not solve it through individual leaders alone.
I really hope that this current situation will lead to a wider adoption of systems engineering. As this is exactly the scope that is adressed by the domain. Not buidling locally and deriving components, but synthesis into the larger scope. It feels like this is a major challenge, as usually we try to apply“divide et impera“ mindset, however now we need a more ecosystem focused approach.
Good post and quite a real problem... Using AI systems to memorize or remember the various siloed solutions will result in increasing the contextual load (token, cognitive or otherwise).