Skip to main content

Design Sprint: foundation for Croonwolterendros

By first learning to understand a fragmented process, we started with the Design Sprint. This gave Croonwolterendros the right start straight away, so we could immediately develop the right platform.

Design Sprint: foundation for Croonwolterendros

Croonwolterendros is a technical installation company that builds and maintains installations, including in buildings and infrastructure. That means a lot has to be monitored every day, from maintenance work and installations to contractual agreements.

  • Client: Croonwolterendros
  • Industry: Technical installation & maintenance
  • Technology: OutSystems, Figma
  • Service: Expert Services / Design Sprint

Benefits for Croonwolterendros

Troubleshooting icon: magnifier over a warning triangle

From assumption to insight

The complete customer journey mapped out and the current user process documented

Presenting icon: person at a board with a flow chart

Validated with end users

Wireframes presented early to the people who work with them every day

UX flow diagram icon

Optimal process defined

Tested and discussed with the end user from the start, not afterwards

Upgrade icon: arrow rising from stacked layers

Working concept

The result is immediately a working prototype/concept, not an intermediate step

Meet our team

Want to find out if a Design Sprint is the right first step for your project? Schedule an introductory meeting and let's look together at your challenge and how we go from insight to solution.

Meet our team

The Challenge

The maintenance calculation process was fragmented across individual Excel files, which made it error-prone, hard to oversee and difficult to scale.

Before Product League built a new platform for this, both parties wanted to be sure the direction was right. The solution had to match how specialists really work. The organisation's key concerns also had to be taken seriously upfront.

The Challenge
Our Approach

Our Approach

Product League chose a phased approach:

  1. First a Design Sprint to gain a shared grip on the current situation and the key pain points, then a Proof of Concept to make the chosen direction concrete
  2. Full platform development followed. This delivers a validated first-time-right process, instead of still having to search during development for what is really needed.
UX Design sprint screenshot Figma

Deep dive

The sprint consisted of a number of consecutive steps, spread across half-day sessions.

From deep dive to wireframe

  • Deep dive – broadly gathering what is going on: goals, context and the key pain points in business, IT and operations.
  • Walking through the current process – looking in detail at how processes and systems currently function, including the exceptions that cause most problems in a spreadsheet-based approach.
  • To wireframes – translating the gathered insights into concrete sketches of a possible solution.
  • Validating with end users – the wireframes were briefly presented to end users, so the direction was tested against reality early on.

People involved

Icon of a person connected to a node

2 end users

CWD — day-to-day practice

Technical support icon: hard hat above a cog

2 developers

Technical feasibility

Number one hand gesture icon

1 decision-maker

Manager CWD

Presenting icon: person at a board with a flow chart

Facilitation & PO

Product League

The Result

By first taking the time for a deep dive and validation, a shared and tested picture of the challenge emerged before the build began. This delivered not only a validated direction, but also buy-in from the decision maker and end users to actually follow that direction. From the wireframes, the project moved straight into a Proof of Concept, as the first tangible step towards the platform that grew out of it.

The Result