Iterations are fine within Lean thinking if doing so reduces delays and is the best way to manage queues. But any approach where iterations are an end goal is not based on lean.
You don’t measure if you’re doing Lean by if you’re doing a practice. You see if you’re doing lean by the frequency of your learning opportunities. Whatever speeds up learning is almost certainly Lean.
Icebergs in a river improves flow the way immutable practices improve effectiveness – they don’t. We need flow of ideas for improvement as much as we need flow of work. While constraints in our design process are useful, constraints in our implementation limits innovation.
Consider the statement “well if we do XXX we’re not doing YYY.” Where’s the question “is XXX better?” Lean’s focus on the actual work avoids this nonsense. But it requires a theory confirmed by empiricism, to be able to answer the question “is XXX better?”
You see if you’re doing Lean not by looking to see if you’re attending to practices or events, but by seeing if the actions you’re taking produces more value for your customers.
@threadreaderapp unroll
• • •
Missing some Tweet in this thread? You can try to
force a refresh
