Quiet Gears
One customer question connects market activity with service delivery
A customer asks when their yacht will return to the water. The colleague handling the request checks the shared mailbox for the promised date, the job sheet for completed work, a supplier message for a delayed part and a colleague for the latest conversation with the rigger.
The team gives a careful answer, but the search starts again when the customer calls later in the week. The assembled answer does not leave the next colleague with a current view. Growth has increased the number of projects and the number of times staff repeat this work.
The engagement began with this customer question. The business test is whether any colleague can see the current commitment, understand what changed and know who acts next without rebuilding the story.
Decision testCan the business improve market follow-up and customer service while preserving the personal attention yacht customers expect?
Growing demand turns updates into a capacity problem
The business manages enquiries, returning customers, vessels, long projects, suppliers and follow-up with a small specialist team. The same people quote work, manage delivery and speak with customers. They know the boats and the customers well. That knowledge helps them solve problems, but it also makes each person a source that colleagues must consult.
Management first needed to know whether slow updates came from staff shortages, uncertain supplier dates or fragmented project information. A review of live projects showed that staff could state most facts, but had to gather them again for each request. Reducing repeated search and clarifying the next commitment became the first priorities. Automatic drafting offered little value until the answer itself was dependable.
Interruptions consume specialist time. A technician stops work to answer a question. A colleague pauses a quote to check an old message. A manager spends time assembling the weekly position. The business then absorbs slower replies, duplicated effort, late follow-up and reliance on the person who happens to remember the latest change.
Research on application switching and information search shows that this type of coordination cost affects many workplaces. The capacity issue has special force in marine services. A British Marine Scotland survey found skills gaps at 82 percent of responding businesses, with 58 percent expecting retirements within five years and 12 percent employing apprentices. The figures apply to Scotland and provide sector context. They do not predict the result for this company.Sources: Harvard Business Review, application-switching study, 2022, Microsoft, Work Trend Index: Will AI Fix Work?, 2023, British Marine Scotland, Economic Value of Boating Tourism in Scotland, 2023
Discovery showed that staff need dependable project context before they need faster drafting.
Management chose a shared project view
Management chose to protect scarce specialist time before expanding headcount or automating customer contact. The selected release brings the customer, vessel, enquiry and active project into one view. It shows the latest confirmed commitment, recent changes, the next action, the colleague responsible and the due date.
Staff will continue updating the tools they use now. The shared view brings the confirmed commitment and next action into one place, so the intervention does not add a second administrative task. A colleague resolves any uncertain customer or vessel match before staff rely on the view.
Staff will not use the initial release to predict completion dates or send messages. A colleague approves every customer reply. This limit keeps the work focused on finding the current answer and acting on it.
The company will introduce a small group of projects first. Each weekly review will compare response preparation time, late actions, message corrections and continued use of private files. Management can stop the release if coordination effort rises or customer care suffers.
The design now has clear business tests
Discovery has produced a shared definition of the customer journey, the minimum project information staff need and the rule that every open action has one identified colleague and due date. The team has also agreed the limits on customer communication. These design decisions are complete. Operating improvements remain unmeasured.
Live use has not shown faster replies, fewer late actions or lower coordination effort. Published projections about searchable company information also cannot supply those answers. Published estimates for customer-system failure range from 18 to 69 percent, so the company must use its internal measures.Sources: McKinsey Global Institute, The Social Economy, 2012, CIO, What to do when your CRM project fails, 2017
Before launch, the team will review a representative set of projects and measure sources consulted per status question, time spent preparing an accurate update, missing required details, duplicate customer or vessel matches, overdue actions and material corrections to customer messages.
Four weeks of live use will decide whether the shared view solves the customer problem.
Four weeks must show less coordination effort
The same project sample and review method will run again after four working weeks. The team will also compare use of the shared view with continued searches through email, job sheets and private files. Management will agree acceptance thresholds before launch.
Success means staff can answer sampled customer questions with fewer searches, every active project has an identified next action, overdue work falls within the agreed limit and customer-message corrections do not rise. Staff must achieve this without creating a separate maintenance task.
If the result meets those conditions, the company can consider connected documents, management reporting and limited drafting support. If staff still rebuild the answer, the team will fix matching, capture or screen design first. The four-week review will use the same customer questions that formed the baseline.
