Posted by APM on 22nd Nov 2013
The APM blog aims to trigger discussions within the APM community. It does this by inviting bloggers to discuss topics of interest to the project management profession.
Bloggers wishing to join the APM blogging community will be assessed against the following criteria.
Posts should be relevant to the project management community.
Posts should aim to further discussion, debate etc.
Posts should be logical and have a coherent argument.
Posts should be interesting to read.
Creating blog posts
Every blog needs a structure – and there are key pieces of information it should include.
As a guide typical blog might include the following elements:
1. Headline – keep it brief; think of a catchy title that will catch the reader’s eye.
2. First paragraph – 35 words ‘selling’ the main interest of the article: who? what? when? why?
3. Following paragraphs – a natural progression of information.
4. Final paragraph – a summary of your central argument or theme.
5. Further information – include links to further reading, author biog etc.
Length – minimum 300 words, maximum 1000 words.
Use plain English. Make sentences and headlines short and to the point and include keywords.
Try to write in a friendly and informal style. Use a personable style – use ‘I’ rather than ‘we’.
Choosing a topic
Before deciding whether something is worth writing about, consider what you are trying to achieve. Every story should serve a purpose and, in this particular case, answer one or more of the criteria listed above.
Always write with your audience in mind. Good blogs deliver a message in a way that strikes a chord with the reader.
The key question from the reader’s perspective is: What’s in it for me? It pays to keep on referring back to this when writing your blog.
The post should present a single idea rather than trying to fit in multiple arguments – these can be used to form future posts instead.
Here are some guidelines on possible subject areas:
- Give your spin on the latest news.
- Pull some interesting facts from your analytics or other market research
- Highlight new industry trends, new ways of working etc.
- Debunk a myth or misconception about your company or industry.
- Express your opinion on a controversial topic, or disagree with a commonly held belief.
- Write about changes you’re making to improve the profession, delivery of projects etc.
- Give a sneak preview of an upcoming product launch eg white paper, book etc.
Things to avoid
Provide your analysis of others’ content don’t repurpose it. In other words, don’t take credit for other people’s hard work.
Opinions should always be stated as opinions and must never be critical or demeaning of another person. Content should be responsible, fair and accurate.
Avoid overt commercial messages. No one wants the hard sell.
Direct promotional links.
Don’t waffle; keep it short and to the point.
NEVER lose sight of your audience. If it’s not relevant, interesting or thought provoking – what’s the point!
Dialogue after the blog
When the blog has been published it will be promoted on APM’s social media channels:
If you use Twitter and would like us to mention you then please send us your Twitter username.
Please respond to blog comments in a timely manner, and also encourage colleagues or fellow committee members to chip in and help get the conversation started.
Get in touch if you would like to contribute.
Sponsored by – APM accepts paid-for content written by advertisers providing it is relevant to the project management profession and meets APM’s blog and style guidelines. All content is reviewed by APM to look at its suitability and APM has the final say on whether the content is published. APM may also have a say in suggesting the types of topics covered.
Supported by – ‘Supported by’ is used to describe editorially independent content. We accept funding from third parties both for new projects and for content we are already producing. Before funding is agreed with a client, APM will assess its suitability and have the final say on whether a funding deal is accepted.
Share this page
Agile refuses to analyse requirements beforehand – and thus declines to provide an initial certainty. This will probably always scare any stakeholder trying to understand whether or not they can show results to the board with the budget that they are granted.
You have a choice. You can either muddle on, stand firm and fix it – or look elsewhere.