Quantcast


Apr 30 2010

Finding and Establishing Cadence: Team Updates & Milestones – Timing Is Everything

leadership and cadence at DellMy mentor at Dell liked to talk about cadence. It was a word that I understood the first time they brought it up. We were talking about a new "project team" I was struggling to get off the ground.

The issue I was having with the team building was one of commitment. I had several Directors as well as several peers in this group. And the mission of the project was to define and establish new "innovation" projects for Dell.com. There were two problems with that idea right off the bat. 1. I was not an established "leader" to the Director-level team members; 2. "innovation" was not always tied to ROI, and thus people's commitment to do the work was going to be a matter of "leadership without authority."

Basically, I needed them and needed their participation. They did not need me, nor did they necessarily want another "project" or another "meeting" to put demands on their workload. In a heavily siloed and matrixed organization I relied on my people skills, my enthusiasm for doing good work, and my ability to lead without authority. (It's a skill they are now teaching in some project management classes, look into it.)

So here's what cadence is all about.

  1. Understand the rhythm or timing necessary to get the work done, while not asking for too much from these "volunteers."
  2. Prepare for every meeting like it was a major presentation, give a detailed agenda, follow up with detailed action item lists within an hour of the completion of the meeting.
  3. Establish a regular meeting that works for everyone who is essential to success. (It's okay to let some nay sayers, or "anti-bodies," drop off the radar, but for the critical path team members do everything you can to accommodate their schedule requests.
  4. Give credit, spread the love, share the wealth. (Many times these "innovation" teams will not have a focused project to deliver on. I this case, we were trying to make the business cases for budgeting and getting approval for new projects. The process was the project.)
  5. Be firm, friendly, and establish your leadership of the meetings. (A high-ranking member of the team in this case, was not all that supportive of my including them on this new team and thus signing them up for meetings and "possibly" action items. But losing this person's involvement would've been devastating to the project. So I bent over backwards to give them flexibility. At the same time, I had to show my commitment to the project, and my commitment to keeping them as an essential player on the team.
  6. Value every one's time. (If you can give back minutes by breaking up your "call" early, do it. And always, always keep everyone "in the loop" on progress, kudos, and visibility within the company.

So the essentials of Cadence, on this project were the things that I could have an impact on.

Frequency of the standing meetings. (Once a week for an hour is a HUGE commitment. But every-other-week for 30 minutes might allow your program to drop off their radar completely.

Frequency and quality of the emails regarding agendas, summaries, action item requests, check-ins and progress. (Too many updates and folks will start to tune you out. Not enough and they will forget about your requests and maybe "miss" a meeting or two.)

Syncing with the style and communication preferences of each member. (Some people like Instant Messaging some people hate it. Some are email adverse and prefer the phone. As in any performance, know your audience. The more you know about working with each individual the better you can support their work on your project.

Always offer to help on any of their non-essential projects. (Returning the favor with volunteerism is a great way to establish raport with your team mates. I would often ask each member, in private, "How can I help you?" Sometimes the offer was suspect and refused. But often I got a few tasks or "reviews" that I could do easily to help establish the connection and camaraderie with the other person.)

Here's the complete point: Without direct authority over some one's time or budget, we are all volunteers on cross-departmental teams. "Air cover" comes in when you need to ask for a higher-authority to give attention to your project for the benefit of every one's motivational participation.

And while air cover from your manager or your manager's manager (VP titles can help motivate more than a Director title) can inject some energy into your troops, it's really the leadership and consideration of your role as volunteer coordinator that will make or break your "innovative" and "non-ROI-driven" project.

@jmacofearth
permalink: http://bit.ly/team-cadence

Fast Company has a nice post on leadership presence.

Tags: , , , , , , , , , , , , , , , , , , , , , , , ,


Sep 03 2009

Creating Passionate Teams – Managers Hold the Spark

Category: career,executive learnings,teaming & leadershipjmacofearth @ 7:00 am

"More than anything else talented people want to be in environments that both appreciate
and cultivate their talents."
Scott Berkun

Collecting two key thoughts about teams and empowered project management. These two folks have changed my entire perspective on teams and management and passionate leadership. Even when we are not "managing" anyone, we are all project managing each other in our work. We manage up to get what we need from the executive leadership. And we cooperate across disciplines and business silos.

“What do you need from me in order to kick ass on this project?” — Kathy Siearra, Creating Passionate Users

From Scott Berkun: How to Manage Smart People …managers have many undocumented, unsaid,
but incredibly important, functions. They have more to do with enabling the happiness and productivity of the people that work for them than anyone else in the organization.

…he created an environment where good ideas rose to the top, further encouraging smart people to
want to contribute. The bossman made working for him feel like a proper relationship:
he got something from us, and we got something from him. I think that this kind of management
style requires more skill and savvy than a more hierarchical drill sergeant type of
manager.

More than anything else talented people want to be in environments that both appreciate
and cultivate their talents.
Any successful manager of talented people has to come in
every day, in every meeting, and directly work towards making this happen. This doesn’t
mean coddling people, or denying the team’s goals in favor of making someone feel
good. Instead it’s about making actions and decisions that both clarify how people’s
talents apply to the team goals, and working to keep the team happy, motivated, and
focused in that application.

One practical way to overcome this [lack openness] starts with a meeting. The manager sets up a meeting
with the employee and opens a discussion about how they like to be managed. The manager
should explain the purpose of the meeting, and asking clarifying questions about what
the other person says. Generally, the manager should say little about their own opinions.
Zero. Zilch. Zip. Instead, their job is to listen, help clarify the other persons thoughts
and then go away and think about what they said.

First acknowledge that you have weaknesses, both in skills and in knowledge. Second, admit that you’re ignorance hurts not only the product or website, but the team itself. Third, get help in hiring experts for roles you are not familiar with, and go out of your way to involve them, and their perspective, in
your decision making process. Deliberately hire first rate strong willed people to represent
disciplines that you tend to undervalue. Force yourself to be on the top of your own
game, and to make sure it’s not bias and ignorance that drive you, but good judgment
refined by divergent perspectives.

references
Kathy Sierra: BrainDeath by Micromanagement
Scott Berkun: How to Manage Smart People

@jmacofearth
permalink: http://bit.ly/team-leadership

Tags: , , , , , , , , , , , , , , , , ,


Aug 19 2009

"Who Asked You to Do This?" and the Critical Path to Work Success

Screen shot 2009-08-19 at 9.04.41 AM

The Vostro: I Believe Page is Gone

My mentor had a great question that often threw light on the murky subject of "ownership."

"Who asked you to do this?" she asked, when I came to her with almost every new problem I was trying to solve.

After trying to explain how I had been asked to do a certain task she would smile and say, "That's not your job."

Wow. I can't tell you how many times this question and reasoning from my "manager" saved my butt.

The biggest example I have of this was when I was assigned to be the global contact for large business when Dell ramped up to launch a new brand, VOSTRO, in the summer of 2007. While VOSTRO was aimed at small and medium businesses, the "channel businesses" did not want to miss out on the opportunity to tell a new story and sell a "new" computer. There was a great campaign that I was proud to be a part of called, "I Believe." It featured testimonials from small business customers and how Dell believed in small business, because, "After all, Dell was a small business once too."

My role on the project was to assess the marketing materials Dell's small business group was putting together for VOSTRO and then make sure my "clients," the business segments in all of the countries where Dell did business, including the US, were provided with large business appropriate materials. So banners and web pages and graphic design that said things like, "Helping Small Business Do More With Less" would become "Helping Your Work Force Do More With Less." [This example is made up and does not represent actual Dell slogans from the campaign.] And then I would make sure 1. that the business partners in all of the major country groups were aware of the upcoming launch and materials AND 2. deliver all of the necessary images and banners and advertising copy was delivered a month in advance of the launch in the 30+ languages of the countries where Dell would be launching VOSTRO.

I had been at Dell a total of two months when my manager gave me this job. But rather than tossing me to the wolves and letting me "figure it out," she would patiently listen to my overwhelm and then come back with her simple question. "Who is asking you to do this?"

It turned out that there were a lot of people working on VOSTRO! And a lot of people assigned to delivering creative and technical assets to the "other countries" and "other groups." What she helped me understand was, while I felt the world on my shoulders with the project, my task was not to create or translate the 100 or so banners. My task was to 1. stay organized and not get overwhelmed; 2. continue to ask for what I needed on behalf of my "clients" the non-small-business leaders around the world; and 3. when I could not secure the delivery of the banners and content I needed to escalate that request to her. That I could do.

So while the massive machine of Dell hummed along around me, creating and building new web pages and new banners and new flash demo files, I was continually asked to refocus my attention on what I COULD manage and let go of the things that I COULD NOT manage. It was a great lesson in large corporate negotiation and navigation.

A number of things broke down in the process of launching a new global brand. And I am certain I could have been targeted for responsibility for those breakdowns, had I willingly accepted all of the tasks that were pushed my way. But I was actually much LESS powerful than all that.

I asked again and again for non-flash assets for the foreign countries. [Flash is still not a global standard, and with slower connection speeds it's actually quite a problem.] I raised the issue in every meeting I had with the creative and production teams. But it was not my issue. I could not create the low-bandwidth images myself. [I knew how, and could have executed on a couple of them, but...]

A week before the launch, my manager and I put the finishing touches on my final wrap-up PowerPoint deck for VOSTRO. And along with the slide where I detailed the request for NON-FLASH assets in BOLD and ALL CAPS, we made a note that we were still not able to confirm the delivery of these mission critical files.

She sent the slide show to the VP of our group with a note regarding the lack of non-flash demos.

I was honored to be on the short list (5 people) who received that email and the ensuing chain of messages that crackled down like thunder for the rest of the day. The fallout from the miss rippled through our organization for the next two weeks as VOSTRO was delayed in some countries. I continued to be amazed that my manager had included me on the thread. After all it was my project, my slide show and my issue that I had not been able raise enough alarm about to actually get the non-flash content created. [I learned later, under different management how zero transparency worked.]

The most amazing response came from the VP at the time.

"Don't we always create low-bandwidth non-flash assets for every launch?"

@jmacofearth
permalink: http://bit.ly/ibelieve

Tags: , , , , , , , , , , , , , , ,





social media innovation group

future posts

A Collaborative Space: WebEx, Go-To-Meeting, Skype, Basecamp (Teaming/Meeting Tools)
Twitter Problem: How do you find enough interesting people to follow? Then how do you keep up with them?
The Agile Mind: Construction, Evolution, Care, and Feeding Instructions for Mental Flexibility

Add to Technorati Favorites

Blogged Blog Directory

Austin Interactive Marketing Association

jmacofearth's socialmedia dashboard via AllTop

99, near perfect hubspot ranking