Writing recommendations
It sounds basic to ask for what you want when you're writing a recommendation, but a common complaint I hear is that many recommendations are too vague.I think the problem is twofold.
First, I think we often get so immersed in the detail we fail to stand back and see the bigger picture. This happens to all of us at times and it often helps to talk to someone not involved in your project or else try writing a summary paragraph and then a summary sentence.
The second problem is the wording of the recommendation and knowing how much detail to include. In my opinion, a recommendation should be sufficiently detailed to stand alone, i.e. make sense without the accompanying text. For example, a recommendation to lease office premises in Brisbane should propose a lease at X site for three years for $y with a maximum fitout cost of $z.
Such recommendations can then be copied and pasted into the minutes as resolutions and everyone will have the same understanding of their meaning. The person who has the responsibility to follow up understands their responsibilities, and the resolution is also a historical and legal record.
So next time you write a recommendation ask yourself:
- Is it clear what I am asking for?
- Is it sufficiently detailed (but not too detailed)?
- Does it make sense without the accompanying text?
- Will it stand the test of time if taken out of context?
- Is it clearly and concisely written?
Labels: recommendations, writing
posted by Unknown @ 11:16 PM
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home