What Nonprofits Taught Me About Building Salesforce for Humans, Not Just Systems
Summary
The insight here emphasizes that Salesforce implementations must prioritize user experience and real-world workflows over just clean system design. It highlights how users reject cumbersome processes, opting for simpler external tools when Salesforce complexity impedes their work. The key takeaway is to approach Salesforce projects with empathy: observe users directly, ask broad questions, and design solutions that people actually want to use, thus boosting adoption and efficiency.
Takeaways
- Build Salesforce solutions by observing and empathizing with end users’ real workflows.
- Avoid overly complex processes that force users to find workarounds outside Salesforce.
- Ask open-ended questions unrelated to Salesforce to uncover true user needs.
- Prioritize usability and adoption over perfect system architecture.
- Nonprofit user experiences can provide valuable lessons for Salesforce implementations.
Salesforce is a tool. Tools exist to make work easier. When the tool makes work harder, people find other tools. My development director with the 47-click donation process wasn't wrong to use a spreadsheet. She was responding rationally to a system that ignored her reality. The system failed her. She didn't fail the system. When I taught Salesforce Administration at NYU, my students learned the technical skills: flows, validation rules, reports, security models, but the lecture I give most often is about empathy. About sitting with users and watching them work. About asking questions that have nothing to do with Salesforce. Because the best implementations aren't the ones with the cleanest architecture. They're the ones people actually use. Nonprofits taught me that. And every implementation I've done since has been better for it. The post What Nonprofits Taught Me About Building Salesforce for Humans, Not Just Systems appeared first on Salesforce Break .