Explore Mossy

Choose a first workflow your team can recognise

Start with an everyday request and trace it to a useful result.

All blog posts

Pick something that happened this week. A customer wanted to move an appointment, a tenant asked for a repair update, or a colleague spent an afternoon putting a briefing together. Write down the start and the outcome in plain language.

Follow the handover. Identify where the answer came from, who could make a commitment and which system needed the update. Ask what should happen if the answer is missing or the customer asks for a person. Give each exception an owner.

Test six examples before widening the scope. Include a routine request, a duplicate, missing information, an out-of-hours call, an exception and a request for a person. Ask the people who do the work whether the result would save them a step.

Observe the work before choosing it

Spend an hour with the people who receive requests, rather than starting with a list of tools. Ask them to show you the last three examples they dealt with. Look for the step where they reopened a conversation, searched for a detail or waited for someone else to decide. A frustrating step that happens twice a year may deserve a different fix from a quiet interruption that happens several times a day. Ask which one they would remove first and why.

Sort the examples by what has to be true before the work can proceed. A standard appointment might only require an available slot and a contact number. An exception may involve a fee, an accessibility request or a capacity decision. Start where the rules are fairly stable and the source of information has a clear owner. If two colleagues describe different rules, settle that disagreement before trying to encode either version.

Describe the smallest useful result

Imagine an incoming call to move a booking. Your first version could stop after capturing the old time, the requested time and the best number for a callback. That is useful if the duty manager currently has to play a voicemail repeatedly or ask the guest to repeat the details. A later version can check availability or update the diary once the team agrees when those actions are appropriate.

Write the result as something a colleague can see. For example, the duty manager receives one task with the booking reference, the proposed change and a reason it needs review. Add the circumstances that leave the original booking intact. Make the fallback just as clear as the normal path. A useful fallback could be a named callback with a time window the team can actually meet.

Run a review with the people receiving the work

Walk through the examples with the team before introducing them on a busy shift. Ask someone who did not help design the workflow to read an assigned task and explain what they would do next. Note where they need to open another system, make a guess or go back to the customer. That is often the fastest way to see that a field has been given the wrong priority or that a handover is missing a decision.

After the first week, compare a handful of outcomes with the old process. Look at whether people had to re-enter information, whether requests reached the right owner and whether customers received the promised follow-up. Keep a short list of improvements with one owner. Choose the next workflow only after the first one feels routine to the team using it.

Explore related Mossy features

Cookie preferences

Essential storage remembers your choices. Optional analytics measure site use.