Beta Product Definition @ Datu Health

Like the alpha version of this product, a Beta was intended provide a unique view of clinical and personal data, but build to the next level of personalization by providing a rules-driven experience based on a holistic user profile.

This effort started with a prioritization of capability and features, using industry knowledge, alpha user feedback and the existing strategic vision as our guide. Based on the anticipated functionality, my team got to work defining the business logic to deliver an experience determined by various combinations of user profile data. We also worked closely with our UX team to design the key interactions.

We consulted with our trusted clinical and operational subject matter experts on the content, timing and conditions for target populations at our Beta pilot sites. Following client review and approval, my team worked with development and product resources to translate our plain language logic into code. This amounted to an implementation of hundreds of triggers, conditions and actions that would enable a personalized user experience.

My primary role on this project was experience planning and client proxy. I partnered closely with the product manager and development team in order to prioritize the backlog and ensure the requirements of our user experience would be met. My approach to difficult conversations, where our scope, schedule and resources were in conflict, was to frame the discussion with “I’m hearing you say we cannot deliver X in this timeline. I know we cannot deliver Y and still have a quality experience. What are solutions that allow us to provide an acceptable user experience while staying on track for delivery?” This resulted in a very productive conversations with my colleagues, bringing us to a place of collaborative problem solving rather than a battle between the business and technical teams.