23 May 2016
Unfortunately for America’s health care system, things haven’t been simple for a while. Providers face issues that cost time and money; consequently, the general population is adversely affected. Here are some (of many) obstacles that medical professionals confront regularly and ways we as designers and developers can help.
27 Apr 2016
Over the last few months, we’ve added Design Sprints to our toolbox; working through exercises to help us define problems, goals, and solutions. A design sprint can be used in any project but I’d like to specifically talk about how it can help with a legacy health care application.
4 Apr 2016
Over the years, we’ve had a number of product ideas. Here are five applications that never survived.
1 Apr 2016
Art, without distribution and discovery, moves nobody. Did it ever exist? Science, without clear explanation and advocacy, won’t be understood by the masses. Will it make an impact?
1 Mar 2016
Redesigning for digital health care will be a hurdle that we need to overcome. Here are just a few main points to show what’s at stake if we ignore or wait for someone else to figure it out.
8 Feb 2016
Don't forget the the middle-man in between you and the user. You know, the company behind the product? AKA your client? Their organization? To build a successful product, it’s just as important to get to know them for a lot of reasons.
12 Jan 2016
Our team recently sat down and started talking about some trends we think might pick up steam for 2016. The conversation ventured down another road, trends we wish would go away. While I would necessarily call these trends, this article points out a lot of nuisances that sites still make us go through, and we still deal with on a day-to-day basis. WHY!?! Make it stop!
8 Dec 2015
As a designer, asking that simple question, ‘why?’, is very critical to my job, and one I need to ask before I start anything. Why?
14 Oct 2015
A few weeks back I saw this article from Jared Spool in my twitter feed - and the timing was eerily perfect. We were in the midst of re-examining what it was we were doing for our client and why. The roadmap we had originally created had shifted and morphed and when all was said and done, there we were with a "map" but the idea of where we were going, our focus, got hazy. To most, it just looked like a bunch of feature changes.
Building a roadmap is challenging. You know the least amount you will know at the beginning, and that is when your team (and your client) want to know what it is you plan to do and how much will it take. Historically, we've tried different approaches to make this more efficient and realistic for us and our clients. But at the end of the day, roadmaps tend to just look like a big list of features, a bunch of "stuff" that we are going to do. In the background, it's all intentional and tied to the needs we've so far determined, but it doesn't make the picture clearer. The idea of identifying the themes to focus our discussion and solutions is one I'm willing to try. It may not be the only answer for roadmaps and project scope, but if anything - it's the place to start.
13 Jul 2015
The better we understand users, the better products and services we can create. User research is a critical, yet often overlooked step in the development process. Read on for a look at a few commonly held misconceptions about user research and learn why it's more more accessible for your project than you may think.
Have a project that needs help?