Caveats for successful case memos

Follow the 2-section format  (problem; recommendation/rationale).

Don't restate or summarize the facts of the case in your problem statement.  A one-sentence problem statement is sufficient.  Two sentences are plenty.

Do use facts and examples from the case in the second section selectively and strategically to defend your recommendation in the last section of your memo.

Focus on convincing the reader why your recommendation is a good course of action.  Spell out the reason(s) clearly.

Good memos make liberal use of transitional words like "because," "therefore," "however" and "for example" because these words show the relationships between ideas.  In other words, they show the reader how statements, recommendations and facts fit together.

Take a stand

• It is not enough to simply recommend that the parties negotiate further.  It is sufficient to recommend further negotiation IF you spell out a negotiation objective for one of the parties.  In other words state the terms of a workable deal and defend why this deal is the best business solution.
• It is not enough to say that a pilot test or more study is necessary

Don't equivocate.  Avoid clauses like "I feel that" & "I believe."

Don't feel that you must come up with an elaborate, novel recommendation.  It is OK to focus on analysis of some of the straightforward options and defending a straightforward recommendation.

Don't make your recommendation too broad or general.  A recommendation like "implement TQM" or "implement CPFR" is probably too general (especially given the cost, difficulty and risk involved in implementing such sweeping changes).   It would probably be more useful to pin-point specific elements of TQM or CPFR that might make sense in the particular situation.

In the last section, it is sometimes useful to anticipate and defuse counter-arguments if space allows--or at least acknowledge these as weaknesses of your solution.

In a one page document, there is no need for a conclusion or closing summary.