Quantum’s next product challenge: designing for the people who will actually use it

Credit first: the study asks a commercially important question that hardware benchmarks usually skip — who will actually use quantum computers, and what will those users need from the software? The researchers identify 11 personas spanning business users, early adopters, government contractors, scientists, algorithm designers, platform builders, high-performance computing (HPC) engineers and developers working close to the hardware.

The significance is that quantum software may have to mature in several directions at once. A business user should eventually be able to judge a quantum-enabled service by familiar outcomes such as cost, runtime, result quality and business value, without understanding qubits or circuits. A high-performance computing engineer — the person who helps integrate quantum processors into classical supercomputers and computing clusters — may need almost the opposite: visibility into hardware constraints, data movement, scheduling, integration details and low-level performance.

That matters because commercial adoption is not only a hardware problem. Even a capable quantum processor will be difficult to deploy widely if every prospective user must also become a quantum specialist. The software stack has to hide complexity where possible while exposing it where necessary.

The boundary is important. This is an exploratory preprint based on an expert focus group and nine completed practitioner interviews, not a representative survey of enterprise customers. It maps a plausible usability problem; it does not show that these users are already running productive quantum workloads or receiving economic value.