In order to transform digital delivery in healthcare and achieve better patient outcomes, we need to learn the lessons from the COVID-19 response and the ongoing digital transformation occurring within trusts.
Learn about how user-centred design, hypothesis-driven development and fast feedback cycles can be used to enable digital projects to be delivered quickly and respond to failure without breaking stride.
We spoke to Ian Roddis, Deputy Chief Digital and Information Officer, and Anna Awoliyi, Chief Allied Health Information Officer for Kettering General Hospital about how we collaboratively worked with ward staff and patients to iteratively improve the NHS Book a virtual visit service based on user research.
Key takeaways from React’s approach to user interfaces and how it might impact user interface development at large
In software development, things occasionally don’t go the way you expected them to. As a team, there are two ways to manage this problem: you can treat them like car crashes, or you can treat them like plane crashes. Both can work, but it’s a choice you should make with your eyes open.
An interview with Elena, a software engineer at Made Tech who loves to join in with user research.
Just as digital service teams are measuring the performance of their products, it’s important also for technology departments and development teams to decide on what good technology looks like so that we can ensure the choices and practices we’re implementing are having a positive outcome for our users.
We’ve worked with a number of organisations who make use of the Microsoft Dynamics NAV suite as their Enterprise Resource Planner (ERP). As is common with similar off the shelf tools such as SAP and FinancialForce for Salesforce, it can be hard to provide a productive and enjoyable user experience, often requiring a number of unituitive steps on several screens to perform basic tasks such as logging a sick day.
Design patterns are solutions to software design problems that are presented in an almost conceptual way. That is to say, a given design pattern has the potential to be applied to a piece of software written in any number of languages but, at a code level, it’s up to the developer to interpret that idea and make it work for them.
In this article I’d like to discuss two concepts that you might not immediately think to compare. I’ve written previously on keeping your stylesheets modular and also on boundaries in object oriented design, so today I bring the two loosely together.