Build It Right, Not Just Fast
Combined Session
Wednesday, September 09, 2026 13:30—14:50
Location: Jupiter III
Wednesday, September 09, 2026 13:30—14:50
Location: Jupiter III
Building an effective IAM roadmap requires more than identifying gaps between the current and target state. Organizations need to translate these findings into concrete, actionable initiatives that can be prioritized, sequenced, and implemented over time.
This session focuses on how organizations can move from an assessment of their IAM landscape toward a structured roadmap for transformation. Building on KuppingerCole’s Identity Fabric and Reference Architecture, the session introduces an approach for deriving action items from identified challenges, maturity gaps, architectural requirements, and strategic objectives.
Participants will learn how individual action items can be defined in a consistent and practical way. This includes describing the underlying challenges, defining clear objectives, identifying concrete measures, and understanding the risks of not taking action. The session will also explore how dependencies between initiatives, organizational constraints, and implementation priorities influence the development of a realistic IAM roadmap.
Using practical examples, the session demonstrates how individual action items can be brought together into a coherent transformation journey. Rather than treating the roadmap as a static project plan, the approach helps organizations establish a structured direction for IAM while retaining the flexibility required to respond to changing business requirements, technologies, and priorities.
Through this session, participants will learn:
- How to translate IAM assessment results and strategic objectives into actionable initiatives
- How to structure and describe IAM action items consistently
- How to identify priorities and dependencies between different IAM initiatives
- How to combine individual action items into a realistic IAM transformation roadmap
By the end of this session, attendees will have a practical understanding of how to move from identifying IAM improvement areas to defining concrete actions and structuring them into a roadmap that guides the next steps of their IAM journey.
Many IAM and IGA projects begin with a reasonable ambition: meet every business requirement. When each request is translated straight into a technical solution, the result is an environment that costs a lot to run and resists change. The reasons are familiar: Some requirements get solved inside IAM although they belong somewhere else, and decisions are made without anyone weighing lifecycle cost, operational effort or real business value. The people who will run the solution afterwards are rarely in the room.
What has changed is the price of building: Custom code used to be slow and expensive to produce, and that expense quietly did governance work for us (at least sometimes). It forced a discussion, a budget, an approval. AI-assisted development has removed that hurdle without removing the cost of ownership. Testing across more than 100 language models found that roughly 44 percent of generated code contains a known vulnerability, while refactoring activity has dropped sharply and code duplication sits at record levels. Writing the code was never the expensive part.
This session looks at why organizations end up over-customized, what genuinely changes in the decision now that code is almost "free" to produce, which rules still hold when you bring AI into your Identity Fabric to support it, and how to check the next feature request without a three-week analysis. Two questions settle most cases: where does this requirement actually belong, and who owns the result five years from now?
