By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
Health Works CollectiveHealth Works CollectiveHealth Works Collective
  • Health
    • Mental Health
  • Policy and Law
    • Global Healthcare
    • Medical Ethics
  • Medical Innovations
  • News
  • Wellness
  • Tech
Search
© 2023 HealthWorks Collective. All Rights Reserved.
Reading: How Do You Decide What Features to Add to Your Software?
Share
Notification Show More
Font ResizerAa
Health Works CollectiveHealth Works Collective
Font ResizerAa
Search
Follow US
  • About
  • Contact
  • Privacy
© 2023 HealthWorks Collective. All Rights Reserved.
Health Works Collective > eHealth > How Do You Decide What Features to Add to Your Software?
eHealth

How Do You Decide What Features to Add to Your Software?

ShahidShah
ShahidShah
Share
4 Min Read
SHARE

 

Given the well-warranted focus on design these days it’s always difficult to find the right balance between features that we should add to our software and those that we leave out. I was running a class recently on how to build product roadmaps for health IT apps / medical device software and the question of how we should decide which features to add came up.

Here’s are just a few of the facets I talked about during that lecture:

 

More Read

negative physician reviews
Physicians and Negative Online Reviews: Think Before You Sue
Why Should a Healthcare Company Create Their Own App?
Digital Health and the Pharmacy: A Prescription for Success
The HealthCare Social Media Review – 28th Edition – Connectivity
Patient Privacy in a Modern Health Care Era: Google Hangout on Air

Given the well-warranted focus on design these days it’s always difficult to find the right balance between features that we should add to our software and those that we leave out. I was running a class recently on how to build product roadmaps for health IT apps / medical device software and the question of how we should decide which features to add came up.

Here’s are just a few of the facets I talked about during that lecture:

  • Will the new feature increase patient safety by a measurable amount?  This is really hard to measure but only because we rarely do risk management for individual features. Forcing to think about this would be important.
  • How many new clients would we sign because we had the feature? This is calculated in whatever way you define users but must be defensible. The sales team usually can help with this but needs input from others (marketing, training, etc).
  • What specific benefits will the users see because of the new feature? Be specific with clicks that might be removed, new business that they may win, money they might save, etc. This is a lot harder to quantify than it seems. If you can’t quantify the benefits, is it worth implementing? Why or why not?
  • Is the feature something our users require due to regulatory burden on their side? These include functionality like MU requirements, HIPAA, or CMS rules. If your customer has a regulatory burden that your product can handle, give it higher priority even if customers don’t ask for it specifically.
  • How much time (which resolves to money) will it save on implementation at our customer sites? This is calculated in minutes per client and must be defensible. Usually the IT team can compute this.
  • How much time (which resolves to money) will it save on training our users? This should be calculated in minutes per client and must be defensible. Usually the training team can compute this.
  • How much time (which resolves to money) will it save on tech or product support? This should be calculated in minutes per client and must be defensible. Usually the training team can compute this.
  • How much it would cost to develop, QA, and deploy the feature (the development team does this)?
  • What kind of positive press or other free PR might the feature create? This needs to be defensible, not just guesswork.
  • What is the risk of breaking things (side effects) for existing users or impacting existing training and knowledge at the clients that will increase support costs because of the new feature?

There are probably a million more considerations but very few of them are easily defensible with good metrics. What kinds of questions do you consider when thinking about new features for your health IT app? I’d love to get your thoughts on how you make such decisions, drop me a comment below.

TAGGED:HITsoftware
Share This Article
Facebook Copy Link Print
Share

Stay Connected

1.5kFollowersLike
4.5kFollowersFollow
2.8kFollowersPin
136kSubscribersSubscribe

Latest News

a woman walking on the hallway
6 Easy Healthcare Ways to Sit Less and Move More Every Day
Health
September 9, 2025
Clinical Expertise
Healthcare at a Crossroads: Why Leadership Matters More Than Ever
Global Healthcare
September 9, 2025
travel nurse in north carolina
Balancing Speed and Scope: Choosing the Nursing Degree That Fits Your Goals
Nursing
September 1, 2025
intimacy
How to Keep Intimacy Comfortable as You Age
Relationship and Lifestyle Senior Care
September 1, 2025

You Might also Like

Nuance PaperPort Goes to the Cloud

August 3, 2011
eHealthTechnology

Video: Driving Value With Technology Investments

May 27, 2012

Emcompassing Theory of Online Patient Diagnosticians Somewhat Overblown

January 16, 2013
share practice
eHealthMedical DevicesMobile HealthSocial Media

Crowdsourcing Doctors’ Insights on What Works Best

March 23, 2014
Subscribe
Subscribe to our newsletter to get our newest articles instantly!
Follow US
© 2008-2025 HealthWorks Collective. All Rights Reserved.
  • About
  • Contact
  • Privacy
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?