


1 / 3
Design System Lead
Overview
I took over as Design System Lead at Bane NOR through NoA Ignite, maintaining and developing an established React library used by more than 20 internal product teams.
I owned the roadmap, releases, stakeholder reporting and support, alongside hands-on component work and coordination with designers and product teams.
Bane NOR manages Norway’s rail infrastructure. I joined through NoA Ignite as Design System Lead, taking over an established React library used by more than twenty internal product teams.
Over five months, I focused on reliable releases, clear priorities and support for teams with different needs. The role combined engineering work with roadmap ownership and stakeholder communication.
My responsibilities
I owned the roadmap, stakeholder reporting, release cadence and support model, working alongside a small core team and contributors from product squads.
- Roadmap — what ships next, what waits, and what we deprecate with a clear migration path.
- Stakeholder reporting — regular updates to Bane NOR and NoA leads on progress, risk, and adoption.
- Release cadence — predictable drops through the existing NX monorepo and Azure Artifacts pipeline.
- Support — triage, DevOps tickets and logging to keep product teams unblocked.
What was already there
The previous lead and core team had established the token structure, CI/CD pipelines, Storybook and a catalogue of more than twenty React components. I built on that foundation.
- Token architecture and build pipelines were in place before I arrived.
- A broad component set was already shipping to active product teams.
- Internal Storybook and package distribution via Azure Artifacts — no public docs site.
- Design support from Bane NOR designers; I focused on delivery, process, and engineering coordination.
How we ran the system
We worked in sprints, with regular design–development discussions, backlog reviews and feedback sessions focused on product teams’ practical needs.
- Sprint cadence for the core team — planned work, support load, and space for urgent fixes.
- Design–dev sync so component APIs matched what designers actually specified.
- Backlog grooming to separate "nice idea" from "three teams blocked on this".
- Adoption surveys, tutorials, showcases, and demos to surface friction before it became a fork.
- Developer feedback sessions — I recorded attendance to help track participation and decisions.
What I pushed forward
I added components where support tickets revealed gaps, rewrote APIs that had drifted and deprecated legacy patterns with migration paths. I also handled DevOps tickets and logging to keep releases moving.
What was hard
More than twenty teams brought different requirements and priorities. The challenge was to support those needs while keeping component APIs consistent and the library maintainable.
What I would do differently
With more time, I would prioritise refactoring and make it easier for product teams to contribute. The feedback sessions helped; I would establish a formal contribution process earlier.
I left in December 2025 with the system still in active use across Bane NOR. My five months focused on keeping delivery reliable and balancing shared standards with product teams’ needs.