
Hello!
I’m a manager, maker, craftsman, and multidisciplinary design leader, creating beautifully-designed experiences that delight users.
Being T Octopus-shaped
🐙
Being T-shaped is over
Modern UX professionals can’t afford to be deep in only one area - the demands to execute exceptional work across a wide range of skillsets requires more.
I strive to be octopus shaped
I’ve developed a full-stack approach to my leadership and craft, which includes proficiency across a wide range of core digital design and management skills.
How I think
🧠
Process ≠ Innovation
Process ≠ Innovation
For too long the product design discipline has been reduced to a set of processes. This is unfortunate, because having some process is better than having none (especially if that process helps develop game-changing experiences). And I fear we’ve conflated process with innovation.
I’m comfortable with any process my team decides to follow, whether the double-diamond of Design Thinking, the steady convergence of Business Optimization, or the iterative nature of Continuous Improvement. It’s not the process: it’s the people, ideas, and work ethic that makes the difference.
-
Convergence & Divergence
USER EXPERIENCE
The foundation of user centered-design, this thought-process encourages practitioners to constantly mode-switch between questioning assumptions and narrowing towards conclusions.
-
Business Optimization
PRODUCT MANAGEMENT
A prototypical product management mindset, this thought-process continually pivots the current state to better land end-state objectives.
-
Continuous Improvement
ENGINEERING
Popular with engineers, this thought-process continually tests assumptions and iteratively refines the current-state to improve outcomes towards success criteria.
Management Philosophy
💭
I’m committed to building high-performing teams, and I do this by employing a unique management approach. On my team you can expect:
Immediate & direct feedback
Obligation to dissent
Inspiring followership
Meritocracy
Cross-functional collaboration
Apprenticeship
Consensus building
One-team mentality
Never say no
⌁
Always say how much
⌁
Never say no ⌁ Always say how much ⌁
Oftentimes UX resourcing and cross-functional needs don’t align. When this happens my teams offer several partnership models so that we…
-
Deep Partnerships
When time & resourcing permit, and the scope is appropriate, UX partners with cross-functional teams and our staffing levels are at (or near) max.
-
Spikes
When UX can make an impact in a shorter engagement (or multiple impacts throughout a program), we spike our engagement.
-
Office Hours
My teams provide availability to cross-functional partners in predictable time-slots so that velocity on keey programs can continue with some UX input.
What Others Say…
📝
As a manager and mentor: Victor pushed me to improve my core design craft and created a team environment that allowed myself and other designers to grow tremendously and take on progressively larger scope of ownership. All along the way, he provided useful insight to guide my design work and approach to collaboration with other teams within Cruise, unblocking key stuck points whenever they arose.
- Spencer James, Direct Report at Cruise
Victor is easily one of the top designers I've had the privilege of working with and learning from across my 10+ years in UX. He has an exceptionally strong attention to detail and love for his craft — uniquely coupled with the passion and talent to develop a compelling story and clear strategy for aligning teams to deliver on a vision.
- Rob Larson, Direct Report at Google
I had the honor of closely working with Victor while at McKinsey. Victor is one of the most talented product and design leaders I have ever met. His ability to be a 'player - coach', engage in business strategy, and his dedication to excellent work - at all costs stands out.
- Josh Weiner, Advanced Analytics at McKinsey
Work Experience
🖇️
How I Work
🛠️
As a colleague and teammate, I’m very interested in sharing in-progress work for feedback early and often. Sometimes those reviews & critiques happen a-synchronously, so I’ve gotten into the habit of recording design walkthroughs and posting them to my cross-functional team in Slack. Here’s a recent example: