Skip to main content

How To Write A One-Page Proposal to an Executive

One day you may need to communicate with an executive. Pro tip 1:  executives do not have time for you to dim the lights and show them forty slides with charts composed of animated dancing leprechauns and flashing arrows that emerge from the void in a checkerboard pattern. Pro tip 2:   Guys, and gals with deep voices, executives also don't need you to use your "Radio Announcer Voice."

As a rule, what executives want is simple: one printed page. No matter what it is, it should be one page. And it should be printed, not emailed.  You should plan to hand it to the executive, and then you should be quiet when they read it and wait for their questions.  It's harder than it sounds.
http://www.simpsonstrivia.com.ar/wallpapers/mr-burns-wallpaper.htm
 So how do you do it?  Here are the steps:
  1. Write the deck that expresses your proposal in as many slides as it takes.  Use imaginative animation and blinking letters if you must.
  2. Remove your title slide.
  3. Insert a new slide at the front of the deck with "Appendix" written on it in big letters.
  4. Now insert a new blank slide in front of your Appendix slide, using the following template:
From here, you are ready to go.  Read and reread your own slides and figure out how much of your content you can afford to put into the limited space on the executive slide.  Put the right information into the goals, rationale, financial, status, and action sections.  Roughly translated:

Goal:  what do you want to have happen?
Rationale:  why?
Financial:  how much will it cost and when?
Status:  how far along is the thing you are proposing already?
Action:  what do you want the executive to do?

The title may turn out to be optional, which will buy you some additional space on the slide.  Also, if your goal is self-evidently good, you won't need the rationale.  If what you want isn't financial, you can skip that section as well.  Do not use microscopic type.  Executives require 20 point type at minimum.

Now, and this is important:  print out the one slide that has content and bring it to the executive in person.  If the executive asks, be prepared to email them the whole deck, including the appendix, when you get back to your desk.

Agilists, note that the executive proposal is reassuringly akin to a "story card:"

AS:  [this executive]
I NEED TO:  [action]
SO THAT:  [goal]

Effort Estimate:  [financial]   Value Estimate:  [rationale]

Isn't that nice?   

Pro tip 3:  the executive does not need to know about the awesome story card analogy.  With executives, the less said the better.

Comments

  1. I agree, the one pager is best. Especially in our instant consumption society where attention span is now at 9 seconds!

    And this is another area where we need to use Feature Injection:
    In order to: [goal]
    I need: [action]

    Resource Estimate: [financial]
    Value Estimate: [rationale]

    But I'm only quibbling over wording. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else. From http://www.yogawithjohn.com/tag/yoga-class/ Here's what you should think about: 1.        Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that: a.    ...

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read. From:  http://www.highestfive.com/mind/how-to-perform-a-successful-interrogation/ Dialogue: WBABA :   ...so in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration! Corporate Standards Guy:   but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actu...

Beware the Dark Triad: Your Worst Change Management Nightmare

What do you think is your biggest blocker, in terms of introducing agile software development to an organization which hasn't used it before?  Ignorance?  Lack of the proper tools?  Cube farms?  These perils are grave indeed, but they are nothing compared to something for which I have just learned the name:  the " Dark Triad ."  Machiavelli tells it like it is--or does he? The Dark Triad consists of three personality constructs: Machiavellianism, narcissism, and psychopathy.  As that source of all knowledge, wikipedia says, The narcissistic personality (in the clinical sense) is characterized by a grandiose self-view, a sense of entitlement, lack of empathy, and egotism. The Machiavellian personality is characterized by manipulation and exploitation of others, with a cynical disregard for morality and a focus on self-interest and deception. The psychopathic personality, is characterized by impulsive thrill-seeking, and in its "primary...