Vol. 15 · No. 1
raymayfield.com
Design process
No two projects are the same
The design process might look standard on paper, but 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 it was never 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 approach. I stay flexible and adapt my process to the needs of the product owner, the subject matter experts and the development team I’m partnering with.
Alignment across streams of work is what makes a Salesforce experience feel seamless. When development is fragmented, users run into disjointed workflows, mismatched interfaces and conflicting logic.
The fix is shared libraries, design patterns and reusable components that every stream uses. They speed up development by cutting duplicate work, keep teams on best practices, make the platform easier to maintain and help teams collaborate.
Those shared foundations also give you a framework that scales. Built for reuse and extension, the platform can change with the business without starting from scratch.