Welcome to the Architect Mindset Self Assessment.
Please answer the following 40 questions to the best of your ability. If you haven't encountered a specific situation before, answer based on your assumption of your behavior in that scenario.
1.
I frequently shadow users when gathering requirements.
2.
I find it easy to say "no" to project stakeholders.
3.
I frequently weigh the technical debt of requests.
4.
I push process to fit systems, rather than bend systems to meet process.
5.
I know when a request may go against best practice.
6.
I try to keep project stakeholders aligned on project goals.
7.
I know when to use a standard vs. custom object in Salesforce.
8.
My colleagues always know the desired outcome of the project.
9.
Transparent communication is one of my strengths.
10.
I frequently build user stories to understand use cases.
11.
I know how to read an entity relationship diagram.
12.
It is easy for me to get adoption of my solutions.
13.
I focus on the desired outcomes more than requested solutions.
14.
I feel comfortable offering alternatives to a bad request.
15.
I can explain Salesforce's multitenant architecture model.
16.
I feel comfortable gathering requirements from users.
17.
I stay away from over-engineered solutions.
18.
I recognize the over-customized portions of my org.
19.
I am confident in my knowledge of relational databases.
20.
I frequently communicate status updates to project stakeholders.
21.
My users know where to find important documentation on the org.
22.
I give my users helpful tooltips and error messages.
23.
I'm familiar with Salesforce platform limits (e.g. DML statements, CPU limits, etc.).
24.
It is easy for my users to understand important documentation.
25.
I can message the reasoning behind a denied request.
26.
I work directly with the end users when I build a solution.
27.
I can articulate the difference between a lookup and master-detail relationship.
28.
I communicate changes and issues to team members quickly.
29.
I understand that Salesforce customizations can decay over time.
30.
I'm comfortable building test cases, user stories, and project documents.
31.
My projects always begin with a project plan.
32.
I always dig into the reasons behind a stakeholder's request.
33.
I know which automation tools present the most and least potential technical debt.
34.
I frequently say 'no' in order to prevent scope creep.
35.
I know how to 'bulkify' triggers and/or flows.
36.
I am comfortable working with different user personas and types.
37.
I always add descriptions to my custom fields in Salesforce.
38.
I outline project team member responsibilities early and often.
39.
Database normalization is a topic I understand.
40.
My documentation is frequently updated to remain accurate.
