Operational excellence
The Definitive Web Request Guide
The Definitive Web Request Guide
I compiled web operations knowledge into a 36‑page guide to streamline onboarding and reduce repetitive stakeholder questions.
I compiled web operations knowledge into a 36‑page guide to streamline onboarding and reduce repetitive stakeholder questions.
Stages
Problem
Stakeholder confusion, UX team frustration
As our web ops processes evolved, it became clear that access and understanding of the documentation was poor. This lack of visibility led to ongoing stakeholder confusion about how to engage us, what was expected of them, and what timelines to plan for. My team was repeatedly fielding the same questions about workflow, best practices, required forms, and turnaround times.
Over time, those repetitive conversations added up. Answering them pulled hours away from actual project work and made it harder to focus on higher value UX tasks.
Onboarding new hires was troublesome
Onboarding new UX team members was also more difficult than it needed to be. I often had to track down scattered documentation and piece together tribal knowledge just to get new hires ready to build pages. It was inefficient and inconsistent, and it meant every new team member started with a knowledge gap instead of a clear, shared foundation.
Problem
Stakeholder confusion, UX team frustration
As our web ops processes evolved, it became clear that access and understanding of the documentation was poor. This lack of visibility led to ongoing stakeholder confusion about how to engage us, what was expected of them, and what timelines to plan for. My team was repeatedly fielding the same questions about workflow, best practices, required forms, and turnaround times.
Over time, those repetitive conversations added up. Answering them pulled hours away from actual project work and made it harder to focus on higher value UX tasks.
Onboarding new hires was troublesome
Onboarding new UX team members was also more difficult than it needed to be. I often had to track down scattered documentation and piece together tribal knowledge just to get new hires ready to build pages. It was inefficient and inconsistent, and it meant every new team member started with a knowledge gap instead of a clear, shared foundation.
Approach
Collect everything we know about web ops
I started by collecting every piece of web operations documentation I could find, from old email threads and slide decks to formal process guides. This helped reveal both what we already had and where the gaps were.
Curate best practices & FAQs
Next, I worked directly with the UX team to capture the things we found ourselves explaining most often. We focused on:
Web best practices we wanted everyone to follow
Frequently asked questions from stakeholders and new hires
Unwritten rules and nuances that were easy to miss
This collaboration made sure the information reflected how work actually happens day to day, not just an idealized process on paper.
Approach
Collect everything we know about web ops
I started by collecting every piece of web operations documentation I could find, from old email threads and slide decks to formal process guides. This helped reveal both what we already had and where the gaps were.
Curate best practices & FAQs
Next, I worked directly with the UX team to capture the things we found ourselves explaining most often. We focused on:
Web best practices we wanted everyone to follow
Frequently asked questions from stakeholders and new hires
Unwritten rules and nuances that were easy to miss
This collaboration made sure the information reflected how work actually happens day to day, not just an idealized process on paper.
Solution
The final deliverable was a 36‑page document called The Definitive Web Request Guide (Figure 1), shared with the entire Marketing organization as the go‑to reference for web operations. It was designed to be practical, scannable, and directly useful for both stakeholders and new UX team members.
The guide covers:
Team structure and our standard web request workflow
Links to templates and web request forms that stakeholders can use immediately
Final content guidelines and web best practices
FAQs and additional resource links for deeper dives
We published the guide in our Digital Resource Center on SharePoint so anyone in the organization could access it via a single, reliable link.
Figure 1. Cover image of The Definitive Web Request Guide.
Figure 2. The Definitive Web Request Guide tables of contents.
Solution
The final deliverable was a 36‑page document called The Definitive Web Request Guide (Figure 1), shared with the entire Marketing organization as the go‑to reference for web operations. It was designed to be practical, scannable, and directly useful for both stakeholders and new UX team members.
The guide covers:
Team structure and our standard web request workflow
Links to templates and web request forms that stakeholders can use immediately
Final content guidelines and web best practices
FAQs and additional resource links for deeper dives
We published the guide in our Digital Resource Center on SharePoint so anyone in the organization could access it via a single, reliable link.
Figure 1. Cover image of The Definitive Web Request Guide.
Figure 2. The Definitive Web Request Guide tables of contents.
Outcome
The guide was received well by both the UX team and our stakeholders. It gave my team a single link to replace hours of repetitive questions and became a core onboarding tool.
Results included:
36
Pages of clearly documented web operations processes and best practices
2 hrs
Saved per week on redndant UX team correspondence
4 hrs
Saved onboarding each UX or stakeholder new hire
Outcome
The guide was received well by both the UX team and our stakeholders. It gave my team a single link to replace hours of repetitive questions and became a core onboarding tool.
Results included:
36
Pages of clearly documented web operations processes and best practices
2 hrs
Saved per week on redndant UX team correspondence
4 hrs
Saved onboarding each UX or stakeholder new hire
Collect everything we know about web ops
I wanted a single, centralized resource that would answer common stakeholder questions before they reached our inboxes. To get there, I started by collecting every piece of web operations documentation I could find, from old email threads and slide decks to formal process guides. This helped reveal both what we already had and where the gaps were.
Compile team knowledge, best practices, and FAQs
Next, I worked directly with the UX team to capture the things we found ourselves explaining most often. We focused on:
Web best practices we wanted everyone to follow
Frequently asked questions from stakeholders and new hires
Unwritten rules and nuances that were easy to miss
This collaboration made sure the final guide reflected how work actually happens day to day, not just an idealized process on paper.
Nicholas Fargher
© 2026 Nicholas Fargher
Nicholas Fargher
© 2026 Nicholas Fargher