CREATE SAFE USABLE MEDICAL DEVICE SOLUTIONS


Driven by close collaboration between design and development

Close collaboration between design and development – before, during and after the UX/UI design – greatly increases the likelihood that the UX/UI will be effective, can be implemented within the constraints of the device, and will meet business objectives and regulatory requirements while truly satisfying end users.

MedAcuity has been helping clients develop truly innovative highly usable safe medical device interfaces for over a decade. Collaborating with our UX design partner, Fathom Consulting, we came up with a number of ‘battle-tested’ tips for your next UX/UI development effort. Check them out below under Key Takeaways.

fathom consulting logo

let us help you develop effective user interfaces

Fill out the form below and someone from our team will be in touch.


KEY TAKEAWAYS


DESIGN & DEVELOPMENT COLLABORATION BEST PRACTICES

  • Tools & Technologies

    Invest in tools and technologies that enable and facilitate collaboration between people and teams

  • Avoid Inefficiencies

    Maintain collaboration between teams throughout the development lifecycle to avoid inefficiencies and rework that results from teams working in isolation

  • Sort Out & Rescope

    Take time to sort out and rescope efforts as design challenges are identified during implementation

  • Design Tool Collaboration

    Intent and rationale of UX design is better conveyed through design tool collaboration, not solely specification

  • Organizational Mindset

    Close collaboration between design and development becomes second nature when it is an organizational mindset evangelized from the top

KEY TAKEAWAYS


PROTOTYPING AND USER TESTING FOR MAXIMUM POSITIVE IMPACT

  • Formative Testing

    Use formative testing with prototypes to get feedback from test subjects to determine what’s working and what isn’t

  • Start Prototyping – Early

    Start prototyping as early as possible – get essential feedback on designs before development resources have been committed to design

  • Proof-of-Concept Prototypes

    Focus software effort on proof-of-concept prototypes where there are questions and implementation risks (feasibility, resource concerns, etc.)

  • Don't…

    Don’t implement software to test design

  • Design Tools

    Use collaborative design tools such as InVision, Sketch and Figma to allow for fast prototyping and “real” experiences to yield better user feedback