{"id":1129,"date":"2024-12-18T15:49:15","date_gmt":"2024-12-18T15:49:15","guid":{"rendered":"https:\/\/blogs.york.ac.uk\/communications\/?p=1129"},"modified":"2024-12-18T15:49:15","modified_gmt":"2024-12-18T15:49:15","slug":"easy-access-to-it-tools-software-and-services","status":"publish","type":"post","link":"https:\/\/blogs.york.ac.uk\/communications\/2024\/12\/18\/easy-access-to-it-tools-software-and-services\/","title":{"rendered":"Easy access to IT tools, software and services"},"content":{"rendered":"\n

Phase two of the IT web rebuild project was a complex and rewarding piece of the puzzle. Working closely with stakeholders, we delivered a new Tools, software and services<\/strong><\/a> section \u2013 spanning over 160 web pages which went live at the end of September. <\/p>\n\n\n\n\n\n\n\n

The new section presents service information in a clearly structured and user-friendly way, and replaces a service catalogue that had become outdated and challenging to navigate. It hosts services managed within IT Services but also by other teams across the University and will become even more comprehensive over time.<\/p>\n\n\n\n

Merging projects and defining roles<\/strong><\/h2>\n\n\n\n

Originally, the IT web rebuild (phase two) and the IT service catalogue were two separate projects. However, due to so many dependencies and crossovers with user needs and content structure, it made sense to merge them into one project. Merging them helped us align our vision, reduce redundancy, and collaborate to create a solution that meets both business and user needs. Combining established projects can create role overlaps, so we created a RACI matrix (Responsible, Accountable, Consulted, and Informed) to clarify roles and responsibilities. This exercise brought clarity and helped our teams transition smoothly into one unified project where everyone was clear on who was doing what. <\/p>\n\n\n\n

Content audit<\/strong><\/h2>\n\n\n\n

To define exactly which \u2018services\u2019 would go into the catalogue, we collaboratively reviewed a content audit of existing web pages about IT services. One by one, we reviewed each service page to work out what we would need to keep, update, merge or delete. Though the layout varied greatly, many pages gave a satisfactory overview of a service. The content would be a useful reference when creating new, consistent service references. In some cases though, we found partial information. This would need expanding or merging with other sources. <\/p>\n\n\n\n

Documenting these decisions in our audit gave us a clear content map. In numbers, we would be streamlining content across 250 web pages into just over 160. All this laid the groundwork for our next step: content modelling.<\/p>\n\n\n\n

Content modelling<\/strong><\/h2>\n\n\n\n
\"Content<\/figure>\n\n\n\n

We led a collaborative content modelling workshop with stakeholders from IT Services to identify what fields would be needed and whether they were required or optional. The end result was a content model for a service reference web page. Here\u2019s what we did:<\/p>\n\n\n\n

    \n
  1. Reviewed our existing content \u2013 what worked, what didn\u2019t \u2013 and discussed how to structure information for a clear user experience. <\/li>\n\n\n\n
  2. Informed by our discussions, we drafted a service page template, with universal fields to suit all service types.<\/li>\n\n\n\n
  3. Built a mock-up of a service reference page and then reviewed the design during a \u2018content crit\u2019 to identify improvements. <\/li>\n\n\n\n
  4. Brought in our front-end developer to turn the mock-up into a proper CMS content type, based on our consistent new structure.<\/li>\n<\/ol>\n\n\n\n
    \"To<\/figure>\n\n\n\n

    Our templates allow us to create content faster and update many pages at once. With fixed text, dropdowns, and a consistent structure, any changes we make in the backend show up across all pages that use these templates. <\/p>\n\n\n\n

    We\u2019ve also added automation for service status messages. By linking to the University\u2019s live service status feed, staff and students can check if a service is down in real time. This feature offers transparency and reduces the volume of queries.<\/p>\n\n\n\n

    \"The<\/figure>\n\n\n\n

    We did more content modelling work for service category pages, for example Communication, collaboration and productivity<\/a>. These pages pull together themed groups of services onto one page. They\u2019re intended for users who might not be sure exactly what service they need, helping them to find a suitable tool, or explore related or alternative services. They each start with a short introduction and featured services, followed by a full list of services in scannable bullet list format.<\/p>\n\n\n\n

    On the main Tools, software and services<\/a> page, filterable searches and categories help users find what they need. <\/p>\n\n\n\n

    Content production<\/strong><\/h2>\n\n\n\n

    Content production on this scale requires careful planning and collaboration. First, we assembled a small team to tackle the content creation and CMS builds. We established a production timeline and regular communication channels, to keep everyone aligned. To maintain momentum and work in the most efficient way, we designated specific focus weeks for content creation and editing which allowed us to turn over a high volume of material while maintaining quality. <\/p>\n\n\n\n

    We divvied up the pages between us and we each had a proofreading buddy to check our work. After proofing the content, we handed content over to information providers and approvers (IPAs). Over 65 of them reviewed content for factual accuracy, making sure every detail was correct and up to date. This collaborative effort upheld our standards and commitment to delivering accurate, user-friendly information.<\/p>\n\n\n\n

    User testing<\/strong><\/h2>\n\n\n\n

    Before going live, we conducted some user testing with students to gather feedback on the new section. The pages performed well overall and we had some useful nuggets of feedback for making small refinements to ensure clarity. <\/p>\n\n\n\n

    Overall, the website worked well if the tester had prior knowledge on what they were trying to find. However, it didn\u2019t perform as strongly when the tester sought an output but was not aware of which tool could achieve it. While the new category pages help guide users, we need to understand how we can do more, and help users find a tool to support their specific needs \u2013 data analysis will help generate and inform solutions. <\/p>\n\n\n\n

    In phase three (the final phase of the project), we\u2019ll focus on enhancing navigation to make the pages even more intuitive, especially for those who need extra guidance on finding a tool or approach to meet their needs.<\/p>\n\n\n\n

    Going live<\/strong><\/h2>\n\n\n\n

    Thanks to meticulous planning and lots of collaboration, we went live on schedule. It wasn\u2019t without its challenges. The production timeline landed over the summer and the start of the semester, which wasn\u2019t ideal for everyone who needed to review and approve content. While everything was signed off and live on time, there will always be room for improvement and more collaboration. So we\u2019ll be working to review and tweak some target areas over the coming months. We\u2019re also putting content governance in place to keep everything current, relevant, and user-focused. <\/p>\n\n\n\n

    With phase two complete, we\u2019re excited to continue the rebuild, keeping usability and collaboration with stakeholders as a priority. <\/p>\n\n\n\n

    Check out the revamped <\/strong>Tools, software and services<\/strong><\/a> section.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

    Phase two of the IT web rebuild project was a complex and rewarding piece of the puzzle. Working closely with stakeholders, we delivered a new Tools, software and services section \u2013 spanning over 160 web pages which went live at the end of September. <\/p>\n","protected":false},"author":240,"featured_media":1130,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-1129","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/blogs.york.ac.uk\/communications\/wp-content\/uploads\/sites\/4\/2024\/12\/Wordpress-blog-phase-two.jpg?fit=825%2C510&ssl=1","uoy_author":{"name":"Harriet Sutcliffe","bio":"I'm a web content developer at the University of York.","image":{"src":"https:\/\/secure.gravatar.com\/avatar\/?s=200&d=mm&r=g","width":200,"height":200,"alt":""}},"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/posts\/1129","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/users\/240"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/comments?post=1129"}],"version-history":[{"count":0,"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/posts\/1129\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/media\/1130"}],"wp:attachment":[{"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/media?parent=1129"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/categories?post=1129"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.york.ac.uk\/communications\/wp-json\/wp\/v2\/tags?post=1129"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}