Today I read a blog by Daragh Farrell at Thoughtworks. Daragh tells the story of a team that had returned to holding retrospectives and expresses amazement at the positive effect of the ritual on team development. Retrospective boosters (like me) tend to stress the role of retrospectives in process improvement and product quality because those have a more direct impact on ROI. I'm glad to be reminded of the more subtle contribution of retrospectives to accelerating team development. High performing, self-organizing teams also contribute to the bottom line through increased productivity, innovative thinking and lower absenteeism and...
This week I'm engaged and enlightened at the Consultants' Retreat and Network, held in Newport, Oregon, on the beautiful central Oregon coast. An impressive cast of consultants and brilliant significant others have gathered to discuss consulting in all its aspects. We use an Open Space format so that every session on our agenda holds compelling and current interest for a subset of us. So far our sessions have ranged from writing books to meditation to Agile artifacts to understanding the consulting context and more, with more to come. We're having a lot of fun. Wish you were here.
Instead of admonishing, tell your story.
Lately, I've been thinking about the importance of striking a balance--finding a way to accommodate seemingly contradictory conditions--and how frequently that can make or break an interaction or relationship. High performing individuals, leaders and teams constantly acknowledge and embrace the paradoxes that come from successful balance.
When in balance, we show our strengths and disclose our vulnerabilities. Teams in balance enjoy the sweetness of harmony, yet work through conflict to achieve creativity and innovation. Most of us appreciate the opportunity to give support to others, and, in order for support to occur, someone has to be willing to ask for...
The word “team” gets tossed about with startling abandon. I’ve heard upper level managers refer to a division or department as a “team.” (An even more egregious error occurs when the same group is referred to as a “family.” But I digress.) What is a team really? In my last posting, I asserted six conditions for “team-ness.” They are a good jumping off point for more blog posts, so I intend to work my way through the list. ( Click here for the complete list. )
The first condition: Shared Goals for results/outcomes/deliverables
I’m going to state it as bald...