Be a Tiger?

As most of the world knows, Tiger Woods was back playing golf for money this weekend.

Sunday, I was at the airport waiting for my flight and found myself watching the finish of the Masters tournament with a bunch of other folks outside an airport bar. With about two hours to go in the tournament, the best players were playing the last nine holes in various groups. Tiger Woods was among them, and the cameras were focused on him rather heavily.

(I find golf on TV rather weird these days. They jump cut from shot to shot, Tiger swings on one hole and then Phil swings on a second and someone else putts on a third and then there’s a commercial, and there’s no context to any of this. TV is no better at showing the thinking and strategic parts of the game than it is with baseball.)

Anyway, Woods was not hitting his driver very well, even by his standards. Tiger Woods isn’t terribly accurate with his driver, the big club, but he’s extremely creative about getting out of the trouble he gets himself into. But that’s a story for another day.

So Woods winds up and smashes a ball off the tee… deep into the piney woods. Woods in the woods, I guess. I don’t know whether he hit any of the spectators or had to have his caddie search for his ball; TV was off showing some other random shots. But when they finally get back to him, they’ve managed to get the camera behind his ball looking toward the green. It’s obvious he has an impossible shot through the trees; you can see a little bit of daylight through an opening perhaps 15 feet above the ground, but his chances of hitting it through there are small — even as good as he is at what’s called scrambling, or getting out of trouble.

At this point, he’s trailing the leaders by a few shots. And he has two choices:

  1. Try and punch the ball through the opening in the trees — possible, certainly, but likely to have bad results if he fails.
  2. Knock the ball out onto the fairway, basically at right angles to the direction he really needs to go — but a safe shot for a competent golfer, which he certainly is.

Only if he gets the ball through the opening in the trees can he win the tournament. Doing so doesn’t put him in the lead — he still has a lot of work to do — but he almost surely cannot win if he takes the safe route, which will cost him a stroke.

Now keep in mind that everyone who finishes in the top ten of a tournament like this makes a lot of money. The winner takes the biggest piece, but most people could live quite well for a year on what, say, the fifth-place finisher receives. And Woods was staring at the difference between, say, eighth and second-with-a-possibility-of-first:

  1. Hits through the trees successfully, has a good shot at second or even first if he plays the remaining few holes well.
  2. Safely pitches the ball sideways back onto the fairway, probably ends up fourth — where in fact he did finish.
  3. Tries to hit it through the trees and fails. Best case, he gets a good bounce off a tree and winds up in the fairway pretty much the same as if he’d pitched it out to begin with, finishing fourth. Or it could bounce back toward him and give him a repeat of this situation, except now it’s cost him a stroke to get there; maybe he finishes sixth. Or, worst case, it could bounce off a tree the wrong way and go out of bounds or be unplayable, costing him three strokes (the one he took plus a penalty plus having to play again from a bad lie) and he’s eighth.

Which would you choose?

You’re a leader in a tough situation. You can take a big risk and — if everything comes out right — make a huge score, but create a mess if things don’t go well. Or you can play it safe, assuring a comfortable profit but not a dramatic victory.

Woods, of course, went for it. And missed, though he got a good break when his errant ball smacked a tree at exactly the right angle and bounced out onto the fairway. But that’s the Tiger in him — nothing matters except victory.

But was it the right choice? The best choice? Would you have done it?

As it happens, eventual winner Phil Mickelson found himself facing a slightly easier version of the same type of shot a few minutes later, deep in the pines after an errant drive, but with a somewhat bigger window in the branches to hit through. He went for it and wound up about six feet from the hole with a terrific shot. On the other hand, former champion and still-among-the-leaders Fred Couples took one of these dangerous shots trying to get into the lead and put it in the water; it doesn’t always work out.

Three leaders, three very difficult risk/reward shots, all went for it. One nailed it, one missed but got a lucky break, and one fell short (literally, as Couples’ shot hit just short of the green and rolled back into the water).

That’s the way it goes. None of them took the safe route. It cost Couples and Woods money, made Mickelson a winner.

You’re the boss. You’re facing a tough shot, high risk, high reward. What do you do?

Is this the right time to be a Tiger?

“Oops” UI of the Week

I was filling out an online form today when I came to this section:

Enter your mailing address...?

It says Mailing Address in big red letters. Then it says Mailing Address in bold black letters. The cursor goes automatically to the first edit box.

So what do I — and I suspect most other folks — start typing? My mailing address, of course.

Designers, it may technically be part of your “mailing address” database table, but we humans on the other end of the screen don’t automatically think, “you want my name here” when we come to an area boldly and colorfully (and redundantly) labeled “mailing address.”

(By the way, this form was the gateway to a site whose core product is known to anyone who travels even occasionally; it’s not a one-off, one-person operation.)

Suprise Inspections

Does your company “take the pulse” of employee satisfaction once a year, or perhaps twice? Does it do so at regular, scheduled times?

Do all the managers scramble in the six weeks ahead of the survey to provide “morale” or “motivation”? (And do half of them spell it “moral”?)

Does it work?

The same goes for employee feedback about their managers. Is it solicited only around performance reviews?

Does that change behavior for the long term?

What if no one* in the company knew when these surveys or feedback forms were going to be sent out?

If you’re a manager and that thought has you even the slightest bit uneasy, then you need to examine what you’re doing and try to fix it. Right now, it’s hard for employees to vote with their feet, but times will get better — and the very best, the ones you most need to retain, can always find new positions. And even if they’re not leaving because there’s nowhere else to go, morale and motivation affect performance, which in turn affects your own review — to say nothing of the lives of everyone involved, from your team to the other teams that interact with yours to the customers who might purchase your output.

There is no “time” for morale and motivation except the present time, every time. It’s not about events, or presentations, or gifts, or pithy and overworked sayings. It’s about how you relate to them, the level to which you extend trust, the extent to which you help when needed and avoid over- and micromanagement. It’s about having their backs, about recognizing that your job is to eliminate the roadblocks that make it hard for them to do their jobs.

Succeed here, and you won’t have to worry about “surprise inspections.”

===================

*When I say no one, I mean no one, including HR. It’s not hard to have these surveys and mails prepared to go out at any time. Let’s say a company wants to “take the temperature” twice a year. It’s trivial to design a program — I could write it in Excel in under five minutes — that you’d run once every two weeks, with a random factor that will come up “Yes” only, on average, twice a year. You send the surveys and such within minutes of the program coming up “Yes,” so everyone, including your own manager, has no advance warning. Of course, you’d suspend running it for eight weeks or so after it comes up “Yes” and you send the survey. (And the programmers out there recognize that you’d have to account for those eight weeks — and the two weeks at the end of the year when you can’t send anything useful — in calculating the odds for the random-number generator.)

The Blinder Side

My kids are watching The Blind Side as I write this. I’m sort-of watching and writing, but I saw it some months ago when I took my nine-year-old son to see it in a tiny (75-seat) theater in Friday Harbor in Washington’s San Juan Islands.

(The island in the San Juans where we have a place has no movie theater. It does have three espresso stands, four real restaurants and a few other places to eat, perhaps a dozen stop signs on an island twice the size of Manhattan, no chain stores, more sheep and cows than people, a plethora of eagles, ravens, and turkey buzzards, a nine-hole golf course where I actually managed to shoot a 46 last week, and an almost unlimited amount of peace and quiet. But I digress.)

In brief, the “blind side” is a quarterback’s back. A right-handed quarterback stands with his body facing right as he prepares to throw; anyone coming from his left arrives unseen, occasionally delivering a devastating hit. The film opens with the horrifying sack of Joe Theisman in 1985. I’m not a big football fan, but I was still in NYC at the time and happened to be watching the Giants game that Monday night. I will never forget the sight of Theisman’s leg bent in a Z shape from the compound fracture, and the moment the film started in Friday Harbor I knew what was coming and had to avert my eyes. I didn’t watch that hit in the film today, either.

But over the years, I’ve thought about that moment often. It happens all too often in the business world, where a team member fails to protect a colleague’s blind side. It’s even worse when it’s the employee’s manager delivering the hit that puts the employee out of the game, so to speak. Some managers appear to get a kick out of it, but most, like Lawrence Taylor (who delivered the hit with no intention of doing that kind of damage), inflict career-ending damage without meaning to. In fact, like Taylor, they’re often surprised and horrified by the result.

The difference is that in football, players play with the knowledge that they are at severe risk, that their careers could end at any moment. In the business world, that self-knowledge is largely absent.

If you’re a manager, it’s up to you to protect your employees’ blind side. You need to keep the blitzing executive linebackers away, even if you incur a penalty in doing so.

Do you do so?

How well do you protect your team’s blind side?

If you’ve never thought about it, watch what happens to Joe Theisman. You may want to avert your eyes 52 seconds into this (not very clear) clip. But whether you want to watch a closeup of his leg shattering or not, think about Joe Theisman and your team.

And protect their blind side.

As a manager, that’s your job.

(And in the spirit of full disclosure, while I shot a 46 on the second round of nine, I shot a miserable 56 on the first nine. I love the game, even though I’m pretty terrible at it.)

Another One Bites the Dust

One of America’s last great independent bookstores — Elliott Bay Books — closed tonight. (Powell’s in Portland is still open, at least.)

The story is here.

They’re reopening in a smaller location, a bit off the beaten track compared to where they were… but at considerably less rent, too.

They were — and will be again — a terrific place for a bibliophile.

I’m an author who has sold far more books through Amazon.com than through bricks-and-mortar establishments, but I still believe the world needs — needs — real bookstores.

(And libraries. Right now, I’m at our place on very rural Lopez Island about 70 miles north of Seattle — but it somehow has one of the country’s great libraries, recognized by whatever association rates public libraries. It’s a real treasure… as is the independent bookstore in the village, Islehaven Books With Borzoi. Yes, that’s its name. And the borzoi sleeps behind the counter. Things are different up here, one reason I treasure this place.)

“The Worst Abuse of Microsoft Excel Ever”

A NYTimes article on analyzing video of basketball games contains the delicious quote, ” ‘It’s probably the worst abuse of Microsoft Excel ever,’ said Kevin Pauga….” Pauga is apparently referring to the use of Excel rather than a database to track all the stats associated with every play of every possible opponent in college basketball’s “Final Four” national championship tournament.

I think he’s wrong. Excel is well suited to doing exactly this kind of rapid data entry, data mining, and analysis, especially with its powerful pivot tables. Technologically, there are more sophisticated ways to set it all up at little additional cost, and I sure hope they’re backing up to a server every few hours.

But look at their apparent criteria:

  • Ease/speed of data entry
  • Analysis along hundreds of axes — who takes what kinds of shots, does a particular player shoot better when he moves to his right versus his left, and a gazillion more that I don’t know how to think about because I’m a baseball junkie and actually used to have nightmares about basketball.
  • Vast quantities of limited-scope data that while theoretically relational can be captured effectively in a single table
  • Stability
  • Ease of developing add-ons such as a basketball-focused interface

To me, that sounds like a good match for Excel. Not a great theoretical match, but a very practical one nonetheless.

So in my capacity as an Excel maven with 38 years of using spreadsheets for all sorts of things the designers never envisioned, I hereby absolve you, Kevin Pauga, of Excel abuse. Indeed, I think this is a pretty cool use of Excel. Hey, MS-Office team, if you’re listening….

Found: The Most Cynical Project Management Post of the Year (So Far)

I was floored this morning when I came across this post about project sponsors. Some choice excerpts:

The problem with project sponsors is that they have got to where they are by climbing a very dirty greasy pole. They now have a privileged aerial view of the executive landscape…. The slightest hint or whiff of them being on the wrong side of an issue, especially if it is your project that is the issue, then it is odds on that you will lose your project patronage…. If we do report the real project status now, it will only lead to investigation and recrimination which will ultimately delay the project anyway. [emphasis added]

In my decades in the corporate world, I have certainly seen my share of execs who fit this description. I’ve also seen at least as many who try their hardest to do the right thing by their teams, their projects, and their company.

Here are a handful of guidelines for project managers dealing with execs:

  • If you bring a problem, also bring a suggested solution and some options to go with it.
  • Be prepared for deep probing on any issue, not all of which may make sense to you at the time. (As a leader/manager, I would often pull hard on one particular thread of what I was presented, both for my own edification and to see if you knew your stuff. If that thread held, I was likely to accept the rest of your arguments and cut to the request-for-action section. If it didn’t hold, I deeply discounted everything you were offering.)
  • Be prepared for the exec to ignore certain areas you think are important; she may know they’re not important, she may already understand them, or she may know that they’re outside her level of competence and is looking to you for an answer, not a dissertation.
  • Take responsibility. Don’t point fingers.
  • Execs have less do-this-now power that you think they do. If you must ask for something, ask wisely. The best (and easiest) help an exec may offer is an introduction to someone in a different group with whom you want to make contact.
  • Virtually all execs believe they got to the executive suite by being smarter and “better” at their job than most everyone else — which is true more often than you may be willing to admit, though it certainly isn’t always true. (Being smarter than 90% of the other folks may or may not make the exec smarter than you… but don’t assume either way.)
  • Don’t ever bring to a scheduled meeting a spreadsheet you haven’t triple-checked or a document (or PPT) with grammatical or spelling errors. (For an on-the-fly review, more leeway is given.) The exec wants to be sure you prepared — and cared enough to do your very best — before he contributes his constrained time.
  • Half of what managers do isn’t visible to their direct reports; three-quarters isn’t visible at levels beyond that. Just because you can’t see what they’re busy with doesn’t mean they aren’t buried in work. More often that you might suspect, part of that work is providing “air cover” for their teams and your project, if for no other reason than you looking bad makes them look bad.

Finally, one quick clue for spotting an exec who does fit the description in the quote with which I began this article: An exec willing to burn his team by name to his peers or in public. It’s one thing to share, “The Acme Project is late,” or even “The Acme Project team’s been telling me the project will be late.” It’s quite another to say, “The Acme Project team has screwed up,” or –worst of all — “Joe has screwed up” or “The leader of the team has screwed up.” That’s departmental politics in the extreme, avoiding responsibility.Even for an exec new to a department, there’s a big difference between “I know the Acme Project has been late, and I’m going to find out what’s wrong and fix it” and “My predecessor screwed up the Acme Project.”

Exec, grunt, or in between, take responsibility. That’s leadership.

Headline: Project Management Book Breaks Project Management

I found the following subject line on a mail in my inbox yesterday:

PMBOK Breaks Project Management

The PMBOK is the grandiosely titled Project Management Book of Knowledge from the Project Management Institute (of which I’m a member).

Wow, I thought, someone else thinks formulaic, by-the-book-only project management can be as much a problem as a solution. The mail was from an electronic newsletter called IT Business Edge. It struck me as odd that an IT publication would be railing against the PMBOK.

Of course, what happened is that my inbox shows only the first 30 characters or so of a subject line. The entire subject is “PMBOK Breaks Project Management into Five Lifecycle Phases.” (It links to this slideshow — and it’s not a slow Flash thingy, so kudos to IT Business Edge for that!)

I’m not sure why this is headline-worthy news; did someone in IT just discover project management?

But now that I think about it… five phases? They’ve got it down as Initiate, Plan, Executing, Controlling, and Closing. Aside from the grammatical issue — it’s either “…Plan, Execute…” or “Planning, Executing…” — there must be at least one and perhaps three additional, explicitly called out phases in an IT project.

The unforgivable omission is Rollout. Without a specific Rollout cycle, there is a tendency — I’ve seen it over and over again — to “dump” the new solution on the users, point them to a (functionally useless) training website, and disperse the team after Closing — but long before the solution is embedded in user processes. Sure, you can technically put Rollout in one of the other phases, but it’s really a post-Execution activity, involving a handoff from the execution team to an operations team… and much more.

There also need to be User “Readiness” and Shakeout phases. These can be subsumed into other phases — e.g., part of Rollout. However, because the activities and players are significantly different, I prefer to call out explicitly at least Shakeout. In addition, if you’re using stage-gates (go/no-go decision points), these phases represent transition points where the sponsors and stakeholders need to get together on a go/no-go decision. (What, you think you can’t say “stop” after the project is rolled out to users? Wrong. If it isn’t working for them, you may well need to perform a rollback, and you’d better have all the stakeholder ducks in a row when that happens!)

As for the names of these last two stages — there aren’t universally accepted terms. I don’t like “Readiness” — it means everything and nothing — but it can serve as a catch-all for user documentation and training, adoption planning, helpdesk/support preparation, and so on. Shakeout represents the first few weeks to a month of actual use on live data, where numerous bugs and configuration errors will crop up, and where the original development/project team should remain in place to address them. One reason I prefer to see this particular phase visible at the highest level is that there is great pressure at this point to move the team on to other projects… especially if the project is late… and since we’re talking about software, the likelihood that it will be late is, oh, 100%. If the executive sponsor and the CIO are aware that there is a full project phase that is just getting started, there is less pressure to move the team, and more weapons with which to fight the pressure.

So maybe leaving off these phases from an IT project justifies the headline after all, with a slight emendation:

Misapplied PMBOK Breaks Project Management

Who Wrote Shakespeare's Plays? Drawing a Lesson in Management

There has long been academic debate as to who wrote the work attributed to William Shakespeare.  (The word “academic” is important; see below.)

Most recent attention has focused on Edward de Vere, Earl of Oxford. There is a whole cottage industry devoted to these so-called Oxfordians. I won’t go into all their arguments, but here’s a summary:

  • How could some rude glover’s son from Stratford know all about the English court, Italian mores, and so on?
  • Nothing survives in Shakespeare’s hand… perhaps because he wrote nothing.
  • de Vere had a long-term relationship with Queen Elizabeth and the Earl of Southampton, prime movers in  the Globe Theater in one way or another.
  • de Vere was an established poet.
  • de Vere traveled extensively in France and Italy, scenes of many Shakespearean plays.
  • There are parallels between de Vere’s life and some Shakespearean plots, particularly Hamlet.
  • de Vere was very cultured, educated, and sophisticated.

There are a few problems with this theory, not the least of which was that de Vere died in 1604, which sort of leaves out some plays… like Macbeth and The Tempest, dated well after 1604. de Vere’s supporters construct an elaborate — and not entirely impossible — structure around how the plays were actually written before de Vere’s death but not published or even staged until afterward.

So what does this all have to do with management?

The First Issue: Occam’s Razor

Occam’s Razor suggests that the simplest solution that fits the facts is most likely to be true. That doesn’t guarantee that it is true, but the more convoluted a solution, the more unlikely.

Or, in more modern terms, never attribute to conspiracy that which can be explained by incompetence.

Saying that someone other than William Shakespeare wrote those plays, epic poems, and sonnets requires a very complex construction to explain away all sorts of contradictions, from the 1604 issue to the fact that folks like his playwright contemporary — and non-friend — Ben Jonson was in on the conspiracy. It’s one thing for the players to keep a secret, since their livelihood depended on it, but it’s another for a competitor who didn’t like Master Will to play along. (On the other hand, one of Jonson’s snipes at Shakespeare can be stretched to suggest Jonson is mocking the attribution of plays to “Shakespeare.”)

Lesson: When a co-worker or someone on your team describes a complex scenario to explain why sales are down or a product is late, be very skeptical. Exhaust the simpler explanations first.

The Second Issue: Listen to the People on the Factory Floor

The people closest to the production of something generally are more knowledgeable than management about the mechanics of production. (There’s a fancy Lean Six Sigma term for this.)

If a project is late, ask the project manager and (in the case of software) the developers. Steven Sinofsky at Microsoft did a brilliant job of this in figuring out why it was taking so long to ship versions of Windows, and got the very successful Windows 7 out the door on time.

If sales are down, ask the people actually out trying to sell the product. They won’t have all the answers, and may well couch it in ways to protect their jobs, but their feet-on-the-ground insights are invaluable… and likely “spun” by their management.

If you’re trying to design something, listen to the users — and, even better, watch what they actually do. Their managers can’t tell you what they do, or even what they think they do; managers can only tell you what they think they want their employees to do.

In the Shakespeare controversy, ask the actors. Any competent actor or director experienced with playing Shakespeare will tell you that it’s clear that the author was a man of the theater, someone who understood in infinite detail how to move an audience, how to get them to laugh, cry, and see themselves in the mirror held by the playwright and the players. There’s nothing to suggest that de Vere had serious familiarity with the theater other than as an occasional playgoer.

Here’s where the “academics” thing comes in. Academics generally see Shakespeare as a poet, a word stylist; lacking a deep involvement themselves in rough-and-tumble theater, they tend to ignore that astonishing playability of Shakespeare’s work. Indeed, many of Shakespeare’s characters are what theater folks call “actor-proof,” meaning that they work on stage no matter how bad the performance. I have seen Malvolio, Sir Toby Belch, Romeo, Juliet, Bottom, Oberon, Polonius, and numerous other characters performed abysmally by actors who had little understanding of what they were saying… and yet these characters were still affecting — and drew huge laughs where they should have. Of course, they missed loads of subtleties and nuance, but they were still good enough to “get by” and not destroy the audience’s willing suspension of disbelief. Note that I’m not suggesting every Shakespearean role is actor-proof, as numerous mediocre performances of Hamlet prove.

Lesson: Pay attention to the people closest to the action.

The Third Issue: Trust Your Ears

As I noted, de Vere was a poet.

He was, in fact, a terrible poet. His verse is to Shakespeare’s as The Archies were to The Beatles.

Now perhaps he got better as he got older, but even Shakepeare’s earliest work, such as Titus Andronicus, is far beyond anything de Vere wrote under his own name before Shakespeare (or, if you must, “Shakespeare”) came on the scene.

Lesson: If you’re listening to someone and something smells fishy, it probably is.

By the way, this last item points to a significant problem in hiring at large companies these days. A manager who trusts her instinct in this regard may wind up hiring only people who look like her with regard to age, gender, ethnicity, and so on. A good interviewer has to spend most of the interview consciously trying to revise or justify the first impression. First impressions are powerful — for both good and ill. Or as de Vere Shakespeare said, this “soliciting cannot be ill, cannot be good.”

But what’s in a name, anyway?

The Most Practical Info I Can Offer (With Tongue Only Slightly in Cheek)

I thought I’d turn this forum over to my practical get-through-life side for a few hours.

“Enjoy Yourself; It’s Later Than You Think”

It’s later by an hour, if you’re in the US and forgot to set your clocks ahead. Go, fix it now; I’ll wait.

Good. Let’s move on.

“Watching the Clothes Go ‘Round”

How much dishwasher or laundry detergent should you use? An expert at the NY Times says it should be a lot less than we normally use. And don’t self-clean the oven right before a party.

There are also definitive instructions on how to load the dishwasher properly. Of course, my wife may disagree. So she loads her way, I load mine, and we agree to disagree but not rearrange each other’s dishes.

“Can You Feel the Love Tonight”

The Hurt Locker won. Get over it. I wish I knew how to say that in Nav’i.

Avatar was the biggest seller of the year, but that doesn’t mean it was the best film.

The biggest selling album of 1967 was Sgt. Pepper’s Lonely Hearts Club Band, right? Abbey Road, of course, in 1969. Born to Run in 1975.

Hey, Jude topped the charts in 1968 longer than Bobby Goldsboro’s Honey. Light My Fire was a chart-topper longer than To Sir, With Love in that year. In 1969, the longest chart-topper was a great Beatles song.

All of these statements are false.1967′s biggest seller was More of the Monkees — not even “The Best of.” At least it had I’m a Believer on it. In 1969, it was Iron Butterfly’s In-a-Gadda-da-Vida. And 1975 brought us Reg Dwight’s Greatest Hits — or, rather, Elton John’s Greatest Hits. It wasn’t Born to Run, but I can’t argue with someone who chose his stage name to honor the great Long John Baldry and the sax player in Baldry’s band, Elton Dean.

And in 1969, the records atop the charts the longest were In the Year 2525 (Exordium and Terminus) — yes, that was the name of it, by one-hit wonder Zager and Evans — and Aquarius/Let the Sunshine In (The Flesh Failures) — again, that was the name, by the Fifth Dimension, who at least weren’t a one-hit wonder and whose covers brought attention to the otherwise overlooked Laura Nyro.

Avatar may have outsold The Hurt Locker 10:1, but that doesn’t mean it was better. More of the Monkees outsold Astral Weeks and Forever Changes 10:1 too.

(If you haven’t heard Van Morrison’s Astral Weeks and Love’s Forever Changes, listen to them and hear two of the most influential-on-other-musicians albums of all time.)

“Happy Birthday to You”

This bit of highly practical advice is directed at me. It’s my wife’s birthday, and I want to acknowledge her in print. Or in electrons….

Get Adobe Flash playerPlugin by wpburn.com wordpress themes