Design Operations: Creating Visibility Through Process

As the design lead supporting multiple enterprise initiatives, I recognized that our intake process had become fragmented. Design requests were arriving through emails, meetings, instant messages, and informal conversations, making it difficult to understand the true volume of work, prioritize requests consistently, or communicate team capacity to leadership.

To solve this, I designed and implemented a centralized design operations workflow using Confluence and Jira. I created a standardized intake form that captured the information needed to evaluate each request and automatically routed submissions to our Kanban board. I also developed a shared request library that gave stakeholders visibility into the status of their requests and where they stood in the design queue. This replaced scattered email requests with a transparent, standardized process — allowing stakeholders to submit requests and track their place in the queue, while giving leadership real-time insight into team capacity, priorities, and workload.

To further support this transparency, I created the MSXD Playbook — a centralized resource documenting everything our XD team was working on and how we worked. This included our design methodology and design thinking process, along with direct links to WCAG accessibility guidelines and brand standards. Consolidating this information into a single source of truth gave business partners and leadership an easy way to understand our process and reference standards without having to track down separate resources, ensuring our work consistently aligned with accessibility and brand requirements.

Together, this new process and playbook created transparency for both the design team and business partners, improved prioritization, reduced administrative overhead, and gave leadership a clear view of active initiatives, team capacity, and delivery timelines. More importantly, it established a scalable design operations framework that enabled the team to manage growing demand while fostering stronger collaboration and more predictable delivery across Product, Engineering, and Design.

wellsfargo.atlassian.net/wiki/spaces/DESIGN/intake
WF
Wells Fargo Confluence
Design & Brand Space / Intake Forms
Space overview Design Request Intake Templates Team calendar
Design & Brand Team

Design Request Intake

Submit a request to the Design team. Submitting this form automatically creates a ticket on the Design Requests Jira board.

Low
High
Medium
Urgent
Drop files or click to browse — brief.pdf attached
Submitted ticket auto-created in Jira
Confluence form → Jira automation → Design Requests board
wellsfargo.atlassian.net/jira/software/projects/DES/boards/1
WF
Wells Fargo Jira
Design Requests / Board
Design Requests Board
Project: DES · 5 columns · updated just now
Backlog 4
DES-482
Refresh homepage hero banner for Q3 promo
HighSC
DES-481
Update ATM signage template
MediumJR
DES-479
New icon set for mobile app
LowTL
DES-477
Branch flyer — savings campaign
MediumMK
To Do 2
DES-474
Email header for card offer
HighAL
DES-470
Social post templates — August
LowSC
In Progress 2
DES-465
Redesign online banking login screen
HighJR
DES-461
Wealth mgmt brochure layout
MediumTL
In Review 1
DES-458
Branch window decals refresh
MediumMK
Done 1
DES-450
Q2 annual report cover design
LowAL
← swipe to see all columns →

*Confidentiality Notice: Visuals have been recreated using AI to protect confidential information while accurately representing my design work.