The Learning-Driven Design Process
We worked as a small, multidisciplinary team in close cooperation with C. H. Beck representatives. We adopted a learning-driven design approach; this entails supplementing our understanding about various aspects of the designed solution at every stage of the process. Regular workshops were central to this paradigm; they motivated us to share new knowledge and run feedback sessions for the achieved outcomes.
The process was divided into several stages:
- Kickoff – This stage allowed us to create a common understanding of the project goal, de-compose the preliminary mock-ups previously designed by C. H. Beck employees, and set up an initial work backlog in terms of design.
- Knowledge collection – During this stage, we conducted workshops for the Legalis system, determined necessary functions for the configurator, and thoroughly studied Legalis’s existing communication materials, including price lists.
- Verification – We conducted short interviews with existing and prospective Legalis users. This allowed us to verify our assumptions and deepen them (thanks to the insights shared by law firm employees). We also implemented elements of netnography, checking what conversations are held by Internet users and which legal bases they are searching.
- Solution ideation – We generated ideas about the configurator’s functions and elements and selected the ones that would best match C. H. Beck’s goals.
- UX/UI design –This is the last stage, leading to the creation of final designs and model texts. The key outcome of this stage is the creation of artefacts that were ready for the development team.
In this implementation, we employed elements of design thinking and service design methods, supplemented with our in-house solutions. We used the e-point Product Canvas and Tool Idea Canvas tools, which allowed us to achieve a clearer understanding of the business requirements (later included in the design brief as our project credentials).
At the ideation stage, we used empathy maps that brought us closer to the user’s perspective. We also used the concept of analogies-trends-inspirations to fuel our brainstorming sessions. Process maps and the service blueprint kept reminding us of the business logic underpinning the solution.
In the UX/UI design phase, our key tools were Sketch and the Sketch Measure plugin, which allowed us to quickly share element specifications with developers.
Our cooperation involved designing a system that would be implemented by the customer. Thus, we had to create a design which would be very clear to the developers.
To ensure this outcome, we prepared the following:
- A document that specified functional requirements and defined the operational modes for all configurator functions.
- Screens with graphic interfaces and specifications (measurements, font styles, colors).
- A document containing the configurator microcopy, i.e. the texts telling the user what is going on and what action options are available.