User Needs as a North Star: a Key Insight From DORA on AI Adoption
"Prioritizing user-centricity isn’t just a design choice; it’s a performance multiplier. DORA research shows that teams who focus on the user have 40% higher organizational performance and significantly higher job satisfaction. In an era where AI allows us to build faster than ever, a user-centric focus acts as our steering wheel. Without it, we risk simply crashing faster."¹
One of the key insights in the 2025 State of AI-assisted Software Development report from DORA is that AI’s primary role is as an amplifier. It tends to magnify an organisation’s existing strengths and weaknesses, rather than fixing underlying issues by itself. The report highlights that the greatest returns on AI investment come not from the tools themselves, but from a strategic focus on the underlying organisational system. This framing shifts the conversation away from “which AI tool should we use?” and towards a more important question: what capabilities determine whether AI accelerates meaningful outcomes, or simply accelerates noise?
The report introduces the DORA AI Capabilities Model as a way to make the “AI as an amplifier” insight actionable, outlining the technical and cultural capabilities that help organisations get positive performance gains from AI rather than simply accelerating existing dysfunction. Among those capabilities, User-Centric Focus stands out — because it’s the one that keeps teams moving in the right direction and because DORA research² shows that teams who focus on the user have 40% higher organisational performance and significantly higher job satisfaction.
User-centricity as a foundational capability
The User-Centric Focus capability that the DORA model highlights as foundational is key because AI can increase output and individual effectiveness, but that doesn’t guarantee better outcomes. When teams can move faster, direction matters more. The report makes this point explicitly: when teams adopt a user-centric focus, AI’s positive influence is amplified; when that focus is absent, AI adoption can have a negative impact on performance. This matches what I’ve seen often: teams can get more productive while becoming less effective, especially when the system optimises for internal throughput rather than external value.
Why “user needs as a north star” needs a mechanism
Arguably, most organisations agree with the idea of user-centricity in principle. The harder part is operationalising it in a way that actually guides decisions, trade-offs, and evolution. In many organisations, “user needs” are assumed, implicit, or contested. Teams often inherit backlogs, roadmaps, or requirements without a shared view of the needs they are intended to serve. This is where I think DORA’s “user needs as a north star” framing becomes especially important. It’s not just a mindset, it’s a constraint that keeps acceleration pointed in the right direction.
And this is also where User Needs Mapping fits naturally. User Needs Mapping is a practical way to make user needs explicit enough to act as an orienting force. It helps teams clarify who they serve, what those users are trying to achieve, and where value is being created (or lost). That clarity becomes the reference point teams need as AI accelerates delivery and decision-making.
Value Stream Mapping is powerful — but only once the purpose is clear
The DORA report also points teams toward techniques like Value Stream Mapping, and for good reason. Value Stream Mapping is one of the most effective ways to make work visible, revealing handoffs, bottlenecks, delays, and friction in the flow of value.
But there’s a dependency that’s easy to miss: every value stream exists to serve one or more user needs. If those needs are unclear, a value stream map can be entirely accurate and still optimise the wrong thing. Teams can reduce waste and increase throughput while drifting further away from the outcomes that matter.
And AI amplifies this problem; as more code is generated, the developer’s responsibility shifts. The work becomes less about producing output and more about steering context, shaping intent, and acting as a proxy for the user. AI can generate coherent artefacts from prompts, but it doesn’t decide what is worth building, or what good looks like for the people relying on the system. The team still owns direction, and direction depends on having a shared understanding of user needs.
This is why I see User Needs Mapping and Value Stream Mapping as complementary. User Needs Mapping clarifies the “why” and the “for whom”, and Value Stream Mapping helps improve the “how”.
A simple test for AI readiness
If you’re investing in AI tools right now, a useful starting question might be:
Can our teams clearly articulate the user needs they exist to serve, and use those needs to guide decisions?
If not, AI will still increase output, but it may simply increase system load, accelerate misalignment, or make it easier to move quickly in the wrong direction.
DORA’s AI Capabilities Model makes a strong case that user-centricity is foundational. My view is that User Needs Mapping provides a practical mechanism for deliberately building that capability, so that AI acceleration translates into better outcomes for users — and more sustainable work for teams.
