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.
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.

OPERATIONS 360
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.
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.
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.
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.
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
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.

Speaking
Topic 1 of 3
Tell me about the last time you prepared the weekly reports. How did you go about it?
Two of the three example interviews describe recurring reporting and less time for everyday support. The support office highlights that the information is needed, but requirements may be poorly coordinated. Review reporting requirements, data flows and time spent before drawing conclusions about causes.
“The figures were almost the same, but the reporting periods and templates were different.”
Describes similar reporting in different formats.
“When we collect the same information several times, there is less time for feedback and support for new colleagues.”
Connects administration with less time for the team.
“We need information for follow-up, but I do not know which information the other functions already ask for.”
Highlights the need for information and better coordination.
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.
Where does duplicate work, waiting or unnecessary handover occur?
What takes capacity away from the work that creates the most value?
Where could better information, systems or AI make work simpler?
Which requirements and controls help the business – and which create friction?
Who can make decisions, and where does responsibility get stuck between roles or functions?
What helps or prevents managers from giving their teams the support they need?
How do onboarding, learning, support and development work over time?
Which ideas and working practices should you test, share or develop?
ILLUSTRATIVE EXAMPLE
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?
Different functions request similar information in different templates.
Teams move data manually. We explore what could be simpler and where AI could help.
Managers have too little time for support, onboarding and feedback.
The team has suggestions, but there is no clear owner with authority to take them forward.
WHAT YOU TAKE AWAY
A consolidated analysis and leadership review clarify strengths, obstacles and possible improvements. See what you can act on and what needs further investigation.
What works and is worth building on or sharing.
Opportunities for improvement and the evidence behind them.
Prioritized recommendations and concrete first steps to test.
Strengths, reported obstacles and important differences across roles, teams and locations.
Testable explanations, dependencies and differing perspectives. We check them against additional sources.
Actions to consider based on potential value, feasibility, risk and uncertainty.
Recommended first decisions and experiments, with responsibilities and measures for follow-up.
WHAT YOU TAKE AWAY
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.
The same symptom can have several causes.
Reporting viewed through eight areas.
A proposal to test
Coordinated requirements could reduce duplicate work and free up time for the team while retaining the information needed for oversight.
“The figures were almost the same, but the reporting periods and templates were different.”Back to the interview
Similar information is requested in different templates and reporting periods. Explore what could be simpler and who has authority to decide.
Map the manual steps and test which systems or AI support could help. Track both time spent and quality.
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 duplicate reporting steps that add no value of their own.
Coordinate reporting requirements. Give the improvement an owner and clear authority.
Test AI support for consolidation and review the quality.
Use time freed up for presence, onboarding and feedback.
We compare experiences and highlight patterns, differences and concrete examples.
Together, we assess what the findings mean for your business and what needs further investigation.
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 privacyIf the findings show that your team needs to develop a skill, we can help with practice and personal feedback.
Explore practice with JourneysILLUSTRATIVE EXAMPLE
A business wants to free up time for customers. Asking about an unusually good week can reveal a practice that could help others.
AI interviewer
Tell me about a week with more customer meetings. What was different?
Account manager
A colleague’s follow-up template meant I didn’t have to write from scratch. I had more time for customers.
AI interviewer
What would make that possible more often?
Account manager
Giving everyone access to templates they can adapt to each customer.
AN OPPORTUNITY TO EXPLORE
Compare more locations’ experiences with time spent and customer experiences.
Test shared templates and AI drafts reviewed by the employee.
Track time, quality and customer experience before wider use.
A FOCUSED ENGAGEMENT
Start with a single role or function. Add perspectives when needed to answer your question.
Understand everyday work for local managers, account managers or specialists, for example.
Compare working practices and conditions across teams, roles or locations.
Explore connections across functions that affect the organization as a whole.
We handle Study design, collection, evidence review, analysis, recommendations and the leadership review.
We review the question, early patterns and preliminary analysis with you. The leadership review concludes with your priorities.
After a change, we can follow up with comparable questions and explain which comparisons the evidence supports. The question, scope, deliverables and price are agreed before work begins.
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.
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.
Understand what is unclear, difficult to put into practice or poorly suited to the situations employees encounter.
Compare experience and local conditions. Capture what helps the change work and what gets in the way.
Listen to customers and employees. See which questions, misunderstandings or practical obstacles the launch has raised.
Build on experiences and ideas from a pilot or previous initiative. Identify what needs adapting before you move forward.
An illustrative engagement
An organisation has launched a shared booking procedure. Some locations use it, while others continue as before.
The question we start with
A procedure going unused may not indicate resistance. It may not work for certain customer requests or with the current systems.
Compare locations where the procedure works with those where it gets stuck. Find out what can be shared and what needs local adaptation.
Try an adjustment in one area. Listen for what changes and consider those experiences alongside your own business measures.
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.
We put people’s experience in context and help you decide how to take the change forward.
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 worksSee how the change is understood and used in everyday work, where it works and where it gets stuck.
Distinguish unclear expectations from practical obstacles and skills needs. Assess differences across locations and roles.
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 privacyQuestions about the engagement
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
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
Tell us what takes time or holds work back. We help you define the question and choose a scope that fits your needs.