Riksbyggen.se had a large and complex CSS architecture, which resulted in long page loading time, Poor scalability- technical debt and struggles in workflow and inconsistent design across the website.

Workshop to identify current components and needs, Evaluating WCAG accessibility status of components, colors and contrast. Identifying new needs based on design evaluation and business priorities,

Component inventory of MVP 1 library including UI kit for Riksbyggen.se website. Signoff with brand manager and product owner. 145+ components with 270+ variables.

Riksbyggen’s React Component Library includes over 145 reusable components. The library ensures consistency, faster development workflows, and a unified user experience across all Riksbyggen applications.

FigJam board – We began mapping the customer journey to find an apartment, exploring how rentals and buying can merge seamlessly. Early ideas focused on SEO requirements, data on interaction, and introducing search from the start page.

Microsoft clarity The project aimed to refine the current interface without major changes. To guide design improvements, we used Microsoft Clarity to explore heatmaps and device data, helping us understand how users interact today.

Navigation Improving navigation on Riksbyggen.se started with research and strategic workshops across the organization. These sessions helped surface content priorities and user needs, forming the foundation for a restructured navigation.

Megamenu We replaced the dropdown with a mega menu, guided by best practices and insights from guerrilla testing. To support Riksbyggen’s goal of increasing engagement, we also added a space for promoting products or services—this will be A/B tested after launch.

Introduced weekly design meetings and a shared sprint format to align designers across different projects, reduce silos, and foster collaboration. Added structured retrospectives using the Start, Stop, Continue method, creating space for feedback, shared learning, and continuous improvement.

Introduced a structured work process for maintaining and evolving the design system. This process includes clear steps for component requests, requirement specifications, development, and testing. The goal is to ensure the design system is consistently applied across all digital channels and teams, while also enabling it to grow in a controlled and sustainable way.

To ensure success I facilitated presentations and onboarding sessions for cross-functional teams to raise awareness and encourage usage. I also worked closely with stakeholders to ensure the system would be actively maintained for future iterations and scalability.

Process flow We faced challenges in the past with scope changes occurring after the design phase had already been approved. These changes impacted timelines and threatened our ability to deliver on schedule. In response, I created this process map to clarify the decision-making path for prioritising requirements. It highlights which types of issues should be addressed first to keep the project on track and minimise the risk of delays.

Created a survey to assess how well teams understood the process for requesting components and using the design system. This helped establish a baseline for awareness and adoption. Prior to this work, a draft design system existed in Figma but was never adopted, highlighting the need for a more strategic, informed approach to implementation and engagement.

Replano - From Insight to Expansion
We began with in-depth research on board members, uncovering key insights that shaped the development of Replano—a digital tool for technical property management. From those findings, we built an initial MVP that is now being scaled and prepared for migration to 2,000 users.

Figma MCP Server + Cursor AI Prototype
To create a realistic scenario for user testing, I prepared an apartment search prototype using the Figma MCP server and Cursor AI. This allowed us to simulate real interactions and evaluate the experience in a more authentic context.

Process flow We faced challenges in the past with scope changes occurring after the design phase had already been approved. These changes impacted timelines and threatened our ability to deliver on schedule. In response, I created this process map to clarify the decision-making path for prioritising requirements. It highlights which types of issues should be addressed first to keep the project on track and minimise the risk of delays.