Content designers can worry: how much do we have to offer major projects to change the website? A lot, I’m now clear, after a project to re-think how the University publishes news content.<\/p>\n
The Digital User Experience team was tasked with finding out how news content helps visitors and our university, and if improvements could be made. At the start of the discovery, I was tasked with supporting our excellent user researchers preparing to talk to visitors to news content.<\/p>\n
We discussed asking these people about actions news content prompts them to take. I wondered if that was expecting too much of news content. Instead, to ensure we weren\u2019t overlooking any impacts, I suggested asking: \u201cCan you remember university news that made an impression on you? What did it make you think or do?\u201d<\/p>\n
Our user researchers thought this was a good question. I had a vote of confidence, and our team could cast our net wide as we sought out the value of news.<\/p>\n
What is \u2018news\u2019 for you? This was a question I asked digital peers in other universities as we embarked on our quest for a rationale for news content.<\/p>\n
While I enjoyed reviewing different approaches in our competitor review, speaking to peers was even more eye-opening. We content designers excel at searching questions. They helped me to find out whether news content\u2019s right to valuable site space had been questioned \u2014 and how it had proved its worth.<\/p>\n
We were learning about opportunities to add more value, as well as the problems with news content.<\/p>\n
One thing I know I brought to the agile discovery \u2018party\u2019 as a content designer was my experience in engaging colleagues at the University.<\/p>\n
The best content is co-designed with stakeholders who are open-minded about how University goals are met. So helping colleagues to take a step back with me always feels valuable. They seemed to welcome a space to think about their hopes for news content in workshops.<\/p>\n
And we were starting to get an idea of what successful news content might look like. First, however, we needed to see what success looked like from the \u2018other side\u2019 of the screen.<\/p>\n
What were people searching for when they came? Where else on our site had they been? And what did they do when they arrived, and next? I loved delving into the data on search intent, behaviour, including scrolling and clicking, and users\u2019 journeys to, and away from, news content.<\/p>\n
I could see that stakeholders\u2019 need for \u2018news\u2019 to help people connect with us was not always being met. Sometimes content is used in ways we never intended. Many lower value visits were quick checks of medical news by people self-diagnosing! At its best, \u2018news\u2019 is not a cul de sac, but a door.<\/p>\n
Presenting such surprising findings to stakeholders helped us all go on a journey together. A discovery is our collective opportunity to completely re-think content to make it more valuable. The culmination was a 3-day workshop to bring everything we found out together.<\/p>\n
I was the only content designer for the majority of the synthesis workshop. The content design project lead had shown me, again and again, how we add value.<\/p>\n
She had gained a deep understanding of existing processes and emerging strategy, and also the possibilities different technologies offer to help improve these. For the final workshop, she would not be there to ask any questions or connect any dots. I had not needed to worry.<\/p>\n
By this point, the little voice asking myself why I was in the meeting, and not busily making some source information accessible, had largely gone.<\/p>\n
I felt comfortable asking a performance colleague why we were reporting a percentage when the total numbers were so small. I was at ease asking user researchers to tell me more about an interviewee using news to \u201clook for inspiration\u201d.<\/p>\n
More than asking questions however, I made a contribution to designing solutions.<\/p>\n
In the final discovery workshop I was excited to get stuck into designing possible solutions based on the evidence before us. As content designers, this is what we do.<\/p>\n
This time, however, I was helping to design a new process for publishing news content. I was quick, as ever, to take us a step back to an earlier stage than initially sketched. \u201cWhere do the ideas for news come from?\u201d<\/p>\n
I was also critiquing, when it was after time to go home, interaction designs for \u2018news\u2019. I was unsure there was evidence for signposting \u2018latest news\u2019, given content designers elsewhere signposted the most important \u2018news\u2019 content by other criteria.<\/p>\n
After all, deciding what is important for the University and visitors to our site is our job, and one that I relish.<\/p>\n","protected":false},"excerpt":{"rendered":"
Content designers can worry: how much do we have to offer major projects to change the website? A lot, I’m now clear, after a project to re-think how the University publishes news content. The first step: working out what we need to know The Digital User Experience team was tasked with finding out how news […]<\/p>\n","protected":false},"author":258,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"categories":[8,18],"tags":[],"class_list":["post-1366","post","type-post","status-publish","format-standard","hentry","category-content-design","category-discovery"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/paLsBb-m2","_links":{"self":[{"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/posts\/1366","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/users\/258"}],"replies":[{"embeddable":true,"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/comments?post=1366"}],"version-history":[{"count":9,"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/posts\/1366\/revisions"}],"predecessor-version":[{"id":1380,"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/posts\/1366\/revisions\/1380"}],"wp:attachment":[{"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/media?parent=1366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/categories?post=1366"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.southampton.ac.uk\/blog\/digitalteam\/wp-json\/wp\/v2\/tags?post=1366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}