Skip to main content.
Navigation:

BarCamp / BarcampLA-2

October 30th, 2006 in Personal

I’ve signed up and I’ll be speaking at this one. It’s being organized by a friend of mine, Kareem.

BarCamp / Barcamp LA 2

What is BarCamp?

(As stolen from BarCampNYC, as copied from…) BarCamp is an ad-hoc unconference born from the desire for people to share and learn in an open environment. It is an intense event with discussions, demos and interaction from attendees.

All attendees must give a demo, a session, or help with one. All presentions are scheduled the day they happen. Prepare in advance, but come early to get a slot on the wall.

Presenters are responsible for making sure that notes/slides/audio/video of their presentations are published on the web for the benefit of all and those who can’t be present.

Anyone with something to contribute or with the desire to learn is welcome and invited to join.

There are no spectators, only participants!

When you come, be prepared to share with barcampers. When you leave, be prepared to share it with the world.

More… »

| Conrad Walton | Personal |No Comments » |

Re: [Pmclinic] Innovate or die

There’s an old adage in sailing - “Never let go with one hand until
you are firmly established with the other.” The same goes for project
work.

Maybe I’m misreading the situation but I cannot see why, if the team
leaders are unsure of what the VP wants, the developers are being
affected by all this. Surely, the team leaders and the VP need to
come to an agreement about what should be done, over what time-frame,
and for what reasons, and *then* the team leaders should implement
those changes in their respective teams.

Recommendations:
Get all the team leaders and the VP in a room with a lot of white
boards/big paper pads and have a brainstorming session around
‘innovation’. Inject some business metrics into it by asking about
‘market share’, ‘time to market’, ‘return on investment’, etc. Set
the goal of the meeting(s) to be to come to a short-term plan for
introducing innovation into the planning and delivery processes. Ask
probing questions around priorities, time lines, and deliverables.
Hopefully, one of two things will happen as a result of this: either
you will understand your VP’s reasons and objectives, or your VP will
understand the rationale for the current policies and practices.
Bring in a facilitator to run the meeting if you think the process
may become too confrontational.

Try to determine why your VP wants the changes. It could be a number
of reasons including: raising the visibility of your department,
changing the perception others have of your department, that change
is directly associated with his compensation plan, that his
perception is that the department is too complacent, etc.

Do not make changes with your team until you know what and why the
changes are taking place. Keep the team insulated and focused on the
job at hand until there is a new, clear objective and then manage the
transition to the new plan. Keep the team informed about the process
(e.g. We are meeting to discuss new ideas.) not the details.

If it turns out that the VP is akin to Scott Adam’s Pointy-Haired
Boss in Dilbert, then your only hope may be to hunker down and ride
the flow of change.

Scott Berkun wrote:

Here’s this week’s situation:

Is innovation for innovation’s sake a good idea? I think not, but my
new VP has it in his head that our entire organization needs to be
more innovative - despite his lack of clarity about what that means.
So all of the team leads (including myself) are like a pack of
wolves, pacing and racing around our projects. New ideas are flying
all over the place (reorgs, new technologies, new directions), but
progress on existing projects has stalled, morale is volatile (rising
and falling daily), and there is a shortage on meaningful decisions
about why we’re changing things, or how those changes will be made.

How can I help my VP sort out what innovation means? (Or is this some
kind of leadership game where he’s testing us by watching our
responses)? Or more cynically, protect my team and existing projects
from this chaos until it passes?

- Innovate or die

_______________________________________________
PM Clinic -
www.scottberkun.com/forums/pmclinic/

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

Re: [Pmclinic] Innovate or die

SUMMARY

I would recommend that they buy a forthcoming book by one of my
favorite project management authors… :)

My advice to your VP: First, figure out if the company is really
willing to accept the risk of innovation? If they are, then encourage
innovation, but start small, and ramp up. Make sure that current
business is being addressed, then provide some time time and
encourage innovation in incremental areas of business. One way to do
this is to implement something like “20% time.” If a big, bold idea
comes up then treat it as a new business idea and vet it through
appropriate management. Make sure to balance the risk of innovation
with the reward of the changes by setting up appropriate rewards and
controls.

BACKGROUND

First off: innovation is risk. If your organization is risk adverse,
your innovation efforts are going to fail spectacularly when people
realize that they will be penalized, passed over, or fired for
innovating. Companies like 3M didn’t start a culture of innovation
overnight. They built it up over a long time and have refined it
carefully over time.

In the Innovator’s Dilemma, the author explains that one of the
problems that innovators have is that they can’t get out of the “rut”
that they are in with their current technology, and therefore, they
miss the next innovation wave. This implies that companies should
continue to attempt to innovate, if possible.

However, innovation has to occur within the context of the business
goals that the company has. Having a database company innovate on
keel designs for America’s Cup boats is probably not the best use of
time, money, or people. (Are you listening, Larry?)

The current approach within the company seems to be “Innovate! There
is no such thing as a bad idea.” Which has caused a lot of
randomness. My recommendation here, would be to spur innovation along
areas where there are currently issues. Find a way to shorten sales
cycles, increase billing opportunities, reduce costs, or introduce
new services to meet new or existing customer demands.

Further, the innovation needs to be constrainted within certain
bounds to be useful. For example, it’s fine to innovate, but not at
the cost of the current business. Therefore, existing goals need to
be met, but innovation is encouraged. Failure to execute on business
goals today will mean that customers are suffering or business is
suffering, or likely both. This will cause customer erosion, brand
erosion, and increased service costs in the near term. This is not
what you are after.

Many innovative companies such as Amazon, Google and others have the
concept of “20% time.” That is that 20% of the employees time is
provided for the employee to focus on new areas of their interest.
The time is expected to be something that is in the customer interest
(working on your tan is not something that would be an approved 20%
time project. :)) However, this time is really about innovating. Some
innovations may be little: fixing bugs that don’t make it through a
triage bar, some may be huge: building a new business to tackle an
emerging business need. The nice thing about 20% time is that it is
reasonably self-constraining.

Large investments, such as building a new business, will require
careful vetting by a group of senior management. All of the rigor
about building a business plan holds here–it’s creating a new
business, and you need to make sure that business will meet the goals
of the parent company from a business and financial aspect.

Finally, balance out the risk and the reward for innovation, and keep
track. Reward people who innovate, and really reward those that
innovate successfully. If someone has an innovation that saves your
company $1M/year, consider giving them a piece of the action. And do
it publicly. Make sure that you have controls in place to keep
innovations that don’t work from taxing your budget or business. Just
like any other risk, build contingencies, and trigger points to stop
work on an innovation if it’s not working.

However, it’s critical to encourage people to take the risks if you
want to innovate. You can’t tell at the outset which idea will work.
You have to let them run with it a bit. Realize that you are going to
seem somewhere between 1-20% success rate. Over time, this may
improve somewhat (though it’s statistically unlikely to go above
about 20%), as you get better about what things work and what things
don’t, but it’s not a “sure bet” under any circumstances. In order to
get the benefit out of innovation, you have to encourage people to
take the risk–fully understanding that their work isn’t likely to
pan out.

-mark

On Oct 30, 2006, at 10:41 AM, Scott Berkun wrote:

Here’s this week’s situation:

Is innovation for innovation’s sake a good idea? I think not, but my
new VP has it in his head that our entire organization needs to be
more innovative - despite his lack of clarity about what that means.
So all of the team leads (including myself) are like a pack of
wolves, pacing and racing around our projects. New ideas are flying
all over the place (reorgs, new technologies, new directions), but
progress on existing projects has stalled, morale is volatile (rising
and falling daily), and there is a shortage on meaningful decisions
about why we’re changing things, or how those changes will be made.

How can I help my VP sort out what innovation means? (Or is this some
kind of leadership game where he’s testing us by watching our
responses)? Or more cynically, protect my team and existing projects
from this chaos until it passes?

- Innovate or die
_______________________________________________
PM Clinic -
www.scottberkun.com/forums/pmclinic/

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

[Pmclinic] Innovate or die

Here’s this week’s situation:

Is innovation for innovation’s sake a good idea? I think not, but my
new VP has it in his head that our entire organization needs to be
more innovative - despite his lack of clarity about what that means.
So all of the team leads (including myself) are like a pack of
wolves, pacing and racing around our projects. New ideas are flying
all over the place (reorgs, new technologies, new directions), but
progress on existing projects has stalled, morale is volatile (rising
and falling daily), and there is a shortage on meaningful decisions
about why we’re changing things, or how those changes will be made.

How can I help my VP sort out what innovation means? (Or is this some
kind of leadership game where he’s testing us by watching our
responses)? Or more cynically, protect my team and existing projects
from this chaos until it passes?

- Innovate or die

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

Re: [Pmclinic] Haunted by the ghost employee

October 29th, 2006 in Project Management

Linda’s post was sooooo on the money - If you don’t know the nature of those
bonds, there’s zero chance you’ll figure out the right thing to do about it.

There are lots of cases when those bonds are impenetrable - at least from
your position as a co-worker and outsider. I’m not saying its fair or right
for this to be the case, only that some friendships have bonds that are
stronger than organizational standards, or people’s sense of fair treatment
of others.

On the other hand, do consider incompetence. I myself has thought I was the
victim of “a circle of friends” when it turned out that the manager that
kept hiring his friend also kept hiring other bad contractors as well: his
poor hiring choices weren’t isolated to his friendships :)

As far as action: you have to trigger whatever mechanism the hiring managers
have for flagging people as bad (contract) hires. They need to get feedback
about their performance, so if there is no system in place for that feedback
getting collected for contractors, or being reported back to the hiring
managers, that’s a safe, round-about way to put in place a system that might
solve the problem on its own.

-Scott

—– Original Message —–
From: “Lee, Linda”
To: “Scott Berkun” ; Sent: Monday, October 23, 2006 11:50 AM
Subject: RE: [Pmclinic] Haunted by the ghost employee

Friends living together was a huge hit on U.S. TV, but friends working
together creates yet a different dynamic. My advice is to make sure you
really understand that dynamic.

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

Re: [Pmclinic] Haunted by the ghost employee

Friends living together was a huge hit on U.S. TV, but friends working
together creates yet a different dynamic. My advice is to make sure you
really understand that dynamic.

Is it based on high school or college alumni association (my son-in-law
was hired over the phone by a manager who went to his high school)? On a
common interest in golfing (do they play together most weekends?)? On
church/community activities? On a social life aside from work that
involves wives and children interacting on a frequent basis? Do they
vacation together, play cards together, just sit around a barbecue
watching Nascar and football together? Are they godfathers to each
other’s children? Have they bought retirement homes on the same
mountain?

Perhaps it’s even based on having worked together in a professional
organization on a project they all loved doing outside of work (I have
many friends I’d recommend on this basis).

If it’s friendship purely based on work experiences and respect, find
out what projects or events tie them together. Maybe a layoff; maybe
training together; maybe just time and familiarity.

Find out how deep the waters flow and in what direction. Figure out what
kind of life raft you need to survive in those waters. Then take the
advice of some of the other posters.

I’ve worked in an environment where several different friendship groups
existed. One was among long-time managers who sort of grew up in the
company together and understood each other’s management style; one was
among the younger (TV friends-like) engineers who partied together every
weekend and most nights after work. One was employees whose family ties
with the company went back as much as three generations and everyone
knew everyone else’s children and parents. By staying neutral and not
overstepping the boundaries of those friendships, some of us survived
without being totally accepted into a clique; others who didn’t grasp
the dynamics predictably didn’t last long and never got rehired.

Remember, this likely is not just about conducting the company’s
business. You might just have to find another place where neutrality is
more the norm. You don’t tell us much about the company. Is it large,
medium, or small? Big city location or small town? Were these guys maybe
founding employees who helped build the company, business unit, or
product line? All of that stuff matters. In fact, if you aren’t building
those kinds of relationships, I encourage you to figure out why you
aren’t.

Been re-hired here twice as a contractor and twice as an employee –
each time with a friend on the inside pushing my resume.

Linda

—–Original Message—–
From: pmclinic-bounces@lists.scottberkun.com
[mailto:pmclinic-bounces@lists.scottberkun.com] On Behalf Of Scott
Berkun
Sent: Monday, October 23, 2006 2:30 AM
To: pmclinic@scottberkun.com
Subject: [Pmclinic] Haunted by the ghost employee

Here’s this week’s situation:

A handful of managers that have worked together for years are good
friends.
One of them, the one with the least competent reputation, left over a
year
ago, and is now being hired back into the company as a perennial
contractor
(product manager) . Every time my team has interacted with him, across
various contracts and on different projects, we’ve had some kind of
performance problem. However given his connections, despite feedback to
the
contrary, he keeps getting rehired (generally with different teams each
time).

What can I do, as a manager myself, to exorcise this ghost employee from
my
world?

- Signed, Haunted by a ghost employee

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/
_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

Re: [Pmclinic] Haunted by the ghost employee

If the Ghost is on one of your projects, then you need to manage him.
Focus on the results that you need, make sure that the expectations
are clear, get agreement on the deliverables, and then hold him
accountable for the results.

When communicating to others about the progress, make sure that you
focus on the performance, not the person. “We are behind because we
haven’t received the vendor bids,” rather than “Ghost screwed up
again.” Once people start to see the pattern, the right thing will
happen, but you have to expose the problem, and you need to make it
equally clear that you don’t have an “axe to grind.”

-mark

On Oct 22, 2006, at 11:29 PM, Scott Berkun wrote:

> Here’s this week’s situation:
>
> A handful of managers that have worked together for years are good
> friends.
> One of them, the one with the least competent reputation, left over
> a year
> ago, and is now being hired back into the company as a perennial
> contractor
> (product manager) . Every time my team has interacted with him, across
> various contracts and on different projects, we’ve had some kind of
> performance problem. However given his connections, despite
> feedback to the
> contrary, he keeps getting rehired (generally with different teams
> each
> time).
>
> What can I do, as a manager myself, to exorcise this ghost employee
> from my
> world?
>
> - Signed, Haunted by a ghost employee
>
> _______________________________________________
> PM Clinic - www.scottberkun.com/forums/pmclinic/

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

Re: [Pmclinic] Haunted by the Ghost Employee

Content-Language: en-US
Content-Type: multipart/alternative;
boundary=”_000_27E66208FD96A64190F6AFB3382BD84903AEE60E79NAEXMSGC108re_”

There are two ways to look at Mr. Ghost. (The problem statement
states that the Ghost is “he.”) One, of course, is as the problem
states, that he is indeed the stumbling block.

Another is that you are at least part of the problem because you
don’t like or respect Mr. Ghost.

I think you need to work on ensuring that the latter is not true even
as you pursue the former.

We are prisoners of our perceptions. How do you find the facts? Why
are the managers continuing to hire him? Can they all be misguided?
Presumably he is supplying something they need - and it’s interesting
that a wide variety of folks seem to need whatever it is.

You’re assuming that they’re not hiring him for the quality of his
work. So let’s posit that he truly is ineffective; then what is he
supplying management?

You suggest they’re hiring him because he’s their buddy, but my
experience is that such rationale goes only so far. It is reasonable
the first time, not totally discounted the second time, but by the
third engagement it has to be more than the old school tie. Is he
giving them good status information? Is he soothing their fears? Is
he making them feel confident and competent? Once you understand
what that is, you can begin supplying it also. In this scenario,
they’re hiring him to meet one particular need and you’re seeing him
in another niche. If so, go meet that need yourself; his presence
may be a blessing in disguise, showing you something you need to do,
a skill you need to acquire, in order to move up.

However, first you need to be sure he’s truly ineffective and not
just ruffling your feathers because his style is different. Your team
may not tell you that; either they share your biases because they
like working with you, or they won’t tell you the truth because they
don’t trust you. You need to find others who owe you nothing whom
you trust/respect and who have also observed Mr. Ghost in his native
habitat. Only when you’re honestly convinced by objective evidence
that Mr. Ghost is utterly useless can you fully take up the
do-it-yourself exorcism guidelines.

(Happy Halloween. I can’t wait for next week’s spooky problem.)
n Steve

Steven B. Levy
Senior Director, Information Systems
Microsoft Legal and Corporate Affairs
Steven.Levy@microsoft.com / 425.705.3748

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

Re: [Pmclinic] Haunted by the ghost employee

Zombie projects earlier this month, and now Ghost employees. How
Spooky!

Seriously, if you have the opportunity to more clearly define at the
beginning what this person should do, then do it. Whether its on paper,
or a 3 person conversation (you, this Ghost, and whoever hired him/her)
do something to set the bar and make Ghost accountable.
Secondly, you can set the bar higher than needed, so you end up getting
something closer to what you really need.

If its too late, then you have some other options.
Third, when you provide feedback (one on one, or to Ghost’s hiring
manager) at any time, be as concrete as possible. Rather than say,
“Ghost is holding up the project by not making a decision”, be able to
say, “Ghost is overdue 5 days in deciding on this item, and its costing
us $x dollars per day in overruns, plus we anticipate that the vendor
we’re using is going to hit us with a change order for delaying the
project and that will cost an additional $xx”.
Last, and it’s a least favorable option for you, but micromanage Ghost.
Riding someone who has a performance problem either helps them, sends
the message you’re going to hold them accountable (gasp), or you’re just
going to make life miserable for them until they improve or move on.

Ghost is apparently a likeable person in your organization and has just
enough domain expertise (as a product manager) to appear to be the best
person in the crowd, and keeps getting rehired. You’ve got the burden
of demonstrating its not cost effective to bring Ghost back.
Alternately, you could try to demonstrate that you don’t need Ghost or
someone else could assume Ghost’s role as product manager, or that
Ghost’s domain expertise is not that exclusive or helpful to the product
being managed, and you can do better with someone else.

Good luck.

—–Original Message—–
From: pmclinic-bounces@lists.scottberkun.com
[mailto:pmclinic-bounces@lists.scottberkun.com] On Behalf Of Scott
Berkun
Sent: Monday, October 23, 2006 2:30 AM
To: pmclinic@scottberkun.com
Subject: [Pmclinic] Haunted by the ghost employee

Here’s this week’s situation:

A handful of managers that have worked together for years are good
friends.
One of them, the one with the least competent reputation, left over a
year ago, and is now being hired back into the company as a perennial
contractor (product manager) . Every time my team has interacted with
him, across various contracts and on different projects, we’ve had some
kind of performance problem. However given his connections, despite
feedback to the contrary, he keeps getting rehired (generally with
different teams each time).

What can I do, as a manager myself, to exorcise this ghost employee from
my world?

- Signed, Haunted by a ghost employee

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/
_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

[Pmclinic] Haunted by the ghost employee

Here’s this week’s situation:

A handful of managers that have worked together for years are good friends.
One of them, the one with the least competent reputation, left over a year
ago, and is now being hired back into the company as a perennial contractor
(product manager) . Every time my team has interacted with him, across
various contracts and on different projects, we’ve had some kind of
performance problem. However given his connections, despite feedback to the
contrary, he keeps getting rehired (generally with different teams each
time).

What can I do, as a manager myself, to exorcise this ghost employee from my
world?

- Signed, Haunted by a ghost employee

_______________________________________________
PM Clinic - www.scottberkun.com/forums/pmclinic/

| Conrad Walton | Project Management |No Comments » |

« Previous Entries