Many of the tools we rely on now, such as passwords, logins and ID checks, evolved as patches rather than part of a clear strategy.
These systems were not built for scale or for the complexity of modern digital life. As people move between roles, devices and services, the cracks begin to show.
During Hippo’s Identity Day, Jim Small explored what digital identity actually is. Not in abstract terms, but through the core functions most systems rely on: verification, authentication, authorisation, consent and federation. He looked at how these functions are delivered today, where the pressure points are and what a more reliable model might look like.

Our Hippo headliner
The internet skipped identity
These systems were not built for scale or for the complexity of modern digital life. As people move between roles, devices and services, the cracks begin to show.
Most of the tools we use to prove who we are online were never designed for it. Passwords, logins and ID checks were patched on as the internet grew.
In his Identity Day talk, Jim Small breaks down what digital identity really is, how it works today and where it is falling short. Exploring the shift from centralised systems to models where individuals control their own credentials.
Passkeys explained
Understanding passkeys and delivery
Why strong tech still needs clear language
Passkeys offer a more secure way to sign in, but most guidance is still too technical. When Pelin Demir’s team rolled them out in an NHS service, the lack of clear explanations made delivery harder. Her blog breaks down what passkeys are, where they fit in authentication, and why clarity matters just as much as the tech itself.

Snippets
Making logins less painful
Getting Identity right is both important and difficult. We asked our team what projects made them proud and two projects came up repeatedly. The first helped the NHS at a critical moment and the second supported a family of well-known brands, each facing the challenge of uniting their global identities. Two complex identity problems in very different contexts.
One login for 50 million patients
The NHS needed a fast, secure way for 50 million people to access digital healthcare. We helped refocus and deliver NHS Login in five months. It’s now used for over 2 million daily authentications and 80+ services, from Covid passes to GP access.
One group. One login.
We worked with a global consumer brand family to design and deliver a single sign-on experience across its portfolio. A unified ID replaced separate logins with one secure, streamlined journey now used by over a million customers, enabling better insight, consent and connection.
If you’d like more information on each of these, we have provided more detail on our website.

No stupid questions
What is “Secure by Design” and why does it matter?
Referenced in recent major government announcements, Secure by Design is an increasingly important part of our work. Like any relatively new terminology, it masks a more nuanced application. Our team have put together a quick briefing on this work and why it is important to organisations to have it in mind when building technology solutions.
- Bridging the gap between security and usability
- Threat modelling and human behaviour
- Iterating for continuous improvement
In this edition
- Why identity needs a clearer foundation: Rethinking identity from first principles
- Making passkeys clearer: Designing systems that are sustainable, accessible and grounded in real user needs
- Identity in action: Two real-world examples the herd helped with
- Secure by design: Why is it important to your organisation?
