Storysoft
WEB APPLICATION PLUS VEEVA SOFTWARE INTEGRATION
Storysoft’s Healthcare Representative Solution aims to help pharmaceutical companies keep healthcare providers (HCPs) engaged with branded content after meeting with a sales representative. This product provides a quick and easy way to share interactive and personalized content via QR code generation, directly from the rep’s device or through a virtual sales call.
Project Duration:
My Role:
My Partners:
the Problem and Ask
HCPs could be engaging
further after a sales call
So let's develop a visual interface for the existing tech
How might we…
Primary Questions
Details
Often after a pharmaceutical rep finishes up a sales call, they typically leave a business card and say "thanks for the time". When this happens, engagement between the brand and the healthcare provider comes to an end. With HCPs receiving thousands of contacts per year, pharmaceutical brands needed a way to keep HCPs engaged with personalized and interactive content to help stand out from the crowd.
When I was first brought onto the Healthcare Rep Solution team, I was to begin designing the interface of both a web app and a software plugin. After getting the details on the intentions of the project, I met with our internal development team, who had created the backend, to ask some questions.
With the extra details, I was able to start some early decision-making that would guide my design process as this project developed further. I knew the software integration with Veeva would need to be visually engaging as well as simple for the rep to use. This was important since the user interaction would be in front of a potential customer.
I also learned that both interfaces would need to account for a large library of content that could be expanded over time. The final takeaway was that each QR code would need to be preceded by some sort of visual and/or textual indication of which Story or other resource the QR code would link out to.
the Process
Understanding the technical requirements and user needs
Sketches, wireframes, and reviews.
The Must-Haves
Details
Going into the first sketches for the Healthcare Rep Solution, I knew I would have to work within certain technical restraints. These limitations were determined by the development team. I would also need to incorporate feature requests from the sales team while focusing on the primary user and audience: pharmaceutical sales reps and healthcare providers.
I started my sketches by taking the required inputs and elements to begin visualizing the layout options. As I sketched, I asked myself:
How should content selection work?
Would there be logos and other brand elements?
What instructions and copy need to be included?
Is this more of a visual experience, or is it text-heavy?
For each interface, I began sketching what I thought the answers could be to divide my ideas into three groups: “This could work”, “This is a maybe and has some good parts”, and “This isn’t the right solution for this project”. From this, some ideas were combined, and some were ditched altogether. The ideas that survived bloomed into wireframes.
During the wireframing process, these ideas saw a lot of refinement. While I was working independently at first, this was when I began to bring in other team members to review. Lots of good feedback and discussion came out of this initial review.
With a few more conversations and revisions, a direction was chosen to evolve from wireframe to prototype for each corresponding interface. These prototypes went through another round and then were passed between myself and the dev team to fine-tune the details.
Sketches
Wireframes
Final Designs
Creating marketing materials
Below are some of the images used by the sales team.
the outcome
Below are my thoughts and findings from this project
Looking back to reflect, learn, and improve
Main Takeaways
Details
As we finished the Healthcare Rep Solution, I began to reflect on what part of the project went well and what I would like to do next time if presented with the opportunity. We learned that software integration eliminated a key pain point for reps, but budgetholders were more resistant to implementing the product. The next step from here is to use this version to gather data and form a case study that can be presented to clients as a selling point.