...source code to be made publicly available. Rather than making a judgement on what source code will be useful and reusable, the default approach should be to publish (sensitive information...
...from the private beta service in order to more fully understand the primary needs of users affected by PAYE income tax. In particular, the service needs to evolve to a...
...be checked to make sure that interactions conform to the current GOV.UK style guide. New interactions that have been developed, such as mapping, should be fed back into the design...
...understanding of the target user group was reached. This research could have included contextual research with target users to understand their experience of finding themselves in debt to the government,...
...instructional text and micro-copy. The content designer should be working alongside the team, getting involved in user research and feeding in to the design and flow of the service. Recruit...
...methods of interaction with their users. They had conducted extensive and, in in the panel’s opinion, sensible research to uncover users with assisted digital (AD) needs. The panel agreed with...
...the ‘Inquiring Citizen’). Opportunities should also be explored to do more user-testing outside of lab conditions and constraints, including accessibility testing. There have been issues with recruiting permanent staff into...
...work closely with HMRC’s Tax Platform team to understand and implement HMRC’s policy to open source by default and code in the open. There are currently no firm plans in...
...of the service team who have achieved a lot in a short period of time. The team are working in an agile way, have all disciplines represented in their team...
...also not passed point 8 – although there are plans to share code within DVLA, and the team expressed a willingness to make its source code open and reusable, there...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.