4 ms·
Organizationally it’s challenging in a few ways. 1. From your perspective you’ve filed an issue that perfectly describes the problem. 90% of the time the engin
by vlovich123 4y ago
Organizationally it’s challenging in a few ways.
1. From your perspective you’ve filed an issue that perfectly describes the problem. 90% of the time the engineer doesn’t actually have enough information and needs follow up. 90% of that time the bug just isn’t actionable because it’s somehow reliant on the user’s configuration OR requires extra logging to be enabled that wasn’t.
2. There’s so many communication layers between you and where the ticket needs to get to to answer your question. That routing takes time. Apple has a big enough challenge managing this just from internal bug tickets.
3. Organizationally Apple is in a no win state. One engineer having a bad day and responding poorly on a ticket impacts their image and generates a news cycle. So now every response needs to be filtered through someone who’s only job is to manage public engineer comms. This is a low value spend for Apple.
4. Some responses might be something like “this will be fixed next release “. Culturally that kind of response would be an anathema at Apple because of the secrecy.
5. Point 4 interacts with point 1 - they don’t want engineers talking in random environments to customers (WWDC is a very controlled environment, the engineers get some training, and it happens just after they’ve announced most things for the year so the opportunity for accidental leaks is smaller).
6. Engineers have a fuckton of responsibilities already. You have to screen a bunch of bugs, develop new software on insane timelines, manage tech debt, keep up with internal trainings, etc.
Could they do a better job? Are there cultural things at Apple that inhibit these things? Yes. I’m sure Apple is trying to fix some of them. But some of these things are trade offs between how Apple chooses to run their business and there aren’t easy answers (if there were these problems wouldn’t exist).
On a personal note, as someone who’s managing a fraction of the volume some of their products get and trying to stay very involved with the community, it’s extremely distracting and demoralizing at times (some users can be very entitled to the point that they’re a distraction and taking away value from the community outreach that’s happening).
- soco 4y agoIs you comment directed at Apple or applies to every company doing support? Because I can have good support - and I had - from others, just never from big names, Apple or whatever. So sorry, I don't buy it. Good customer service can obviously be done, if the company cares about it, and Apple just doesn't care. Or Google. Or Facebook.
- harpiaharpyja 4y agoThis is just a thought experiment, but if we replaced each of the "big names" with a collection of smaller companies would we be able to get the same level of innovation? I think so. I believe it's being good at something that makes a company grow, not the other way around. Just looking for an answer to all those comments asking if the problem is tractable.
- soco 4y agoI also don't see what's innovation to do with customer support. Are you trying to say that one can only be innovative when offering shitty customer support? Or that the innovation IS the shitty customer support? I'm confused.
- harpiaharpyja 4y agoIt's a bad choice of words, replace it with the objective function of your choice.
- manmal 4y agoI think you are mistaking B2C feedback with feedback from developers, who Apple relies on to make apps and provide exactly that kind of feedback. Whenever I talk to an Apple employee on Twitter about a bug I’ve found, they tell me to file a Feedback. At WWDC, we are also often told to file any unexpected behavior and feature requests as Feedbacks.
- vlovich123 4y agoNo I’m not. Developers often offer only marginally better feedback which you can observe if you’ve ever triaged bug reports within Apple or elsewhere. You individually may do a fine job but in aggregate you have many of the same problems.