13 ms·
Can I Talk to that William Fellow? He was so Helpful (2009)
- zitterbewegung 10y agoI wonder if there was a reason for taking the call? Possibly to see some aspect of support calls by doing it?
- 67726e 10y agoWell TFA says he was on a guided tour, so I imagine he wanted to get a better sense of what the support folks have to go through. We do something similar at work, where you can do a "ride along" to get a better idea of what folks using our internal tools needs are.
- XaspR8d 10y agoIt was also a very useful employee relations move: Bill wasn't "above" the task of a customer support call and demonstrated respect for the support workers by performing his best in their role, even if very temporarily.
- tjr 10y agoI wonder if Bill wouldn't have happily fielded the second call from that customer too, had he been asked.
- nxc18 10y agoI think its interesting to see real-world customers and how they use software. Being in university, I get to see a whole range of people. You realize that people don't really have a robust mental model of how their computer works or how the software they use is structured. Then we 'computer people' wonder why they struggle with our software. There are so many times I'll watch someone go through a laborious process to find a google doc, despite having seen a link to it on their screen at least 4 or 5 times. Or I'll see them go to the search bar, type in google, then start their search. Or go to the file menu rather than use shortcuts (every. single. time.). Or use tabs to manually center things rather than use the center button. Even relatively advanced users will completely miss the existence of styles in Docs & Office. And all of these are just the basics. We really do need to make software easier/more intuitive.
- Klathmon 10y agoI'm running out of people to do it with, but I love taking someone in the company who has never used, read about, or even seen a program and setting aside some time and just handing it to them and saying "do x". It's such a massive help in finding what can be confusing, what requires industry knowledge, what is easy for a developer vs a user, etc... It's so often that we as developers take some knowledge for granted, and helping the user either get that knowledge, or not need it is monumentally helpful. Sadly, I've found that once they do that, they are "tainted" and can't really do it again as well with that product, so it's something I try to do as late in the process as possible. But it has been what prompted me to throw out an entire redesign for a screen and start over very late in the process, and to good effect. I'm seriously afraid our usability will suffer when we run out of people to do this with.
- InitialLastName 10y agoInterns are a great solution to the "running out of new, untainted eyes" problem.
- lb1lf 10y ago-I do this from time to time to test one-off service/support docs prior to shipping them off to my customers. (I work in the marine industry; when a customer has a problem, he's often way out on the high seas, outside of even helicopter range - so, effectively, if whatever issue he's facing cannot be solved with what he's already got on board and some detailed instructions, he's SOL.) After breaking down the solution (hopefully, we're able to isolate the problem!), I bring all the required hardware, software, scripts and my first draft for the solution document to someone Not Into Automation & Control(tm) - say, the cafeteria or cleaning staff and ask them to work their way through it. It never ceases to amaze me how many things we just take for granted after working in a field for a few years. ("Oh, but surely it is self-evident that..." "F--k no, it isn't!") Result: Someone not at all involved in the day-to-day management of our products feel a much stronger attachment to the company and what we do to stay in existence; a customer gets a procedure which is so detailed, they can have anyone do it; I get to sleep well as I know the tasks sent offshore are as detailed and correct as I can possibly make them - and everybody is better off. At least I like to think so.
- fourthark 10y agoComment lower down remembers that the staff suggested it. And William did not perform so well.
- deleted 10y ago[deleted]
- ceejayoz 10y agoI've seen the CEO of https://en.wikipedia.org/wiki/Wegmans https://en.wikipedia.org/wiki/Wegmans ($7B grocery store chain) in the Pittsford Wegmans parking lot picking up trash all by himself (no photo op). He drives a Ferrari in.
- zlynx 10y agoI don't know what you do for a primary job, but don't you get a feeling of refreshment and accomplishment from doing something different now and then? Especially when you can see actual progress and improvement instead of going to meetings and reading summary and analysis documents all day. For example, I'm a programmer, but every now and then I open up and clean the office coffee machine, or mop up a spill in the break room. This isn't what I'm being paid for but doing a good job at it makes me happy, and NOT doing it would be being a jerk.
- hashhar 10y agoWow, I think you have written down what makes me not want to go into management (I've just graduated). The feeling of "seeing"/"measuring" impact (either code churn or shipping or affecting people) is a very good and satisfying one. I also think the satisfaction factor is different for different people but that is what eventually people call "Job Satisfaction" and is a very important thing in the long run. Without satisfaction I don't think someone will be able to do the same job (maybe at the same place) for his/her life.
- bostonpete 10y agoI don't see how a role in management is at odds with job satisfaction. You mentioned you just graduated -- maybe your impression of management is based on the caricature that tends to be portrayed in pop culture? As a manager, I feel like I am able to see a (hopefully positive) impact of the work I do -- impact both on customers/users and on the members of my team.
- hashhar 10y ago
- emiliobumachar 10y agoA chance to catch something obviously wrong that gets in the way of the workers but that they lack the power to fix. Big companies sometimes drop the ball. No grunt complains to the face of the CEO. Apparently he missed one such thing by sheer bad luck. From the comments: "Bill queried the knowledge base, which was normally painfully slow, but this time it was snappy and responsive."
- mathattack 10y agoThis is a best practice amongst many high performing organizations. Engineers who intuitively understand how their products are being used become much better designers. Similarly, managers get to understand the real pain of their customers.
- deleted 10y ago[deleted]
- devoply 10y agoBelievable but at the same time might be just marketing, especially the last part. Call me cynical.
- brudgers 10y agoThe story is consistent with Joel Spolsy's first person account of Bill Gates: https://www.joelonsoftware.com/2006/06/16/my-first-billg-review/ https://www.joelonsoftware.com/2006/06/16/my-first-billg-rev...
- djsumdog 10y agoUgh, the guy who discourages people from working on side projects because of potential contract violations?
- alangou 10y agoI would say that's a misreading of his intent - informing developers about the contract law governing their employment is to help people not get burned at a later date because they were iffy about the details of this or that clause. Of course, being informed about it may very well discourage some people from pursuing side projects. But then this comes down to whether you'd rather have developers continue with their side projects oblivious to the potential consequences of doing so.
- djsumdog 10y agoThat's what I thought too. Especially since the story mentions the username "billg." Wait, so did he log out the support person and then log himself in before taking the call? I mean it's possible, but it's also possible it's just a nice story.
- spudlyo 10y ago"Okay, let me see if William is available." The product support engineer brings up the customer's service record and looks at the name of the support engineer who handled the earlier call: billg. Those details were fictionalized by the author. Everyone who wasn't actively on a call at the time new all about Bill's call, because we were all standing around my cube when it happened. Not long after the call was over our entire team knew all about the call, what the issue was, and how Bill handled it. If I recall it was about an obscure linker error message.
- leggomylibro 10y agoThis sort of thing is a very helpful exercise - to any of you who manage developers that work on anything customer-facing, consider setting up a day for them to spend fielding customer support contacts for your product. It's amazing how myopic you can get after working on a product for awhile. The time spent in contact with ordinary users who are reporting issues helps to bring you back to reality: how do users typically user the product, what common edge cases do you fail to consider, what are common pain points in the UI, etc.
- RangerScience 10y agoThis. I went from engineering to sales (solutions architect, woo!) for almost two years. Amazing experience, and one of the best and most informative parts was actually getting hands-on with the people who use the product. Get a much better idea of what matters, what doesn't, and why.
- HeyLaughingBoy 10y agoYup. Same reason the medical instrumentation company I worked for used to try to get developers to shadow medical lab techs for a day. The things we as developers thought were important were often completely irrelevant to our end users and vice versa.
- tomjen3 10y agoI answer second level support. I hate doing it, but it is true that we get to see some of the things that confuses our customers. Plus it is therapeutic, you are never going to feel like you will look stupid to a support person again.
- makmanalp 10y agoAt KAYAK we had these red phones that would ring loudly until someone picked them up, and some technical worker would have to answer it and solve a customer's problem. This was controversial to say the least, for many reasons, but it was also extremely educational to see the misconceptions or worries or troubles that people had about the product you create. I enjoyed these even as a backend developer - often a problem or annoyance that manifests as a very surface-level thing to someone has deep code/architectural implications, and it grounded us to the people we were building things for, instead of striving for the perfect internals and architecture in la-la land.
- StreamBright 10y agoJeff Bezos does the same, also if you are working on one of the retail teams you are encouraged to take support calls once a year.
- Twirrim 10y agoThere's a bunch of tools that Amazon customer service reps have, and procedures, that have come directly out of Jeff doing customer support work every now and then, e.g. the Andon Cord (any customer service rep can pull any item from sale worldwide, instantly, through the andon cord process, from which a team of dedicated staff evaluate the product and why the cord was pulled). http://www.shmula.com/customer-service-andon-cord-jeff-bezos-and-customer-experience/10901/ http://www.shmula.com/customer-service-andon-cord-jeff-bezos...
- hguant 10y agoI believe this was pioneered by Toyota - any one on the floor could flag that there was a problem with production or an inefficiency on the floor, and work would stop until a lasting solution was found. EDIT - Wikipedia has more detail. Apparently the main reasons workers pulled the cord were "missing parts, safety issues, tool malfunctions and defects found/created." https://en.wikipedia.org/wiki/Andon_(manufacturing) https://en.wikipedia.org/wiki/Andon_(manufacturing)
- hkmurakami 10y agoYeah it's one of the first things they tell you about in factory training. And they definitely emphasize pulling the cord (or pressing the button, depending on the line you're on) if in doubt at all.
- Twirrim 10y agoAbsolutely, Jeff nods to Toyota when he talks about the cords origins.
- thefalcon 10y agoAt Blizzard, Mike Morhaime came and answered support tickets as a Game Master for a day. The next day, several terrible policies disappeared.
- caseysoftware 10y agoWhile I was at Twilio (mid-2011, through late 2013), every new employee was required to respond to 20 tickets regardless of role. It may have been a hold over from when we were really small but I always thought it was a great reminder that at the other end of that API were people building real projects that might make or break their company, teach them something new, or might be having a bad day that you can help just a little.
- pizzacowboy 10y agoI like that. We do something semi-similar at Optimizely, where we have all go-to-market employees walk through the ticket answering process with our Technical Support Engineers. Makes the customer demands feel very real, and gives other parts of the org ideas for discrete improvements.
- 3131s 10y agoAutomattic does something similar too: "When you join full-time, you’ll do customer support for WordPress.com for your first three weeks and spend a week in support annually, for evermore, regardless of your position" https://automattic.com/work-with-us/ https://automattic.com/work-with-us/
- animex 10y agoI spend a few days in the support trenches now and then to see what our agents were commonly facing when dealing with clients. One such day, it became apparent that most calls were investigating credit card charges since we're a SaaS that powers many sites. Watching the CSRs navigate through an ugly and slow transaction search screen made it painfully obvious we need to re-tool that for them. Within days we had a much faster db query and more flexible search parameters that helped them quickly find transactions. I'd often poll the CSRs for new feature requests and look for common threads. A small % increase in efficiency over many reps adds up to alot of $$$s saved and customer satisfaction.
- phil21 10y agoMy largest frustration with technology and specifically software developers is that they don't exist to code but most in the field seem to forget that simple fact. They exist to solve real world problems for people, using software as a tool. I don't know how anyone can possibly do that even if they don't actively engage their user base and proactively solve workflow issues the end-users may not even know are technically possible. Very frustrating to watch entire teams spend years on internal corporate business logic apps and never even once spend time with the teams consuming them. The results are always entirely predictable.
- pyb 10y agoThe problem is that in many companies, sadly, the management do everything they can to isolate developers from their users.
- cableshaft 10y agoYep. I get told what to do by BA's at this company (I've had more direct interaction at some previous companies). I'm not allowed to talk with the users of the apps we make. I just get told what needs to get changed here by others. Presumably they're the ones going through that process.
- ersii 10y ago
- fiatjaf 10y agoThat reminds me of that other episode in which Bill Gates sends an email to some Microsoft people about his failure to find information and run some program in his Windows machine, saying that everything was horribly difficult and obscure.
- noblethrasher 10y agoThe rant was about the difficulty of buying and installing Windows MovieMaker: http://blog.seattlepi.com/microsoft/2008/06/24/full-text-an-epic-bill-gates-e-mail-rant/ http://blog.seattlepi.com/microsoft/2008/06/24/full-text-an-... Funnily enough, I just shared this with a friend two days ago.
- phonon 10y agohttp://antitrust.slated.org/www.iowaconsumercase.org/011607/7000/PX07199.pdf http://antitrust.slated.org/www.iowaconsumercase.org/011607/... Scroll to the bottom :-)
- colanderman 10y ago"So they told me that using the download page to download something was not something they anticipate" This is comedy gold. What boggles my mind is, there are lots of people who have good usability taste. But so many software vendors seem to have no-one with taste in a position to do anything about it as their priority. Hence so many crappy UIs…
- wwalser 10y agoThe delta between the ability to identify that something is poorly designed (taste) and the ability to create a well designed version of a system is immense. The problem isn't that people with taste aren't in positions capable of effecting change. The problem is that design is very very hard.
- deleted 10y ago[deleted]
- 10y ago
- stinkytaco 10y agoPhone support is hard. I did it as a full-time job for about 18 months and still do it regularly as part of my job now. Trying to convince someone who is frustrated, confused, angry or just obstinate to work with you is it's own skill. They are your eyes, ears and hands and it takes a lot more than just being good with the technology, you have to be good at support.
- stephengillie 10y agoIf you can take the person aside and ask them in the right way, they can tell you everything about what's not working - both what is blocking them today, and also the smaller problems that have been haunting them for a while. The first part is to try to learn from them - how do they normally use the system, what isn't working today, and any errors that are (or aren't) showing up. The hard part in this is in actually wanting to help the person and/or solve the problem, and not getting caught up in your own superior ability to avoid the problem. The first step to good troubleshooting is checking your own ego at the door.
- lovemenot 10y agoSomething feels a bit off about this story. At the end, the customer is said to exclaim - oh my god, that was Bill Gates! At the end of 1989, Microsoft was not as famous as it later became. MS/DOS was just one of several competing DOSs in a much smaller market. And DOS was their main product. I doubt that even amongst most MS customers there'd have been name recognition for Bill Gates, let alone such reverence.
- kschua 10y agoI was thinking along that line too! I have only really heard of Bill Gates after Windows 3.1 came out
- THE_PUN_STOPS 10y agoIt does seem a bit apocryphal, but I think that's okay if you take the story as more of a learning parable than an account of facts.
- lovemenot 10y agoI agree to the extent that is not also hagiography. Unfortunately, cult of Bill / Steve etc. does tend to become dominant.
- vram22 10y agoWhat other DOSs? I know of DR-DOS, but not any others. Also, not sure, but I think MS-DOS was the biggest from pretty soon after it was created. I'm not even sure that DOS was their main product (though it was a big one). I had read the book Le Noveaux Magiciens, about Microsoft, and though I don't remember the chronology now, IIRC, language products were also big for them, like BASICs for various platforms. They even had an MS-C (used it for a product) and MS-Pascal and MS-Lisp. Could be wrong about languages being big earners for them, though.
- lovemenot 10y agoThere were a few : https://en.m.wikipedia.org/wiki/Timeline_of_DOS_operating_systems https://en.m.wikipedia.org/wiki/Timeline_of_DOS_operating_sy... I recall Amstrad in UK had its own DOS in the early 1990s. They had to declare MS compatibility, which supports your view of MS already being dominant. I also don't remember much before 1989, but I believe the languages business was earlier and more niche. Ever read Gates' 1976 rant about hobbyists ripping him off? https://en.m.wikipedia.org/wiki/Open_Letter_to_Hobbyists https://en.m.wikipedia.org/wiki/Open_Letter_to_Hobbyists
- drwl 10y agoIs this so surprising? Kevin Hale, YC partner, talks about how it was implemented at his startup Wufoo with interesting results about how it drove engineering to improve the product. On his Stanford lecture video for those who are interested.
- bananaboy 10y agoI worked for some friends a long time ago doing traffic control plan software (at http://www.invarion.com/ http://www.invarion.com/). We were a startup, three of us in the office, that's it, so when customers would phone one of us would have to talk them. A lot of the customers were not super technical, and I would have to answer questions about features that I had implemented, or bugs that I couldn't have imagined. It was illuminating, and gave me a new respect for developing software and really considering the end user and their needs and abilities.
- BillBohan 10y agoI met that guy. I was working for Tandy, repairing TRS-80 Model I circuit boards when he and his partner, Paul came to Tandy Apparatus with some engineers from Tandy R&D. They had the first masked ROMs for Level II BASIC. They put them on a board and tried it and it didn't work. I took the board I had just repaired and went to them and told them that they were in a repair area and all of the boards were in need of repair. I offered the board I had repaired and told them that it should be able to run their ROMs. They moved the ROMs to that board and powered it up. It came up with a MEMORY SIZE? prompt and William said to press enter. I did and it gave a READY prompt. I typed in a one-line program to print numbers and it started scrolling numbers down the screen. William was so happy that he offered me a job at his company. He said that he had about a dozen employees. For personal reasons I was unwilling to locate outside Texas and turned down his job offer.