Why our dashboard works
...duplicating some of the data. Not only was this increasing the time it took to put the data together it was increasing the time it took for the intended recipient...
...duplicating some of the data. Not only was this increasing the time it took to put the data together it was increasing the time it took for the intended recipient...
...that it has helped that product’s intended users to achieve their needs. In the case of the manual, we wanted our users to be able to find what they wanted...
...or die by the user’s ability to find what they need, so search and navigation are key to early user buy-in and adoption some tools have excellent metadata ingestion and...
...oversimplified view of customer journeys. Anne’s team used individual level data to follow customers through the Verify service, concentrating on customers with “less happy journeys”. They used data to devise...
...in seeing how the user needs for the manual have changed. This is especially important in the age of Government as a Platform. A digital infrastructure shared across government needs...
...useful in feeding insight into our development process. Our team is already planning our next product audit with the team at the MOJ’s Lasting Power of Attorney service. We’ll blog...
...this situation, and to understand the types of common issues users are highlighting, we can use topic modelling. Finding hidden topics in comments The idea of topic modelling is that...
...users have needs too. In my next blog post I’ll tell you more about the dashboard itself. I’ll describe how we decided: what to include where to host it how...
...to think about how to show when content was last updated and how it has changed over time. We also need to make sure the structures are in place to...
...us provide trusted information to users and make sure other useful and trusted content from others is surfaced. Schema.org allows us to put in links to other pages with relevant...