Why single sign-on matters more than it might seem
Some of the biggest barriers to good conversations at work are obvious. Time is tight. Confidence can dip. Priorities compete for attention.
But sometimes the thing that gets in the way is much simpler than that.
Sometimes it is the login screen.
It sounds like a small detail, but small details shape behaviour. If a platform is awkward to access, people are less likely to use it in the moment. If it feels separate from the rest of the working day, it becomes something to come back to later. And “later” often turns into not at all.
That is why we have introduced single sign-on to Maps and Pathways.
Users can now access the platform through Google, Microsoft, SAML and Wonde, without needing a separate password or an extra login process.
On the surface, that might look like a modest update. In practice, it removes one of those everyday frustrations that quietly puts people off engaging.
That matters because development platforms should not feel like another task to manage. They should feel easy to pick up when the right moment is there, whether that is after a piece of feedback, ahead of a conversation, or during a moment of reflection that would otherwise be lost.
One of the things we hear regularly from organisations is that development systems can end up feeling like something people have to make time for, rather than something that supports the work they are already doing. That is exactly what we want to avoid.
Maps and Pathways is designed to sit alongside the day job, not outside it. The aim is to make reflection, feedback and professional conversations easier to have, not harder to start.
Reducing password fatigue is a small part of that, but it is still an important one.
When access is simple, people are more likely to engage. They are more likely to log in while something is still fresh in their mind. They are more likely to capture a thought, respond to feedback, or continue a conversation that matters. And over time, those small moments build better habits.
It is easy to talk about the bigger features in a platform like this. Things like 360 feedback, reporting, insights and professional growth conversations are all important.
But the truth is, the smaller details often decide whether those bigger features get used at all.
A quick login. A familiar sign-in route. A platform that fits into the systems people already use.
Those things shape the experience just as much as the functionality does.
Single sign-on also matters at an organisational level. Most organisations already have their own identity providers, security requirements and user-management processes in place. It makes far more sense for Maps and Pathways to work with that environment than to sit awkwardly alongside it.
That means less admin for internal teams, stronger alignment with existing security processes, and a smoother experience for users from day one.
Most importantly, it means less time spent getting into the platform and more time spent using it well.
At the heart of Maps and Pathways is a simple idea: better development happens through better conversations.
Everything we add should support that. Sometimes that means introducing new capabilities. Sometimes it means removing friction that never needed to be there in the first place.
Single sign-on is one of those changes.
It is a practical update, but it supports something much bigger. When someone is ready to reflect, share feedback or have a meaningful conversation, the platform should help that happen straight away.
Now it does.
