Operational Systems & Workflow Design

As the company grew, its operational processes became increasingly complex. Project information, purchasing, installations, and invoicing were being managed through separate workflows, making it difficult for teams to maintain a clear understanding of what was happening, who was responsible, and what required attention next.

The challenge wasn't a lack of information it was a lack of visibility and connection between processes.

The existing Asana environment presented an opportunity to move beyond basic task management and establish a more cohesive operational system. The objective was to reduce manual follow-up, clarify ownership, and provide teams with a more intuitive way to understand both current and upcoming work.

The challenge was approached as a systems design problem, examining the relationship between people, information, processes, and timing rather than treating each operational issue independently.

The strategy focused on transforming Asana into a centralized operational hub using four core principles:

Centralize → Standardize → Visualize → Anticipate

This approach established consistent project structures, connected financial and operational information, and introduced shared visual tools that made upcoming activity easier to understand at a glance.

The system was structured around the natural flow of the business:

Project → Purchase → Installation → Invoice

Mapping these relationships created a foundation for shifting the organization from reactive follow-up toward more proactive planning and accountability.

The existing Asana environment was restructured into a series of interconnected workflows designed around the company's operational needs.

Project Tracker

A standardized project-tracking structure was introduced to create greater consistency across active work. Clear project stages, ownership, and status information made it easier to understand where each project stood and what actions were required next.

PO & Invoice Tracker

Purchasing and invoicing were brought into a centralized workflow, creating a clearer connection between purchase orders, projects, invoices, and follow-up. This reduced reliance on disconnected manual tracking and made outstanding financial items easier to identify and manage.

Install Calendar

Installation information was transformed from individual tasks into a shared operational view. A centralized calendar provided greater visibility into upcoming installations, scheduling requirements, and workload, improving coordination across the organization.

Invoice Calendar

An invoice calendar extended the same forward-looking approach to financial activity. Upcoming invoicing requirements became more visible and predictable, allowing the team to anticipate what needed to be invoiced and when rather than relying solely on manual reminders.

Together, these workflows established a more connected operational rhythm providing a clearer view of what is happening, who owns it, and what is coming next.

The result was more than a reorganized project management platform. The redesigned system established a shared operational language that improved visibility across projects, purchasing, installations, and invoicing.

The new workflows supported:

• Greater visibility across active and upcoming work

• Stronger accountability through clearer ownership and next steps

• Better coordination between operational workflows

• More proactive planning through shared calendars and forward-looking views

• Reduced administrative friction through centralized information and less manual follow-up

  
  

The project demonstrated how design strategy can extend beyond physical spaces and traditional design deliverables. By identifying operational friction and redesigning the systems behind the work, a project management platform became a more intuitive, connected tool for organizational operations.