ronutz

The Roles · Who supports it

High-touch operations manager

Held this role - at a vendor, on national infrastructure accounts, 2003-2004

A named vendor engineer assigned to one large customer, holding their support relationship end to end. Where standard support answers whoever calls, a high-touch role knows the customer's environment, their change calendar and their people, and carries their cases through the vendor's organisation personally. The arrangement exists for customers whose outage is a public event.

What the day looks like

  • Holding the customer's open cases and knowing each one's actual state rather than its recorded state.
  • Convening the vendor's specialists on a fault that crosses several product areas.
  • Reviewing planned changes before they happen, which prevents more cases than any diagnostic skill.
  • Reporting to the customer's management in terms that connect engineering activity to service outcomes.
  • Carrying the customer's defect and feature positions into the vendor, with the weight the account justifies.

What it answers for

  • The customer's support experience as a whole, across every case and every product line.
  • Escalations reaching the right people at the right severity, early.
  • The accuracy of what the customer's management is told.

What it is measured on

  • Availability and incident outcomes on the account.
  • Case ageing and escalation counts.
  • Renewal of the support contract, and the account's willingness to act as a reference.

Who it receives from

Support and engineering
Case progress, defect status and release plans.
The customer
Change calendars, architecture decisions and early warning of pressure.
The account team
Commercial context that shapes what is possible.

Who it serves

The customer's operations and management
One person who knows the whole picture.
The vendor's support organisation
Context that turns a generic case into a specific one.
Product management
A large customer's requirements, evidenced.

Who else has a stake

  • The public, when the customer operates national infrastructure and the outage is felt outside the building.
  • The vendor's executive sponsors of the account.
  • Every engineer inside the vendor whose queue this role reaches into.

What it takes

  • Technical credibility across a portfolio, sufficient to convene specialists and follow them.
  • Organisational navigation: knowing who inside the vendor can actually move a thing.
  • Communication calibrated to the audience, from packet detail to a board summary in the same day.
  • The steadiness to hold a relationship through an incident and remain trusted afterwards.

What the job turns on

The visible work is incident response and the durable work is prevention, which produces quiet. A high-touch engagement that succeeds shows fewer escalations, calmer reviews and a customer who stops needing to phone — and every one of those reads as reduced activity. Making the prevented incident visible, in the reporting and in the review, is what keeps the arrangement funded and is as much part of the role as the diagnosis.

Where it leads

Roles that lead here

The work itself

The Practice covers how this work is done — triage, escalation, evidence, handover — across the whole corpus.

Read The Practice