Designing an error dashboard, and contributing to the design community

Error dashboard This sprint we did a bit of a handbrake turn and picked up a new little problem to work on. The team had become aware of a spike in errors and we wanted to explore if we could display these to users via the RAVS interface so that they could fix things themselves. These errors are caused later, when we send our data to other parts of the NHS, so they aren't things we can spot as the user completes the everyday parts of our service. Since it was quite a technical problem, I decided to work closely with a few people on the team to help keep the work on track. I've been putting in regular check-ins with our content designer, product manager, software developers and business analyst. I've also tried to capture every question and suggestion that is raised as we critique and iterate the design. I think this has really helped us to move quickly and stay aligned. We're aiming to do some user research on the prototype next sprint. Watch this space. Reviewing design community…