BYGGFÖRETAGEN - UX designer ⎯ web app

Unifying systems for a smarter, simpler reporting experience

The redesigned tool unified multiple fragmented systems into one intuitive platform, making it easier for users to manage time and payroll reporting across companies and agreements. By streamlining workflows and improving usability, the solution reduced user confusion, empowered self-service, and laid the groundwork for fewer support requests. The new interface now better supports a wide range of users — from office staff to on-site workers — with a clearer, more efficient experience.
Background
Byggföretagen, a leading industry organisation within the Swedish construction sector, had developed a time and payroll reporting tool used by its member companies. Similar tools were in use across other industry associations, each with their own versions but facing many of the same usability and structural challenges. This initiative set out to unify these efforts by creating a shared solution — a single, streamlined user interface for time and payroll reporting across organisations and their affiliated member companies.
Over time, the user interface and underlying technical system had evolved into a patchwork of overlapping features and fragmented workflows. This led to an inconsistent and often confusing experience for users. One major pain point was that users with employees covered by multiple collective agreements (kollektivavtal) had to log in to several different systems, often struggling to understand where and how to report for each employee.
The system also needed to support multiple user groups with distinct needs and varying levels of digital proficiency, from office administrators to on-site workers. The existing solution could no longer coherently accommodate these diverse requirements.

A key goal of the initiative was to reduce the volume of support requests by improving usability. By redesigning the interface around real user needs and streamlining key workflows, the aim was to modernise the tool and deliver a significantly more intuitive and efficient experience.
My contribution in this initiative
  • Aligning around the user journey
    To kick off the initiative, I facilitated a cross-functional workshop with key stakeholders from each organisation, representatives from customer support, and the system's developers. Ahead of the session, I prepared a high-level user journey map that served as a shared reference point. The goal was to validate commonalities across existing systems and quickly identify friction points in the current experience.

    The workshop helped align the different organisations around a unified user journey, while also highlighting areas that required adaptation to accommodate their specific needs. As a bonus, the session surfaced several high-priority pain points, which sparked early ideation and gave me valuable input for the conceptual design of the new user interface.
    1
  • Design, prototype and test
    Based on insights from the initial workshop and an audit of the existing solution, I redesigned the user journey to support a more self-sufficient experience. The goal was to reduce the need for customer support by enabling users to complete key tasks on their own, such as modifying submitted reports or adding additional companies to report for, without confusion or external help.

    I worked in short, iterative cycles in close collaboration with the CIO, system owner, and developers. Together, we ensured the new experience felt cleaner and more intuitive and remained feasible from a technical and cost perspective.

    Before moving into usability testing, I facilitated a review workshop with key stakeholders and support staff. This allowed them to give early feedback and ensure the proposed design covered all critical use cases and edge conditions.

    I conducted usability tests to validate the updated design with six users representing the primary target groups. I then analysed the findings and presented them to the broader stakeholder group to inform the next iteration.
    2
  • Finalize the design and the designsystem
    The usability testing went smoothly, with no significant issues identified. In fact, the response was, Why couldn't this have been like this from the beginning? It feels smooth to report!

    I made a few final refinements based on user feedback to improve clarity and interaction details. I also ensured the design was well-documented and fully prepared for handoff to development.

    Since the organisation didn’t have an existing design system, I took the initiative to establish a foundational one tailored to this product. I introduced a new visual language — including colour palette, typography, and reusable components — to ensure visual consistency, scalability, and maintainability.

    Given the limited budget, I adapted MUI components and applied custom styling to achieve a softer, more user-friendly interface. This approach provided a practical, WCAG-compliant starting point for future development.
    3
  • Ready for development hand off
    To ensure a smooth transition from design to development, I documented all user flows, components, and interaction details in a clear and structured format. I then facilitated a handoff workshop with the development team, where we walked through the full user journey and reviewed key functionality together.

    The session helped create alignment on edge cases, technical constraints, and implementation priorities, reducing ambiguity and increasing confidence that the final solution would deliver on both user needs and business goals.

    The solution is currently in development, and we plan to evaluate its impact by running Hotjar surveys and tracking the number of support-related inquiries. This will help us measure how well the new experience addresses user pain points and supports a more self-sufficient, intuitive service.
    4

Below is a brief preview of both the new and existing design. While the full solution includes much more — including a mobile-adapted version — these examples provide a quick overview of the visual direction and key improvements.
An initial workshop was held to identify friction points in the current user journey and generate ideas to address and prioritise the most critical user pain points. Participants included stakeholders from each organisation, customer support, and developers for the existing solution.
Support a single service for reporting payouts across the construction sector — with the flexibility to easily report for multiple companies.
Mitt Lösen - Easy to navigate, understand, and find previous reports
Mitt Lösen - Report manually, by adding employees or upload a file, for employees condect to various collective agreements (kollektivavtal)
One of the most frustrating issues users faced was the lack of feedback when uploading a file. If an error occurred, the system provided no information about what went wrong — leaving users to guess what needed to be corrected.
The current service lacked self-service functionality for managing companies directly in Mitt Lösen, which resulted in a high number of support calls. Based on this insight, we decided to include this functionality in the new solution to increase user autonomy and reduce support dependency.
Previously, if something went wrong during reporting and a correction was needed, the process was often unclear and required assistance from support. To improve the experience, we built this functionality directly into the service — making it easier and more convenient for users to manage corrections on their own, without external help.
Easily find help, by guides, FAQ and contact support
The result from the usability testning - for communication with stakeholders