Design Process

As you probably already know that while the design process might look standard on paper, companies—and projects—rarely are. Sometimes you walk into a project mid-stream and find it’s fully waterfall, partially broken, or lacking structure altogether. Maybe there’s no time for user research, or worse, it was never even part of the plan.

Over the years, I’ve worked across a wide range of companies and design environments, and one thing is always true: no two are the same. That’s why I don’t believe in a one-size-fits-all design approach. As a designer, I’ve learned to stay flexible—adapting my process to fit the needs of the product owner, the subject matter experts, and the development team I’m partnering with.

There’s no single “right” way to design. As a seasoned designer, I’ve come to understand that being effective often means being adaptable.

Design Process

A successful design strategy is rooted in a deep understanding of the user. By applying Design Thinking and actively empathizing with users, we can ensure that their needs, behaviors, and pain points remain central throughout every phase of the design process.

This user-centered approach enables us to capture and address the full scope of the user experience—whether it's a customer or an agent—ultimately guiding us toward defining the right, most effective experience. The goal isn't just to design functional solutions, but to create meaningful, intuitive interactions that deliver real value and lasting impact.

Design Thinking for Salesforce

Ensuring alignment and continuity across different streams of work is essential to delivering a seamless and cohesive user experience in Salesforce projects. When development efforts are fragmented or inconsistent, users often encounter disjointed workflows, varied interfaces, and conflicting logic, all of which undermine the overall effectiveness of the solution.

To address this, it is crucial to create and adopt standardized libraries, design patterns, and reusable components that can be leveraged consistently across all streams. These shared assets not only accelerate development by reducing redundant work but also enforce adherence to best practices, improve maintainability, and foster collaboration across teams.

Moreover, establishing these common foundations provides a scalable framework that supports future enhancements and strategic initiatives. By building with reusability and extensibility in mind, teams are better equipped to evolve the platform in response to changing business needs without having to start from scratch.

In summary, standardization and cross-stream coordination are not just efficiency enablers—they are critical pillars for delivering a unified, high-quality Salesforce experience that can grow with the organization.