Skip to Content

Content design

Posts about writing, designing and testing content based on research, data and clear user needs.

12 posts

Posts tagged with Content design

Make content clear by listening first Link post

This is an excellent content design primer on the Digital Access Solutions
And Assistive Technology (DASAT) blog by Nikki Fiedler, Co-Founder of Content Design Hub.

Content design is about function: does this help the person complete their task? If someone can’t find, understand or use the information, the content hasn’t done its job, no matter how polished it reads.

Don't assume everyone you work with knows what content design is, even if they probably should. Send them to this or similar articles if you need to explain how it works and why it's different to good, old-fashioned copywriting.

Updating the skills content designers need in government Link post

If you work or hope to work in government here in the UK, this update to the skills you need as a content designer is definitely worth a look.

Though there had been some iteration, the 6 skills for content designers had remained largely consistent since the Capability Framework was first published in 2017. These 6 skills had given the profession a valuable shared reference, but the role had continued to evolve. [...] It was time for a major update.

The headline news is that of the now 8 skills needed as a content designer, only 1 of them is unique to content design. And it reads:

Content management and architecture. Using and developing processes, systems and standards to enable effective, sustainable and reusable content. This includes organising complex information, designing publishing and review workflows, and supporting content reuse across different channels and contexts.

Here's the role description for a content designer in government too. I find it really useful to see it all laid out in the way. That said, in my experience as a consultant, the reality is usually much messier than all of this suggests. Soft skills are very much a necessity as a content designer in government.

You need to be really, really flexible. A good listener. An advocate. No two teams or projects are the same, so it's important that you can adapt quickly. You should be able to work with the content you have and the cards you're dealt.

Content design versus the “form of words” Link post

Ray Newman on the pursuit of content perfection often sought by stakeholder types, especially in government:

The antithesis of content design is the old skool Civil Service idea that, if you just try hard enough, you can find “a form of words” that will make everybody happy, nobody sad, and nobody angry.

Or, at least, obfuscate the unpopular policy sufficiently that nobody will realise they should be mad about it.

And then towards the end of the post:

But sometimes, you need to hold the detail back; or disappoint some people to make it clearer for most people; or clearly and directly tell people something they won't want to hear.

It’s rarely easy to balance these, and the many other concerns in the mix. But that’s why the content needs to be designed – not just knocked out, banged together, or scribbled on the back of a napkin.

I think there is also something here about research, constraints and making informed decisions.

You need research to understand who your content is for and how it might affect them, either positively or negatively. But you also have the internal pressure of deadlines and budgets – these are frustrating, but very real content constraints. They too affect your decision making.

As Ray says, this is why many of us call ourselves designers these days and not copywriters. Our choices are based on the situation in front of us. We take all that we know about our users and design the best content we can at any given time.

In my experience, good content design is rarely about finding the ideal 'form of words'. It's about listening, compromise and pragmatism. Writing good content is a messy, movable feast, not a meal to be cooked to perfection.

Headers, headings, and titles Link post

Love this clear explanation from Martin Underhill of what headers, headings and titles are, and why they are very much not the same.

This resonates:

Three particular terms I often hear being used interchangeably are ‘header’, ‘heading’, and ‘title’; I even catch myself doing it sometimes! Let’s have a look how they can be confused.

And this seems pretty sensible:

What a designer calls something should not differ from what a developer calls it, and the easiest way to ensure this consistency is to use the terminology defined by the super smart people who wrote HTML and ARIA.

If you work in content that lives on the internet, I think you should know the differences and be able to explain them.

Basically:

  • header – usually a banner area where a logo, strapline and navigation lives
  • title – search-friendly metadata that describes the page and appears in the browser, not the page itself
  • headings – the h1, h2, h3 content that helps structure a page and provides an outline of your content

If you're reading this and thinking, "Hmm, still not sure," then I highly recommend you go check out Underhill's post. It includes much more detailed definitions and useful examples to help you out.

Your documentation is still in your Mum’s filing cabinet Link post

This post by Geri Reid questions the traditional folder-based approach to documentation:

For years we’ve treated documentation like a filing cabinet. Put the thing in the right folder and give it a label. But much as it pains me, people rarely wander through my carefully crafted hierarchy, admiring the taxonomy. They search, skim, follow links. And the second finding information feels like work, they’ve checked out and just asked someone.

I have to say, this was exactly my experience on a recent guidance project. Users would often find the document they wanted and make a direct copy to keep locally. Of course, when guidance was updated, that local copy was soon out of date.

For these users, knowing where to quickly find guidance was important. To heck with the shared folder structure! And for those times where they couldn't find the right guidance document at all, they would simply ask a colleague for the answer.

Needless to say, I learnt a lot from this experience. It's important to organise documents in a clear, sensible way that people can easily navigate. But don't think for a second that users will or want to carefully wander through your folder structure to find what they want.

How to create design documentation Link post

A short and handy intro to design documentation from Colin Baird:

Design documentation is an important part of the design process. It records the thinking behind the designs. It preserves knowledge for future team members. It gives you evidence when stakeholders challenge design decisions. A screen-by-screen explanation ensures that you don’t miss anything. A decision log gives a high-level overview of the who and why of design decisions.

I'm in the process of documenting some of my design work at the moment. For example, I recently updated some content based on feedback from the clinical assurance team. So I made a note of that in our shared decision log.

Having that decision documented will help anyone new to the project understand that there is a very good reason why things are the way they are. They can be reassured that the design work was based on sound clinical guidance.

Read Baird's post if you want to get started with this kind of thing yourself. There is even a useful four-column example you can swipe for your decision log. Lovely stuff.