Moving The Needle

• Building frameworks that transform capability into scalable impact
• Creating systems that sustain quality amid growing complexity
• Establishing infrastructures that elevate execution to strategy

Here are four distinct ways I’ve moved the needle to create operational leverage that amplified impact far beyond what individual effort could achieve.

Early in my career, I led the creative direction for multiple digital properties at Wachovia, while also working at the technical frontier—defining standards-based design practices, developing reusable interface patterns, and engineering one of the industry’s first frontend frameworks to unify and streamline implementation across product teams. Long before the iPhone existed, and before “responsive design” was even a term, I was focused on how to make digital experiences more accessible, adaptable, and scalable.

In this dual role, I designed interfaces for multiple Wachovia brands while also building the operational scaffolding beneath them. I prototyped advanced UI concepts to demonstrate how accessibility and performance could be maximized. I authored usability and code standards that brought consistency across decentralized teams. And I earned a patent for a progressive enhancement method that allowed a single UI to adapt seamlessly across mobile devices and assistive technologies.

The technical innovations I pursued early in my career pointed to something deeper in my leadership orientation. I learned to operate fluently in both creative and technical domains, and that dual capability allowed me to extend the influence of design into infrastructure. That’s where systems thinking took hold for me as a way to make creativity more scalable, quality more consistent, and complexity more navigable. It was the beginning of a pattern that would come to define how I lead.

As Ally’s design practice evolved from a small centralized practice into a distributed organization embedded across dozens of product teams, it became clear that creative excellence wouldn’t scale on talent alone. We needed operational clarity—systems, roles, standards, and routines—to raise the floor for consistency and confidence across the board.

I formalized DesignOps as a vital functional area of Ally’s growing design org. As an operational support function and the nucleus of our practice, building out the DesignOps team with world class talent was the strongest signal of design maturity during my tenure. The team codified structures, tools, and collaboration models that made quality more repeatable and ambiguity less routine. By creating a strong foundation for how we worked, DesignOps gave teams the stability they needed to work with autonomy, speed, and conviction.

A critical dimension of this work was elevating accessibility from a QA checkpoint to a pillar of user experience. I assembled a team who’s charter was to embed inclusive design into our standards, components, and operational policies. But the real shift came when Kimmy Kaplan Dowdee—one of the most gifted designers on my team—stepped boldly into the newly created role of UX Accessibility Principal. It was a first for Ally, and a professional risk for her.

Under Kimmy’s leadership, inclusive design quickly scaled from an aspirational principle to an enterprise program with its own roadmap, governance, and strategy. As her manager and mentor, my job was to clear a path for her to navigate, and then get out of her way. And given the level of strategic influence and operational maturity she so effectively demonstrated, I soon elevated her role to become Ally’s first UX Director of Inclusive Design.

I take pride not just in the systems I built, but in the leadership those systems empowered. Kimmy’s meteoric rise in influence and the inclusive design ethos she drove are among the clearest signs that the design practice at Ally didn’t just grow under my influence, it scaled with values intact. Through strategic operational leadership, I nurtured a more principled, confident, and empowered design organization, one in which competitive excellence and inclusive thinking were two sides of the same coin.

Delivering a reliable product experience across dozens of distributed teams required more than shared intent—it required a system. I led the creation of a comprehensive design system that functioned as both a brand foundation and an operational engine, giving product teams the clarity, tools, and confidence they needed to make better decisions, faster.

We started with the fundamentals: codifying the visual and rhetorical identity of the brand—our color model, typography, spacing system, iconography, and illustration style—all underpinned by guidelines for voice and tone as our baseline signals of clarity and trust. From there, we extended the system into tools that product teams used every day: UI components built with accessibility by default, design specs embedded with inclusive principles, and patterns integrated directly into both design and code environments.

But we didn’t stop at the interface. We wove in strategic scaffolding that allowed teams to solve problems with greater context and consistency. Shared heuristics for experience evaluation. Journey frameworks to guide end-to-end thinking. Personas that reflected real user behaviors and expectations. Strategic themes that framed each initiative in terms of broader business and customer goals.

This system gave us more than just a consistent look and feel. It gave us a shared language and a common standard for what “good user experience” meant at Ally. And it turned quality from something we reviewed after the fact into something we could build from the start—faster, smarter, and at scale.

In a rapidly scaling organization, complexity is inevitable. At Ally, as our product teams expanded, so did the diversity in approaches, terminologies, and interpretations of quality. While this diversity brought innovation, it also introduced challenges in maintaining a cohesive user experience across our digital ecosystem.

Recognizing this, I developed a design playbook with a strategic framework for harmonizing user experience across a broad portfolio of digital products. The playbook offered a set of journey-based heuristics that formed guardrails for experience design, guiding product teams toward common standards and shared goals. It served as a bridge between design, product, and engineering, fostering a unifying sense of what quality meant in the context of an Ally-branded user experience.

The playbook’s impact extended beyond design teams. It became a cornerstone for cross-functional collaboration, enabling clearer communication and more aligned decision-making across the organization. Its adoption signified a cultural shift toward intentionality and coherence in our product strategies.

• Navigating ambiguity with structured, decisive action
• Adapting leadership style to context rather than convention
• Taking initiative beyond formal responsibilites when circumstances demand

The next five examples demonstrate how I’ve moved the needle by recognizing when the moment demanded something different—when conventional approaches wouldn’t suffice, and a more adaptive, responsive form of leadership was needed to transform complexity into clarity.

Every growing design system accumulates debt—it’s a byproduct of progress. What determines whether that debt is manageable isn’t its presence, but its visibility. I developed a readiness scoring model and diagnostic framework to expose design debt in operational terms—transforming vague concerns about quality into structured insights that link design integrity to business performance.

The model was inspired by something far outside the world of design: the “combat readiness” framework I once used as a Marine. I adapted its principles to measure a product’s state of UX integrity—not whether it had achieved pixel-perfection, but whether it would hold up under pressure. A tank with a broken axle can’t be deployed; a product with inaccessible features or confusing instructions can’t deliver on customer trust.

I developed a library of 150 requirements distributed across five experience dimensions—style, accessibility, simplicity, enablement, and effort. Each audit surfaced design liabilities, risks, and tactical breakdowns, scored across five analytical lenses: the what, how, and why of experience quality, the opportunities created by failure, and the concerns triggered by neglect. The results were presented not as a static report, but as a fully interactive diagnostic tool—an Excel-based application with dashboard navigation, journey-level analytics, and defect parameters that formed insights what mattered most: remediating debt with high impact and low complexity.

What made this work was not the volume of data but the clarity of perspective. Readiness reporting became a planning instrument—one that helped product leaders focus resources, empowered teams to course-correct, and gave the business a measurable view of UX quality in production, not just in theory. Readiness was a gauge of whether we walked the talk of good user experience at Ally.

As the Ally Design org scaled beyond 50 practitioners supporting a product portfolio of growing complexity, resource allocation became both a strategic lever and a cultural pressure point. Without a system, planning was inconsistent. Some teams were spread too thin, others underutilized. Designers juggled conflicting priorities, and team leads had no reliable way to see or support where load was accumulating. The lack of structure was eroding focus and threatening both quality and morale.

I led the development of a capacity forecasting model that replaced intuitive allocation with structured planning based on real variables: discipline, team complexity, and administrative load. We designed workload ratios tailored to role and context, visualized utilization trends, and introduced a rhythm of operational planning that allowed us to see problems before they became crises. What had been anecdotal became empirical. Instead of being in a reactive posture toward capacity and utilization, managers became more strategic.

The results were felt immediately. Utilization variance, once swinging between 50% and 180%, leveled out at a more sustainable and reasonable 80–100% range. Team leads gained foresight and flexibility. Designers had more stable footing and fewer surprises. And across the org, we could scale with confidence, knowing we had the visibility to plan, the structure to adapt, and the systems to support a growing, distributed team.

During a series of acquisitions at Ally, I was often brought in to stabilize design operations as bridges were being built to connect incoming product teams to the rest of the organization. These acquisitions were stress tests for culture as much as they were for operations. The transitions were rarely seamless. Teams arrived with different structures, values, cadences, processes, and assumptions about how design fit into product strategy. My role wasn’t to impose structure, but to interpret needs, clarify expectations, and engineer trust fast enough to preserve momentum.

Rather than treat these transitions as tactical onboarding exercises, I treated them as opportunities to lead with clarity and care. I built custom integration plans for each team, tailored to their context, tools, and culture, and provided structured support to help them find their place in our practice. I offered direct mentorship to incoming ICs and leaders, translated expectations across organizational boundaries, and designed engagement models that respected what made each team effective.

When Ally acquired Health Credit Services (HCS), the incoming design leader left early in the transition, leaving behind a demoralized team, a frustrated tier of product and engineering partners, and no apparent groundwork for integrating with Ally operationally or culturally. When tapped to step in and stabilize the situation, I quickly established new staffing models, intake and delivery mechanisms, clarified priorities, and rebuilt trust across functions. By partnering closely with product leaders to align our design support with their business goals, we not only retained 100% of the acquired design team through the transition, but established design’s credibility as a strategic partner.

As one executive put it, “Brian brought calm, positivity, and resolve… the true feel of a trusted partner.”

Between 2018 and 2022, the design practice at Ally grew by 145%, a wave of expansion driven by new product development, acquisitions, and accelerating digital ambitions. But rapid growth across geographies came with risks: inconsistent integration, diluted standards, and strained coordination between teams that had never worked together, and in some cases, had never even partnered with a design team before.

To meet the moment, I initiated a geographic expansion strategy that placed fully-formed, self-sustaining design teams in key product hubs outside of our Charlotte headquarters, specifically Detroit and Southern California. These were not satellite support roles; they were embedded teams with local autonomy, strong ties to product and engineering counterparts, and a clear mandate to uphold the principles and standards of Ally’s centralized design vision.

To support this distributed model, I introduced operational scaffolding that made geographic distance irrelevant. We built coordination tools, onboarding routines, shared documentation systems, and communication cadences that allowed distributed teams to work with autonomy without sacrificing cohesion. And we invested early in asynchronous workflows and knowledge-sharing protocols—well before the pandemic forced remote-first operations.

These structures not only stabilized growth, they became the foundation of our team’s resilience. When lockdowns began, we didn’t scramble. We scaled. The UX team transitioned seamlessly to fully remote work because the systems we had built for geographic flexibility had already created a culture of autonomy, trust, and coordination. The challenge of expansion became a proving ground for sustainable operations, and ultimately, a blueprint for continuity through disruption.

As Ally’s design organization scaled, our space didn’t. During the in-office years leading up to the pandemic, Ally’s Charlotte-based product teams were growing fast, but our office space was not. We became fragmented across different buildings and different floors. New hires were crowded into makeshift desks, and working around a layout optimized for individual focus, not collaborative problem-solving. When the problem peaked, Design accounted for  50% of occupancy while being crammed into just 20% of available floor space. Morale was waning, productivity was uneven, and retention risk was growing.

Corporate Real Estate had no plan to fix it. So I made one.

I developed a detailed space plan proposal for a purpose-built design studio that would consolidate over 100 team members on a single floor of the Charlotte headquarters building, increasing occupancy efficiency by 38% and enabling the kind of impromptu, high-bandwidth collaboration our work required. I handled the research, user needs assessment, layout design, and executive presentation. I even specified amenities: modular seating, line-of-sight desk configurations, flexible collaboration zones, quiet focus areas, and smartboards to facilitate team critiques and working sessions.

It was far outside my role, but essential to sustaining the team. The space we built wasn’t just more practical and functional, it was more human and collaborative. It helped teams move faster, work smarter, and feel engaged. It also allowed me to demonstrate something for my team that I had often encouraged them to do: solve the problems you see. If the environment isn’t working, change it. Leadership requires initiative.

• Cultivating conditions where others discover their leadership potential
• Translating individual strengths into organizational influence
• Creating frameworks that make growth visible, accessible, and equitable

These last five examples show how I moved the needle by shifting focus from immediate outcomes to enduring impact, building leadership capacity in others and creating the conditions where talent transforms into influence.

Even the strongest teams can fray under complexity. As Ally’s design organization grew—spanning new geographies, disciplines, and seniority levels—we began to experience the organizational strain that comes with scale: miscommunication, uneven visibility, and cultural drift. Informal rituals and shared assumptions could no longer carry the weight of alignment. We needed a more durable structure—something that could hold the center while enabling local autonomy.

I founded the Experience Leadership Guild (XLG) to meet that challenge. It was a 15-member interdisciplinary council composed of principals, managers, and directors representing every region and function. The XLG was modeled on servant leadership to promote shared responsibility, growth, and engagement of individuals and teams across the design org. Our focus was simple: Culture (how we lead), Craft (how we operate), and Scale (how we grow).

The XLG tackled everything from practice maturity and career pathing to brand values, psychological safety, and industry influence. But what made it transformative was how we delegated leadership to individual contributors. We matched stretch initiatives to personal growth goals, mentored without micromanaging, and celebrated the outcomes as both cultural wins and leadership development milestones. This turned the Guild into a dual engine: it steered organizational health and accelerated succession readiness at the same time.

Over time, the XLG became our cultural scaffolding. It preserved cohesion across distance and change, gave the team a unified voice in how the practice evolved, and reinforced the idea that leadership isn’t a title—it’s a service. For many on the team, contributing to the Guild was their first real taste of cross-functional leadership. For the organization, it was a scalable model of distributed impact, one that brought clarity and confidence exactly when the complexity of growth might have otherwise eroded them.

As the scale of operations at Ally grew bigger and more complex over the years, we began to see the limits of our existing career framework. Titles meant different things to different people. Expectations varied from team to team. Feedback and growth conversations felt inconsistent, even arbitrary. For a team grounded in purpose and performance, this kind of ambiguity was corrosive. It undermined confidence, trust, and ultimately equity. I saw an opportunity to rebuild the foundation.

I led the complete redesign of our career ladder, from title taxonomy and role definitions to behaviorally anchored expectations and growth signals. We didn’t just clarify what each level meant; we defined how progress was demonstrated in practice, across multiple archetypes and work styles. I built a matrix that distinguished between craft impact, team contribution, strategic influence, and cultural leadership—ensuring growth wasn’t limited to the loudest voice or most visible artifacts. It gave room for different kinds of excellence to be recognized and nurtured.

Inclusivity was a core design principle. That meant pressure-testing language to avoid bias, equipping managers with shared criteria and coaching tools, and co-creating key elements with senior ICs and people managers to ensure the framework felt fair and actionable. We validated the system through a series of calibration workshops and continued to iterate as new patterns emerged. Over time, the career framework became a cornerstone of our culture. It brought clarity to performance expectations, transparency to promotion decisions, and consistency to how we developed and retained talent—especially as we continued to grow across disciplines, geographies, and levels of experience.

Titles and compensation were part of it, but the deeper goal was to bring transparency to expectations and create a shared language for growth. By designing clear and visible paths forward, we gave people something even more powerful than a promotion: a credible sense of where they stood, where they were going, and how to get there.

In the wake of the pandemic, the logistical shift to remote work triggered a disruption in cohesive team culture and career continuity. At Ally, an internal engagement survey in 2023 revealed a steep decline in morale. Teams were disoriented. For some, their career momentum felt stalled following several years of working from home. A growing perception took hold: leadership opportunities, and the promotions that followed, had become increasingly out of reach. I joined a leadership task force to diagnose the issue and figure out what needed to change.

The group consensus was that individual contributors weren’t “leading loudly enough” in the absence of the sort of face-to-face, organic influence that we once took for granted in office settings. Promotions weren’t happening, the logic went, because managers weren’t seeing enough assertiveness, presence, or influence. The proposed solution was to tell our expert practitioners in creative disciplines to simply “step up.” But I felt it was not that simple. These weren’t business analysts or MBAs who responded to performance pressure with volume or force. These were experts in creative disciplines—instinctively curious, innately humble, often unsure how their natural strengths translated into the kind of leadership that executives recognized or rewarded.

So I took a different approach. I spent nights and weekends over several months developing a leadership playbook, crafted specifically for our design team. It featured seven chapters and more than fifty topics ranging from storytelling and persuasion to resilience and professional presence. Each topic was tied to Ally’s vision and values and offered clear behavioral guidance, including an action plan for how to cultivate, demonstrate, and activate leadership behaviors in an authentic way that played to individual strengths.

The playbook was a cultural touchstone. Designers could see themselves in it. Managers could use it to coach more effectively. It was written to reframe leadership presence as a pattern of service, curiosity, and clarity; a set of behaviors that could be grown with intention. It gave the team a common language for influence and a structure for developing it without compromising who they were.

What started as an act of resistance became an instrument of clarity. And in a moment when ambiguity and disengagement threatened to take hold, this book helped our team reconnect to the purpose, pride, and personal agency that define what leadership really looks like in a creative practice.

One of the most consistent challenges I’ve seen across teams—regardless of size, maturity, or culture—is misalignment between a person’s instincts and the nature of the problems they’re asked to solve. Talent isn’t the issue. Engagement is. Designers often excel at their craft but struggle to find consistent momentum or confidence because the work they’re assigned doesn’t match the way they think, strategize, or create under pressure.

After years of diagnosing this pattern through observation, coaching, and performance development, I distilled what I’d learned into a framework I call Five Dimensional Design™. It’s a theory that developed while I was building Rockturn, drawn from one of its core taxonomies. The idea is simple: not all design work is the same, and neither are the people doing it. By identifying distinct “dimensions” of problem-solving within product development that align with certain temperaments, we can better align individuals with those temperaments to the kind of work that energizes them—not just the nearest work that needs doing.

The framework focuses on problem-solving temperament, and the ways in which designers navigate ambiguity, pressure, and complexity. Some are theorists who thrive in conceptual stages. Others are refiners, drawn to detail, precision, and iteration. Some are best when planning, others when adapting. The real power of the framework lies in its potential to diagnose fit, revealing whether performance issues are actually misplacements, and whether low morale is a symptom of context, not competence.

While this is a nascent theory that is yet to be validated inside an organization, its roots are deep. It reflects the synthesis of everything I’ve learned about how people operate when the stakes are high and the context is unclear. It’s a strategic lens for talent planning, coaching, and development. And it’s a safe bet that the right kind of work, matched to the right kind of mind, will transform not just output, but outcomes.

Rockturn wasn’t built to fill a knowledge gap. It was built to confront a leadership vacuum—one created by accelerating complexity, commoditized creativity, and a creeping sense among designers that their tools were evolving faster than their judgment. After 25 years of leading design in highly regulated, high-stakes environments, I could see a pattern forming: the more sophisticated our systems became, the more pressure designers felt to operate like technicians instead of strategic thinkers. The result was growing disengagement, plateaued potential, and a quiet resignation about what their role could actually become.

So I stepped away from practice to build a platform that could support something I hadn’t yet seen: not a system to enforce consistency or showcase artifacts, but a living, navigable architecture of judgment, context, and capability. A way to help people rediscover what it means to think creatively and act confidently in the face of disruption. That platform became Rockturn, a knowledge engine that contextualizes principles, methods, and theoretical frameworks to amplify strategic thinking and confidence in problem-solving.

From the beginning, I developed Rockturn along two tracks: Head and Heart. One was built to cultivate curiosity, offering a compendium of insight and interdisciplinary knowledge to support practical growth. The other was designed to foster ambition and courage—to reframe disruption as a creative opportunity and restore a sense of purpose in the face of technological change. The platform had to deliver both: insight without ambition is theoretical; ambition without insight is directionless.

That tension is embodied in the “surfist” mindset, the core philosophy around which Rockturn was conceived. Like a big wave surfer on the ocean, a surfist is someone who recognizes the waves of change not as threats, but as forces to be understood, respected, and ridden with intention. To give form and substance to this metaphor, I published a manifesto at Rockturn outlining ten surfist principles rooted not in fear or hype, but in humility, curiosity, and the will to adapt with perseverance and grit.

Building Rockturn meant operationalizing everything I’d learned about enablement, leadership, and strategic problem-solving. I used AI as a force multiplier, engineering a human-in-the-loop workflow that allowed me to research, synthesize, and refine over 600,000 words of original content in just six weeks. That’s the equivalent of ten full-length books, distilled, structured, and surfaced across five taxonomies and 1,500+ topics—all designed to help designers expand their influence by acquiring a broader base on insights on business, technology, and human behavior.

Dive deeper into my approach to development and growth: