18F/18f.gsa.gov

View on GitHub
_posts/2016-05-23-a-sestina-on-sunsetting-content.md

Summary

Maintainability
Test Coverage
---
title: "A sestina on sunsetting content"
date: 2016-05-23
authors:
- emileigh
tags:
- content design
- communication tools and practices
excerpt: "Sunsetting can be contentious in government. We manage websites for the public,
which feels like managing content for everyone’s needs. When you have to think about everyone, that makes it a lot more complicated to delete things."
description: "Sunsetting can be contentious in government. We manage websites for the public,
which feels like managing content for everyone’s needs. When you have to think about everyone, that makes it a lot more complicated to delete things."
image:
---

*Note: The sestina is a poetic form. It’s constructed of six stanzas, of
which each contain six lines. In the first stanza, the last word of each
line is reused throughout the poem, to end the lines in each subsequent
stanza, following a set pattern.*

We’ve used our blog to write about [creating new
content](https://18f.gsa.gov/2015/12/17/plain-language-betafec-new-content-design/),
<br/>but we haven’t discussed managing published pages. Specifically, when to
delete them.<br/>
In the content design world, we call this concept “sunsetting.”<br/>
Sunsetting can be contentious in government. We manage websites for the
*public*,<br/>
which feels like managing content for *everyone’s* needs.<br/>
When you have to think about *everyone*, that makes it a lot more
complicated to delete things.<br/>

Additionally, there are unique consequences to the government “deleting
things.”<br/>
Our websites impact citizenship, voting, taxes. This is life-changing
content.<br/>
From broad swaths to tiny subgroups, when we see needs<br/>
we write for them,<br/>
and what we publish becomes official record that *belongs to the
public.*<br/>
Knowing all this, how can we form a strategy for sunsetting?<br/>

Step one of sunsetting:<br/>
Look at your pages. When was the last time you reviewed or updated
everything?<br/>
Policies change, procedures change; we need to reflect that to the
public.<br/>
If something is outdated but historically important, you can make it
“archived content,”<br/>
which can be as simple as taking outdated pages and putting the label
“archived” on them.<br/>
Otherwise, update or delete information so it’s easier for readers to
find what they need.

It’s trickier to prioritize information that people rarely look at or
only sometimes need.<br/>
Don’t send pages over the horizon by sunsetting<br/>
just because it’s been awhile since readers visited them —<br/>
for example, caucus information or how to take part in the census, those
kinds of things.<br/>
You shouldn’t delete and relaunch valuable, accurate content<br/>
because of the cyclical interest of the public.

Ultimately, you want to emphasize pages that are timely and draw the
interest of the public.<br/>
But the foundation of your site should be built on ever-present (not
transitory) needs.<br/>
Keep things up to date; trust that, in time, people will come back to
important content.<br/>
That’ll save you the pain of sunsetting<br/>
and resuscitating and sunsetting and resuscitating things.<br/>
In short: Do your pages fit a clearly identified public need? If so,
keep them.

And bear in mind that “keep them”<br/>
doesn’t necessarily mean keep them as is. You’ll see shifts in the needs
of the public.<br/>
Usability testing, interviews, and analytics will illuminate things<br/>
you should change or update to meet the public’s needs.<br/>
Make iteration part of your strategy for sunsetting.<br/>
Your readers will thank you for not having to wade through unnecessary,
outdated content.

Hopefully this [sestina](https://en.wikipedia.org/wiki/Sestina) has
inspired you to think about them (pages and needs).<br/>
Are you a member of the public or government with questions about
sunsetting?<br/>
[Reach out!](mailto:18f@gsa.gov) We’d love to chat with you about
content!