Evolving DesignOps Questions & Answers

Evolving DesignOps Questions & Answers

John Holt, Software Designer

Q. Tell us about yourself and your experience as a Software Designer.

Software Designer, that is my new go-to moniker moving forward, or flashing-back. UX design is one of many design principles that I specialize in, and Lean UX is my preferred research and testing methodology. I have been at the forefront of major industry shifts from the evolution of UX from a digital transformer to now, an AI-force multiplier.  My career begins with the digital transformation of a print Civil Rights journal in 2003, where I managed remote production from the Paris – a pioneering first using Timbuktu VoIP software. I’ve led 0-1 product discovery and design for startup and legacy B2B platforms in regulated industries like maritime safety (American Bureau of Shipping), AI lifecycle governance (Southern California Edison), and logistics (UPS, XPO). As well as, many retail and enterprise brands from early in my career like Macey’s and AT&T.

Recently, I’m actively building a DesignOps management system for deterministic AI design systems for enterprise. I hold the Microsoft Azure AI Essentials and Atlassian Agile Project Management certifications; for a few years now, I’ve been actively building the governance layers and operational frameworks that enable organizations to integrate AI without sacrificing quality, trust and predictability. I see UX design evolving from a service role into a regulatory governance function of frontend performance, ensuring legal compliance, usability stewards, and accessibility evangelists for a safe “deterministic” AI-driven future.

Currently, my work supports proactive risk mitigation, regulatory compliance, and design continuity. Expertise in systems thinking and 0-1 startup environments with complex challenges. I’m leading AI experience design for enterprise platforms, with deep expertise in agentic workflows, prompt engineering, and adaptive design systems.

Q. What inspired you to pursue a career in software design?

My inspiration came from my early work as a journalist and graphic designer; the realization that design could be a tool for empowerment and operational excellence. In 2003, I led the digital transformation of Greater Diversity News a regional Civil Rights journal. I transformed the print production into a digital process using PDFs and design software like Quark and InDesign. GDN was facing financial challenges like many other publications when online news took over. It was a time of innovation, and I was transitioning to GUI design and developing interfaces in HTML and CSS. I later moved into UX research at AT&T, where I discovered that the most satisfying work was uncovering solutions to complex usability problems.

Q. Walk us through your software design process, from identifying a problem to delivering the final solution.

My process is rooted in Lean UX, systems thinking, and a new DesignOps discipline that enables design departments to scale and integrate deterministic AI systems responsibly.

Discovery & Research: I start by understanding the problem space through stakeholder interviews, user research, and competitive analysis. I use mixed-methods research to build a complete picture of user needs and business goals.

Synthesis & Definition: I synthesize research into personas, user journeys, and empathy maps. I work with PMs and engineers to define scope and map out user flows that balance user needs with technical feasibility. I move into rapid sketching and low-fidelity wireframing, then refine into high-fidelity, interactive prototypes in Figma. I use component libraries and design systems to ensure consistency, this is the foundational layer of DesignOps that allows us time to innovate. I test prototypes with real users early and often using tools like Maze and Hotjar. I analyze feedback and iterate.

Governance & Build: This is where the paradigm shifts. With Figma’s new Code Layers and tokenized design systems, I’m building the governance layer that encodes design constraints, rules, and conditions into the output code layer. This ensures the frontend is predictable, compliant, and performant. I work directly with engineers to unify UX and engineering into a single, powerful force, using DesignOps frameworks to ensure ethical, compliant, high-trust AI production becomes a practical reality.

Q. Describe a product or feature you designed that you’re most proud of. What was your role, and what impact did it have?

I’m most proud of my work on the enterprise AI prompt portal for Southern California Edison (SCE). I led the end-to-end (0-1) UX design for this regulated AI-lifecycle management project, working through Logic2020. My role was to establish standardized AI adoption across teams with varying technical expertise. I conducted discovery research to identify adoption barriers, including varied AI literacy and lack of UX standardization. I created adaptive user flows and built a fully interactive prototype for stakeholders. The real breakthrough came when I pushed the project through Figma Make. The obstacles and possibilities I discovered during that process ultimately led SCE to embrace a design-to-code automation pipeline with AI features that hit the mark. This project demonstrated that the future of UX is about treating code as a design material and using DesignOps, tool standardization, governance, and operational frameworks; the infrastructure that enables design teams to deliver higher-quality experiences at greater velocity. In the American Bureau Shipping project in my portfolio is something I’m particularly proud of. It is a complex problem-solving scenario that required a complete shift in the product direction.

Q. Describe a challenging design problem you faced and explain how you solved it.

One of the most challenging problems was at Applied Systems, where I worked on the discovery phase for their AI-driven insurance agency integration. The core challenge was unifying a legacy platform with a new, AI-native experience while preventing the AI from generating “hallucinated” code.

My solution was to treat the design system as a governance layer within a mature DesignOps framework. I collaborated with information architects to create tokenized constraints within our Figma design system. By defining governed, parameterized design tokens, we created a single source of truth that aligned designer, engineer, and AI workflows. This eliminated hallucinated code generation and ensured a unified experience across the legacy and new platforms.

This experience confirmed what I’ve been advocating: generative systems, when properly integrated through a mature DesignOps framework, enable design teams to deliver higher-quality experiences at greater velocity. It’s not about a new design methodology. It’s about the maturation of DesignOps into the operational discipline that enables design departments and outputs to innovate and scale.

Q. How do you balance user needs, business objectives, and technical constraints when making design decisions?

This is the core challenge for me and product design, and the answer has evolved, but remains similar – lots of new ways of describing the same software design processes. I approach it as a negotiation and a partnership. I always ground the conversation in user data. I share user journey maps or personas to show the impact of a decision on user experience and efficiency. It’s my job to intercede and solve painpoints created by clunky tech and reduce resistance to task completion. I frame design decisions in business language. At ABS, the 40% task time reduction wasn’t just a UX win; it was a massive business efficiency win.

Partner with Engineering: I involve engineers early in the process. But now, instead of just checking feasibility, we work together to build the governance layer that encodes business logic, user needs, and technical constraints directly into the design system. This is where DesignOps matures: we create operational frameworks that close the divide between engineering and UX design, making them one unified force. Product can then fully engage with innovation and business development without the burden of managing constant iterations and design pivots. My Atlassian Agile Project Management certification has been instrumental here. It gave me the frameworks to manage these trade-offs in an agile environment, ensuring we balance velocity with quality.

Q. How do you collaborate with product managers, developers, and other stakeholders during a project?

Collaboration is how I work best, and I see it as a continuous, transparent dialogue that allows us to iterate and ideate – the new design-to-code pipeline elevates this collaboration to a new level. I partner with PMs from the very beginning. We co-define problems, align on metrics for success, and prioritize work based on user and business value. I rely on them to navigate business strategy.  I involve developers early and often. But now, instead of just handing off mockups, we work together to build the governance layer. With Figma’s Code Layers and tools like Claude, we’re creating a pipeline where design and engineering are one unified force, multiplied over several verticals. Product can then fully engage with innovation and business development without the burden of managing design deliverables, constant iterations, and sprint velocity.

I run structured design workshops to align on vision. I present work in stages using prototypes to help stakeholders visualize the final product before a single line of code is written. The DesignOps frameworks I’ve built for ABS and SCE: tool standardization, component libraries, and documentation practice, are the operational infrastructure that makes this collaboration seamless, scalable and predictable.

Q. What design tools and software are you most proficient in, and how do they support your workflow?

My workflow is built around the new reality that “design is the code”. Figma is my primary design tool. I use it for everything from brainstorming with FigJam to building high-fidelity prototypes and advanced design systems. I’ve been on the cutting edge, building design-to-code pipelines with Figma Make, VS Code, and Claude. I’m deeply familiar with Figma’s latest features, Code Layers, Motion, shaders, generative plugins, and Weave tools, which allow us to treat code, motion, and shaders as design materials on the canvas.

I use Maze for unmoderated prototype testing and Hotjar for analyzing behavior on live sites. For deeper qualitative research, I’ve used Marvin. I love Jira and Confluence to document design decisions and align with the product team. This is a cornerstone of DesignOps, ensuring documentation and operational infrastructure scale with the team.

Front-End & AI Tools: My background in HTML/CSS/JS and React allows me to better communicate with developers. I hold the Microsoft Azure AI Essentials Professional Certification, which validated my understanding of AI infrastructure. I’m actively exploring Azure AI and Google’s A2UI to understand how AI can influence design workflows. I also use Claude Code and Claude Design for prototyping and design-to-dev workflows.

Q. How do you ensure your designs are accessible, user-friendly, and consistent across different devices?

Accessibility (WCAG 2.1): I build accessibility into the design system from day one, not as a final compliance check. I use accessible color contrasts, appropriate font sizes, semantic HTML, and screen reader compatibility. At ABS, I established their first UX standards by building a fully WCAG 2.1 compliant modular design system. This isn’t just good practice; it’s an ethical stance. As UX designers become architects of the frontend code layer, we must ensure accessibility oversight and put rails between people and AI dark UX practices.

I rely on governed, tokenized design systems in Figma defined components, styles, and variables that serve as a single source of truth. At Applied Systems, I used tokenized constraints to unify the experience across a legacy platform and a new AI-native system, eliminating design drift and hallucinated code generation. This is DesignOps maturity in action: tool standardization and component libraries that scale. As a consultant at Raibach Interactive Design, I routinely balanced multiple high-stakes projects for clients including UPS, Orkin, and ValGenesis simultaneously. My prioritization approach is systematic:

I start each week reviewing all project statuses, deadlines, and new requests, then create a clear action plan prioritizing work with the most immediate or critical deadlines. I proactively communicate with PMs and stakeholders to manage expectations. If conflicts arise, I discuss trade-offs openly and adjust timelines collaboratively rather than burning out.

I structure my day with focused deep work sessions for core design tasks (prototyping, research synthesis) in the mornings when I’m most productive, reserving afternoons for meetings and collaborative work. This approach, combined with my Atlassian Agile Project Management certification, ensures I deliver quality work across multiple projects without compromising velocity or design excellence.

Q. A sudden drop in engagement is a clear signal something is wrong. I approach this as a structured investigation:

Analyze Data: I dive into quantitative data using Hotjar or platform analytics. Are users dropping off at a specific step? Is there a new error? A sudden change often points to a technical regression or confusing UI update. Data tells me what I need so that.. the user can… I reach out to users through in-app surveys or short interviews to understand motivation and friction points. I partner with engineers to confirm there are no technical issues or bugs. Was there a recent deployment that could have affected this feature?

Re-validate & Iterate: If it’s a UX problem, I ideate on a solution, create a prototype, test with a small group, and iterate until the solution works. I then encode those learnings back into the design system’s governance layer to prevent future issues—treating the design system as the operational infrastructure that ensures quality, trust, and predictability.

Q. What motivates you to deliver exceptional product design, especially in a remote work environment?

What motivates me is the impact our work has on real people and the belief that design and AI together can be a force multiplier for human capability, rather than a replacement. Whether it’s saving a 15-person operations team 16+ hours a day, as I did with the mobile route management project, or enabling a team at Southern California Edison to adopt AI more effectively, solving complex human problems is my core driver.

In a remote environment, my motivation shifts to a deeper sense of ownership and discipline. It’s about being relentlessly proactive with communication and documentation, sharing prototypes early and often, creating clear documentation, and over-communicating my rationale. I’ve been working remotely since 2003, using early remote-access technology to manage production.