Performance, Speed, is probably the most important feature a system can have. It creates the impression of quality, responsiveness, friendliness and effectiveness. Whereas slow performance will do the exact opposite. It will make people feel that the system is mean, low quality and ineffective.
Case in point: DirecTV
I have had DirecTV for over 15 years. Mainly, I use it rather than cable because I can watch the Jets games in California. (NFL Sunday Ticket) Lately, in the past year, I have noticed the performance has degraded substantially. I click “guide” and it takes 5-10 seconds for the guide to appear. I click UP and it takes another 5 seconds to go up. I want to whiz through the channels to decide what I want, not watch a frozen screen.
Every click on the remote is agony. I can’t stand it. It is ridiculous. It should be instantaneous. What is the point of having this gigantic set-top box if it can’t hold one damn guide in memory? Why is it so slow?
I actually decided to call support and they told me to send it back and they would give me a new receiver. Sounds great in theory, except the new one is acting funky too. Not as bad, but still pretty awful. What can I do? I hate DirecTV because of this. Combine that issue with the lack of fast internet access like cable has and all of the sudden, I am a customer in jeopardy.
Speed solves many problems and slowness causes many others. It happens because priorities do not put speed above other concerns. DirecTV actually changed their UI recently to add in fancy features. Did these features slow things down? If yes, then they fucked up in a serious way.
Features are great, but speed is greater. I’d rather have the old UI be ugly than the new UI be slow. I wish more engineering organizations thought this way. Do you work on features or on speed? I think too many companies out there answer the wrong way.