Thursday Oct 29, 2009

Success and Failure

Failure as a springboard to success. Nice piece there from Jono Bacon on how to fail gracefully, recover, and move on -- learning all along the way. I like it. Very practical advice for managing projects -- or doing anything, really -- in a community environment where credibility can be earned and/or lost rapidly and publicly. Much of the issue involves just recognizing your mistakes, apologizing, and fixing things so your actions support your words. Works for me. But I think many people struggle with this concept because they wait too long and the issue gets too big and complex. Then they feel they can't back down. Too much has already been said. So, they spin. What I have found is that if you get out there fast and correct things early -- whether it's your fault or your company's or someone else's in the community -- it's much more casual and normal and most people will engage pretty well. Early apologies on the small stuff tend to be more understated and easier to deliver than those bigger ones later on.

Also, Jono utters this gem in the article: "In my experience of working with communities, successes provide an incredible opportunity to learn about our strengths, but failures provide the inverse opportunity to learn about our weaknesses." I totally agree. People have always told me that you have to fail because "that's the only way you ever learn anything" or words to that effect. I never agreed with that. Actually, that notion always pretty much made me sick to my stomach. The truth is that you learn just as much from success as you do from failure -- it's just that you learn different lessons, that's all. You need a balance of both. That's obvious, right?

Sunday Oct 25, 2009

Conducting Leadership

Here`s a interesting way to spend 20 minutes -- TED Talk: Itay Talgam: Lead like the great conductors. Great presentation. Lots of fun. There are so many ways to lead. And you can see both obvious and subtle differences expressed in some of the great conductors Talgam profiles. Some control forcefully and dramatically. Others relax and have fun and enthusiastically guide people along effortlessly. While others are more quiet and gently create an environment where musicians can express their talent so it`s difficult to tell who leads who. Fascinating stuff because you see it all unfold as a performance. Personally, I think the best conductors (or the best anything) just blend into the music so the focus is on the music and not on them.

That last bit is important. Many leaders miss it entirely and it undermines them completely. For me, the word "leadership" has very little meaning now. Actually, I view the word largely in the pejorative. The very concept has been so thoroughly abused these days (read a newspaper lately?) I am hard pressed to find leaders I can look up to and learn from. In fact, I have pretty much given up on the exercise as a waste of time. Don`t lead. Instead, do. Just do. And if you must lead or, gasp, call yourself a leader, then lead with doing in mind. That is the only way you will ever earn any credibility among those you think you lead. It`s also the only way you will ever attract naturally those like-minded individuals who want to grow with you -- not as a result of you.

Wednesday Aug 26, 2009

Emanuel as a Project Manager

Interesting article in the NYT about Rahm Emanuel and his management style -- Emanuel Wields Power Freely, and Faces the Risks. I`m not interested in any of the political propaganda and myth making in the article (although I do find that stuff entertaining at times), but instead I`m much more drawn to how Emanuel manages a president. That`s a difficult task in general and especially these days, but that`s what Chiefs of Staff do for the most part. And there are some simple project management lessons here that are obvious because the position is so high profile and this Chief of Staff plays that card to the max. The constant emailing and phone calling to extend presence. The requiring of and then responding to weekly written reports from staff members to keep people focused. The carrying around of note cards and to-do lists to not forget anything. The maintenance of a personal database of contacts running into the thousands of names to demonstrate influence. The mandating of deliverables so achievements can be measured and quantified. And the assertion of power as pervasively as possible in an effort to leverage and create even more power (or in Rahm`s case, intimidation). All of that is basic stuff to a good project manager. The difference is only scale.

So, I wonder how Emanuel would deal with some of the projects I am working on?

Monday Aug 03, 2009

Meetings, Meetings, Meetings

Here`s an excellent article from Paul Graham exploring the very real distinction between how managers view meetings and how makers view meetings -- Maker's Schedule, Manager's Schedule. Makers, in this case, can be writers, programmers, or anyone making things for a living. Basically, managers meet so often that they split up their days into 1 hour chunks back-to-back because that fits how they think and work. But makers simply can`t function that way. Makers need more time to do their thing. They think very differently than managers, and one hour just doesn`t cut it. In fact, two or so manager-oriented meetings can destroy a maker`s entire day. And big problems come in when you mix these two styles of work. I totally agree with the article. But I would go a bit further and suggest that the best project managers are actually makers who work on a makers schedule. They still do project management, but they work their tasks with a makers mind, not a manager`s mind.

Thursday Mar 05, 2009

The Chief of Staff

I have always been interested in the role of Chief of Staff. Presidents have these guys around, and so does the military. And now a lot of companies have them as well. It seems like an odd role at times, though. Good chiefs have massive power in their own right, but they also have to reflect the boss almost perfectly so their own opinions vaporize. Seems like an interesting dance. Here is a very interesting and long piece on Obama`s chief of staff -- Rahm Emanuel: The Gatekeeper.

The Stories of Community

Why Stories Matter: The art and craft of social change -- "Learning skills and practices is not like learning a formula; it’s more like learning how to ride a bicycle. You can read 10 books about it or listen to someone lecture about it all day, but how do you really start learning to ride a bicycle? You get on. And you fall. That’s how you learn practices. That’s how you learn organizing." -- Marshall Ganz

Nice article from Marshall Ganz on using the power of story (four specific levels of stories, actually) to engage people and build communities that drive change. Story telling is as old as it gets and remains probably the most effective way to deliver information that resonates. Here`s a little Ganz video, too. Good stuff.

Monday Mar 02, 2009

The "New" Organizers

People have been organizing and building communities forever. But every once and a while a team does it particularly well. The Obama campaign's community effort was an example of that and it's well outline here -- The New Organizers, What's really behind Obama's ground game. What I like about their strategy was that they combined the best of multiple worlds to create something new.

From Zack Exley's post: "The 'New Organizers' have succeeded in building what many netroots-oriented campaigners have been dreaming about for a decade. Other recent attempts have failed because they were either so 'top-down' and/or poorly-managed that they choked volunteer leadership and enthusiasm; or because they were so dogmatically fixated on pure peer-to-peer or 'bottom-up' organizing that they rejected basic management, accountability and planning. The architects and builders of the Obama field campaign, on the other hand, have undogmatically mixed timeless traditions and discipline of good organizing with new technologies of decentralization and self-organization."

That's interesting. You don't often hear community building described that with organizers using the best of both top-down and bottom-up approaches. So, in that sense I agree with the "new" bit, and it's a welcome lesson for all of us work in community-building positions -- any community.

I found that post on the Obama's guys from Barton George -- It takes a Community (and they could use a Marketing Guide) — Mozilla Debut’s theirs -- as he was talking about community development efforts at Mozilla, Ubuntu, Debian, and OpenSUSE, and he points to the new Mozilla community marketing guide (see Patrick Finch). I sent these links to advocacy-discuss on OpenSolaris so we can talk about these issues, too. Teresa started the thread recently in an effort to get some ideas going for how we can do more as a community to organize ourselves. We've had this discussion before on OpenSolaris (many times, actually), but we still have some work to do to really document a substantial guide that we can all get around and drive together. We have some very good bits and pieces spread across the community, but perhaps its time to bring it all together into one document and label it as such?

Saturday Feb 28, 2009

Never Waste a Really Good Crisis

Huge article in the NY Times about the financial crisis. It's called The Big Fix, by David Leonhardt. Really nice bit of perspective and history and a great read. But what keeps jumping out at me is one quote that puts things into an interesting context:

"TWO WEEKS AFTER THE ELECTION, Rahm Emanuel, Obama`s chief of staff, appeared before an audience of business executives and laid out an idea that Lawrence H. Summers, Obama’s top economic adviser, later described to me as Rahm’s Doctrine. 'You never want a serious crisis to go to waste,' Emanuel said. `What I mean by that is that it's an opportunity to do things you could not do before.'"

That's absolutely true. Even a quick flip through history demonstrates this concept quite clearly and it cuts right across a variety of societies. The leaders of countries (the smart leaders, anyway) tend to use a serious crises to change policy significantly and usually in ways that, in retrospect, represent an obvious paradigm change. In other words, big changes that are only realized later. I'd feel better about it if the power elite suffered the same consequences of these paradigm shifts as the rest of us, but that's not how the world works. I get that. Also eerie about Emanuel's comment is just how much it reminds me of Naomi Klein's latest book, Shock: Disaster Capitalism, in which she documents leaders manipulating events, shocking their populations, and changing policies radically (and generally to the detriment of the people). This phenomenon is not new, and it's not used exclusively by leaders of so-called capitalistic societies. Noam Chomsky has talked about the concept for years, especially and most recently with respect to how governments around the world used 911 to clamp down and reduce freedoms if those tendencies were present in the first place. The crisis was their opportunity. And they didn't waste it. Now, in the quote above, Rahm is obviously talking about fixing things, but the process is the same as wrecking things: you do it using a crisis.

So, if the power dudes view a good crisis as an opportunity never to be wasted, why don't we feel the same way and do the same thing? It's certainly a different way of thinking, but it can be liberating if you look ahead and actively jump paradigms on your own terms instead of holding on to the past as it crumples under your feet because others are acting in their own interests. This is a good lesson for project management as well. The life cycle of any great project snakes around like a river running wild, so it pays to step back occasionally and plan for those times when things break badly. They are opportunities "to do things you could not do before." Take advantage of them.

And finally, here's Rahm's crisis video at the Wall Street Journal.

Sunday Feb 15, 2009

Transparent Leadership Obvious to Everyone

Japan Airline Boss Sets Exec Example (CBS Evening News). Here`s another great report about Haruka Nishimatsu`s leadership at Japan Airlines. There`s nothing complicated here. This should be recognizable to everyone who works for a living -- those who earn their way every day. It`s leadership. Many leaders brand themselves special and leadership itself as some special art that only a few can master. I think that`s propaganda. The best leaders grow from the bottom up, they continually earn their support serving the community from which they came, and they don`t distance themselves from everyone once they attain their status. Simple. Nishimatsu is rare. So is leadership.

JAL tag here on this blog. JAL tag on delicious.

Wednesday Jan 28, 2009

Requesting New OpenSolaris Projects

I've been setting up OpenSolaris User Group projects and mailing lists on the site forever (100+ now). Starting this week I'm also setting up development projects and communities. The process is 100% manual, but it's not too bad at this point. As long as you don't have to mess around with Jive, setting up project spaces and lists can go pretty quickly. And that brings up another point. I am no longer setting up Jive gateways to Mailman lists. Jive doesn't scale well to the number of lists we have, and the gateways break too frequently. Plus, the forums attract too much spam. So, we are going to replace Jive entirely as part of the new webapp we are building. In the meantime, we can't keep creating new forums that need fixing since that takes critical infrastructure resources away from doing much more important work on the site. In fact, I'm actually deleting forums on a limited basis where I can. Also, we are coming to a critical time over the next couple months migrating to the new site, and when that process is under way we'll start the requirements gathering conversation for replacing Jive. Our Mailman lists, on the other hand, work just fine for their capabilities. I'm looking forward to finding a new web forum solution that suites the community's needs. Stay tuned for that.

Also, here's a reminder when requesting OpenSolaris projects. When you request new projects on the project-set list, please give the name of the project, the name of your list, and the user names of the leaders who got the project/list approved. I need all three bits of info, so it that's not in the thread you forward to project-setup, please add it. This will expedite the creation of projects. And please be mindful of trademark issues. Use generic, descriptive words to title your project. For background on this, go to the projects portal, the project set up page, and the project lead reference page.

Finally, as you know we will be moving to a new project creation process after the new OpenSolaris Constitution is approved in the upcoming March 2009 elections. Until then, we are using the current system. Here is more information on the proposed group creation process.

Saturday Jan 24, 2009

Don't

2009: Don't Just Do Something: "I had been looking at the problem in the wrong way. As is natural and intuitive, I had been looking at what to do, rather than what to not do." -- Matt May

Great quote. If I could only do more of this not doing I'd be much better off. I think too much. I do too much. And that's not an effective long term strategy.

Monday Apr 14, 2008

Starting Fires

Scott Berkun is back and Making Things Happen in project management. I have to pick up a copy of this book when I'm in San Francisco in a couple of weeks. I participate in Scott's project management community, and I learn a great deal as a result. Looking forward to the updated read.

Monday Sep 24, 2007

Opening from Closed: 3 Quick Steps

Over the past four years I've been trying to boil down to just a few steps just exactly how we are building community on the OpenSolaris project. After all, we are opening a previously closed project that already had significant operations, so there has to be some sequence here, right? Well, it may not seem like it at times, but there is. And it's complex. But I think I can fit just about everything into one of these three big buckets right here:

3 Steps to Opening from Closed:

  1. Move your own operations outside in stages. Begin with the obvious stuff such as lists, people, and conversations. Then move to code and infrastructure and tools and such. Absolutely nothing will happen outside, however, unless you first start talking outside and building a body of content outside that everyone can see and participate in. It doesn't matter that there is no community yet. It will develop over time. Just close the internal lists, open external ones, and move yourself outside. You may have to keep some closed lists to discuss the proprietary stuff you haven't opened yet and you may have to live in two worlds for a while too. But this should be temporary.
  2. Engage external people as insiders. This is an attitude shift. You have to see external developers as your peers. They are not a market and you are not building a corporate program. They are your peers and you are building a community of equals. Everyone's an insider and everyone's an outsider. Next you start working and collaborating on the code and infrastructure you've been moving out as well. Over time, a new dynamic will form where you create stuff outside, but first just get the closed bits out there so you have something to work on together. You can talk forever. Eventually, you have to work on something.
  3. Build community and leadership. I've always believed that the building of community occurs as a result of talking outside and working outside. It's really very simple. You will attract people if you are open and if there's something for everyone to do. And you have to talk to each other to get anything done. Now, over time you will have to enable people to grow and lead projects and such, so you have to let go. You are no longer running a closed project or corporate program. You are now part of a community, and you have to earn your way just like everyone else under whatever system the community creates. This last step of letting go is just as importing as the first step of moving our own butt across the firewall. Without it, nothing happens.
What do you think? And better yet, how many more big details can you add to the three buckets? Each step has a million details, of course, and many steps happen simultaneously and repeatedly as you open -- especially on large projects involving millions of lines of code, thousands of people, and processes that would fill a library. It takes time. Get used to that idea right up front. It's not quick.

Saturday Jul 30, 2005

The Art of Managing Projects

Nice little podcast here with Scott Berkun, the author of The Art of Project Management. It's really short, so give it a listen if this stuff interests you.

What's nice about Scott's take on project management that it seems quite realistic. Which is refreshing. He takes things like politics, power, execs, and egos seriously when he talks about managing projects, developers, schedules, budgets, and everything else that comes into play. So much to learn. He's got some interesting stories from Microsoft, too. :)

Scott's web site is full of resources for project managers. I'm participating in his PM Clinic forum now. It's interesting to exchange ideas and information with other PMs across the industry.

About


Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
Bookmarks

No bookmarks in folder