11–20 of 204 posts
On the trip side, the car rental selector is something special. You can't check multiple vendors at once, so if cars are in demand, expect to spend a while discovering you can't get one.
And we can probably wager that a better UX doesn't yield the developer a better pay cheque.
So, future investors - look at the startups that address the user problems, not the client problems, even though the latter are paying.
As the author mentions. This was a failure on and down the chain, from QA to PMs. When I see software like this, it reeks to me of contractor work. We hire them to handle something that we don’t have time for our core team, and or something not very important. The result is the devs do a minimal job to get paid. QA doesn’t care and the PMs either didn’t see it, or have bigger fish to fry.
As the author mentions. This was a failure on and down the chain, from QA to PMs. When I see software like this, it reeks to me of contractor work. We hire them to handle something that we don’t have time for our core team, and or something not very important. The result is the devs do a minimal job to get paid. QA doesn’t care and the PMs either didn’t see it, or have bigger fish to fry.
That’s funny. I used to work for a high-end consulting company, and we always marveled at the level of dysfunction in our clients’ IT departments. They would call us in when their devs couldn’t/wouldn’t do the work. We were pretty expensive by comparison, but at least we got the job done. I guess it just depends on the kind of contractor you hire.
I will say that it does have good integration between the company card transactions and the expense reporting feature.
I am more mystified than the author at why my 75-mile range electric car offers a default sorted list by full street name, then by state, happily inquiring as to whether I intend to drive 225 miles to my entered street name before a matching entry that’s 4 miles away.
I found concur to mostly work for me. It’s kludgy for sure, but I always get paid and expenses handled fast. Sometimes within a day.
These kind of bad UX problem can be easier to rationalize once we understand the money flow. Would you stop using it because of such UX? Would your stopping cause the company to stop procuring SAP? Was the search the selling point in the first place when the sales representative pitch the software to finance department? Probably no, no and no. So are all other bad UXes. And we can probably wager that a better UX does…
The key thing about enterprise software is that it's never sold to end-users, it's sold to senior managers and executives. The contact that this group will have with the software is to approve transactions (e.g., Reqs, POs, Expense Claims, etc) and maybe view some reports. You can bet that these interactions are very streamlined.