This is a post by Kate Ho, our Head of Product.
Understanding content debt
In software development, there’s a term technical debt: it’s a metaphor used to describe the amount of work required to tidy up a system in order to keep the code clean. Cleaner code means it’s easier to make changes and updates.
Code debt becomes a problem as a system gets bigger and matures. For example, over time you’ll have parts of code which might have been written a long time ago (legacy code), and may not reflect the current requirements of the system.
Why does no one talk about content debt?
Doing a quick search on Google for technical debt throws up a lot of articles, but do the same for content debt, and you’ll see that it’s a hardly-used phrase with nowhere near the same popularity. With a big site like mygov.scot, we’re constantly adding more and more information about how to access information… but one of the biggest issues is how to make sure that we keep our information up to date and relevant.
Content debt can look like:
- broken links
- changes in policy, and not reflected in the information
- changes required as a result of user feedback
- inconsistent content across multiple pages
- badly designed/poorly linked content
In helping us deliver this, the