High-level Problem

Throughout my time at both Pivotal and SRP, I acted as a design lead on all product teams. Despite the multitude of projects I worked on, the process all stayed fairly consistent. The most common scenario was we were given an ask from the leadership team to help them replicate an existing tool but make it better. The vagueness of the ask usually meant we would have to facilitate a Kick-off with key stakeholders and the product team to ensure a shared understanding of what we were being asked to do.

Role : Lead Designer | Design Director

Tools : Sketch, Google Suite, Miro, LucidChart

Lead design and research efforts for 6 product offerings within 4 enterprise organizations. Worked directly with leadership team of all enterprises, on efforts such as internal transformation initiatives, executive decision making, product optimization efforts, and internal process improvement initiatives. I partnered closely with product managers and developers to ensure we all had clarity for the problem we were solving and had an understanding for how we could create iterative value for our users. My output ranged from facilitating workshops with the product team (user value V. user impact, risk/opportunity, Now/Near/Next, etc) to creating high-fidelity wireframes for the development team.

Background

Modern Fortune 500 companies produce an unfathomable amount of information every single day: everything from HR records and financial statements to cat GIFs posted to Slack. Consider the most common form of electronic data created by organizations: email. An average employee at a large company like IBM sends and receives around 50 emails on a normal work day. After just one year of service, this employee would have racked up 13,000 emails. This means that every year a company like IBM sends and receives about 5 billion emails! Storing this data, either on premise or in the cloud is one of the largest expenses most fortune 500 companies face.

While retaining this data is costly, when companies are involved in a lawsuit they must be able to produce evidence when requested. In fact, most industries require that companies retain data for a certain amount of time, regardless of the size.

The focus of StoredIQ for Legal is to give paralegals, attorneys and IT staff the tools they need to discover and produce relevant information when they are facing impending litigation or an internal investigation.

Move From Personas to User Groups

When joining the team, the research that had been conducted was based around a large scope of personas. One of my main goals was to reduce that persona base, and narrow down user-groups for a more targeted approach, using the Jobs-To-Be-Done approach.

 Research

While working on ILG, I had the opportunity to conduct countless types of research studies. One of the most important things I worked on, was synthesizing research that had been conducted prior, and turning those into valuable insights that may have been overlooked.

Wireframes

The last issue I worked on, involved a new concept for visualizing information. I led a 60-min design sprint with the team, to create concepts before feedback sessions and re-iterations.

Current Product

To provide a preview as to the product look and feel, I've included images below.