Bringing Users to the Forefront of Business Strategy

Helping teams plan around what pharmacy staff need to accomplish

Omnicell · Senior Product Designer

Who are we building for?

At Omnicell, “Pharmacy Administrator” covered people with very different responsibilities, from pharmacy technicians to Chief Pharmacy Officers. That label gave us too little context to connect a product decision to the person doing the work.

Product, engineering, design, and business teams also needed a clearer connection between proposed features, user needs, and business goals. I worked with colleagues across these groups to make that connection more explicit, starting with how we described our users.

Start with responsibilities

A job title alone couldn’t tell us what someone needed from the product. Responsibilities could change with a person’s shift, certifications, or the composition of their team.

I organized our understanding of users around pharmacy permissions. With the design team, I listed the known permissions and developed Jobs to Be Done for the responsibilities they represented.

For example, someone managing temporary staff needed to create accounts with appropriate access. Someone responsible for restocking needed to respond when inventory reached a critical low. Both could fall under our existing administrator label, but their situations, decisions, and goals were different.

These job stories gave us a more useful starting point for discussing what a feature needed to help someone accomplish.

One Pharmacy Administrator label branches into two distinct jobs: track inventory to understand an item across the enterprise, or check purchase data to verify information before trusting it. Condensed from permission-based job stories.
Breaking a broad persona into permissions and the jobs behind them.

Connect individual features to the larger workflow

I developed journey maps and brought them into strategy discussions and day-to-day team conversations. They helped us consider how individual features fit into a larger workflow and where someone needed information or support to move forward.

One opportunity captured in the business case involved pharmacy leaders investigating inventory across a health system. They needed to compare sites and identify where to make changes, but relevant information and optimization recommendations were spread across different parts of the product.

Looking at the whole workflow helped us describe the problem more clearly: people needed to move from identifying an issue to deciding what to do about it. That connection gave us a stronger basis for discussing proposed improvements.

Original journey-map comparison for maintaining inventory par levels, restyled. The previous shared flow has total score minus 0.5 and the note that it is used for two use cases which should be addressed deliberately. Item flow: expected new experience scores 1.5; desired future state scores 2.5. Cabinet flow: expected new experience scores minus 1.5; desired future state scores 2.5. These are qualitative scores from the original map. Journey points were not named in the original.
The shared flow, expected new experiences, and desired future states for maintaining inventory par levels, with item and cabinet flows shown separately.

Agree on the problem earlier

I created a Project Overview document to bring product, engineering, and design into the conversation earlier. It gave us a shared place to define the problem and discuss success criteria before getting deep into a solution.

I also worked with business leaders to understand their goals and examine proposed business cases. We discussed who would benefit, what would change for them, and how that change supported the business.

Making those questions part of the initial conversation gave the team a clearer basis for evaluating the work.

Make the investment case clearer

I helped a business leader refine an annual business case into a more concrete, user-centered proposal with defined success criteria. My contribution was connecting the proposed investment to specific responsibilities, workflow problems, and intended benefits. I was laid off before learning the funding decision.

Original value-statement rework. Before, vague: Expand our value prop for Customer and Customer in large enterprises. After, specific: Success statement: Customers only need to go to one place, our app, to determine performance-related data. The original anonymized placeholders are retained in the visible text.
A broad value proposition becomes a concrete success statement.

The work gave colleagues shared references for different kinds of decisions: job stories for understanding responsibilities, journey maps for discussing the experience, and a Project Overview for agreeing on the problem and success.

Conversations across design, product, engineering, and business helped me connect the details of pharmacy work to the decisions the team needed to make. Turning those insights into something we could examine together helped us clarify what mattered and give the team a stronger starting point for developing solutions.

Want to discuss this project? Contact Joe at contact@josephnewelldesign.com.