Start with the performance question you need to answer.

Prepare a review with real examples, find out why one team performs differently, make development plans specific or pass on a routine that works. Each starts with a question HR already has.

Prepare a review
Bring the employee’s example and the manager’s observation into the same meeting.
Explain a result
Ask the teams behind similar numbers what they did differently, and compare their accounts.
Pass on what works
Capture the steps and exceptions from the people who run a routine, then test it in a second team.

Explore the use cases

Give people something specific to work on.

Prepare employee development conversations with real work examples. Use employee and manager input to agree a practice goal, support and a check-in.

Explore the page

Choose the decision the conversation should inform

If the next step is a manager and employee meeting, start with performance review preparation or a development conversation. If you are trying to understand something that happens across teams, start with employee listening. If the work depends on experienced colleagues remembering what to do, start with knowledge transfer.

Define what you want to bring out of it

A review brief should bring examples and open questions into the meeting. A team debrief should make patterns and gaps visible. A handover resource should help someone carry out a particular task. Choosing the output first helps you decide who to include and which questions to ask.

Give the next step an owner

Name the person who can use the findings. A manager can agree a development action, a site lead can test a change to a handover, and a process owner can review a new guide. If several teams are involved, use the campaign workflow to coordinate scope, participation and review.

Questions that come up

Where should we start with Lontra?

Pick a question someone in the organization already needs to answer. A review cycle, a recurring operational issue or a handover coming up all give you a group to involve and a clear moment to use what they share.

What should I bring to a demo?

Bring the question, the people you would involve and the decision or meeting it should support. We can use that context to discuss the scope and a practical first campaign.

Can a first campaign involve more than one team?

Define which perspectives the question requires. If the problem sits between two teams, including both can be useful. Agree how the group will review what comes back before widening the scope.

Bring one performance question.

See the product on a question like yours, and what a first campaign could involve.

Book a demo