Creating the perfect Salesforce app can be frustrating for everyone: admins, developers, consultants, customers, users. Do you know what you want to order? And what do you expect it to be when it arrives? Let’s talk about what you need to know to get the most out of solutioning in Salesforce. Walk away with a new approach to aligning wants, needs, definitions, and processes with stakeholders.
9. #CD22
What Is an Architect?
Salesforce Architects are big-picture thinkers
and in-depth problem solvers. They design
systems for the long-term that stand up to
high volumes and won’t fail at critical points.
Introduce the discussion. We are going to spend some time together here on what may seem completely unrelated to Salesforce. But, if you’ll trust me for the next few minutes and have an open mind, we are going to start by re-architecting your thinking. So the question is: is a hamburger a sandwich?
If we start with these basic ingredients, the “sandwich” could come out looking like a hamburger, a hot dog, a taco, or a pizza. And any of these would fill your hungry tummy but it might not be what you actually wanted.
I queried folks on Twitter about what they build for their customers. And a whopping 87.2% THINK they build what the customer needs. What they want vs what they need is an entirely different story. But, let me ask the audience: is there ever any difference between what you think the solution is and what is actually wanted or needed?
This is where an architect comes in. Whether you are an admin, a developer, an executive, a consultant, you may be called upon to play the role of an architect. With any luck, there is someone in your sphere who has these superpowers. They may not be the most technical person or the most hands on person. What you want is someone who can imagine that not only is a hamburger a sandwich but it could be a pizza, too. So, how do we think like an architect? The exercise we started with is a good beginning. Here are some more traditional thoughts.
Salesforce has created a path specifically designed to assist practitioners on their journey to becoming a Certified Technical Architect. Most times you are not going to need (or be able to find or afford) a full-fledged Certified Technical Architect. However, you should be thinking like an architect, no matter what your role is. I’ll provide some resources at the end that will help you on your Thinking like an Architect journey. And...
If nothing else, asking the right questions is critical to defining the correct information.
If you have children...
This sounds like a no-brainer but you would be amazed at how far off you can wander if you don’t understand and reiterate, constantly, the actual goal. Write them down. Revisit them. Put them at the top of every document and/or documentation.
What are some examples of goals?
Let’s talk about what comes after the all important goals question.
The team you are working with internally may be relying on you to be the SME, especially where Salesforce is concerned.
Document what you have so far. We’ve defined what it is we actually want to accomplish and for whom. We’ve defined what is important to the users and how we are going to measure success. The document or recipe is where our plan is actually created to make this happen. And, we are well on our way and have not said a single word yet from a technical standpoint.
Your recipe may look any number of ways but again the important thing is to align around the goals you have defined. This is where the technical experts begin to fill in the blanks and use their creativity to meet the goals as defined.
If the goal was truly a hamburger, that’s what you want to deliver.