CX/UX Discovery · Liber · Insight leadership and research operations
Making customer insight part of product decisions at Liber
Customer insights existed across Liber, but there was no shared way to bring them into product development.
As CX/UX Discovery Lead, I worked with people across the organisation to build a common approach to discovery, starting with the decisions teams needed to make and what they still needed to learn.
I tested and refined the approach hands-on in five ongoing projects, then developed the methods, tools and guidance to help teams put it into practice.
The work was approved by Liber’s management team and introduced across the product development department.
- My role
- CX/UX Discovery Lead
- Year
- 2026, ongoing
- Industry
- Learning materials
- Company
- Liber AB
- Scope
- 4 months

The way of working
- Decisions aheadWhat do we need to decide?
- Research questionsWhat is still uncertain?
- DiscoveryExplore needs and test concepts
- InsightsInform the decision
The value of a learning material lies in carrying the teacher’s planning without taking it over
Teachers build their teaching from the subject team’s planning, the pupils and the situation, and then pick the material that fits.
The short version
The problem
Customer and user insights were gathered across Liber, but there was no shared way to document, find or use them in product development. Earlier knowledge was overlooked, research was sometimes repeated and decisions risked being based on assumptions.
What I did
I mapped the existing ways of working and developed a shared discovery approach with people across the organisation. I then tested and refined it hands-on in five ongoing projects, helping teams connect research questions and customer insights to the decisions they needed to make.
What I delivered
A decision-driven discovery process, a resource bank with 18 guides, templates, workshop resources and AI supports, and the foundations for a customer panel that was still being developed.
What it led to
All five projects gained customer insights to inform their next decisions. In some projects, the findings confirmed the direction. In others, they led to changes in future product strategy.
Liber’s management team approved the new way of working, and it was introduced across the product development department.
What I led
An insight operating model
One shared flow from question to decision, with defined decision points and clear responsibilities between CX and the project teams.
Five teams, coached hands-on
I worked alongside five live projects through every step: choosing, planning, carrying out and following up their research. As a result, all five could weigh their decisions by customer impact.
Research operations
A resource bank with 18 guides, templates, workshops and AI supports, and a customer panel for faster recruitment that is now being built up.
AI in the research process
Ten ready-made prompts, including one that takes a team from transcripts to observations, insights and remaining uncertainties.
The problem
Liber had valuable knowledge about its customers and users, but it was scattered across the organisation. Without a shared way to document, find and use those insights, teams couldn’t always build on what was already known.
This led to three recurring problems.
Existing insights were overlooked
Knowledge from earlier research wasn’t always available when new projects started. Teams risked missing insights that could have helped them make better decisions.
Studies were repeated
When earlier findings were difficult to find or reuse, teams sometimes investigated questions that had already been answered.
Customers came in too late
Customers and users were often involved after a solution direction had already taken shape, rather than helping teams understand the needs and problems worth solving.
As a result, decisions risked being based on assumptions, and concepts could be developed before their relevance and value had been tested.
Goal and challenge
The goal was to make customer and user research easier to carry out and more useful in product decisions.
To make that possible, we needed to work on three things together: a shared way of working, practical method support and better access to the right customer and user groups.
The outcomes we wanted to achieve
Learning materials that better meet the needs of teaching
By understanding how teaching works in practice and involving teachers and pupils in exploring and testing solutions.
How we planned to measure itSales and NPS.
Better-informed decisions and fewer late changes
By using customer insights to address important uncertainties and testing concepts before development had progressed too far.
How we planned to measure itThe number of late changes during production.
Faster research and less duplicated work
By clarifying responsibilities, making it easier to reach the right participants and reusing knowledge from previous research.
How we planned to measure itTime from starting research to making a recommendation, and how often existing insights are reused.
The challenge: one approach for different teams
Liber’s teams worked across different functions, projects and product areas, each with its own needs and established ways of working.
We needed an approach that was structured enough to support consistent research and better-informed decisions, but flexible enough to work in different kinds of projects.
Make customer involvement part of everyday work
Just as importantly, the approach needed to make it easier to involve customers and users throughout product development, rather than relying on occasional research activities.
How I worked
My role
I led the work to understand how customer and user research was carried out across Liber, where knowledge was getting lost and what prevented teams from using insights more consistently.
Through interviews and workshops, I developed the new way of working together with key people across the organisation. I structured the process, clarified responsibilities and decision points, and created support for how teams could build on existing knowledge, identify uncertainties and plan the right research.
Rather than developing the approach in isolation, I wanted to test it in real projects and learn what teams actually needed.
The team
The work brought together people from CX, process management, product management, publishing and project management.
Their different perspectives were important. We needed an approach that supported better product decisions while also fitting how teams planned, developed and delivered learning materials.
Piloted and refined in five ongoing projects
In May, I joined five projects already under way and worked closely with the people leading them.
I supported the teams throughout their research, from choosing the right questions and methods to planning, conducting interviews, analysing findings and using the insights in their next decisions.
At the same time, I used what we learned in the projects to refine the process and develop practical method support.
- 1SwedishPrimary school, years 1–4
- 2SwedishLower secondary school, years 7–9
- 3New digital platform for mathematicsLower secondary school
- 4MathematicsUpper secondary school
- 5SFISwedish for immigrants
What the interviews gave us
- about 120observations
- about 25insights
- 3–5findings per main research question
- 6–8opportunity areas per area
To support the analysis, I created an AI prompt that helped teams work systematically from transcripts to observations, findings, core insights, opportunity areas and remaining uncertainties.
The support was used across all five projects and could also be applied to earlier research material. This helped make customer knowledge easier to structure, compare and reuse.
Most importantly, it helped teams move beyond summarising interviews to understanding what the findings meant for their product direction and decisions.
Why the pilots mattered
Working alongside the teams through the entire research process showed us where they needed guidance, clearer responsibilities and practical tools.
Instead of introducing a generic discovery framework, we developed an approach shaped by Liber’s actual projects, people and ways of working.
What the pilots taught us
The five projects revealed three recurring challenges in how research was chosen, carried out and turned into decisions.
These findings helped us shape the new way of working.
1
1. Choosing the right research
What we saw
Teams didn’t always know which questions mattered most. Sometimes the research method was chosen based on the time available rather than what the team needed to understand.
Going forward
Start with the decision ahead and identify the uncertainties that could affect it. Then choose the research method that can best help reduce those uncertainties.
2
2. Planning and carrying out research
What we saw
Responsibilities weren’t always clear, particularly around who should formulate interview questions and how participants should be recruited. Recruitment also lacked coordination.
Going forward
Make responsibilities clear from the start. Agree on who develops the research questions and coordinate recruitment through a shared customer panel.
3
3. Turning research into decision material
What we saw
Interviews were documented and summarised, but the findings weren’t always analysed and connected to the choices teams needed to make.
Going forward
Go beyond summarising what participants said. Identify patterns, develop insights and work together to understand what those insights mean for the next decision.
A concrete example: start with what we already know
One of the pilot projects already had an earlier needs analysis that described several of the target group’s most important needs.
But the new research had begun before that knowledge was brought into the project.
When we compared the earlier analysis with the new findings, we realised that several important needs were already known. What the new research added was a deeper understanding of when and how digital solutions could create value.
It was a clear example of why research shouldn’t start from a blank page.
- Start with existing knowledgeGather what the organisation already knows. Separate evidence from assumptions and identify what is still uncertain.
- Focus on what matters for the next decisionPrioritise the questions that could change the team’s direction or recommendation. Avoid investigating what is already understood well enough.
- Choose the right next stepLet the remaining uncertainties determine whether the team needs to explore needs further, validate existing findings or test a concept.
The important change was to treat research as a way to support decisions, rather than an activity to complete.
The new way of working
What we learned from the pilots shaped a shared approach where research starts with the decisions teams need to make.
This meant three important shifts.
Fromactivity-driven
Todecision-driven research
Start with the decision and what the team still needs to learn, rather than choosing a method first.
Fromproject-specific
Toreusable customer knowledge
Make existing and new insights accessible, so teams can build on what Liber already knows.
Fromad hoc research
Toa shared approach
Give teams clear responsibilities, practical tools and better access to the right participants.
Four principles behind the approach
1. Start with what we already know
Build on existing customer knowledge before planning new research.
2. Separate knowledge from assumptions
Make clear what the evidence supports and which questions remain unanswered.
3. Connect research to decisions
Know which decision the research is intended to inform.
4. Explore needs before solutions, test before investing
Understand needs and test concepts before committing to larger investments.
From initiation to production
I adapted the approach to Liber’s existing product development process and decision points.
The five steps take teams from existing knowledge and open questions to insights and recommendations.
- 1. Start with what we knowGather existing knowledge, identify important uncertainties and formulate questions connected to upcoming decisions.
- 2. Choose the method and planSelect research methods based on those questions and plan activities before the project planning decision.
- 3. Explore needs and possible directionsUnderstand the target group’s situation and needs. Use qualitative research to explore why and quantitative research when it matters how common something is. Then develop ideas and concepts to investigate further.
- 4. Test ideas and conceptsWork with customers and users to understand what creates value, what works and what needs to change.
- 5. Prepare the decisionBring together findings, insights, open questions and risks into a recommendation: move forward, explore more, change direction or pause.
If important questions remain, teams can return to research or testing before the production decision.
Two situations where the approach is used
Situation 01
Exploring a need
The team combines existing knowledge with research involving teachers or pupils to understand which problems matter most before choosing a solution direction.
Situation 02
Testing a concept
The team tests assumptions and alternative concepts with customers or users. The findings help them choose a direction, improve the solution or decide not to invest further.
Practical tools for discovery
To help teams use the new approach, I built a resource bank with 18 practical tools: AI supports, guides, a template and workshop material.
The resources support teams throughout research, from initial questions to findings, insights and recommendations. CX is responsible for keeping them accessible and up to date.
The research flow, step by step
From the decisions ahead to insight: the steps a team goes through in every CX/UX research effort, each one with its own method support.
- Gather existing knowledge and identify what remains uncertain.
- Formulate and prioritise research questions for upcoming decisions.
- Choose methods based on those questions.
- Define the target group and recruit participants.
- Prepare interview questions, test tasks and materials.
- Conduct the research and collect data.
- Analyse and synthesiseTranscripts → observations → findings → core insights → opportunity areas → remaining uncertainties
Resources are organised by where teams are in the research process.
- Plan before project planningUse existing knowledge to formulate questions, choose methods and plan research. 5 resources.
- Carry out CX/UX researchSupport for the research brief, interviews, concept tests, usability tests and surveys. 11 resources.
- Analyse and synthesiseTurn collected material into findings, insights and opportunity areas. 1 resource.
- Share and use insightsConnect what the team has learned to decisions and recommendations. 1 resource.
Four types of support – 18 resources
10 resources
AI supports
Ready-made prompts that help teams formulate questions, prepare research and analyse material.
6 resources
Guides
Step-by-step guidance for research activities.
1 resource
Template
A shared research brief completed by the team.
1 resource
Workshop resource
Support for working through questions and choices together.
Easier access to the right participants
The third part of the work is a shared customer panel, which is still being developed.
Its purpose is to make recruitment easier and coordinate contact with customers and users.
Faster recruitment
Less time spent finding participants for interviews, surveys and tests.
A better match
Clear criteria help teams find people with the right experiences and needs.
Less duplicated work
Coordinated recruitment reduces overlapping contact with the same customer groups.
Better customer relationships
A shared overview helps keep contact coordinated and considerate.
Project teams define who they need to speak to and why. CX and the customer panel will support participant selection, contact and coordination.
Intended outcome
Less time between identifying a research need and completing the research.
Bringing discovery into product development
I connected discovery to Liber’s existing product development process, defining what teams should do in each phase, which decisions the research should inform and which tools could support them.
When is new CX/UX research needed?
When an important question about customers or users could affect product direction, quality or an upcoming decision.
Know what needs to be explored before the project starts
- What do we know?
- What remains uncertain?
- Formulate research questions
- Choose methods
- Plan activities
- Planning decision
We moved important research questions earlier in the process. Before the planning decision, teams needed a clear picture of what was known, what remained uncertain and which research activities were needed.
Activities
- WorkshopCompile existing customer knowledgeBring together earlier insights and identify gaps relevant to the decision.
- GuideAI supportFormulate and prioritise questionsDefine what the team needs to learn and why.
- AI supportWorkshopGet support with questions and methodsTurn uncertainties into clear research questions.
- GuideAI supportRecommend a methodChoose methods based on the knowledge needed.
- Plan activitiesInclude research in the project plan.
- Bring research into the decision materialShow existing knowledge, questions and planned activities.
Carry out, synthesise and use the research
- Conduct research
- Document observations
- Analyse and synthesise
- Identify insights and opportunity areas
- Assess remaining uncertainties
- Connect findings to choices
- Make a recommendation
Teams conduct research, analyse findings and use them to inform their next decisions. Plans can change as new questions emerge.
Before the research
- TemplateWrite the research briefPurpose, questions, target group, methods, responsibilities and practical requirements.
- Plan the activityCoordinate timing with the project plan.
- Recruit participants or send the surveyFollow the shared recruitment process.
- GuideAI supportPrepare questions and test tasksWrite neutral questions and relevant tasks.
- GuidePrepare materialsGet the concept, prototype or other test material ready.
During the research
- GuideQualitative researchInterviews, observations, concept tests and usability tests.
- Quantitative researchSurveys or other structured data collection.
After the research
- GuideAI supportDocument observationsCapture evidence-based observations that can be traced to their source.
- Save knowledgeDocument quality-assured observations in the insight portal.
- GuideAnalyse and synthesiseIdentify findings, patterns, insights, opportunity areas and remaining uncertainties.
Connect findings to decisions
- GuideAssess the implicationsExplain how insights affect the available choices.
- GuideAssess remaining uncertaintiesIdentify what still needs exploring before making a recommendation.
Test and improve before launch
- Production decision
- What still needs to be understood or validated?
- Plan
- Carry out
- Analyse
- Improve the solution
- Launch
During development, research helps teams investigate remaining questions, test solutions and identify problems while they can still be addressed.
What matters in this phase
- GuideChoose the methodStart with the questions or quality requirements.
- Time it rightRun research early enough to inform development.
- GuideTurn findings into improvementsConnect research to changes and priorities.
Using the same support as during planning
- TemplateGuideAI supportPrepare, carry out and documentResearch brief, recruitment, questions, test materials, research and documentation.
Learn from real use
- Launch
- Observe actual use
- Gather feedback
- Evaluate
- Improve
After launch, teams can combine customer feedback, usage data and earlier research to understand how the product works in practice and what needs improving.
What matters in this phase
- Identify signalsNPS, the insight portal, customer support, sales, product data, usage data and earlier research.
- Assess the need for deeper understandingDecide whether further CX/UX research is needed.
- GuidePlan the follow-upChoose the method and approach.
- Turn findings into improvementsUse what the team learns to inform changes and priorities.
Using the same support as during planning
- TemplateGuideAI supportPrepare and carry outPlanning, recruitment, questions, materials and research.
GuideAI supportTemplateWorkshop Resource labels indicate which guides, AI supports, templates and workshops support each activity.
Impact and next steps
The five pilots showed how customer insights could support more informed product decisions.
In some projects, the findings confirmed the direction teams were already considering. In others, they led to changes in future product strategy.
The pilots also helped us test and refine the approach around what teams actually needed.
Approved and introduced across product development
After the pilots, I presented the approach and a proposal for the next steps to Liber’s management team.
They approved it, and the new approach was introduced across the product development department.
The next step is to make it a natural part of everyday work. Four priorities going forward:
- 1. Use the approach in upcoming projectsLet product decisions, existing knowledge and open questions guide the research.
- 2. Clarify responsibilities and everyday supportCX owns the methods, quality and guidance. Product teams are responsible for what they need to learn and how insights inform decisions.
- 3. Continue building the customer panelIncrease participation in priority target groups and make it faster to reach the right people.
- 4. Make customer knowledge easier to reuseCreate a shared structure for documenting, finding and using observations, findings and core insights.
What the work achieved
Liber gained a shared discovery approach, tested and refined in five ongoing projects, with practical method support and management approval.
The longer-term effects on product quality, efficiency and customer outcomes still need to be measured as the approach becomes part of everyday work.
“Thank you, Mikaela, for helping us at Liber raise our skills in customer insight work! You’re a star!”
“What a fantastic job you’ve done at Liber! So inspiring to read about everything you’ve achieved and the development you’ve contributed to. It’s been so much fun, and I’ve learnt so much, working with you!”
“Thank you for an outstanding job with us!”