MVP and Salesforce Designer
Cross-skilling builds a common designer-developer language
Good collaborators never want to back a teammate into a corner. To avoid this, Loftis looks for the limitations and constraints early on.
“That helps us build a better story and really solve a problem,” he said. The Salesforce platform provides guardrails. So he asks every designer if they’ve created a Trailhead account, a dev or demo org, and bookmarked Salesforce Lightning Design System (SLDS) pages.
He wants them to know about API limits and data maximums. After all, it’s free and easily accessible. “If not, I worry.” This comes from lived experience. Early in his career, he threw designs over the fence america phone number list to development without any technical knowledge.
Today, Loftis is capable with CSS and HTML – and wants you to be, too. “I’m gonna leave you alone in JavaScript. But I think that you should even know that.”
Here’s why: Small design decisions can constrain many Scrum teams. A custom design may take three dev teams six months to build with custom APEX and Lightning Web Components (LWC). Alternatively, a page layout with declarative configuration may take one developer three weeks.