Design Operations · Wells Fargo

Design Operations: replacing scattered requests with one system of record

Role
Design Ops Lead
Tools
Confluence, Jira
Focus
Intake process, team capacity visibility

The challenge

Design requests were coming in through scattered emails, team messages, and hallway conversations, making it nearly impossible to prioritize work or give stakeholders visibility into where their asks stood.

The approach

I designed and implemented a centralized design intake form in Confluence that routed submissions directly into our team's Kanban board, replacing ad hoc requests with a single, standardized entry point. Stakeholders could submit structured requests and track their place in the queue, while leadership gained real-time visibility into team capacity, workload, and priorities.

Confluence intake form → Jira board automation

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

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 →
Outcome

Fewer back-and-forth clarifications, fewer dropped or duplicate requests, and a defensible way to prioritize based on actual bandwidth, not who asked loudest or most recently.

Why it mattered

Beyond the immediate process fix, this gave the team a repeatable structure for protecting its own capacity, and gave leadership a clear, data-backed view into what the team could realistically take on.