The situation
Anza was a growing enterprise platform with complex workflows spanning solar, storage, and transformer products, six distinct surfaces for buyers and suppliers. But when I arrived as the company's first Lead Product Designer, design operated downstream. The team received requirements and executed on them.
There were no documented design principles anyone could point to when evaluating a proposal. No structured process for reviewing design work with stakeholders across the organization. And no formal path for a designer to say "I found a problem worth fixing" and make the case for prioritizing it.
Good design work could happen, but it depended on individual relationships rather than repeatable process. And usability issues that weren't already on a product manager's radar tended to stay unfixed.
Design principles
I authored Anza's design principles and presented them at the company's internal "What the Tech" summit, a talk to the full product, engineering, and business organization. The goal was to give every team a shared vocabulary for what good design meant on our platform, so decisions could be evaluated against criteria rather than taste.
Four core principles, each grounded in how they applied to Anza's specific context:
- User-Centric Mindset. Start with the user. Design based on real behaviors and needs, not assumptions. Build feedback loops through user focus groups, A/B testing key workflows, and direct observation of how buyers actually navigate the platform.
- Interaction & Usability. Make every interaction clear, consistent, and forgiving. Acknowledge actions immediately, prevent errors early, and make recovery simple. A buyer evaluating a multi-million-dollar energy purchase shouldn't have to stop and think about how the interface works.
- Visual & Aesthetic. Use typography, color, and spacing to communicate, not decorate. Maintain brand consistency and accessibility standards. The goal was design that felt intentional and cohesive across all six product surfaces.
- Process & Mindset. Design is a team sport. Work cross-functionally, ship iteratively, measure what matters, both qualitative and quantitative, and document what you learn so the next project starts further ahead.
Two supporting principles completed the framework: Progressive Disclosure (reveal complexity only when it's needed, so the first encounter with a feature feels approachable rather than overwhelming) and Content-First Design (clear, human-friendly language guides users better than clever UI).
The Design Review Board
I established a cross-functional Design Review Board and wrote the framework that governed how it operated. The DRB brought together design and QA leadership, engineering leadership, product leadership and PMs, business leads, the CTO, and technical leads, every discipline that had a stake in how the product evolved.
I designed it as a six-phase process, not just a meeting. Work moved through early design experiments, async feedback in design channels, iteration and refinement, customer validation, and final polish before reaching the DRB itself. By the time I presented a proposal, it had already been pressure-tested with internal feedback and, where possible, real users. The board's job was alignment and a decision: approve, approve with changes, or send back with clear direction, not to brainstorm or bikeshed.
A ground rule I wrote into the framework: feedback had to be tied to user needs, business goals, or feasibility. Personal preference wasn't actionable feedback. And once a decision was made, we moved forward.
Critically, the DRB wasn't limited to PM-assigned work. It was also the mechanism I used to advocate for improvements I identified on my own: usability issues, design debt, and interaction patterns that nobody had filed a ticket for but that were creating real friction for users.
What went through it
The DRB became the path for every significant design improvement I led at Anza. Some were assigned; many I initiated after finding friction in the product myself:
- Navigation and filtering overhaul. I spotted that buyers were working around clunky filters rather than using them, friction nobody was reporting. Brought the redesign through the DRB; filter usage more than doubled after it shipped.
- Page header unification. Inconsistent headers across product areas meant every surface felt slightly different. I designed a unified header pattern with sticky behavior so context stayed visible during long scrolls, and brought it through the DRB as a platform-wide standard.
- Ranking table toolbar. The data tables buyers used to evaluate products had controls scattered in different places. I designed what I called a "toolbar," a row of contextual actions above the table that consolidated everything into a consistent, predictable pattern.
- Kebab menu standardization. Action menus across the platform used different patterns, different placements, different behaviors. I audited them and proposed a consistent kebab menu component that became part of the design system.
- Create Project sheets. Creating or editing a project required a full page transition, pulling users out of their workflow. I proposed moving the flow into a right-side sheet component, preserving background context, reducing perceived friction, and aligning with the interaction patterns we were establishing across the platform. I presented the tradeoffs and asked engineering whether keeping the energy rate form inline (rather than opening yet another modal) was feasible.
- Solar Pulse dashboard. What became Solar Pulse, a new product surface offering live market data, started as a DRB proposal to replace the static homepage with something buyers would return to daily.
What changed
The principles gave everyone a shared reference point. Instead of debating whether a design "felt right," teams could evaluate decisions against documented criteria, and I could reference the principles when making the case for why a particular improvement mattered.
The DRB gave design a repeatable seat in the room. Improvements didn't depend on catching the right PM in a hallway conversation or waiting for someone else to notice a problem. There was a process, it had executive visibility, and it worked.
The combination meant design could influence what got built, not just how assigned features looked. Several of the improvements I brought through the DRB, including the navigation overhaul, the dashboard, and the page headers, all shipped and became core parts of the platform that other case studies on this site describe in detail.
Reflection
Process scales; personality doesn't. Building a review board and documenting principles meant design's influence didn't depend on any one relationship or my personal persuasiveness in a meeting. It was a system that could survive someone having a bad day.
The best way to earn a seat at the table is to keep showing up with well-reasoned proposals. The DRB wasn't just a forum. It was proof that design could identify valuable problems, not just solve the ones it was handed. Each time a design-led improvement shipped and moved a metric, the next proposal got an easier hearing.
Principles are only useful if people use them. Presenting at the summit and referencing the principles in every DRB review kept them alive as a working tool. The alternative, a well-designed principles deck that sits in a shared drive, is a common failure mode for this kind of work.
Design's influence doesn't come from having good taste. It comes from having a process that lets you prove it.