#theoryofconstraints — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #theoryofconstraints, aggregated by home.social.
-
Most organizations have no problem with output, but rather with responding to signals. This is a problem because when t(decision) > t(production), the system becomes structurally disconnected from reality. It is completely worthless to deliver faster if decisions take too long, because then any knowledge gained is immediately devalued.
A thread 🧵
#SystemsThinking #WorkFeedbackLoop #Flow #TheoryOfConstraints #DecisionLatency
(1/2)
-
Most organizations have no problem with output, but rather with responding to signals. This is a problem because when t(decision) > t(production), the system becomes structurally disconnected from reality. It is completely worthless to deliver faster if decisions take too long, because then any knowledge gained is immediately devalued.
A thread 🧵
#SystemsThinking #WorkFeedbackLoop #Flow #TheoryOfConstraints #DecisionLatency
(1/2)
-
Most organizations have no problem with output, but rather with responding to signals. This is a problem because when t(decision) > t(production), the system becomes structurally disconnected from reality. It is completely worthless to deliver faster if decisions take too long, because then any knowledge gained is immediately devalued.
A thread 🧵
#SystemsThinking #WorkFeedbackLoop #Flow #TheoryOfConstraints #DecisionLatency
(1/2)
-
Most organizations have no problem with output, but rather with responding to signals. This is a problem because when t(decision) > t(production), the system becomes structurally disconnected from reality. It is completely worthless to deliver faster if decisions take too long, because then any knowledge gained is immediately devalued.
A thread 🧵
#SystemsThinking #WorkFeedbackLoop #Flow #TheoryOfConstraints #DecisionLatency
(1/2)
-
Most organizations have no problem with output, but rather with responding to signals. This is a problem because when t(decision) > t(production), the system becomes structurally disconnected from reality. It is completely worthless to deliver faster if decisions take too long, because then any knowledge gained is immediately devalued.
A thread 🧵
#SystemsThinking #WorkFeedbackLoop #Flow #TheoryOfConstraints #DecisionLatency
(1/2)
-
Introducing a #TeamTopologies enabling team into your org implies that there are enough teams that have the time, motivation and matching priorities to get enabled.
Competing against mismatched priorities and out-of-bounds work-in-progress is an uphill battle at best. Align priorities first and maintain alignment with #FlightLevels, apply the #TheoryOfConstraints to the work flowing between the teams, think about how teams work together with #TeamTopologies.
-
#Kanban systems use local WIP constraints; #TheoryOfConstraints systems use global WIP constraints.
Local feedback loops are inherently faster than global feedback loops.
-
My biggest trouble with advocating against #PullRequests and gating merges behind #CodeReview is that it is legimately effective for finding defects when done thoroughly. You get something valuable for the cost in review work, increased batch sizes, and multitasking. It makes it harder to convince myself and others that it's better to drop it for the sake of flow.
#Programming #SoftwareEngineering #SoftwareDevelopment #TheoryOfConstraints
#TrunkBasedDevelopment