I frequently weigh the technical debt of requests.
I focus on the desired outcomes more than requested solutions.
I communicate changes and issues to team members quickly.
I outline project team member responsibilities early and often.
I frequently shadow users when gathering requirements.
I know when a request may go against best practice.
I try to keep project stakeholders aligned on project goals.
I can explain Salesforce's multitenant architecture model.
Transparent communication is one of my strengths.
I frequently communicate status updates to project stakeholders.
I'm familiar with Salesforce platform limits (e.g. DML statements, CPU limits, etc.).
I feel comfortable gathering requirements from users.
I always dig into the reasons behind a stakeholder's request.
I find it easy to say "no" to project stakeholders.
I know how to 'bulkify' triggers and/or flows.
I am comfortable working with different user personas and types.
I give my users helpful tooltips and error messages.
I always add descriptions to my custom fields in Salesforce.
I push process to fit systems, rather than bend systems to meet process.
My users know where to find important documentation on the org.
I understand that Salesforce customizations can decay over time.
I frequently say 'no' in order to prevent scope creep.
I feel comfortable offering alternatives to a bad request.
I stay away from over-engineered solutions.
It is easy for my users to understand important documentation.
I know when to use a standard vs. custom object in Salesforce.
I know how to read an entity relationship diagram.
It is easy for me to get adoption of my solutions.
I frequently build user stories to understand use cases.
I work directly with the end users when I build a solution.
My documentation is frequently updated to remain accurate.
I know which automation tools present the most and least potential technical debt.
I am confident in my knowledge of relational databases.
My projects always begin with a project plan.
I can articulate the difference between a lookup and master-detail relationship.
I can message the reasoning behind a denied request.
Database normalization is a topic I understand.
I'm comfortable building test cases, user stories, and project documents.
I recognize the over-customized portions of my org.
My colleagues always know the desired outcome of the project.