Depends. If you’re the team’s bottleneck/constraint, avoid interruptions at all costs. If you’re not, you’re a potential blocker for the bottleneck - in which case you want to be as interruptable (by the bottleneck) as possible. https://twitter.com/MikeIsaac/status/1042497174028705793 …
-
This Tweet is unavailable.Show this thread
-
The reason for this comes from manufacturing. If a bottleneck machine is sitting idle, the cost of it being idle is the *burn rate of the entire system.* So, 1 min of distracting bottleneck is 1 min of entire team’s burn - as is 1 min of bottleneck waiting for answer.
1 reply 1 retweet 5 likesShow this thread -
This account owner limits who can view their Tweets. %{learnmore}
-
Replying to @davidjrusek
Same principles apply. A lot of software development practices from the assembly line. Kanban, etc. Also, depends how you define machines :P
3 replies 0 retweets 0 likes -
This account owner limits who can view their Tweets. %{learnmore}
-
This account owner limits who can view their Tweets. %{learnmore}
-
This account owner limits who can view their Tweets. %{learnmore}
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.