Knowing the right level of interaction design
...that are easy to use and understand. They’ll prototype these solutions – often in code because interactions are made of code, not mock-ups – to test ideas with users and...
...that are easy to use and understand. They’ll prototype these solutions – often in code because interactions are made of code, not mock-ups – to test ideas with users and...
...a Market Research Society (MRS) Company Partner, so we also align our policies with the MRS Code of Conduct. At the heart of our approach sits the User Research Ethics...
...disputes translation of technical concepts to non-technical users so they’re understood by all Our Technical Architects work closely with delivery teams and are hands-on – they might code prototypes or...
...role levels in Infrastructure, Network, DevOps and Software Engineering. It helps colleagues easily map which skills they need to develop for promotion or sideways career moves. The framework includes a...
...needed in LEDS Person, data such as nationality, currency, or country code are available across the whole stack, helping to keep information consistent and convenient. As the team keeps working...
Software Developer, Sharon Briscoe Having been a long serving civil servant with almost 20 years of experience under my belt in casework and management, I hadn’t considered a career change...
...that’s being built: some code, user research, content, a change to a process – anything. The team tells how they came up with the solution, what it does and how...
...of guidance on building and maintaining digital services, including the Service Manual, Design Principles, the Technology Code of Practice and the Digital Service Standard. It’s incredibly useful, but people don’t...
...an online application form easier to understand, or optimising the underlying code for a service – increases your own emotional investment in a project and therefore your motivation. Next time...
...able to interact with. Building a code-rich prototype didn’t mean the rest of the team were excluded from the day. Everyone played their part; building dummy data sets, mocking up...