Communication and presentation for Project Management

The specification categorises this as:

• appropriate for target audience
• conveys intended meaning
• effective use of graphics to support meaning
• use of fluent English and appropriate technical language  
• appropriate tone for project documentation.

Remember that being a project manager is a professional position, and you should portray your company as professional through your use of media. For example:

Appropriate for target audience

The content should use terms that are likely to be understood by the client. Do not provide documentation that reads like a programming book and is full of overly technical language that the client could not reasonably be expected to understand.

Conveys intended meaning

Words like ‘should’ and ‘like’ are not appropriate in a project management document, nor are emoji.

Whatever is written should be unambiguous – get someone to proofread your work before sending it on.

Effective use of graphics to support meaning

If a graphic or image would save a paragraph of description, then it is highly appropriate to use an image in the documentation. Do not just add random images for the sake of it.

Use of appropriate technical language and fluent English

• Your work should not be a set of bullet points
• Correct language
• Don’t be overly technical

Never publish work that is not written in fluent English – this means that points are made in sentences and paragraphs, that link together. Using bullet points just makes you look lazy. Who would want a project carried out by a company that can’t even bother to write up the proposal properly?

Appropriate technical language means technical language relevant to the project can be included where necessary. You should make a judgement call as to whether the language is specific to the project content, and therefore likely to be understood by the client, or whether it is more specialised: if this is the case, and it is required, then it should also be described.

Appropriate tone for project documentation

You are a professional developing a system for a client – they aren’t your friend, at least not in the context of the project.

Your communication should be professional, avoid colloquialisms (don’t call them ‘mate’ or use phrases like “and job’s a good’un”. Avoid making jokes – this is meant to be a serious document.