IAM, IGA & identity platforms
Identity lifecycles and access governance across Entra ID, Active Directory, and Omada — human and non-human alike.
Open to new opportunities
IT Project Manager & IAM Coordinator
I lead complex IT projects in critical infrastructure. The technology is rarely the hard part — the people around it are.
About
Before IT, I spent four years running a pool of around 20 healthcare consultants — negotiating contracts, handling penalty-clause disputes, and mediating when a client and a consultant genuinely disagreed. Nothing teaches you stakeholder management faster than a placement falling apart on a Friday afternoon.
In 2024 I retrained: a vocational degree (YH) in IT Project Management, then PSM I. Most recently I coordinated IAM, IGA, and identity security at Trafikförvaltningen, Region Stockholm — an environment where getting access wrong isn't a support ticket, it's a NIS2 question. The domain was new to me. The part where fifteen people want different things and someone has to make it add up was not.
That's the short version of why I work the way I do: I'd rather have the uncomfortable conversation early than manage a risk register full of things nobody wanted to say out loud.
Practising what I work with: this site is fully static, loads nothing from third parties, and measures visits without cookies or personal data.
IAM/IGA coordination in one of Sweden's most complex operating environments.
Workshops, demos, retrospectives, and hands-on backlog work.
Kanban, DoR/DoD, and documentation people actually use.
I believe in being direct and clear, even when it's uncomfortable — it builds trust faster than anything else. Process and tools, AI included, are only worth something if they actually make life easier for the people using them; I never lose sight of that in the pursuit of efficiency. And I invest as much in building and maintaining relationships as I do in optimizing a workflow — most of my best opportunities have come from people, not processes.
Skills
A selection of what I work with day to day — from agile coordination to identity security.
Identity lifecycles and access governance across Entra ID, Active Directory, and Omada — human and non-human alike.
Planning and follow-up across cross-functional teams, plus the workshops, demos, and retrospectives that keep it moving.
Holding the line between business, IT, security, architects, and external vendors — including when they disagree.
Sourcing and requirements work inside public-sector rules, NIS2, and GDPR.
Tracking what could derail a delivery, and removing the friction that slows it down.
Board structure, DoR/DoD, and records management in Jira, Confluence, and JSM — documentation people actually use.
Experience
From critical-infrastructure IAM coordination to delivery ownership for a 20-person consultant pool.
Trafikförvaltningen, Region Stockholm
Nvrmind, Stockholm
Vårdbron, Stockholm
Complementary coordination and delivery experience
Selected work
Concrete examples of how I work — situation, action, and result.
25–50M SEK project budget scope
Situation: Trafikförvaltningen's IAM, IGA, and IDP (both public and internal identity platform) were managed by an external supplier — limited in-house control and exposure to vendor-driven change.
Action: Took part in the large-scale insourcing project — contributed to public procurements and RFI processes, traditional project management with dependencies across stakeholders organization-wide, budgeting, risk analyses, project specifications, architecture, records management, status reporting, and requirements management, all within the frame of NIS2 and GDPR.
Result: Increased in-house control over critical identity infrastructure and reduced dependency on the external supplier.
Situation: The IT department, around 300 people, worked in silos with differing ways of working across groups — making collaboration and communication across the department difficult.
Action: Took part together with Scrum Masters and agile coaches in a department-wide initiative to break down silos, establish shared ways of working, and optimize communication between groups that otherwise worked in very different ways.
Result: Increased collaboration and clearer shared ways of working across the entire IT department.
30,000+ human & non-human identities 25–50M SEK project budget scope
Situation: Roughly 30,000 identities — human and non-human — were, and to some extent still are, fragmented across many different systems within Trafikförvaltningen and among partners, subcontractors, and transport operators, making oversight and traceability difficult.
Action: Contributed to a large-scale project consolidating these into a shared identity register, with a focus on security, traceability, and data quality across the entire ecosystem of parties.
Result: Improved visibility into all identities — human and non-human — across the full supply chain, strengthening both security and data quality.
Situation: Project planning for the “Operational Security” group was done manually in PowerPoint — hard to track real-time status for 28 people.
Action: Migrated the entire planning process to a dynamic Jira/Atlassian view, introduced DoR/DoD as delivery criteria, and ran workshops for both employees and consultants.
Result: A shared, up-to-date overview for 5 teams and clearer delivery criteria across the group.
Situation: Need for unified guidance on AI tools (e.g. Copilot) grounded in NIS2, GDPR, and information security.
Action: Drove the initiative together with other project managers and agile coaches, evaluated Microsoft 365 Copilot from a cybersecurity perspective, and produced an AI FAQ.
Result: Clearer guidelines on where data may be processed and what applies to information-security-classified documentation.
5 people in the team I led
Situation: An external client was running its sales process on Salesforce, but needed a system built around how the business actually worked rather than adapting the business to the platform.
Action: Led the project and an internal team of five, including myself, as project manager. Owned client contact and delivery follow-up, and ran the work in Scrum — which mattered, because requirements kept changing during the build and each change had to be absorbed without stalling the team.
Result: A delivered, custom-built replacement for an off-the-shelf platform, and a client relationship that held through a moving scope.
Credentials
scrum.org
Issued 2025-05-29.
View certificate Verify at Scrum.org300 YH credits
2024–2025.
Tools
Contact
Feel free to reach out directly via email/LinkedIn, or send a message through the form — I'll get back to you as soon as I can.