Assume that, you are working as a Head of Product in Platforms Strategy in HealthTop Digital Company in Boston, which is a complex healthcare platform that delivers integrated health services to patients and has various patient-doctor interactions which are automated with self-service encouraged at every opportunity, providing more timely care access and treatments with insurance fully-integrated for cashless automated service of insurance purchase & claim management.
The platform is for customers who are willing to buy health insurance & it is for doctors and they don't pay - but when patients come (and patients have come, loads!) then the doctors do get reimbursed through insurance companies. The revenue is that little slither for each reimbursable consultation. So in effect, the service has value.
The company has remote sales rep team who use the CRM platform to manage customers and help in on-boarding doctors on Hubspot.
The company has already performed some tests whether it would be worthwhile building it and if there is market/demand for it and discovered there was.
They have put together a series of third party software together to deliver a "patched-up service” that the platform would ultimately provide, and built an integration layer on top to make the transitions seamless.
Even with this integration layer, because they are currently relying on these multiple third party software, their clinician user experience is terrible—as the customers(clinicians) have to sign into 4 different tools during on boarding, and have to use these 4 tools during a consultation.
Now you have two options:
To incorporate some of these third party tools' functions into their integration layer so that clinicians have a better experience using their software, with the goal of ultimately having just one (our) software tool to do everything they do - which becomes part of our USP.
OR
Continue to improve on the integration layer so we can 'plug-and-play' into better third party tools such that clinician experience over time improves, and that integration layer becomes part of our USP.
Here are a few details about the company
Platform current journey
Data retention from/to 3rd party tools
Use own database to store data and pass it over to hubspot for different user types.
Mailchimp is used for email campaigns
Major payment modes and users
Customer pay when buying insurance. Business earns commissions set from range of 10-20%
Doctors get paid when customers turn into patients. Business earns commission on claims from range of 5%-25%
Sales rep get paid from business commission 2-4%
Technology company uses now
CRM - Hubspot
Marketing - Mailchimp, Hubspot
Engineering - nodejs, mysql, java, AWS Web Services, Php, Javascript
3rd Party Insurance Companies APIs
Website - Webflow
Your practice
Which approach is better? And why? What are some examples of one vs another?
How would you plan out the approach you choose (you can set & list the assumptions that lead you to the approach)
Which teams should you connect or need to get this project off-the-ground and rolled out?
Based on the plan you choose do the Spec-writing. It should include
Objectives
Success metrics to track
Assumptions
Requirements
Acceptance Criteria
Design the UX for all user types
Build out Sprints for team
Build a Roll-out plan
Feedback on the assignment in the form of retrospective which should contain
What went well during different phases of the project?
What needs improvement? (you can gather collective feedback from the discussion groups)
Action points to remember or Key takeaways
Tools recommended to use (any other tool can be used)
Trello or Jira for Add, Delete, Edit Tickets for Engineering
Notion/Google Docs for note taking and planning
Confluence/Google Docs/Google Sheets for Requirement gathering, manuals and other documentations
Figma/Miro for UX flow
Jira/Google Sheets to make gantt chart
You can use this to submit your practice, I can review and connect with you to help
Comments