At Hospital IQ, we use input from various sources to inform how we develop our software platform — market research, competitive analysis, and feedback from users, among others. Our development timelines have always been rapid, even as we’ve grown and added additional layers of process over time. Even so, based on priorities, some requested features can take a relatively long time to be implemented, while others become stale or irrelevant as time progresses.

One feature I’d been waiting to see implemented for several months was deployed recently. The feature seemed like a no-brainer: an adjustment to spreadsheet exports from one of our bread-and-butter perioperative block utilization reports, to include the same real-time information seen on the screen at the time of export, rather than a laundry list of several dozen fields that were often opaque to client users outside Hospital IQ. I had heard complaints about these exports from multiple clients and was certain the change would be universally beneficial.

However, within a few days of the feature being deployed, I heard from multiple users asking “How can I get the ‘complete’ version of this export?” Apparently, users had come to rely on the old version of these exports to generate some of their deliverables, so for them what I saw as an “improvement” was anything but.

Fortunately, our team was able to quickly assess the feasibility and practicality of reintroducing the legacy version of these exports, while also retaining the new-and-improved version, and within a day we had deployed software offering both options. Now, we’re able to satisfy both the users who want to export what they see on the screen as well as the users who’ve come to rely on the longstanding laundry list.

This anecdote showcases some of the advantages of our robust-yet-nimble software development process:

  • Thoughtful short and long-term planning
  • Tight coordination between product management and engineering
  • Ability for quick turnaround on feature requests when appropriate

These advantages give us the ability to continue strategically building out our platform with features to help clients manage their operations and drive value, while tactically addressing feature requests when needed. Hospitals aren’t one-size fits all, so the value of closely listening to the customer base allows us to leverage needs and continually inform the ongoing development of a software platform. It’s a best-of-both-worlds scenario that allows us to consistently deliver client results, ultimately leading to better patient care.

Author