Hacker News new | ask | show | jobs
by watwatinthewat 2509 days ago
I work at a Navy research center. We don't try to be profitable but take DoD clients to cover costs, trying to break even yearly. The point there is we are mission or tax funded but work for customers.

The projects in my department take customer data, process/develop it in some way, and push it back out. Since we don't deal with the display at the end, there is a constant push for slides, demos, etc., from management to help sell it.

Hacked up demos by non-ui software engineers then became the product, and we have million dollar contracts coming for a mobile app and something that works in the browser.

The center's selling point is it's way cheaper than a private company or contractor, so subcontracting a UI designer isn't an option. I'm sure we'll have a working product, but it will probably be something like you describe. We shouldn't have taken it on, but when someone with money says, "I love it! How much?" it's hard to say no.

This is not an uncommon situation.

2 comments

If they are going to own mission critical software they need to have a UX budget. The buyer has to pay for UX or they shouldn't expect to get anything but afterthoughts. If fact one could argue that a UX package should be the spec in an RFP.

It would be VERY cheap to invest in training procurement teams in how to buy and own effective software, especially in light of the billions that get wasted when they can't articulate their needs to the point that a vendor can't be successful.

There isn't really room for iteration and continual feedback on a warship. It has to be done right the first time then maintain stability in every conceivable scenario and reduce the need for ongoing training after updates.

From what I have read, a major source of error is lack of sleep. With 4 hours of sleep, it doesn’t matter what the UI/X is...
UI/UX does matter, actually, especially on 4 hours of sleep. It is much easier to get confused with a complex interface on less sleep than more.
I don't disagree, but reading the following paragraph: "The report provides a detailed overview of the actions that led to the collision: when crew members tried to split throttle and steering control between consoles, they lost control of the ship, putting it into the path of the tanker." you're hard pressed to blame either lack of sleep or touch interfaces. It's quite obvious in this case there's an extreme lack of QA, no?