Monday, March 5, 2012

Leaders and Managers

At one time--quite a few years ago now--as a contractor in the construction business with several teams of hard-working people, lessons about improving the way people come together to accomplish goals was a daily part of life. It still is today but one such incident from that earlier time stands out with great clarity, a memory and line of thinking that has only grown more important with the passage of time.


Two new employees (first day on the job) are excavating around the perimeter of the job site one afternoon. Due to terrain and existing obstructions, they are manually excavating a trench with shovels and picks.  Eventually, the trench becomes a footing for a small stone retaining wall alongside exterior concrete walkways. Even standing on the other side of the job site, the grumbling and muttering between the two excavators along with their frequent questioning stares around the area at the activity of others is a sure indication of some issue. 


The Supervisor (also a new employee) and I are discussing plans and logistics in a "quiet" spot. The drama implicit in the actions of the two newbies grumbling their way through the sticky, black clay is demanding more and more of my attention. After we decide the planning and logistical questions, I ask the Super how the two new employees are doing. He shakes his head, lowers his eyes, staring soulfully at the tip of his boots, saying, "I just don't know. They seemed sharp enough--and, maybe they are. They claimed they were ready to work but... well, they might not pan out."


"You want me to have a talk with them," I quietly suggest?


"Sure," he says looking up, "Maybe you can talk some sense into them."


So I make the rounds of the job site, wandering a bit and casually talking with crew and subs while incrementally approaching the two shovel wielding newbies. When I reach them, I introduce myself, shake hands, and ask them how their first day is going.


Their initial response is a rather dismal, "OK, I guess," without any eye contact. To continue the conversation and draw them out I ask, "What are you building here?" pointing to the excavation.


The answer is stunning. They both simultaneously exclaim, "That's the problem: We don't know!"


Yes, that is certainly a problem: Sound familiar?


It happens a lot in every area of human endeavor. Instead of bringing new people on board through the sharing of vision, goals, and desired outcomes, a different approach is taken. One that involves unilateral command, disciplinary action, and micro-management. It goes something like, "Dig a hole from point A to point B at a depth of C with a width of D. Get it done today or don't come back tomorrow." 


That is a recipe, as a manager, for long fruitless hours, stress, heart attack, poor outcomes, and failed projects. A machine might be "managed" in that way but people must be led. 


So, I gave 30 minutes of time to the new employees discussing our company, our organization and the project we were working. Not "laying down the law," instead having a frank and open discussion. When they understood the basics and questions were answered, we reviewed the details of this specific excavation. We pulled out plans and discussed what the client wanted, where, and how we expected to make it happen. I showed them where what they were doing today fit into the plan, why it was so important, and how we were depending on them to achieve the desired outcome. 


They "got it." Done.


When they understood the goals and had a clear picture of the outcome expected, they went back to work without grumbling, without questions, and continued to do excellent work for the remainder of the project. The excavation was finished that day ahead of schedule and without any need for rework or any further conversation. 


When I explained the situation to the Super and showed him how it worked on subsequent occasions, he became a skilled mentor in bringing people on board and a highly valued member of the organization. The two excavators, last I heard, were quite successful as owners of their own businesses. 


People who are talented and capable, people who are committed, engaged, and on board with the goals will self organize to achieve those goals. 

Posted by: William W. (Woody) Williams

Thursday, March 1, 2012

Planning Value

The value in creating plans is not found in blindly following them but in using them as tools to intelligently and proactively manage inevitable change.
Posted by: William W. (Woody) Williams

Wednesday, February 29, 2012

Inevitable


Change is both rapid and constant. Proactively embrace that fact in ways that drive improvement.

Creating plans, process, and methods that address the inevitable changes of circumstance may seem daunting.  However, to do otherwise is to expect that circumstances change to fit plans, processes, and methods which makes disaster inevitable.

Posted by: William W. (Woody) Williams

Saturday, February 25, 2012

Why small is sometimes big

‎"Starting small" doesn't necessarily mean doing small things. Starting step one of massive, complex, daunting goal broken down and prioritized in manageable chunks is "starting small." Starting is the key.
Posted by: William W. (Woody) Williams

Friday, February 24, 2012

Intelligence, talent, and genius

Almost anyone with intelligence and some talent is able to complicate matters; arrive at a solution that is bigger, more complex than the problem. There is, however, a world of difference between intelligence, talent and genius. Some portion of genius is required to solve problems in ways that simplify, rather than complicate, the outcome.
Posted by: William W. (Woody) Williams

Monday, February 20, 2012

Risks and Obstacles

A risk is not an obstacle; it hasn't materialized. Equating risks with impediments or barriers is placing a mental obstacle of our own construction directly in our forward path.
Posted by: William W. (Woody) Williams

Tuesday, October 4, 2011

Hyperbole

Hyperbole is the downfall of requirements, proposals, and status reports.
Posted by: William W. (Woody) Williams

For most business endeavors, too much success is just as disastrous as complete failure.
Posted by: William W. (Woody) Williams

Monday, October 3, 2011

I am a project manager


I am a project manager: At its most basic, that means knowing "how" to get things done. That "how" stands, primarily, for "process." Many, but not all, my thoughts here share that focus on process.


I am deeply involved in both program and portfolio management. That means not just"how" but "what" and "why" and "when." "What" is to be accomplished could be referred to as "the ends." "How" the thing is accomplished, then, refers to "the means." "Why" is the strategic framework. "When" is about organizing the various "what's" into a logical sequence of events.


Standing outside the context of business and business technology I often speak to social, political, or cultural issues. Not here on this forum but on others. We (myself along with other project managers) have something to share; it's important. Important in the context of business, technology, and important in the larger context of getting things done in life.


Regardless of how carefully and rightfully the vision is crafted, goals defined, and success factors enumerated, if the methods, techniques, processes, and people employed are imperfect, those imperfections become realized in the outcome. In a sense, the end becomes the means.


We never achieve greatness (success) through flawed means. The most brilliant strategy is brought to naught by tactical failure. No amount of individual effort can overcome it; no amount of shiny rhetoric can gloss it over; neither advertising nor marketing can salvage it.

Posted by: William W. (Woody) Williams

Thursday, August 25, 2011

Quotable: Disaster

Disaster Quotes Page 2 - BrainyQuote

"If a sufficient number of management layers are superimposed on top of each other, it can be assured that disaster is not left to chance." ~Norman Ralph Augustine
Posted by: William W. (Woody) Williams

Friday, April 23, 2010

Why do projects succeed?

We've all seen "top ten" lists and read "why projects fail" rants. Here, we've discussed project failure as well as on Twitter #pmot, and LinkedIn. It may be (creating another "top ten") the number one item of discussion among project professionals. If not, it's certainly near the top.

Projects fail for every reason... all reasons. At some level there may be value in knowing what all those reasons are but--let's face it--when the list is written, it is everything.

Question is: When we have the list in front of us, what do we do with it? How valuable is that data? How do we know which particular item on the failure list is applicable to any given project... and especially the project we're starting now?

A lot of effort and analysis can go into crafting answers to that question. The answers are largely project specific. The answers are treated like any other project risk. If we're good at risk management, that effort might be useful. If we're bad at it, the effort is wasted.

The biggest obstacle (e.g. risk, failure point) we will face in a project is the one we did not anticipate. If we're good at handling unanticipated obstacles, we may go on to succeed. If not, we won't. The list won't help if the biggest threat is something not on the list.

So... Why do projects succeed?

That may be the more important question. The answer may lie in how well we handle unanticipated events.
Posted by: William W. (Woody) Williams

Thursday, April 22, 2010

Similarity and Success

In my consulting work withing large, complex organizations, I began to realize remarkable similarities among organizations. In fact, there were more remarkable similarities among successful, large organizations than remarkable differences.

In smaller organizations I found this not to be the case at all; quite the opposite. The differences among younger, smaller organizations and particularly between them and their larger cousins are considerable.

After decades of monitoring innovation, progress, and outcomes within businesses of all sizes, I came to understand that the successful outcomes were more closely related to those similarities than the differences.

At the organizational and meta-process level, the more attributes you have in common with other successful enterprises, the higher your chances of success.
Posted by: William W. (Woody) Williams


Tuesday, April 20, 2010

People or Process

Committed, engaged, talented people may succeed despite deeply flawed processes but it is incredibly difficult and they burn out rapidly. Even the best--world class--processes may deliver flawed outcomes without committed, engaged, talented people. It is not "one or the other," it is "both."

Monday, April 19, 2010

Process Improvement Opportunity

Common business plan: Hare-brained Idea > Foregone Conclusion = Instant Wealth

Friday, April 16, 2010

Contact with the enemy...

Planning is often followed by blind adherence to a plan. The first leads to success; the second to failure. Plan accordingly.

Friday, April 9, 2010

Friday Epiphany

Friday Epiphany: The biggest obstacle you will face is the one you never expected.

Engage

Talk isn't cheap when it leads to understanding. Engage.

Thursday, April 8, 2010

Complexity and risk

As system complexity increases, predictability--even of a small change--decreases while probability of its harm increases.

Monday, April 5, 2010

People Problems

"People problems" are caused by people, not technology. People are also the solution.

Wednesday, March 31, 2010

Be careful who you wish for...

A group -- no matter how well formed -- of managers and sales people nodding agreement to requirements should not make you feel safe.

Tuesday, March 30, 2010

Fill the gap

Projects fill gaps between organizational goals and current status. If not, question why.

Monday, March 29, 2010

Change yourself and change the world

The ability to change yourself is precursor to effectively changing others.

Saturday, March 27, 2010

Do it all yourself... or be a leader.

Those who must do everything themselves never become great leaders.

Friday, March 26, 2010

Influence or control?

Influencing is not "controlling."

Wednesday, March 24, 2010

Social Studies

Innovation, transformation, and change are fundamentally social.

Tuesday, March 23, 2010

Changing

To change, we must overcome peoples fear of losing status, power, control, security, and comfort in newness.

Monday, March 22, 2010

Is it a plan... or a schedule?

A schedule is not a plan but a plan always has a schedule.

Friday, March 19, 2010

So... it's been a while

So... it's been a while. One of the "features" of blogging, I suppose. Perhaps one of the traps. The ability or need to walk away sometimes. Need, in this case.

I've been *doing* a lot of project management over the past several months. And program management. And portfolio management. As the "Senior" in the Enterprise Program Management Office for a smaller organization, the hats change constantly. Sometimes so fast they rip your hair out.

So, I focused on hat changes and left the blog idle for a few months.

That is changing.

More to come.

---woody

Friday, October 23, 2009

Simple Problems...

Simple problems can be made confusing, complex and insoluble if enough meetings are held to discuss.

Thursday, October 22, 2009

Instant Destruction

Credibility and trust take a long time to develop; are destroyed in an instant.

Wednesday, October 21, 2009

Focus for Accountability

IT projects focused on implementing a system instead of a business goal lack accountability.

Tuesday, October 20, 2009

Change and Choice

The forces of change are constant. Helping make change occur in a positive manner is a choice.

Monday, October 19, 2009

Delivering Matters

When a project fails to deliver what it's supposed to deliver, little else about the thing will matter.