Free up time for work that creates value.

What takes time away from essential work – and what do successful teams do differently? With Operations 360, you can find obstacles, build on effective practices and choose improvements to routines, systems and support.

Two colleagues reviewing business information on a tablet

OPERATIONS 360

You see the results. The potential lies in everyday work.

Reports show how the business is doing. People doing the work can help reveal what needs to change: obstacles to remove, practices others could use and opportunities to free up time.

What is holding the team back?

See where unclear routines, inadequate support or conflicting requirements make work harder.

You can decide on: Support, working conditions or practices that need to change.

How do we free up time for work that creates value?

See what you can simplify, coordinate or stop doing to make more time for work that makes the biggest difference.

You can decide on: Tasks to simplify, coordinate, remove or automate – and their order.

Which ways of working are most effective – and how can more teams use them?

Understand what successful teams do and what others need to work in the same way.

You can decide on: Practices to share and support for wider adoption.

Which improvements would make the biggest difference?

Build on employees’ ideas and prioritize the next steps: simpler routines, clearer responsibilities, better systems or AI where it adds value.

You can decide on: Priority initiatives, ownership and follow-up measures.

AI INTERVIEWS IN PRACTICE

What takes time away from the work that matters?

A business with several locations wants to free up time from administration and give its teams better support. Follow a local manager’s AI interview, compare perspectives and see the evidence it provides for the next step.

Fictional example · Operations 360

The question starts it. The follow-up adds context.

A question about reporting starts a deeper conversation. The AI interviewer follows up on the answer and asks for concrete examples from everyday work.

Speaking

Topic 1 of 3

Everyday reporting

Tell me about the last time you prepared the weekly reports. How did you go about it?

Eight perspectives on how work gets done.

Reporting requirements, systems and authority affect the time managers have for their teams. Connecting eight perspectives can reveal how problems relate and where to start.

  1. Processes and procedures

    Where does duplicate work, waiting or unnecessary handover occur?

  2. Time and resources

    What takes capacity away from the work that creates the most value?

  3. Systems, data and AI

    Where could better information, systems or AI make work simpler?

  4. Reporting and governance

    Which requirements and controls help the business – and which create friction?

  5. Responsibilities and authority

    Who can make decisions, and where does responsibility get stuck between roles or functions?

  6. Leadership and culture

    What helps or prevents managers from giving their teams the support they need?

  7. The employee journey

    How do onboarding, learning, support and development work over time?

  8. Improvement and innovation

    Which ideas and working practices should you test, share or develop?

ILLUSTRATIVE EXAMPLE

When administration takes time away from the business.

A business with several locations wants to free up time from administration and give its teams better support.

What needs to change to free up time and put improvements into practice?

A possible connection to investigate
  1. Requirements create duplicate work.

    Different functions request similar information in different templates.

  2. Systems work takes time from the business.

    Teams move data manually. We explore what could be simpler and where AI could help.

  3. Team support gets pushed aside.

    Managers have too little time for support, onboarding and feedback.

  4. Ideas for improvement get stuck.

    The team has suggestions, but there is no clear owner with authority to take them forward.

From everyday experience to your next decisions.

WHAT YOU TAKE AWAY

From everyday experience to your next decisions.

A consolidated analysis and leadership review clarify strengths, obstacles and possible improvements. See what you can act on and what needs further investigation.

  1. Where you are strong

    What works and is worth building on or sharing.

  2. Where the potential lies

    Opportunities for improvement and the evidence behind them.

  3. What to do first

    Prioritized recommendations and concrete first steps to test.

  1. A shared picture of operations

    Strengths, reported obstacles and important differences across roles, teams and locations.

  2. Possible explanations and connections

    Testable explanations, dependencies and differing perspectives. We check them against additional sources.

  3. Improvements to prioritize

    Actions to consider based on potential value, feasibility, risk and uncertainty.

  4. A practical action plan

    Recommended first decisions and experiments, with responsibilities and measures for follow-up.

WHAT YOU TAKE AWAY

From people’s experiences to clear next steps.

We put people’s experiences in your business context. You receive analysis, recommendations and help prioritizing what to change, test or investigate further. The engagement is shaped around your question.

Illustrated decision brief · Operations 360

Why does reporting take time away from the team?

The same symptom can have several causes.

Operational map

Reporting viewed through eight areas.

Processes and procedures
Similar information in several templates
Time and resources
Less time to support the team
Systems, data and AI
Manual work in two systems
Reporting and governance
Different periods and information needs
Responsibilities and authority
Unclear authority to coordinate requirements
Leadership and culture
Time for feedback needs investigation
The employee journey
Onboarding had to be postponed
Improvement and innovation
A suggestion for a shared template

A proposal to test

One shared reporting template.

Coordinated requirements could reduce duplicate work and free up time for the team while retaining the information needed for oversight.

Check the evidence
Review reporting requirements, manual steps and time spent with more local managers, finance and operations.
Start with a small test
Try a shared routine and template in two locations before deciding whether to introduce it more widely.
Assign an owner
Leadership appoints a process owner with authority to coordinate finance and operations.
Follow up
Compare time spent, information quality and time for team support before and during the test.
One of the voices · Local manager A
“The figures were almost the same, but the reporting periods and templates were different.”
Back to the interview
Two directions to explore
  1. Coordinate requirements

    Similar information is requested in different templates and reporting periods. Explore what could be simpler and who has authority to decide.

  2. Simplify data handling

    Map the manual steps and test which systems or AI support could help. Track both time spent and quality.

From connections to a first test.

If the evidence supports the hypothesis, start with a pilot in two locations. Track time spent, information quality and the support the team receives.

  • Remove

    Remove duplicate reporting steps that add no value of their own.

  • Simplify

    Coordinate reporting requirements. Give the improvement an owner and clear authority.

  • Automate

    Test AI support for consolidation and review the quality.

  • Develop

    Use time freed up for presence, onboarding and feedback.

  1. A clearer view of the problem

    We compare experiences and highlight patterns, differences and concrete examples.

  2. Analysis in your context

    Together, we assess what the findings mean for your business and what needs further investigation.

  3. Recommendations you can act on

    You get help prioritizing actions and a joint review of the conclusions.

The question, scope, deliverables and price are agreed before work begins.

Read about security and privacy
When the next step is practice

If the findings show that your team needs to develop a skill, we can help with practice and personal feedback.

Explore practice with Journeys

ILLUSTRATIVE EXAMPLE

What works may already exist in your business.

A business wants to free up time for customers. Asking about an unusually good week can reveal a practice that could help others.

A conversation about what works
  1. AI interviewer

    Tell me about a week with more customer meetings. What was different?

  2. Account manager

    A colleague’s follow-up template meant I didn’t have to write from scratch. I had more time for customers.

  3. AI interviewer

    What would make that possible more often?

  4. Account manager

    Giving everyone access to templates they can adapt to each customer.

AN OPPORTUNITY TO EXPLORE

An effective practice exists. How could more people benefit?

Evidence for your next decision

  1. Compare experiences

    Compare more locations’ experiences with time spent and customer experiences.

  2. Choose what to test

    Test shared templates and AI drafts reviewed by the employee.

  3. Follow what changes

    Track time, quality and customer experience before wider use.

A FOCUSED ENGAGEMENT

Start where the need is greatest.

Start with a single role or function. Add perspectives when needed to answer your question.

One critical role

Understand everyday work for local managers, account managers or specialists, for example.

One function or region

Compare working practices and conditions across teams, roles or locations.

Several business areas

Explore connections across functions that affect the organization as a whole.

Does the change work for the people using it?

A new system, routine or offer is in place. Listen to customers and employees to see what works, where things get stuck and what needs adjusting.

How does change meet everyday work?

Completing a launch does not tell you how the change works in practice. People’s experience helps you see what you need to understand better.

Why is the new way of working not being used?

Understand what is unclear, difficult to put into practice or poorly suited to the situations employees encounter.

Why does it work in some locations?

Compare experience and local conditions. Capture what helps the change work and what gets in the way.

How does the new offer work with customers?

Listen to customers and employees. See which questions, misunderstandings or practical obstacles the launch has raised.

What should we understand before the next rollout?

Build on experiences and ideas from a pilot or previous initiative. Identify what needs adapting before you move forward.

An illustrative engagement

Launched does not mean adopted.

An organisation has launched a shared booking procedure. Some locations use it, while others continue as before.

The question we start with

What makes the new procedure work in one location but not another?

What we explore

  • How do employees understand its purpose and what they are expected to do?
  • What happens when a customer request does not fit the planned procedure?
  • Which support and local conditions differ?
What do we need to check before choosing an action?

Explore the explanation

A procedure going unused may not indicate resistance. It may not work for certain customer requests or with the current systems.

Keep the exceptions

Compare locations where the procedure works with those where it gets stuck. Find out what can be shared and what needs local adaptation.

Follow the next attempt

Try an adjustment in one area. Listen for what changes and consider those experiences alongside your own business measures.

Possible next steps

  • Adjust the procedure where it does not work in real situations.

  • Clarify responsibilities and give the team the support it lacks.

  • Adapt onboarding and practice before the next stage of the rollout.

Understand what needs adjusting.

We put people’s experience in context and help you decide how to take the change forward.

In-depth interviews that add context.

AI interviews make it possible to listen to experience from more roles and locations. Follow-up questions help participants describe what actually happens when the change meets everyday work.

How Studies works
  1. A clearer view of implementation

    See how the change is understood and used in everyday work, where it works and where it gets stuck.

  2. Explanations to work with

    Distinguish unclear expectations from practical obstacles and skills needs. Assess differences across locations and roles.

  3. Recommendations for the next step

    Decide what needs adapting in the solution, rollout or support. Prioritise what to try and follow up.

The question, scope, deliverables and price are agreed before work begins.

Security and privacy

Questions about the engagement

Good to know before you start.

Does the change have to be implemented already?

No. We can explore conditions before a rollout, experience from a pilot or how an implemented change works. The question and participants are chosen to fit your stage.

Can we compare locations or roles?

Yes, when the approach and evidence support it. We plan which perspectives are needed and make clear what the comparisons can tell you. Differences in experience need interpreting in context.

Can you show the impact of the change?

Studies helps you understand people’s experience and possible explanations for what you see. The evidence can be considered alongside your business measures. Interviews alone do not establish that a change caused a particular result.

Do we also need Journeys?

No. Studies can be a standalone research engagement. If the next step is practice, you can choose a separate program with Journeys. Evidence and content are reviewed and approved before use; nothing is transferred or published automatically.

How do we get started?

Tell us about the change you are working on and what you need to understand. We define the question, relevant participants and deliverables that will help you move forward. Scope and price are agreed before work begins.

Questions about Studies

Good to know before you begin.

Which questions can you help us answer?

We help you understand how customers experience your business, what the team hears in customer interactions and what employees need to thrive and succeed. We also explore ideas, effective ways of working and experiences of change. Your question determines whose voices you need and how the analysis can help you move forward.

What do we take away?

You get a clearer view of what affects your business, a consolidated analysis and recommendations to consider. We review the conclusions together and help you prioritize what to change, test or investigate further.

How do we get started and what does it cost?

We start with your question and the decision you need to make. We then agree on a focused engagement with clear scope, deliverables and price before work begins.

Do we also need Journeys?

No. Studies can be used independently for customer insights, operational improvement or capturing practical expertise. If you want to create training, you select and review the evidence to use in Knowledge or a Journey and approve the content. Nothing is transferred or published automatically.

How do AI interviews differ from a survey?

Participants speak in their own words, and the interviewer can ask for clarification and concrete examples. This adds context to the response. We combine interviews with quantitative surveys when the study needs to explore both people’s experiences and how responses are distributed.

Can customers and external partners take part?

Yes. You can invite both internal members and external contacts using personal links. Explain the purpose, what you want participants to discuss and how their responses will be used.

Can we use multiple languages?

Yes. Choose and review the language versions before publishing the interview. The report can be produced in a selected language. Check important wording and quotes in context.

How do anonymised responses work?

You choose identity settings before inviting people. Anonymised results hide direct identifiers and raw transcripts. Summaries and reviewed quotes may still contain recognisable details, and contact information may remain in the invitation list. Review both the design and access settings before promising participants anonymity.

Do we need to review the AI analysis?

Yes. AI can miss nuance or draw conclusions that go too far. Review findings, quotes and differences between responses. Where transcripts are available, they can support checking; they are not available in anonymised results and are subject to retention rules. Your sample and business knowledge remain essential to the decision.

A first conversation

What would help work run better in your business?

Tell us what takes time or holds work back. We help you define the question and choose a scope that fits your needs.

Talk about your questionClose the form

Popscale AB uses your details to handle your request and get back to you. This form is not a newsletter sign-up. Questions about your personal data?