Discussion about this post

User's avatar
Tonianne DeMaria's avatar

I've been thinking a lot about "productive struggle," that point where cognitive dissonance and controlled stress can actually enhance learning and adaptation to a new stimuli or context or concept, much in the way we see creative tension on teams drive the need for kaizen.

An analogy: my first (honest) Kanban board. Finally seeing my work in Backlog / Options was akin to that darkened corridor in my post below: both triggered a threat response. In each case, my perception of reality was terrifying to the point of being frozen. And cognitive dissonance resulted because I *thought* I had all my work under control, but alas...

Then my natural inclination was to either hide those items...or abandon my Kanban altogether, because as my favorite early Kanban community saying goes,

"I didn't have these problems before Kanban."

To which the response of course is, "No, you DIDN'T KNOW you had these problems before you started visualizing them with Kanban!" 😉

But much in the way I had that simple handrail guided me through the darkness of that art installation in Milan, my Kanban gave me the minimum viable structure *not* to do / solve everything at once but rather, take the next possible step, act on feedback from that move, then continue. PDSA in action. (Prada-Do-Study-Adjust?)

The real magic happens when I emerged from the darkness and find myself in that admittedly absurd but wholly delightful "Mushroom Room." In Kanban, that "room" is where I see the same tasks repeatedly showing up, the true costs of multitasking, what part of my workflow seems to welcome bottlenecks etc.

So do we solve for discomfort in our systems? Are they bugs...or features? I'd argue so long as we have clarity over their cause and the agency to address them, they're the latter, and the only way we will ever grow beyond our current mental models.

Much appreciation to Tony DeCaria, whose comment in my post inspired my thinking. 🙏🏼

No posts

Ready for more?