3 ms·
When I worked technical support for some big routers and switches we had very defined rules for various ticket priorities: P1 - Entire network is hard down, I
by duxup 4y ago
When I worked technical support for some big routers and switches we had very defined rules for various ticket priorities:
P1 - Entire network is hard down, I can straight up power cycle all your gear at will. Oh I can't? Not a P1...
And so on.
Obviously as Engineering manager things aren't as solid but having defined rules about "urgent" and so on really do help.
Our sales team used to have to fill out a form before they got their VP to start pulling chains. Way too often they'd get their VP calling everyone up demanding action and ... nobody would even have a point of contact with the customer. Like how urgent can it be if the customer doesn't want to work on it?
Solution was they filled out the form. VP "signed it" (digitally) and sent it to support. If I called that phone number for the customer contact and they didn't answer ... it was no longer urgent.
Sales VPs actually liked that process too.
The good thing was if it was urgent I had good contacts and data in front of me to ACT quickly.
- ajmurmann 4y agoThis is a lot harder with feature work. My team might be working on a new API that enables team A to build feature A. Now someone interested in feature B needs "just a small API change" to enable their feature B which "was promised to important customers to be available this month". It gets pretty fuzzy. Your idea of having some standard questions pre-answered is always helpful though. In this case that might be stuff like expected revenue. Of course in my example the person interested in feature B also needs a talking to for committing both fixed scope and fixed time externally (already bad) while not talking to all impacted parties ahead of time.