Version Control Testing – what we learnt

20 April 2016

We wanted to find a way to make it easier for you to confirm you’re viewing current information on our website. That’s why we recently tested two version control enhancements on ATO Beta. Now we have some positive results we’d like to share with you.

What we did

  • We designed a test to find out if a history feature would help you confirm you’re looking at the latest information and identify any changes (clearly identifying minor, major and legislative changes)
  • We used Loop11 – an online testing tool that allows you to interact with a prototype to complete tasks and answer questions
  • We asked participants to complete two tasks:
    1. Find out if a piece of content is the most current version
    2. Find out what changed in the 2015 update to a piece of content
  • We also gave you the opportunity to provide feedback.

The results

Task 1: Find out if a piece of content is the most current version available
Success rate: 85%
Average time: 30 secs
Task 2: Find out what changed in the 2015 update to a piece of content
Success rate: 84%
Average time: 65 secs

 

We had 129 participants – approximately half were either tax professionals or familiar with ato.gov.au.

We had a huge success rate – the majority of users could identify if content was current and what changes had been made.

Your feedback also told us:

  • Don’t make you open a separate page
  • Put a version history link at the top of the page
  • Link from previous versions to the current version
  • The current version should be clearly marked.

Thanks so much for your input. We’re continuing to work on improving our online services through ATO Beta, so stay tuned for more updates.

Want to post comments anonymously?

Type a comment, type your name, then check the box "I'd rather post as a guest"

disqusGraphic