Showing posts with label 80:20. Show all posts
Showing posts with label 80:20. Show all posts

Tuesday, 16 July 2013

Recipe for a simple content migration

Biscuit mix
Biscuit mix by eddie welker on flickr,
used under creative commons
This short checklist and method gives an overview for web and intranet editors who've not planned a migration before. It's purely from the editorial point of view, and omits any technical jiggery-pokery.

You will need:

  • User requirements. Who are your users? What do they want? How will they use this information?
  • Knowledge of the information architecture (IA) of the new site.
  • Contact details for the content owner.
  • Editorial style guide and any guidance on new content formats.
  • Support from a manager and/or policy if there is conflict and you need to escalate.

Method:

Pre-heat the content owners by letting them know in advance that you will be needing their input.
  1. Audit existing content, working with the content owner and overall user requirements.
    • Decide what is current information that needs to be migrated, and what can be archived. 
    • Identify content that needs re-writing to fit into the new IA or templates, and anything that needs editing to style or is a bit out of date.
    • Identify gaps where new content is needed.
  2. Arrange any archiving procedures - ensure copies are saved elsewhere and can be accessed by the required audience.
  3. Commission new content to fill the gaps.
  4. Arrange for any updates to old content to be supplied.
  5. Draft edited versions of the old content in new style and template.
  6. Edit any new or updated content that has been supplied.
  7. Send all the draft, edited pages to the content owner. (Either use Word with tracked changes, or a preview version of the website, depending which best shows the changes you have made.) Invite comment and set a deadline for approval.
  8. Receive approval or negotiate the final version with the content owner (apply the 80:20 rule if necessary, to reach a compromise).
  9. Publish.
  10. Schedule for review.

Serving suggestion:

Garnish your freshly-prepared content with an email alert or a homepage news feature.

Wednesday, 19 June 2013

When to back down

Boxing Glove Wind Chime?
Boxing glove wind chime by JPott on
Flickr, used under creative commons
When do you back down, and when should you be bolshy? Is it a matter of experience, or are there any hard and fast rules?
 
There is plenty of best practice guidance that can be applied to websites:  
  • Accessibility
  • Editorial style
  • Branding
  • Usability
  • Cross-platform compatibility
And lots more, especially for public sector websites.
 
Sometimes it’s hard to follow all the rules. Sometimes it's impossible – these rules can conflict with one another. For example, NHS branding guidance states that logos should be top right. But what happens if usability testing of your new homepage design shows that users commonly expect the logo to be the home button, and the home button to be top left. How do you resolve that?

It's also common to be asked to do something that breaks these rules. For example, you can be put under pressure to put a news item on the homepage that doesn't belong there.
 
You certainly don’t want to give in to pressure and just do something that’s against your judgement because you’re being asked to by someone higher up the food chain. But if there is a clear conflict of opinions or reasoning, someone has to make a choice. That’s where your organisational priorities and web strategy can come in.

In the logo placement example, is it more important to your organisation to do exactly what the NHS branding people tell you to do, or to make your website behave in the way your users expect? In the homepage news item example, is it more important to get an urgent message across, even though it's only relevant to a small handful of staff, or to delay the message while the content author sorts out a better way of communicating with his niche audience?
 
Because whichever way you go, you need to be able to explain why you chose that route, either pointing to empirical evidence (e.g. user testing) or a documented decision path (e.g. a policy, corporate document, meeting minutes, or email chain). Be clear who is empowered to make those decisions – is it you, or do you have to escalate?
 
If you really don’t want to back down on something, ever, you probably need to enshrine it in some form of policy, or if your organisation operates on a less formal structure, by convincing the highest authority (such as the CEO) of your case, so you know they’ll always back you.
 
For your own sanity, it is worth applying the 80:20 rule. This might mean applying all your best practice guidance in 4 out of 5 situations, and allowing 1 in 5 pages to not come up to scratch; or it might mean applying 4 of your principles without exception, and being flexible on the fifth rule. 
 
Eighty per cent compliance should be enough to demonstrate the usefulness and worthiness of the guidelines, without giving you a reputation as a harridan. The worst thing you can do is be so inflexible in applying rules, that people walk away and look for another solution in order to bypass you, whether that’s phoning your colleagues or boss to see if they’ll give a different answer, or building their own separate website.
 

Key points:

  • A little compromise can be the key to a successful working relationship for years to come.
  • Listen and understand their point of view.
  • Know your boundaries and how far is reasonable to go to fight your corner, and when to back down for the greater good.
  • Know what to do when you can’t solve the problem yourself.
 
A lot of this is about experience, but it’s also about being confident in your arguments (why you are asking for something to happen) and in knowing where you and your policies stand in the pecking order, not of who is more influential than whom, but of organisational priorities.