Nolte / Nolte Care · Jan 2018–Apr 2020
The work changed every time the client changed.
I led support operations and technical escalations across a portfolio that included WordPress, React, React Native, payment-connected systems, HubSpot, Jira Service Desk, and clients in very different industries.
Environment
- Web / application
- WordPress · React · React Native
- Operations
- HubSpot · Jira Service Desk
- Integrations
- Payment processors
- Client contexts
- Nonprofit · real estate · ecommerce · fitness · investing / financial
The job
Get oriented fast enough to be useful without pretending every system is the same.
At Nolte, the next escalation might come from a plant retailer, a New York real-estate business, a nonprofit, a fitness brand, or another client application with its own history and expectations. The job was not to memorize every environment. It was to enter a live system, establish what had changed, understand enough of the stack to narrow the issue, and keep ownership intact as developers or vendors became involved.
I coordinated developers, vendors, clients, Sales, and Marketing around issue triage, feasibility, resolution, and post-launch work. I also built SOPs, onboarding material, issue-tracking practices, and escalation habits so support knowledge did not disappear between clients or team members.
Selected client environments
Different businesses, different systems, same obligation to become useful quickly.
I worked closely with these organizations through Nolte / Nolte Care. The systems, business context, and support needs varied by engagement.
Ecommerce client platformWhat changed for me
Support became a portfolio-management problem as much as a troubleshooting problem.
Liquid Web had given me depth inside managed hosting. Nolte added range: different codebases, business models, stakeholders, support expectations, and delivery rhythms. The technical skill was still diagnosis, but the operating skill was context switching without dropping the thread.
That meant learning to enter systems I did not build, preserve the customer context while I learned them, and bring developers or vendors a narrower problem instead of a vague escalation.
What Nolte added
Range, client ownership, and a repeatable way into unfamiliar systems.
I learned to carry the support discipline from one environment into many without flattening the differences between them. That is still one of the things I am most comfortable doing.