Live data from Hacker News

Why Enterprise Software Sucks

twitter.com

471–480 of 570 posts

Re: Why Enterprise Software Sucks

#471

I think this gets it wrong. The real reason enterprise software sucks is that enterprises have complex and unique workflows and would prefer to buy software that they can fit to their workflow rather than change the workflows of their profitable business with tens of thousands of staff who will need retraining. If you look at all of the most successful software of all time they are the complete antithesis of the Unix…

> prefer to buy software that they can fit to their workflow rather than change

Existing users' familiarity with existing tools and the ability to accomplish existing tasks with existing skills are all part of the competitive landscape for any tool that must compete for people who use it by choice. In other words, if the user chooses the tool, they will choose a tool that allows them to accomplish what is necessary, given their existing skills. That this choice is so often lacking is just a symptom of the reduction of individual agency in the modern corporation. There is no fundamental law preventing software from becoming more usable and more powerful over time.

In fact, for as often as enterprise procurement keeps old interfaces around longer than they should be, it is just as often responsible for replacing something that everyone knew how to use with something worse, rendering institutional knowledge worthless overnight.

> most successful software of all time

By what definition of success?

> People hate them because they are complex, configurable, and have 1000 features.

> But that's the same reason they can [meet the need.]

Good design is precisely about enabling complex work with well-chosen, simple yet powerful tools. Your statement implies or at least suggests that any tool that meets a complex set of business needs must be something people hate, which is equivalent to saying that well-designed tools cannot exist -- equivalent to giving up on design.

All the evidence shows us is that good design is rare, and much more so whenever tool users are not tool choosers.

If you believe good design is possible (as you suggest later, that it is just expensive) then what you're saying is simply that bad design is cheaper, and is the default outcome when good design is not valued, all of which is certainly true. However, you still have to explain why good design fails to thrive in the market, and why large numbers of people are using trash tools that everyone hates and no-one could ever love.

This may be explained by the principal-agent problem, by network effects, as in the case of platforms and productivity tools, by a lack of user awareness, or various other reasons, but simply saying that good design costs and doesn't happen by accident is not a sufficient explanation for what we see happening in the market. You might believe that the market is correct here, and good design simply isn't worth the cost, but it wasn't clear to me if that's your position.

> That the end user isn't the purchaser isn't going to change that fundamental reality that businesses are complicated.

The fundamental reality here is that good design will only be rewarded when the people who suffer from bad design are empowered to choose otherwise. As long as the cost of good design is borne by party A, while the pain of bad design is borne by party B, and party A pays for and chooses the tools, then bad design will continue to dominate.

Re: Why Enterprise Software Sucks

#472
post #192

Earlier quoted context omitted.

> Since when are Word, Excel [...] enterprise software? Since Word 1.0. Why do you think it is called Microsoft Office ? The 1989 edition of Microsoft Word cost $500, equivalent to over $1,000 today, for a single seat. That's not consumer software. Microsoft Home didn't exist until 1993, a decade into Office's life, when it had achieved complete enterprise dominance -- thanks largely to its competitors' failure to re…

>Why do you think it is called Microsoft Office? Some friendly fyi of MS history... Microsoft didn't use the "Office" branding until 1995. Before that, the computer industry called it "productivity software" instead of "enterprise software". In the 1990s, other software companies (like Borland and IBM) were bundling word processors + spreadsheets + presentations + databases into an "office suite" for a lower package…

Microsoft Office was first introduced for the Mac in 1989 and for Windows a year later.

Re: Why Enterprise Software Sucks

#473
post #401

Earlier quoted context omitted.

What did blackberry do so well in email?

Keyboard. Touch sucks for writing.

I can type so much faster with Swype-style typing. I completely don't understand the die-hard keyboardists

Re: Why Enterprise Software Sucks

#474

Earlier quoted context omitted.

> just give me ISO8601 dates, please; HackerNews, you, too! Strongly seconding. It's an annoying UX antipattern, especially as it loses precision over time ("28 minutes ago" is fine, but "yesterday" or "5 days ago" or - even worse - "2 years ago" is not; having the date specified to hours or minutes is actually useful, especially in context of a site with international audience). Doubly so on HN, which doesn't even b…

I prefer the HN method of 28 min, yesterday, 2 hours ago, etc... for HN. The older a comment or post, the less relevant it is to a particular discussion. This site is for real-time discussions of articles, so it is optimized for that use-case. The older a comment, the less relevant it is towards the immediate discussion. Thus, older comments have less precision, because those details don't matter for the discussion.…

ISO8601 date/time can easily be transformed into the fuzzy format HN uses, but not vice versa since the fuzzy format is lossy.

If HN sent dates to the client in ISO8601, the client could then transform that format into the format of their choosing with client-side javascript (either a userscript, or delivered to the user by HN.)

Re: Why Enterprise Software Sucks

#475

Earlier quoted context omitted.

And yet neither Android nor iPhone today as as good at doing email as Blackberry was 10 years ago. They do lots of other things a lot better, but email? Nope.

What did blackberry do so well in email?

Search. I could instantly search basically my entire inbox in 2005. That was the power of BES. I still can't do that today on Android or iOS. If I'm looking for an email from 6 months ago or last year it takes FOREVER to find.

Re: Why Enterprise Software Sucks

#476
post #401

Earlier quoted context omitted.

Keyboard. Touch sucks for writing.

I can type so much faster with Swype-style typing. I completely don't understand the die-hard keyboardists

I could touch type on blackberry far faster and more accurate than swype. Swype is better than nothing but it's not as good as the bb keyboard was.

Re: Why Enterprise Software Sucks

#477

Earlier quoted context omitted.

Shadow IT will always be created when the existing system or IT group can't or won't support the users' needs (imagined or not).

A good rule of thumb is, if you think your doesn't need Shadow IT, it means you're not already part of your company's Shadow IT circle.

that is a funny comment :) thank you.

Re: Why Enterprise Software Sucks

#478

I worked at a school that used the Frog VLE. There was a big push for us to use it for student assessment. I tried, I honestly did. 1. I used it to set homework assignments. 2. .py files were blocked and students couldn't upload them. 3. They submitted code as .txt instead. 4. I'd click on my class to view submissions, it showed the top 5 submissions. 5. I'd click on a submission and it would download. 6. I'd view th…

It's the same reason architects can't design biochemistry laboratories. And trust me, they're bad.

Re: Why Enterprise Software Sucks

#479
post #142

Earlier quoted context omitted.

A lot of SaaS businesses aren’t really SaaS, they’re glorified custom development shops with a few high paying customers. That’s not a great business to run though as it’s very difficult to scale. Far too many fall into the trap of saying yes to the first BigCo that comes by early on because they need the $$. While they neglect every other niche and business where it could fit like a glove. Or more often doesn’t even…

Are SaaS businesses really customizing for high paying customers? They may build new features which are then made available to other businesses but I would be surprised if there are separate source trees. The other issue is that a "great business" and "scale" are not synonymous. In fact many of the current batch of companies of great scale, like Slack, have spent enormous amounts of money to get there, and still lose…

That’s why I said they aren’t true SaaS companies. There are thousands you’ve never heard of in every major city with a few super niche customers.

And scaling beyond 2-3 real customers does make a very big difference for any legitimately good company.

Re: Why Enterprise Software Sucks

#480
post #197

Earlier quoted context omitted.

Enterprise software is a sub-class of business software. Enterprises often operate quite differently from SMBs. Public US companies will have things like SOX compliance. And, the enterprises offering up services, like email, may be competitors in another space. If you are competing with Google on phones do you want them to host your email? Likely not. The business world is complex. Some complex business software is f…

Excel is programming, it just doesn’t call itself that so people won’t get scared off.

I wanted to do everything in Excel lately, but it (at least 2013 that I'm stuck with) seems to be a horrible frankensteinian mishmash of features that don't work together. For instance, there almost seems to be the infrastructure for building a virtual database in a spreadsheet, but there are a million different things that trip you up, like the not-quite-integration of PowerPivot, the use of DAX instead of SQL, the missing VBA interface for crucial things. I still don't know why you can use OData from Excel, but then you add something to the data model and try to get to it from PowerPivot, and you don't have permissions for the exact same URL and then the whole thing gets corrupted.

Within Office, it seems more practical to do ambitious things with Access, although that has its issues too. I apparently completely corrupted a database I've been using just by pasting part of a SQL statement that was >= 1024 characters as part of a VBA script.

Post reply on HN