We’re proud to announce that Deakin University’s non-invasive smart solution for blood glucose monitoring project will be the first recipient of our Design Aid program.
Does your software look like it belongs in the 90s? If it does, you’re not alone. Sure, maybe it still works. It's technically powerful. And there are loyal customers. But for years the design has been driven by developers and it shows.
5 years ago today, Marc, Ollie, Brett and I were hunched over our computers in Ollie's living room wondering what they hell we were doing. We had no clients, no website, we didn’t even have a name. Like everyone who starts a business, we had no idea if what we were doing would work.
Navy has come a long way since then, and we've got a new mission we're ready to share.
The problem we see is that e-health products are usually developed as technology projects rather than tools to support healthcare workers. If you’re creating an e-health product, consider these 5 design principles.
“The rule I teach my students, is: Do not solve the problem that’s asked of you. It’s almost always the wrong problem. Almost always when somebody comes to you with a problem, they’re really telling you the symptoms and the first and the most difficult part of design is to figure out what is really needed to get to the root of the issue and solve the correct problem.” - Don Norman
If you work in the tech industry, it’s easy to forget that older people exist. Most tech workers are really young, so it’s easy to see why most technology is designed for young people.
New research by Navy Design has highlighted poor design and usability as key contributing factors to the underwhelming performance of the Personally Controlled Electronic Health Record (PCEHR).
Testing with real users is a fundamental part of a good design process. But most usability labs are clinical, artificial and cold. Here are three things you can do to make your lab more like the real world.