The situation
Quotes, first replies, and order confirmations have a visible target the team can manage.
Worked the post-go-live responsiveness problem — quotes, email, and order confirmations — and gave those intervals a target the operation can manage.
The situation
Quotes, first replies, and order confirmations have a visible target the team can manage.
What I found
Quotes, first replies, and order confirmations were slow enough that customers said so before the queue was visible.
What was in the way
A new system does not repair a fuzzy process. Requests still arrived in several inboxes. Aging was not in one place. The old path and the new path were both half-true.
What I did
Named the three intervals that matter, set a visible reply target, consolidated orphaned inboxes, and put backlog and quoting rate in front of the people who own the work.
A platform decision is an operating decision. After go-live, quote turnaround, email replies, and order confirmations tell you whether the new system is actually how work moves.
Summary
Customer-facing work had grown up across tools and workarounds. After a core system went live, the practical test was responsiveness. The work was to name the intervals, set a visible reply target, and put aging where the people who own the queue can see it.
Customer-related work had evolved across multiple tools. That showed up as inconsistent handling, inconsistent capture, and reporting that was difficult to standardize.
The platform work was treated as an operating-model decision: the system should support the business, not digitize the old workaround.
Qualitative
Quote turnaround got a visible target and a view of aging.
Qualitative
First replies moved to a managed interval instead of whenever someone noticed.
Qualitative
I set a first-reply target with the team so "faster" had a definition.
Goal-setting for responsiveness, including a first-reply target.
Backlog age, quoting rate, and request status in one place.
Where requests entered, and the path they should use instead.
This work sits with CX audit and Go-live is when the customer starts measuring you.
Bring a problem
A short note is enough: what is breaking, what you have already tried, and what a good month would look like. If I am the wrong person, I will say so.