Communication can be a challenge. I think back to the U.S. President Ronald Reagan, who ordered that many decisions for him be put on a single sheet of paper, with two choices at the bottom of the page. That's where he'd check off one of the boxes and initial.

Think of how some commercials are done: a problem is presented, then the product is introduced that solves the problem. Hooray! Your pitch has to have some of the same elements.

My friend OP describes it as SPARB:

• Situation: Describe the existing situation;
• Problem: Explain what the problem is;
• Action: What needs to be done (and at what cost);
• Result: What the result is; and
• Benefit: How the organization benefits.

To summarize even further, make it into a Cost/Benefit case study. Something like "Customers are finding ordering from the web site too complicated. We can simplify the process from seven steps down to three steps in two to three days time. Can we build a prototype and show you?"

I'm guilty of long-windedness, but even I understand that when you're pitching something, it needs to be terse. You have to have half an hour boiled down into half a minute, then be able to expand on the fly. For example, if I'm talking to the CTO, I don't mind presenting a half-baked idea, because he may have some other things on the go that may change what I perceive to be the problem, and therefore my approach to the problem. If I'm talking to the Director of Development, I need to have something much more buttoned-up and ready to go. Know your audience, and tailor your presentation appropriately.

Updates: Minor typo fix at 1807 Dec. 30, 2006..

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.