Simon's learning log

Month: January 2017

Book review: Rivers of London

14 January 2017 /

I was really quite surprised at how much I enjoyed Rivers of London, the first of Ben Aaronovitch’s Peter Grant books. It was one of those books I pick up for £0.99 on an Amazon Kindle deal because it sounds interesting, but by the time I actually get to read the book, I’ve forgotten any hint of the synopsis. So, a page or so in, when Pc Grant is approached by a ghost witness to a murder, I was amused, puzzled, and a little delighted.

Aaronovitch is quite aware of the potential silliness of the whole concept, but has delivered a book that really feels set in the London I came to in 2001. He seems to bring together coherent ideas of life in the Met Police, of the mythologies and geographies of London and the South East, and importantly science and the supernatural. At times, especially early on, some of the asides feel too glib, but more often than not they’re well observed and pithy.

My rating of 4/5 on GoodReads still feels overgenerous, it’s probably as low a 4/5 as one can go. As a piece of sub-genre fiction, it is very enjoyable and also a lot of fun.

GatherContent webinar: Content Strategy for Agencies masterclass

14 January 2017 /

Engagement phase

  • Kick-off questions
    • Do you know how much content you have on your current site?
    • Have you (or will you) audit the content on your current site?
    • Are you archiving old and poor quality content on your current site?
    • Do you know who is going to (re)write all the content for the new site?
    • Does someone have overall responsibility for content quality during the project and beyond?
    • Do you know (roughly) how many hours per week will be dedicated to maintaining content on the new site?
    • Does the current site’s content have dedicated (subject matter expert) owners?
    • Do you know if any content is syndicated from other systems?
    • Will or do you have a (digital) content style guide?
  • Content audits: why bother?
    • what content types currently exist (and will continue existing) ?
    • what state is the content in?
      • will it need lots of work?
    • where is content feeding in from?
      • e.g. social, RSS, APIs, CMS
    • is some content out of control and are there constraints aroud its accuracy, format, availability?
    • how much content will the new navigation need to handle?
    • has the existing team been able to maintain what they already have?
    • what content is or has been popular / unpopular?
      • what analytics is available?
  • Content audits: how to…
    • Assign an auditor who will be involved throughout the project
      • often this is best for someone within the organisation
      • not a job to “chuck to the intern”
        • but someone who understands digital communication
    • Download your content inventory template sheet (GDoc)
      • C0lumns include: content owner; functionality and forms; files and media; statistics; key messages; accuracy/relevance; content quality; archive / migration readiness; RED FLAG for immediate attention; Notes
    • OR use an automated tool
      • e.g. www.content-insight.com
    • Capture a skeleton of the site
    • Perform a detailed audit of the site
  • Content audits: Estimating
    • look for a sitemap (footer / ./sitemap.html / XML sitemap)
    • Google: site:www.client-site.com + advanced search
    • gauge repetitive content – no need for qualitative analysis of staff profiles/news items
    • Create spreadsheet to estimate time required
      •  Client input required
  • Content ecosystems
    • e.g. university site might have website, international student site; facebook; twitter; alumni site; intranet; prospectus; handbook …
    • run a session with a client
    • use post-its and pens to capture sources of content
    • turn into a diagram or spreadsheet
    • note sources client has direct control over
    • annotate interesting content types
    • included in your discovery report
    • share insights with wider project team
  • Competitor landscape analysis
    • …
  • Design and build phase
    • design with proto-content
      • e.g. current site’s content
      • e.g. competitor content
      • write your own throw-away content
      • use draft content
      • commission sample content
      • Use typical and edge-case proto-content
        • e.g. push the design
        • multi-date events + best format
        • events that have started but haven’t finished
  • Content production planning and prioritisation
    • Content “hats”
      • the writers (similar template for videographers, …)
        • skills
          • writing for the web
          • ability to apply style guide
          • domain knowledge (ideally)
        • responsibilities
          • research and consult subject experts
          • draft and revise content
          • source relevant media
      • the senior editor

Sarah Richards – Lighting fast content design webinar (12 Jan 2017)

12 January 2017 /

Brief notes

  • Intro to GDS etc
  • Content design – GDS-style
    • Moving away from subject experts to skilled writers
    • Targeting user needs – Discovery process
      • Gives you
        • language
        • architecture
        • tone
        • style
      • Research
      • Vocabulary
        • e.g. Forums, interviews, …
      • User stories
        • Leads to very targeted material
        • Good for shared understanding
        • What is being covered
        • what is not being covered
        • Should have
          • acceptance criteria
          • format
          • performance indicators
          • archive date (or review)
      • Designing with data
        • Gives you something better than opinions
        • Perspective and distance
        • also a chance to listen
        • forms the architecture of the content
    • Tricky conversations
      • Often, we talk at, not listening to
        • giving solutions
        • making arguments
      • “Looking at each other and thinking ‘you’re an alien'”
      • Crit sessions – encourage respectful and productive sessions
        • Rule 1: Everyone did the best job possible with the information they had at the time
        • Rule 2: Talk about the product only, not the person who created it
        • Rule 3: Constructive criticism only. “That’s crap” is unhelpful and unacceptable
        • Rule 4: No one has to defend a decision
        • “How are we as a team going to make this better?”
  • Reading psychology
    • People often say e.g. “older users do this…”
    • Reading is (basically) the same, worldwide, regardless of language
    • Reasons a page may be failing
      • Eyes skip across text & 10-15% is skipping back (regressive reading)
        • New terms lead to more regressive reading
        • Makes reader feel uncomfortable
        • Reduces …
  • Working together gives you
    • a better product
    • an easier life
  • Show, don’t tell

© 2025 Simon's learning log

Theme by Anders Norén — Up ↑