Showing posts with label deliverables. Show all posts
Showing posts with label deliverables. Show all posts

Sunday, December 22, 2013

Leader vs. Leadership: A Vital Distinction for Success

Leadership Bookshelf

Why we are so disappointed in our leaders?

We expect leaders to possess superhuman strengths, clairvoyance, sound judgment, integrity and charisma that most of us may personally lack. We are quick to criticize and become disappointed when those above us on the organization chart fail to meet these expectations.
As an antidote, there are tens of thousands of books and articles that give advice to those leaders to promote our fantasies of what leaders should be.

False Hope?

Yet today’s leader’s impact on behavior (as evidenced by the general level of leadership in corporations and the government) demonstrate that thee intended improvements from books and training have failed to materialize.
In short, despite the investment of billions of dollars each year on leadership development, the needle has failed to move much.
Rather than continuing to be disappointed on such a massive scale, perhaps we should develop a more effective set of best-practices in leadership development.
Rather than promote leaders as paragons and then be disappointed when they are not, I recommend we shift how we think about leaders in the first place and then change how we do leadership development.

Redefining “Leader”

A “Leader” is a person. When we focus on leader, we evaluate individual capabilities and hope that the individual uses the information to improve their performance. Sometimes we provide additional support to help the person make the change.

This is the medical model for leadership development:
Determine what is broken and then fix it.
A variation on the model is to find the person’s strengths and encourage them to exhibit more of them. The reasons these approaches don’t work are many and could itself be a future whitepaper. Some are explained in this webinar with Training Magazine Network.

Redefine “Leadership”

Rather than defining leadership as hierarchical, what if we saw it
  • As a corporate function similar to HR and Finance that has…
  • Three measurable deliverables: Direction, competence, and implementation…
  • That are completed not but just the people at the top…but is a shared responsibility…
  • That people complete by using processes that many have learned and by
  • Using the best organization/leadership language and tools…
  • That people have learned in  practice fields in which people use the new language and tools to address the existing strategic challenges
  • We are able to work across silos as a network of leaders who are closely bonded together because they jointly are responsible for the three deliverables, use common processes, language, and tools, and have had shared experience/competence/and confidence to work on the complex issues that matter.

Redefine Leadership Practice

Then we could…
  • Reduce individual competency/personality assessment
  • Focus on the strategic needs of the organization and not individual development needs
  • Create a stronger connection between leader development and improved organization performance
  • Rely less on the capacities of a few individuals and instead build organization-wide resilience
  • Move from leadership development activities which have demonstrated limited impact on organization performance to practices which help organizations more directly achieve strategic objectives
  • Build organizations that can more readily adapt to change
  • More easily able to re-engage employees who for far too long have focused on survival and not thriving
  • Significantly reduce the waste of time and money on analysis and instead focus on effective collective action
For specific ideas for new leadership tools and language,  check out these tools in The Leader’s Toolbox

The Implications:

Organization consultants, Human Resources and organization development professionals will need to realign their products and services to deliver more powerful products and services.

We need to stop writing about the trivial, have the fortitude to face the facts, realign our deliverables to clients/internal customers, and focus more fastidiously on outcome rather than process results.
This will requires the fortitude to say to ourselves that we have been less than successful and embrace the willingness to take on something new.

Recalibrated Leadership Mindset

In 1995 after having used the conventional leadership methodologies, I woke up one morning and realized this:
  • No one had ever thanked me for providing 360-degree competency feedbacks
  • No senior leader ever asked me when we were going to do the next one
  • I could never tie business results with organization performance
I faced the fact that my work had been less effective than I wanted. I contacted a number of peers who experienced the same. I then spent five years writing Leading for a Change: How to Master the Five Challenges Faced by Every Leader as a way to find a more productive framework.

I no longer provide competency or personality assessments as part of leadership training focusing instead on practical language and tools to do the leadership work.

——————— Ralph Jacobson
Ralph Jacobson is the founder of The Leader’s Toolbox
He provides a powerful platform for change through Coaching, Training & Consulting

Monday, June 10, 2013

Four simple principles for highly effective teams


 

The only principles that make a difference are the ones you know by heart, swear by, and live by. Everything else is just blather.

For a long time, I've been fascinated from afar by Agile programming practices, which have proven themselves on all these levels. I've wondered why they haven't been adapted for use by all types of teams, because they hold the potential to make teams far more flexible, innovative and productive.

So here's my shot at adapting those practices into four simple principles that all business teams can use. My hope is that they can help teams both execute and innovate in an excellent manner. I'd also like to acknowledge that Toria Thompson helped me develop some of these ideas.

This is a work in progress - I welcome your comments and will be happy to embrace any suggestions you have that further strengthen this approach:

Value the value: Too many teams operate without clear metrics, and thus they end up making fuzzy decisions. This is a slippery slope to disappointing results. Instead, teams should assign a tangible value to every deliverable, and – this is the important part – teams should track and validate these projections as work goes on. In this manner, team members can’t game the system, inflating values to give their pet projects priority treatment.

The philosophy underlying this principle is simple: businesses exist to make money, and if a project doesn’t support that goal in a tangible way, the team shouldn’t be doing it.
  • State the value of each project.
  • Create metrics that quantify the stated value.
  • Validate the value actually delivered, and reward team members for it.
Be open and honest: Keep all team communications, facts and status reports in the open and highly visible.

Look at the way your team currently operates. Is the purpose of every action crystal clear? Do you know why Lisa has been locked in her office for three days, or why John is conducting 32 interviews this week?

Clear and open communications have immense benefits. It should be obvious to everyone who is doing what, and why. When team members get stuck, they get help faster. When they succeed, others follow faster.
  • Avoid private communications.
  • Conduct disciplined weekly progress report sessions.
  • Hold daily “stand-up” sessions (you stand to keep them short).
  • Use images, mockups, etc. to make things clearer.
  • Make it easy to understand the purpose of every work product.
Shorten workplans: Break deliverables into smaller pieces that can be finished in shorter time periods.

The longer a team works before delivering a tangible result, the more likely the deliverable is to fall short of expectations. A far better approach is to break large projects down into smaller pieces, and to regularly complete deliverables.

By shortening workplans, teams also make it easier for team members to explore new strategies and take risks. This is because the cost of taking a risk and failing is minimized; you lose a week instead of six months. This tactic also maximizes flexibility, because at the end of each project the team can decide what to do next.
  • Shorten the length of time between deliverables.
  • Try to make every deliverable useable and functioning, rather than just a description of something that still needs to be done.
  • Whenever possible, make processes and deliverables reusable and adaptable for other purposes
Create interdependence: No one wins unless everyone wins. Period.

This is the best way to get a team to function like, well, a team. It also fosters insights, flexibility, and resilience.
  • Create shared metrics.
  • Partner team members from different disciplines.
  • Have members with similar skills swap tasks often, even in the middle of working on a deliverable.
  • Share responsibilities, ideas, concerns and alternatives.
If these principles make sense to you, you might want to give them a try. But I'd like to suggest you do so only on one condition: that all team members voluntarily want to adopt these principles.

Bruce Kasanoff is a writer and speaker.

Image credit: photo by Flickr member VisualPanic.

   
by:Bruce Kasanoff