It takes many different mindsets and behaviors to make a team hum. I am appreciating a view of collaborative behaviors developed by David Kantor (as part of his work on Structural Dynamics), and am finding it useful as a way to hold up a mirror to a team that is interested in understanding and improving their communication.
A refresh to one of my more popular posts…
Now more than ever companies are exploring ways of measuring and visualizing how their teams are doing (KPI’s; ROV’s, NPS, etc.,)
The general idea being ya can’t improve what ya don’t measure. And without some sort of systemic approach with clear visualization – things would very much be a guessing game.
While a team can rollback a code push that didn’t go well, refactor a feature that didn’t hit the mark, the one thing they can never recover is lost time. Use this retrospective technique to expose the thieves of time pestering your team,
We often hear “Lean” and “Agile” together in the same breath. Are they the same? Or different? Lean originates from Lean Manufacturing, the Toyota Production System, aka the Toyota Kata. Lean is a set of principles for achieving quality, speed & customer alignment. (Hmm… hope that sounds familiar and very …
What makes your teammates lose sleep at night? The best way to find out is simple, but not always easy: ask them!