Operations Analytics & Workflow Management Hub

Tools: Google Sites, Google Forms, Google Sheets Status: Active and in use

Overview

This project started with a conversation.

During a discussion with senior management about data collection and operational efficiency, a frustration came up that I recognized immediately: our team's resources were scattered. The daily schedule lived in one place, incident reports in another, internal trackers somewhere else entirely. Finding anything required knowing where to look, and follow-through on requests was difficult to monitor consistently.

I left that conversation with an idea. What if everything lived in one place?

What I Built

I designed and built a team intranet using Google Sites as the central hub. Everything the team needed operationally was consolidated into one accessible platform:

A daily schedule, visible and up to date in one place. An all-in-one Operations Tracker combining ticket tracking, incident reports, and work order logs with open, pending, and closed status visibility. A daily schedule request form with its own embedded tracker so requests could be submitted, monitored, and followed through without anything falling through the cracks. Internal button links connecting the team to key internal pages without having to search for them. And a Meet Our Team page, built for corporate visits, giving visitors a face and a brief description of who we are before they even walk in the door.

The daily scheduling process was also redesigned using conditional formatting in Google Sheets, reducing manual effort and improving accuracy for schedulers.

Why It Worked

Every tool in the hub was built around a specific pain point that had been identified in that initial conversation and in subsequent conversations with the team. Nothing was added for the sake of adding it. The goal was always to reduce friction, not create more of it.

Standardization was a deliberate choice throughout. Consistent formats made it easier to track patterns, generate reports, and prioritize incoming issues without having to interpret differently formatted data every time.

Impact

The platform was presented to senior leadership and selected for regional rollout. The entire team adopted it as their primary operational hub. To date, 4 of 12 locations in the region have adopted the model and are actively building their own sites, with additional locations in the process of migrating from Confluence to Google Sites.

To support further adoption going into Q2, I developed a Google Sites 101 guide designed for team members who would not typically be expected to have web building experience. The guide has been made available to all 65 locations nationally, giving every team the tools and confidence to build their own hub without needing outside help.

What started as an idea from one conversation is becoming a national standard.

Note: This project contains proprietary internal tools and cannot be displayed publicly. The description above reflects the scope, methodology, and impact of the work.

Lessons Learned

The best operational tools are invisible. When a system works well, people stop noticing it and just use it. The goal was never to build something impressive. It was to build something that made the team's day easier.

Presenting to senior leadership also reinforced something I had learned from research work: a tool without a clear narrative does not get adopted. Data and systems need context and a story to drive real behavior change.