5 ms·
I've sometimes wondered why it seems companies aren't measuring time wasted by slow applications. I can't count the number of times I've called customer servic
by crazygringo 5y ago
I've sometimes wondered why it seems companies aren't measuring time wasted by slow applications.
I can't count the number of times I've called customer service and have to wait 2-3 minutes for the agent to bring up some screen as they apologize and explain "our systems are really slow". It regularly takes up a majority of the call's time.
Back in the early 1900's, time and motion studies [1] in factories were all the rage. And today Amazon certainly optimizes for the actions warehouse employees are required to do.
But when it comes to the actions people do with computers, I've never once seen a company actually measure wasted time waiting on slow applications. It seems like such an obvious thing to try to optimize. And it's not like it requires constant surveillance or anything -- it's just statistical sampling. Watch 10 randomly selected employees for two hours each or something, with their consent.
In many cases "good UX" is impossible to measure in any conventional sense. But when it comes to repeatable enterprise tasks, the time aspect actually can be measured.
Does anybody know why companies don't? It feels like such low-hanging fruit.
[1] https://en.wikipedia.org/wiki/Time_and_motion_study https://en.wikipedia.org/wiki/Time_and_motion_study
- georgewsinger 5y agoInteresting point.
- jrockway 5y ago> I've called customer service and have to wait 2-3 minutes for the agent to bring up some screen as they apologize and explain "our systems are really slow" I have a friend who works in a call center. They work 10 hour days with no breaks between calls (the queue is often 40-50 people deep). (They do get the federally-mandated breaks of course.) "Our systems are really slow" is 100% true, but is also probably a welcome break for the agent. So if you are the clever software engineer that goes in and removes the sleep(180s), that's probably great for a few hours until all the call center agents burn out and leave early and use their spare time to start organizing a union. (Of course, if you save 2 minutes a call with software, you can just give people a mandatory 1 minute break between calls and come out ahead -- a true win/win. But that would require that the software team and the call center management team coordinate, and I don't think that's ever happened once in the history of large companies. You'd be the first!)
- wjnc 5y agoPerhaps I’m totally going Euro but shouldn’t the MBA in charge at least try to measure employee happiness, churn and absence to try and measure if the work is fulfilling? I work at a large listed insurer and I know nobody shits on the hard work customer facing colleagues do. It’s hard work, with often old IT and usually customers outside of the fast track that have unique needs. Our senior management is motivated to help say once a year to keep a feeling for both customer and colleagues etc. I would split your point in two dimensions: 1. Software should support efficiency and speed. (We often fail at that.) 2. Tough jobs exist and it’s up to the employer to make them worthwhile and at the least prevent burn-out.
- dredmorbius 5y agoOften there's a lot of insight to be gained by reading what vendors and industry publications have to say on a topic. DDG suggests that this is a leading call centre industry publication. This is their article list: https://www.connectionsmagazine.com/articles/by-topic/ https://www.connectionsmagazine.com/articles/by-topic/ I've skimmed a couple of sections. There are a couple which look at workplace issues (career & self-improvement, workfroce management). Nothing jumps out immediately, but there might be some hints. Note that what you find in articles and practices on the ground ... may differ. Vendors advertising workforce-related systems and services (especially monitoring, tracking, recruiting, etc.), or legal / compliance organisations, could also give some possible insights. Overall, it's a low-wage, low-skill, but also low-hazard environment (no dangerous equipment, encounters, etc.). Much of it is outsourced to low-cost regions with many English speakers (Philippines, India, Mexican border towns, Florida, etc.). Alternative employment may be scarce, unemployment high. Change any of those dimensions and you might see conditions improve.
- gonzo41 5y agoIn contrast, look at AutoCad or Photoshop, and ArcGis. Mega complex ui's, what they do is more like programming than office productivity. So user workflow is going to be more difficult. I've worked on in a large bank doing sales with slow IT systems, (The Mainframe was awesome quick though, shout out to black screens!). The bank coached staff to use there tools in an order and structure their conversations so they'd have buffer for information and systems to be there when needed. Warehouse work is very repeatable compared to most work with a computer.
- specialist 5y agoI used to joke "AutoCAD is an 800lb angry gorilla sitting between you and your work." Then I met a UI researcher, hired by Army Corps of Engr to explain the missing productivity, who went way past time & motion to strategies. The interplay between tools and techniques, influencing how people organize their tasks. Matrices to highlight weird noun (line, circle, text) and verb (copy, move, delete) interactions. In other words, he showed how strategies from manually drafting did not translate to CAD and proposed new strategies (metaphors) and training appropriate for the new medium. Then validated his ideas with usability testing. Brilliant stuff. Like facepalm obvious once you see it. Crickets. Both Autodesk and Bentley Systems were hostile to user centric design based on real world data and lived experiences. The geeks and sales pukes who had never designed or drafted knew what designers and drafters needed, so piss off. Besides, they're printing money, validating their efforts. And you aren't. So piss off. Lather, rinse, repeat.
- bsder 5y ago> Both Autodesk and Bentley Systems were hostile to user centric design based on real world data and lived experiences. That's because customer support is the number #1 variable cost on that kind of software. If you change anything, you start absorbing customer support calls from your enterprise customers. This is how I knew that Microsoft doesn't carry support costs for Office and Windows--they rearrange GUIs willingly.
- specialist 5y ago
- LocalH 5y agoCall center metrics are all about average call length. However, the slowness of the software is largely ignored, in my experience. I worked at a call center once where logging in to the network would take approximately fifteen minutes, depending on workstation, before you could actually start working. They just didn't care. At this particular call center, average handle time was expected to be kept under 6 minutes. One day I had a very good average of under 5 minutes per call, and I received a single inbound call that required use of their translation service (which was a number with which you would dial and initiate a three-way call, and that would translate between you and the caller, with all the requisite delay between communications that one would imagine). That call ballooned into a 45-60 minute ordeal that totally screwed my handle time for the day. The shit cherry on top? The next day, I got bitched at because my handle time for the previous day was too high. When I said "well, that one call was a translator and took like an hour" the only response was "your handle time is too high, don't let it happen again". By the time another week had passed, I had already left the position. Call center jobs are largely exploitative and demeaning. Outsourcing customer service should be illegal, period.
- oblak 5y agoThere only two things I remember about my first day at a large telco. The one relevant to this topic was the call centre. I had never seen cubicles in real life before. Looked absolutely horrible even from the outside. What really made an impression on me, though, was the fact that they had this printed owl on the door. Immediately told everything I needed to know about the place
- princesse 5y agoI'm not familiar with the meaning of a printed owl on a door, why was that significant to you?
- b3morales 5y agoI've become a bit skeptical that the "loading, please wait" delays are real. It seems like they're often used for upselling me to some other product, while I'm just trying to get my current one fixed.
- kitsunesoba 5y agoSimilar observations could be made about jankiness/glitchiness in software. The amount of time burned on fighting misbehaving software has to astronomical, in some cases eclipsing the productivity brought by the features that dev energy was spent on instead of general stability and quality. Take Photoshop for instance. Just about anybody who spends even a moderate amount of time in it will tell you that even though it's become more capable in the past 15 years, it's also become a lot more frustrating and bug-ridden. Personally speaking, I would be just as if not more productive using something like Photoshop 7/CS1/CS2 than I would be with Photoshop CC.
- ant6n 5y agoI'm reading this comment because I task-switched away from VSCode which is hanging again. Waiting for glitchy software takes you out of the zone and makes it more likely to go to reddit/Twitter/hn and lose a lot more time than the glitch.