Re:What I’ve learned from users
by quickthrower2 on Tuesday September 20, 2022 @06:56PM
(#32918886)
TOC is quite interesting and not as mainstream as something like SCRUM, but could be a better option.
I like that it is more evidence-based and thought out. However I think applying this is challenging - for the same reason as scrum - because methodologies like this require leaders to let go of their control-ego and trust the system. And systems like TOC which require a lot of thinking, understanding and are easily corrupted by misunderstanding it are fragile to the reality of a hierarchical team structure where the bosses personality can dominate processes more than the process. As such I believe (may not be true) that taking good principles from TOC would be better.
I have seen TOC tried to be applied in a software job and it turned into the typical "JIRA-style" nightmare of estimations, pressure, short term thinking and so on. I don't think that is what TOC is about, but what it can end up with when it hits the ground. SCRUM has the same issues of course. Because these methodologies are not meant to be an al a carte menu of options, where the ones that make the bosses eyes light up are chosen. But they are complete systems. Like it might be fun to only do bench presses at the gym and nothing else, and still eat badly, but that won't work - you need to do the whole regime!
That is why in reality I prefer systems that can be offered al-a-carte. Maybe TOC can be I am not an expert and haven't read the book. But I like for example if someone comes to lead a team and sees how things are done and slowly tweaks things towards a long term goal. For example come in and get people work as a team not individually so that work is delivered sooner and there is less WIP.
I like that it is more evidence-based and thought out. However I think applying this is challenging - for the same reason as scrum - because methodologies like this require leaders to let go of their control-ego and trust the system. And systems like TOC which require a lot of thinking, understanding and are easily corrupted by misunderstanding it are fragile to the reality of a hierarchical team structure where the bosses personality can dominate processes more than the process. As such I believe (may not be true) that taking good principles from TOC would be better.
I have seen TOC tried to be applied in a software job and it turned into the typical "JIRA-style" nightmare of estimations, pressure, short term thinking and so on. I don't think that is what TOC is about, but what it can end up with when it hits the ground. SCRUM has the same issues of course. Because these methodologies are not meant to be an al a carte menu of options, where the ones that make the bosses eyes light up are chosen. But they are complete systems. Like it might be fun to only do bench presses at the gym and nothing else, and still eat badly, but that won't work - you need to do the whole regime!
That is why in reality I prefer systems that can be offered al-a-carte. Maybe TOC can be I am not an expert and haven't read the book. But I like for example if someone comes to lead a team and sees how things are done and slowly tweaks things towards a long term goal. For example come in and get people work as a team not individually so that work is delivered sooner and there is less WIP.
A bit rambly but those are my thoughts!