← All case studies / Jonathan Wadsworth

Enterprise Application

Activity Execution Manager

The person who plans a field activity and the person who executes it in a store have almost nothing in common: different devices, different context, different definition of done. The tool had to serve both without becoming two products.

Role
UI/UX Designer
Client
Coca-Cola Consolidated
Platform
Web & Mobile Field Application
Activity Execution Manager interface

The Challenge

In-store merchandising and promotional execution had been tracked through a manual spreadsheet process: someone assigned a task, and there was no reliable, role-aware way to confirm who was supposed to do it, whether it had actually been completed, or who needed to sign off on it. As the volume of in-store activities grew, that process stopped scaling.

The Approach

I designed Activity Execution Manager around a maker and doer model: the screens and actions a user saw were determined by their credentials, so a task creator saw assignment and approval tools while the person executing the task in the field saw only what they needed to mark a task complete. Keeping those two roles visually and functionally distinct was the core design problem, since the same platform had to serve both without either role wading through controls meant for the other. The doer's entry point was designed for a phone rather than a tablet, reflecting how that role actually works in the field.

The Outcome

Activity Execution Manager replaced the manual spreadsheet process with a role-aware system where task assignment, execution, and approval each had their own clear interface, instead of everyone working from the same undifferentiated sheet.

Selected screens

Screens from both sides of the maker and doer model: the task creator's assignment view, and the field executor's matching, more restricted view of the same task.