For example, a patient might enter some information, a clinician might review it and a laboratory might return a result. We need to understand what happens between those steps. Who sees the result? What happens if it doesn't arrive? How does somebody know there's something they need to act on?

Those questions affect what we build. They also involve people across the business, so I'd want the clinical team, the people running the service and the technology team working through them together. Otherwise, it's quite possible for everybody to have a slightly different understanding of what the software is going to do.

Working through the service

I'd want to see the actual process, including what happens when something doesn't go to plan. That means looking at how information moves, who can access it, what gets recorded and how the team would investigate a problem later.

In NHS work, there are clinical safety standards that address these responsibilities. DCB0129 concerns the manufacture of health IT systems, while DCB0160 concerns their deployment and use. The detail matters, including which organisation is responsible for which part. A technical team can't settle all of that on its own.

The software itself can still be complicated, and it needs proper testing. My concern is that we can spend a lot of time discussing the technology before we've agreed some fairly fundamental things about the service we're trying to deliver.

I've worked across technology, product, delivery and governance, and this is where those areas come together. We need to know what the business wants to achieve and what that means for the people using and running the service. That gives the development team a much clearer basis for their work.

The same questions come up outside healthcare. If you're introducing a system that changes how people work or how customers are looked after, I'd want to understand the process and responsibilities before committing to a particular solution.