Agile Organizations - Daring Greatly, by Jean Tabaka - Rally Software

Agile Organizations - Daring Greatly, by Jean Tabaka - Rally Software Agile Organizations - Daring Greatly, by Jean Tabaka - Rally Software

A Leader's Guide to<br />

Harnessing Complexity<br />

<strong>Agile</strong><br />

Business<br />

Bob Gower<br />

& <strong>Rally</strong> <strong>Software</strong>


<strong>Agile</strong> Business: A Leader’s Guide to Harnessing Complexity, By Bob Gower<br />

<strong>Agile</strong> <strong>Organizations</strong>—<strong>Daring</strong> <strong>Greatly</strong><br />

By <strong>Jean</strong> <strong>Tabaka</strong><br />

“...there is no effort without error and shortcoming; but<br />

who does actually strive to do the deeds; who knows great<br />

enthusiasms, the great devotions; who spends himself in a<br />

worthy cause; who at the best knows in the end the triumph<br />

of high achievement, and who at the worst, if he fails, at<br />

least fails while daring greatly...”<br />

—Theodore Roosevelt, April 23, 1910<br />

Dr. Brené Brown opens her bestselling book <strong>Daring</strong> <strong>Greatly</strong> with this<br />

quote <strong>by</strong> Theodore Roosevelt. Through it, we see how powerful one<br />

person can be when he or she chooses to “dare greatly.” But what does<br />

this mean for an organization? How does this apply to <strong>Agile</strong>? And what<br />

can we do now to become organizations that truly dare greatly?<br />

<strong>Agile</strong> transformations request a lot from us: they ask that we stick<br />

our toe in unfamiliar organizational waters and step outside our<br />

comfort zone. This requires some pretty significant daring on our<br />

part and a lot of organizational vulnerability. But with that daring and<br />

vulnerability come great gifts and the potential to create sustainable<br />

and transformative <strong>Agile</strong> change that goes beyond mere adoption.<br />

<strong>Daring</strong> greatly and acting through vulnerability requires courage.<br />

Think about an organization steeped in practices of detailed, longterm<br />

plans. While this planning may seem to provide the organization<br />

with a sense of security and direction, that isn’t always the case. What<br />

does it look like to act courageously in such an environment? How<br />

does it feel to invite change despite our fears?<br />

Instead of holding on to long-term plans, we seek opportunities for<br />

change. We recognize that as we welcome change, we also welcome<br />

growth.<br />

Cultivate a Culture of Vulnerability<br />

“Failure is not an option.” “You better be right.” “I’m trusting you; don’t<br />

screw up.” Does any of this sound familiar? Each of those statements is<br />

a prime example of organizational invulnerability.<br />

<strong>Daring</strong> greatly requires that we cultivate vulnerability—that we open<br />

up and run toward difficult things—knowing that our work may be<br />

harder and that we may eventually falter.<br />

Copyright <strong>Rally</strong> <strong>Software</strong> 2013<br />

www.rallydev.com


<strong>Agile</strong> Business: A Leader’s Guide to Harnessing Complexity, By Bob Gower<br />

This is hard enough to think about as an individual, let alone from<br />

an organizational point of view. To be vulnerable, a company must<br />

be prepared to take bold risks, even if it means potentially appearing<br />

too exposed. When we let down walls of invulnerability, we show<br />

tremendous courage and create opportunities for continuous learning.<br />

And in these deep breaths of vulnerability, the seeds of an <strong>Agile</strong><br />

adoption grow to become true <strong>Agile</strong> transformation.<br />

Eliminate Shame, Comparison, and Disengagement<br />

Think about how your organization sets goals and what the<br />

ramifications are for not achieving them. Does your organization have<br />

a culture of empathy or shame? Are team members meant to feel<br />

empowered <strong>by</strong> their learning or ashamed <strong>by</strong> their failure? If it’s the<br />

former, you’re on the right path in daring greatly to be <strong>Agile</strong>. If it’s the<br />

latter, your <strong>Agile</strong> adoption will most likely fail.<br />

Shame is corrosive. Comparison demoralizes. And when employees<br />

experience these things, they disengage. In such a toxic culture,<br />

the organization has ensured that no team will act courageously or<br />

cultivate its own vulnerability. Employees won’t step forward with<br />

an eye toward innovation and growth; they will hold back for fear<br />

of being perceived as failures. Teams will set low standards, adopt<br />

inattention to results, and discourage accountability.<br />

To be truly transformative, our organizations must not only act<br />

courageously and cultivate vulnerability; they must eliminate<br />

shame. Despite historically popular motivational tactics, shame is<br />

diametrically opposed to long-term team resilience and employee<br />

engagement. We eliminate shame within our organizations <strong>by</strong><br />

embracing empathy, cultivating compassion, and nurturing<br />

understanding. Successful <strong>Agile</strong> transformations can only thrive in<br />

organizations that are free from shame. By eliminating shame, teams<br />

turn small failures into fast-learning opportunities.<br />

<strong>Daring</strong> greatly is both an individual and organizational skill. Such<br />

daring requires courage, vulnerability, and the elimination of shame,<br />

comparison, and disengagement. If you feel your organization is ready<br />

for a healthy <strong>Agile</strong> transformation, dare greatly and help create a<br />

culture that embodies a spirit of innovation and learning.<br />

Copyright <strong>Rally</strong> <strong>Software</strong> 2013<br />

www.rallydev.com


Visit www.rallydev.com/<strong>Agile</strong>Book for<br />

the latest <strong>Agile</strong> Business news, videos<br />

and updates.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!