How I leadI lead by showing what's possible before I ask others to build it. Not because I have all the answers—I don't. But because the gap between "here's what we should do" and "here's what could actually work" is where teams learn, trust forms, and real progress happens.My approachInformed by decades of real-world problem-solving, my work has always been rooted in UX design, long before it became a formal discipline. I cut through ambiguity to deliver meaningful results—whether that's partnering with enterprise organizations, scrappy startups, or small businesses.
I specialize in bringing design strategy and systems connectedness out of the abstract and into practical reality. My neurodivergence gives me a particular way of seeing patterns, breaking silos, and translating complex system thinking into work that teams can actually execute. It's a strength I bring to every engagement.
How I work bestFront-load meetings, then focus. I work best when we converge early on project direction, then I have dedicated time for deep work and delivery.
Intermittent convergence. I like ad-hoc short check-ins throughout the week rather than standing meetings. That rhythm keeps us aligned without fragmenting focus.Give me coffee, then momentum. I'm a night owl. Front-load your expectations in the morning (I need caffeine to warm up), and I'll deliver thoughtful, focused work.
Quiet space for deep work. When I'm focused—especially on writing, design, or systems thinking—I need quiet. I'm not antisocial; I'm just optimizing for the work itself.
What I bringClarity in ambiguity. I have a knack for untangling complex problems and communicating the path forward. Not simplifying too much—just making the actual problem visible.
Egoless design philosophy. My work is grounded in user research and rapid iteration. I value honesty over kindness. Direct constructive feedback helps me grow; I expect the same from my team.
Breaking silos. A lead engineer I've worked with put it this way: "Before Brent arrived, design handoffs often lacked context around design decisions. By involving engineers earlier in the design process, he encouraged valuable feedback, leading to more refined designs and fewer mid-sprint changes." I don't see design as separate from engineering or product—I see it as the connective tissue.
Design systems at scale. I've built systems from zero, scaled them across teams, and created contribution models that let teams extend without fragmenting. From semantic tokens to governance infrastructure, I approach complexity through systems thinking.
Optimization and velocity. I'm comfortable operating at scale—coordinating across 10+ teams, modernizing legacy enterprise services, shipping design in high-stakes federal environments. I know how to set up workflows and tools, so teams produce high volume without sacrificing quality.
What I Specialize In- Design ops and human capital development
- Product strategy and digital transformation
- Design systems (from 0-to-1 builds to enterprise scaling)
- Digital service modernization in government and enterprise
- Responsible AI integration into product workflows
- Scaled agile delivery across multidisciplinary teams