Will Smith on Living and Success

Actor Will Smith passionately espouses his philosophy for life and success in this well-crafted video. Numerous linkages to the Responsibility Process and Keys to Responsibility are evident. As you watch, listen for references to intention, awareness, and confront.

This video is evocative and inspirational to say the least. If it doesn’t inspire you to own who you are and step up your responsibility practice, what will?

Tip: Listen to Will’s first sentence in this video. 8 words. That phrase confronted me — as did many others. What will it take for you to say the same thing with the same conviction?

Comments please.

Popularity: 3% [?]

  • Share/Bookmark

Related Posts

Should you “throttle” responsibility?

Leaders who are relatively new to learning about the mind’s internal Responsibility Process™ often ask:

“What about the person who is too responsible?”

One such question landed recently after I co-presented a webinar with Zach Nies (VP Products, Rally Software) called The Best Kept Secret of Agile Software Quality. Our message was that quality is a 3-legged stool of process, technology, and people. Most organizations attempt to understand and improve process and technology, but don’t adequately understand how to address the people leg of the stool. That’s where the Responsibility Process helps. The Responsibility Process is a great framework for developing teams and environments of true shared responsibility where people will voluntarily confront and overcome silos and other barriers to quality.

Here’s the question I received later that day: How do we best manage “responsibility throttling”?  At some point, if an individual takes on too much responsibility, his/her effectiveness is compromised.  Is this topic covered in any of your publications?

Great question. And I love the term “throttling.”And most of us realize that over-committing and under-committing are both problems.

There are three conditions worth considering

  1. The individual who takes on too much
  2. The teammate or leader of an individual who takes on too much
  3. The leader who assigns too much and does not get push back

A previous post looked at the first condition. This post will tackle the second condition. I’ll address the third condition in a subsequent post.

I wrote back:

Please don’t ever think of throttling responsibility

What you refer to as taking on too much isn’t responsible at all. It is most likely a mindset of Obligation and is a knee-jerk reaction to “feeling bad if I don’t do something” (which is the mindset of Shame).

This pattern is a common anxiousness that something won’t be addressed, so “I have to” take it on. Remember, we graduate upward from island to island. Someone with too much on his or her plate in our society gets to brag and complain about their importance — a coping mechanism.

No one can take on too much true responsibility — if you are clear that responsibility is defined as owning your power and ability to create, choose, and attract. The most responsible people I know learn how much they can pile on their plates and still be effective. And the most responsible leaders I know understand how to set clear priorities and move everything else aside so their colleagues have breathing room.

I’ve sat in executive meetings in agile organizations and seen a highly responsible CEO test the executives as to whether the action items they signed up to for the coming month and quarter could be accomplished in a sustainable fashion. It was a beautiful thing to watch such dialog. Such leaders believe that one of the worst things they can do is allow their reports to over-commit. The next week I was in a board room with a Senior VP who was piling more and more and more onto his folks to prove he could drive accountability. Guess which organization is thriving?

So what is a well-intentioned leader to do?

First, I recommend you increase your own study and practice of responsibility as taught by the Responsibility Process and the Keys to Responsibility. This will help you acquire a much clearer perspective of your own and others behavior so you will see that you want to encourage true responsibility but perhaps throttle acts of Shame and Obligation — or simply biting off more than can be chewed.

Second, apply the Responsibility Process as a framework for leadership, growth and change to support the agile principles and values of people and interactions, few clear priorities, sustainable pace, continuous learning and improvement. It’s a powerful combination.

Third, and most specifically, create a focused feedback loop for the person who takes on too much so he or she can begin to see what you see in their behavior. Help him to understand the idea of a few clear priorities and sustainable pace.

Let me know your thoughts.

Popularity: 3% [?]

  • Share/Bookmark

Related Posts

  • No related posts

The Best Kept Secret of Agile Software Quality – Webinar Replay

I was honored to collaborate with Zach Nies, VP Products, Rally Software on The Best Kept Secret of Agile Software Quality which was apparently viewed by over 900 people on Tuesday, January 12, 2010. You can watch the replay. We present for an hour and answer questions for another 25 minutes.

The theme is using the Responsibility Process as a framework to take ownership and build environments of shared responsibility where quality issues can be addressed and overcome. It was a bit of a controversial topic. We received a lot of supportive feedback as well as some dissenting comments — often a sign of being on the edge.

Download the Presentation PDF | Go to the Replay

Do you struggle with quality?

Shared responsibilit for quality

In Agile software development, the whole team is responsible for quality, but there are many barriers to accomplishing that goal. When quality issues arise, teams often resort to a silo-based approach to finger-pointing and justifying, citing lack of control or time constraints as the root cause. Most development teams truly want to improve quality but they don’t know what to do, and often feel frustrated and powerless to change the status quo.

But there is a solution. Join Dr. Christopher Avery, expert on the Responsibility Process, and Zach Nies, VP of Products at Rally Software and an expert on Agile quality, as they reveal the secrets to achieving sterling software quality at your organization.

You will learn how to see common Quality problems in a new way and understand their causes. Many people only focus on process and technology to address these issues; we will talk about a 3rd component: you. You will learn:

  • the relationship between quality and ownership
  • the difference between accountability and ownership, and how this difference affects quality
  • How the Responsibility Process can be used as a framework for people and interactions to continuously improve quality
  • How to apply the Responsibility Process to your development team

Don’t miss the chance to re-energize your teams and unite them via the shared goal of delivering better quality software.

Download the Presentation PDF | Go to the Replay

Popularity: 4% [?]

  • Share/Bookmark

Related Posts

Are you too responsible?

Soon after a leader has learned about the Responsibility Process, often she will ask:

“What about the person who is too responsible?”

What a great question. Read this if you take on too much, or if you know someone who does. Three conditions are worth considering:

  • If you are the individual who takes on too much
  • If you are the teammate or leader of someone who takes on too much
  • If you have a leader who commits employees to too much

This post will tackle the first condition. Subsequent posts will address the other conditions.

The question usually rolls out like a plea for help: What does the Responsibility Process say about someone who takes on too much? I think I’m too responsible because I take on more and more even though I can’t handle more.

Because I can be a little slow, it took me years to figure out that the very best response from me was a probing question. I now reply with “Why do you take on too much?” I now predict with better than 90% accuracy what the leader will say: No one else stepped up and I felt bad it wasn’t going to get done, so I had to do something.

The Responsibility Process always leaves clues

That’s what is so cool about the Responsibility Process. It is reflected in our language so if we know what to listen for, we can learn so much about ourselves and others.

So, why can I predict that response with 90% accuracy? First, the Responsibility Process teaches that taking on too much isn’t responsible at all. How does it teach that? Because in the mental position of Responsibility you feel freedom rather than overwhelm. You are taking charge of your life and moving forward. And I never hear someone who has taken on too much sound like they feel really really good about it.

So, even though they use the term responsible, I look somewhere else on the chart for a better answer. Remember, all 7 positions in the Responsibility Process represent a different definition-in-use of responsibility. But 6 of those positions aren’t really owning it at all. For example, the phrase “my broken leg from skiing is his responsibility” may use the term responsibility but the mindset is one of Lay Blame. So when I hear the phrase “too much responsibility” I listen for the mindset rather than the word.

Someone who feels that they have to take something on is not operating in the mindset of Responsibility.

It looks much more like Obligation to me

But, you say, she does not have to take it on. Agreed. The thought of “have to” is a mindset, an unconscious choice based on an assumption of being trapped. When you do it to yourself you only think you have to. The truth is you don’t have to do anything. We choose to for whatever reason.

Here’s the second reason I can predict the response above with 90% accuracy. The Responsibility Process also teaches that each of us tends to be more conditioned toward one of the positions of irresponsibility than the others. If you are the kind of person who takes on too much, each time you take on an extra load you probably think you are doing the right thing. It’s the weight of the whole load together that feels like you are overly responsible.

But look at the answer to my probing question “Why?” They say “I felt bad” (that’s Shame) “so I had to” (that’s Obligation).

Remember, you graduate from a lower position in the Responsibility Process to a higher position when, for whatever reason, you refuse to hang out in that lower position around an upset. So, I’ve learned that about 90% of the time when someone tells me they are overly responsible, they are really Obligating themselves to something in order to avoid feeling Shame that it won’t get done.

It’s a common and recognizable pattern.

You can never have too much true responsibility

I mentioned above that taking on too much isn’t responsible at all. While it may seem like the right thing to do at the time, the truth is that you will remain overwhelmed and many things (for which others may be counting on you) will go undone. It can be seen as selfish—taking opportunity off the table for others, then doing nothing with it.

But the real reason is that there is no such thing as too much real responsibility. As you learn to own more and more of your life, you own more of your choices. And then you own more of your relationship to the universe around you. And when you do that you feel a part of everything—you interact with everything.

So taking on more is not the same as feeling a part of more. Yes, reduce your Obligation, and increase your true Response-Ability.

Takeaways

If you have a tendency to take on too much or coach people with such a tendency, here are some takeaways from this post:

  • Remember the keys to Responsibility are Intention, Awareness, and Confront. Read the post again to see how it is reminding you of your true intention, making you aware of your mindset, and inviting you too confront what is really true.
  • Listen to your reasons for taking on something. If your reason is to avoid feeling bad then ask yourself this: How I can let go of feeling bad without piling more on my plate?
  • Remember, you are free to choose. Yes is a choice. No is a choice.
  • You can also play to your own conscientiousness by asking yourself Is it better to take something on that you know probably won’t ever get done than to not take it on in the first place? After meditating on that question for awhile you may find your answer changing.

Popularity: 19% [?]

  • Share/Bookmark

Related Posts

Software Quality Webinar with Rally’s Zach Nies

Rally software’s VP of Products Zach Nies and I will present a free webinar The Best Kept Secret of Agile Software Quality. The date is January 12, 2010

Our premise is that software quality is a 3-legged stool composed of process, technology, and people. Most of the focus on improving quality goes into process and technology, but we believe the most gain is made from focusing on people and interactions.

Zach and I started talking about this at Agile2009 in September over lunch. He was telling me about how Rally’s customers complaints about their quality always make him think about Responsibility Process as a tool for improving quality. So we are going to make the case for using the Responsibility Process as a personal, team, and organizational approach to constantly improving software quality and value delivery.

We are going to give as many tips and tools as we can, offer more to download, and reserve 30-40 minutes for answering questions.

At this point, just a couple of weeks before the webinar, our presentation is coming together and the registration page is open. Already more than 500 people have registered — the fastest sign-up for any Rally webinar thus far.

Please join us. Register for the webinar

Details from the registration page

Date and time: Tuesday, January 12, 2010

1:00 pm Eastern  Standard Time (New York, GMT-05:00)

12:00 pm Central Standard Time (Chicago, GMT-06:00)

10:00 am Pacific Standard Time (San Francisco, GMT-08:00)

Duration: 1 hour 30 minutes
Description:

In Agile software development, the whole team is responsible for quality, but there are many barriers to accomplishing that goal. When quality issues arise, teams often resort to the silo-based approach of finger-pointing and justifying, citing lack of control or time constraints as the root cause. Most development teams truly want to improve quality but they don’t know what to do, and often feel frustrated and powerless to change the status quo.

But there is a solution. Join Dr. Christopher Avery, expert on the Responsibility Process, and Zach Nies, VP of Products at Rally Software and an expert on Agile quality, as they reveal the secrets to achieving sterling software quality at your organization. This event will include 50 minutes of presentation, followed by 30-40 minutes of extended Q&A, so come and get all of your questions answered.

You will learn how to see common quality problems in a new way and understand their causes. Many people only focus on process and technology to address these issues; we will talk about a 3rd component: you. You will learn:
* the relationship between quality and ownership

* the difference between accountability and ownership, and how this difference affects quality

* How the Responsibility Process can be used as a framework for people and interactions to continuously improve quality

* How to apply the Responsibility Process to your development team

Don’t miss the chance to re-energize your teams and unite them via the shared goal of delivering better quality software. And don’t forget to bring your questions.

Again, please join us. Register for the webinar

Popularity: 7% [?]

  • Share/Bookmark

Related Posts