Skip to main content
Logan Leiter

Approach

How I take the work on.

Every engagement, whether it is a survey, a queue, or a system that just went live, gets the same pass. If we cannot answer these, we are not ready to design a workflow.

01

Feedback that does not change the week

Problem
The survey comes back, the detractors are real, and nothing in the operation is required to move.
Approach
A listening system and a closed loop: owners, a clock, a dashboard, and a review leadership will not skip.
Outcome
Feedback has an owner. Unhappy customers get a follow-up. The score is no longer the end of the story.

02

Slow replies after a system goes live

Problem
Quotes, email, and order confirmations slip because the old path and the new path are both half-true.
Approach
Name the few intervals that matter, set a first-reply target, and make aging visible in the system of record.
Outcome
Responsiveness becomes a managed interval with an owner, not a complaint that surfaces in a meeting.

03

No front door

Problem
Requests arrive everywhere. Routing depends on who you know. Key accounts are handled as a hallway exception.
Approach
A common door for transactional demand, a written exception for key accounts, and a front-line role shaped around that rule.
Outcome
Fewer orphaned requests, and a model that can take more volume without being reinvented.

04

Tools that do not match the work

Problem
The signal lives in a survey tool, the follow-up lives in a board, and the service request lives in an inbox.
Approach
Build the missing joints: a review dashboard, a survey-to-task path, and a portal or procurement connection with a definition of done.
Outcome
The Tuesday view matches the work people are actually doing.

Operating rules

What I will not drop

  1. Every significant request enters through a defined channel with an owner. Ambiguity is not a queueing strategy.
  2. The week has a cadence: the review, the 1:1, the cross-functional sync. Each one ends with a written outcome.
  3. What good looks like is agreed before the build.
  4. Escalation is written down.
  5. The work closes with a retrospective. That is a requirement, not a celebration.

What I optimize for

Preferences that change the work

  • Cause over symptom

    A slow reply is often a missing owner or a system that does not match the path. Fix that before adding headcount to the queue.

  • Repeatable over impressive

    A workflow should get cheaper every time it runs. A one-off save is how next year’s fire drill gets scheduled.

  • Visible over asserted

    If we cannot see aging, response rate, or the detractor list, we do not get to say the program is working.

  • Honest numbers over round ones

    If I haven't measured it, I won't put a number on it.

Bring a problem

Tell me where customers are waiting.

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.