Lately I have been noticing a concerning pattern around organizations leeping to Kanban  quickly.  From what I have seen, organizations value cycle time.  Well, either that or it is a new interesting metric that enterprises are still learning how to cheat.  But I digress.  Let's assume that organizations honestly value cycle time and the belief that making that predictable and exposing bottlenecks will make their product deliveries smoother.  Great.  I agree.

The implementation is similar to the challenges we have with 'agile adoptions' - most organizations following the Analytic mindset (@flowchainsensei) - can't rethink how to structure work.  Instead, similar to 'agile adoptions', what I am seeing with Kanban is bending an idea and opportunity for change until it buckles...and becomes another process in a standard analytic model.  Let me explain.

Say you have a standard, silo'ed organization. There is dev, test, perhaps a DBA group, sysadmins, operations, etc (and that is just on the pure builder side).  Instead of saying 'our cycle time across the complete delivery...end to end is bad, how can we address that?'  What I am seeing is organizations saying 'Developers should have their own Kanban board, DBAs should have their own Kanban board, so should infrastructure, etc'

Doing the wrong thing righter is waste.  How do we move past this?  How do we leverage these opportunities to create meaningful change?