ProspectScout

I joined the team when there was a partially completed MVP with multiple incomplete user flows. The screen below is an example of the starting point when I joined. I had to re-think the screens already in progress and start other flows completely from scratch. This required collaborating with the engineering team to ensure that the user experience design updates made to pre-existing screens would require minimal refactoring.

Asynchronous collaboration without a product manager. I was mainly working with stakeholders and a small team of engineers. During the process, changes in the direction of the product were communicated verbally on calls. There were instances of score creep and items being assigned to the engineers without a design. As such, I had to step up to advocate for design principles and prioritize thorough communication to ensure that the user's perspective was at the forefront of the product at each stage.

Make the application intuitive so that users could easily create campaigns suited to their business goals.

Prioritize information architecture. From the order of menu tabs to data table columns, conversations with stakeholders helped me hone in on the most important information depicted on each screen.

Implement the Material Design System to ensure design consistency throughout. Due to the large scope of this project, it is integral to keep user flows straightforward. We also want scalability as new features are added. Using a system sped up my wireframing process and made collaboration with engineering more efficient.

A lot of my time was spent understanding the lead generation industry. I explored the tools currently used by the stakeholders (mainly Close and Pipedrive), and conducted a competitive analysis to understand how this product would stand out. During this research and exploration stage, I asked the stakeholders high-level questions, that would lead to more feature-specific questions, which helped bridge the gap in my understanding of the new platform and their users' journeys.

In order for me to speed up my understanding and explore possible solutions, I created wireframes and prototyped them in Figma. My goal during this stage is to hone in on user flows.

Once the wireframes were completed, I scheduled a meeting (or recorded a video demo) to present my work to stakeholders. During this stage, I was able to ask for more clarification and locate the missing puzzle pieces in my understanding. Typically, I met with stakeholders at least once a week during a standup meeting.

Using the feedback I receive from the previous stage, I use this time to update the wireframes with the additional information and present the new versions to stakeholders again. I repeat this process until my wireframes are approved.

To give users a high-level snapshot upon first login, we created a dashboard that displays aliases by status and shows a chart with recent alias activity which the user can adjust to view various date ranges.

To increase the likelihood of closing leads, we set up default campaign settings. This way, the user would only need to update settings that are campaign specific, such as timezone or working hours. This should minimize user drop-off as all fields are already optimized on campaign creation.

We created a global inbox to manage lead communications from directly within the application. This way, the user does not need to open LinkedIn to respond to each message from a prospect. This will save the user time and increase efficiency.