Four degrees of separation that help simplify work

by jonathan on September 15, 2011

From: http://changingminds.org/blog/0902blog/090225blog.htm

Much work these days is packaged up as projects, with plans, resources and time-bound deliverables. Managing projects is a skill as the various risks and issues can easily trip you up. In particular the sheer complexity can cause much extra work and conceal important issues.

Here, then, are four ways of making things simpler by separating out things that need your attention in different ways.

1. Separate rapidly changing things from slowly changing things. This makes changes (and communication about them) easier. For example a strategic plan, which changes little is separated from a rapidly-changing tactical plan.

2. Separate things that require attention now from points of information. This allows a sharper focus on action. For example items that require decisions may be covered first in a meeting, then information discussions continued in the remaining time.

3. Separate planned action from unexpected action. This allows both to be clearly managed and for plans to be revised as needed. For example issues are managed separately from standard project plans, thus allowing both onto the stage.

4. Separate internal project communications from external communications. Internal communications can be detailed, technical, textual and full of jargon. External communications should be focused, brief, visual and use Plain English.

You can also use the principle of separation to create clarity in documents and presentations by:

* Using colour, bold fonts, and other visual contrasts.
* Using lines and physical separation.
* Visual/physical separation into sections, pages, documents.

{ 0 comments }

Selected Rules of Consulting

by jonathan on September 15, 2011

Photo by Peter Hayes (click for original)

Gerald Weinberg is the grandmaster of consulting and project management. From the hundreds of hints and tips on offer in his excellent secrets of consulting series, Adrian Segar explores his favorite 19 :

You’ll never accomplish anything if you care who gets the credit. (The Credit Rule.) Check your ego at the door.

In spite of what your client may tell you, there’s always a problem. (The First Law of Consulting.) Yes, most people have a hard time admitting they have a problem.

No matter how it looks at first, it’s always a people problem. (The Second Law of Consulting.) I learned this after about five years of being engaged as a technical consultant and repeatedly having CEOs confiding to me their non-technical woes…

If they didn’t hire you, don’t solve their problem. (The Fourth Law of Consulting.) A common occupational disease of consultants: we rush to help people who haven’t asked for help.

If it ain’t broke, don’t fix it. (The First Law of Engineering.) Must. Not. Unscrew the tiny screws just to check what’s inside.

Clients always know how to solve their problems, and always tell you the solution in the first five minutes. (The Five-Minute Rule.) Unbelievably, this is true—the hard part is listening well enough to notice.

If you can’t accept failure, you’ll never succeed as a consultant. (The Hard Law.Everyone makes mistakes, and that can be a good thing.

Helping myself is even harder than helping others. (The Hardest Law.) The hardest things to notice are things about myself.

The wider you spread it, the thinner it gets. (The Law of Raspberry Jam.) Or, as Jerry rephrases it: Influence or affluence; take your choice.

When the clients don’t show their appreciation, pretend that they’re stunned by your performance—but never forget that it’s your fantasy, not theirs. (The Lone Ranger Fantasy.) “Who was that masked man, anyway?”

The most important act in consulting is setting the right fee. (Marvin’s Fifth Great Secret.) Setting the right fee takes a huge burden off your shoulders.

“We can do it—and this is how much it will cost.” (The Orange Juice Test.) Jerry uses an example straight from the meetings world for this one—event professionals will recognize the situation, and appreciate the insight.

Cucumbers get more pickled than brine gets cucumbered. (Prescott’s Pickle Principle.) Sadly, the longer you work with a client, the less effective you get.

It may look like a crisis, but it’s only the ending of an illusion. (Rhonda’s First Revelation.) A positive way to think about unpleasant change.

When you create an illusion, to prevent or soften change, the change becomes more likely—and harder to take.(Rhonda’s Third Revelation.) Notice and challenge your illusions before they turn into crises.

If you can’t think of three things that might go wrong with your plans, then there’s something wrong with your thinking. (The Rule of Three.) The perfect antidote to complacency about your plans.

The best marketing tool is a satisfied client. (The Sixth Law of Marketing.) Word of mouth is the best channel for new work; being able to satisfy my clients led me to a successful, twenty-two year IT consulting career without using advertising or agents.

Give away your best ideas. (The Seventh Law of Marketing.) When you teach your clients to handle future similar problems themselves, they’ll appreciate your generosity and are more likely to give you further work or good word of mouth to others.

{ 0 comments }

Some truths about project management

by jonathan on September 15, 2011

Enjoyed these rules from Immo Böhm  writing about Software Project Management.

“Nothing is impossible for the person who doesn’t have to do it.” and “You can con a sucker into committing to an impossible deadline, but you cannot con him into meeting it.”

{ 0 comments }

Approximately correct strategy

by jonathan on March 31, 2011

Jason Bates (@JasonBates) tipped me off about the concept of “Approximately correct strategy”, from an interview with by Dick Harrington (former CEO of Thomson Reuters) by HBR columnist Anthony Tjan:

Recently, I had dinner with Dick Harrington, former CEO of Thomson Reuters

We talked about his three most significant lessons learned over his very successful 25+ year career as a Fortune 250 executive.

Dick Harrington (DH): First, you have to have an “approximately correct” strategy — you have to know where you are going, but directionally correct is the key. Two, you have to be highly focused and intensely execute that strategy by motivating and aligning the troops you have. And three, it always comes back to the customers and the fact that you have to manically know your customers and drive everything from that.

TT: Nicely done. So let’s start with the first point. People often worry about architecting a perfect business plan or strategy and then get lost in the minutia. How do you know when you are “approximately correct,” as you say?

DH: You want to be approximately correct instead of precisely incorrect. There is a point at which additional information or research will not change the basics of your strategy. When you get your strategy there, you have to “Nike it” – you just do it. If you continue to refine and refine, you’ll never get into action, and the incremental value of research just won’t be worth the time and money. Schedule time frames and be religious about them to launch, get feedback, and see if the strategy is acceptable to the customer or if you need to adjust.  

From: http://blogs.hbr.org/tjan/2009/08/lessons-learned-from-30-years.html

{ 0 comments }

How to ask for things

by jonathan on March 29, 2011

Solid advice:

You can maximize your odds of getting what you want by minimizing the work the other person has to do to help you.

From: Unschooled » Blog Archive » How to ask for things

{ 0 comments }

Do you a Catfish in your tank?

by jonathan on March 29, 2011


Photo by slappytheseal . Click for original.

Or are you the Catfish?

“Vince Pierce: They used to tank cod from Alaska all the way to China. They’d keep them in vats in the ship. By the time the codfish reached China, the flesh was mush and tasteless. So this guy came up with the idea that if you put these cods in these big vats, put some catfish in with them and the catfish will keep the cod agile. And there are those people who are catfish in life. And they keep you on your toes. They keep you guessing, they keep you thinking, they keep you fresh. And I thank god for the catfish because we would be droll, boring and dull if we didn’t have somebody nipping at our fin.” – From “Catfish” (2010)

{ 0 comments }

How Anonymous hacked a major security firm

by jonathan on March 11, 2011

Ars Technica has a fascinating inside story of how Anonymous hacked security firm HB Gary, after the security firm vaunted that it was about expose members of the group.

It is a tale of wincing humiliation for HB Gary, security experts who allowed themselves to be utterly humiliated by an attack that not only compromised their website, but led to their entire e-mail archive being published online, many of their core company servers being completely compromised and terabytes of backups deleted.

It is a genuine cautionary tale. Their folly was not merely taunting capable and motivated adversaries, but rather of not following security best practices, which as experts, they know well.

Read on…Anonymous speaks: the inside story of the HBGary hack

{ 0 comments }

Devops classic: Dev and Ops Cooperation at Flickr

by jonathan on January 28, 2011

This presentation is a classic, one of the founding media of the Devops movement.

The summary of the presentation is the kernel of what we know as Devops today:

  1. Automated Infrastructure
  2. Shared version control
  3. One step build – code to set of files in one step
  4. One step deploy
  5. Shared metrics
  6. Use IRC and IM Robots (they use IRC and squirt logs and alerts into their IRC stream. Search engine indexes them.)
  7. Culture
    1. Shared Run-books and Escalation plans
    2. Healthy attitude about failure – plan to respond, not just prevent. Fire drills.
    3. No finger-pointing and blame

The slides are here:

Also see Matt Zimmerman’s excellent post on Devops and Cloud.

{ 0 comments }

You do NOT disagree

by jonathan on January 11, 2011


From: 109705.strip.sunday.gif (GIF Image, 640×287 pixels)

{ 0 comments }

Declaration of Interdependence (Kanban)

by jonathan on January 4, 2011

I enjoyed this 2005 declaration from David Anderson:

Declaration of Interdependence

We are a community of project leaders that are highly successful at delivering results. To achieve these results:

  • We increase return on investment by making continuous flow of value our focus.
  • We deliver reliable results by engaging customers in frequent interactions and shared ownership.
  • We expect uncertainty and manage for it through iterations, anticipation, and adaptation.
  • We unleash creativity and innovation by recognizing that individuals are the ultimate source of value, and creating an environment where they can make a difference.
  • We boost performance through group accountability for results and shared responsibility for team effectiveness.
  • We improve effectiveness and reliability through situationally specific strategies, processes and practices.

From: David J. Anderson and Associates

{ 0 comments }