What I Notice
Short observations from inside real operations.
Sometimes the biggest opportunity is hiding in something everyone has learned to tolerate. Each note covers one pattern I keep seeing: what it is, why it happens, what it may be costing and what I would look at first.
What I Notice #01
Your support problem may not actually begin in Support.
Support teams absorb demand created upstream. Here is how to tell whether your support problem is a support problem at all.
Read the insightWhat I Notice #02
If five people need a meeting just to know what's happening, you may have a visibility problem — not a meeting problem.
Status meetings usually exist because the state of the work is not visible anywhere else. Fix the visibility and the meeting stops being necessary.
Read the insightWhat I Notice #03
Automating a bad process can simply give you a faster bad process.
Automation preserves the assumptions of the workflow it encodes. Redesign the work first, then automate what genuinely repeats.
Read the insightWhat I Notice #04
If escalation depends on knowing the right person, tribal knowledge may be doing the job of process.
Escalation built on relationships works until the right people are unavailable. Explicit criteria and decision rights make it durable.
Read the insightWhat I Notice #05
Your best AI opportunity may be hiding inside work employees stopped complaining about years ago.
Tolerated work generates no escalation, so it never reaches a roadmap — which is exactly why it is often the strongest automation candidate.
Read the insightWhat I Notice #06
The problem may not be the handoff. It may be how many handoffs you've accepted as normal.
Individual handoffs look reasonable. Counted end to end, they often explain most of the elapsed time in a workflow.
Read the insightWhat I Notice #07
Your highest-performing employees may also be your most expensive workaround.
When strong performers hold the process together, the system looks healthier than it is — and the risk sits with individuals.
Read the insightWhat I Notice #08
Sometimes a support ticket is actually a process defect wearing a different name.
Categorizing tickets by symptom hides their origin. Classify by cause and the recurring defects become visible.
Read the insightWhat I Notice #09
If employees spend more time finding context than acting on it, technology may be creating work instead of removing it.
Every additional system adds a place to look. Past a point, the tooling produces more searching than it saves.
Read the insightWhat I Notice #10
Before buying another platform, ask what problem the existing platforms were supposed to solve.
New tooling replatforms the current workflow, including its gaps. Confirm the constraint is the tool before replacing it.
Read the insightWant another set of eyes on it?
You don’t have to know what’s broken before you call me. Finding it is part of what you hire me to do.