What Makes a Salesforce Professional Valuable

It’s a big world for the Salesforce professional. There are tons of features to learn, tools to master, certifications to grab and trails (Trailhead) to be explored. There are weekly meetups, online communities, conferences, webinars and workshops. If desired, one could LITERALLY eat, breath, sleep, and dream Salesforce.

To a large extent, I too am involved in the community. I have certifications. I do the Trailheads (Expeditioner), and I try to stay abreast on new tools and functionality. I believe it is my responsibility as an admin/developer to keep learning.

However, I sometimes have a fear that Salesforce professionals dance on the precipice between professional understanding of the tool and obsessive loyalty.

The obsequious professionals collect and treasure digital accolades like badges and certifications a little too much and it’s common for many to have a few years of professional experience in the application development world.

To be clear, this isn’t a BAD thing. In many ways, this is not dissimilar to my experience. See my previous article: https://www.linkedin.com/pulse/perfect-detour-from-english-major-personal-trainer-grant-ongstad/.

In my work experience as an Admin/Developer I try to keep remembering two simple things:

1)     Serve the Business, Not the Application

Unless you work for Salesforce, Salesforce doesn’t pay your bills – the person or organization that signs your check does. They use Salesforce because it may be a tool that can solve their problems and help scale their business and, in some cases, it may not be.

They do not care if you use flow, process builder, workflow rule, or apex they only care if you solved their problem. If Salesforce reporting cannot handle their unique groupings and summaries as well as an existing excel report – don’t be afraid to tell them!

Businesses don’t just hire Salesforce professionals because they know Salesforce, they hire them in the hopes that they can solve their problems.

Whether you are an Admin, Developer, Cloud Consultant, Salesforce CPQ expert, Architect, or all of the above, your first allegiance is to the business and its requirements.

My boss once told me that tools and applications come and go but if you can understand the goals and mission of the business, how it operates, and where they are heading that I’d always be in demand.

2)     Be a Solution Architect

Every change, customization and enhancement should be considered in relationship to the entire system architecture. You are not just an order taker who reads a requirement and implements a change without question. What effect will this change have on existing customization, user experience, reporting etc.? Are you making assumptions about how users are interacting with the system vs how they are actually using it?

A solution architect thinks ten steps ahead when implementing or recommending a solution rather than jumping to the neatest and shiniest tool. Sometimes the solution is a change in an internal process.

I don’t intend to throw shade on those who truly love Salesforce. For many of us, the tool has provided a rewarding career path and I believe the demand will only continue to grow. It is also tremendously important to have skilled users of the tool. Everyone who wears the badge (yes, on Trailhead too) of the Salesforce professional should have an in depth understanding of it.

I only hope that we never lose sight of the customers we serve and of the skill that make us most valuable: The ability to understand and solve problems.

Advertisements

The BSA’s of The Business Systems Analyst

rawpixel-com-565456-unsplash

My job title can sound pretty vague, ‘Business Systems Analyst’ sounds like a few important words strung together. To those outside of the software development world, and perhaps even to those inside, it’s anyone’s guess to what that means. Whenever I’m asked ‘what I do’ , I typically respond one of three ways:

“I am in Software Development”

“I am in IT”

“I wear many hats…”

All are true, but none of them – even when combined, paint a complete picture.  I did a bit of research to find out how others would describe the role of the Business Systems Analyst. I found some pretty insightful things, here is a video from the Technology Profession YouTube channel that does a great job highlighting the job responsibilities as well as the main skills needed. For me, the easiest way to define the role is to break it up into three fundamental components that are already included in the title: Business Systems Analyst.

is for Business

The first, and most important of the three. This is who the Business Systems Analyst serves. The BSA must know the Business, it’s mission, and it’s goals, including an understanding of how the business generates revenue, how the business positions themselves within their market and the overall growth strategy.

I often find myself going down a rabbit hole of tasks and emails before bringing myself to and thinking how does what I am doing effect the goals or mission of my organization?

is for Systems

This is the technological arm of the BSA. Each business relies on systems to successfully deliver their product or service to the customer. A BSA must understand the main systems that the business unit utilizes including the most common use cases, their limitations, and gaps.

The BSA is also responsible for knowing the data each system relies on, how that data interacts with other systems, and the importance of the data.

Perhaps equally as important as knowing current systems, the BSA will need to know how to develop and manage new systems. To do this, he or she should understand the software development life cycle and be relatively up to date with current technologies and trends in their space.

is for Analyst

This is the creative problem solving arm of the BSA. Ultimately, a BSA’s key value proposition is in their ability to implement and come up with new solutions.

Understanding the current state is a fundamental part of the role and the other part is discovering how to improve. The BSA continually challenges the way things are done and looks for ways to optimize.

On the road to optimization, the BSA collaborates with the business, developers, and stakeholders to create a wonderful and hopefully adopted solution.

The Business Systems Analyst is a highly enjoyable and rewarding role. The BSA gets to collaborate with many different business units, take part in the creativity of the development team and contribute to the goals of the business.

If you’re a BSA or work with BSA’s what are some other things you think are important to the role?

The Perfect Detour – From English Major to Personal Trainer to IT Professional

coffee-cup-desk-pen

 

A few months before my last day of college I no longer wanted to do what I went to school for – to teach English at a university. Meanwhile my best friend and colleague was off to his graduate program the following semester, still burning with the same passion he started with. The morning after my college graduation ceremony, I remember waking up with a sinking feeling in the pit of my stomach. The following years were a struggle, both financially and emotionally. I did not know what I wanted to do, or what I was necessarily good at. I submitted resumes for various jobs that involved writing – technical writing, marketing, PR – until eventually taking what I could get. During the following years, I worked several jobs in different jobs and industries.

Until recently, I believed that all of the time spent working outside of my current career in IT was a waste. I was embarrassed over my resume – a hodgepodge of unrelated experiences, certifications, and education. Looking back, I can see that these past experiences, education and employment were leading and shaping me for my future career in software development. A career I get to wake up excited for. A career I am fulfilled by and a career that marries what I enjoy with what I’m good at. I stand now, proud of my resume, despite its eclectic nature. Here are the experiences I will likely never remove from my resume along with some of the skills I’ve learned, borrowed, and abandoned.

English Major

I’m often met with shock when I tell people I Majored in English. ‘Don’t you already speak English?” some would quip. At first, my education would seem like a complete 180 from my current role. That couldn’t be further from the truth.

What I learned

·        How to write clearly

Until recently, I took my writing education for granted. After all, everyone knows how to write! Now I realize how rare the skilled writer is – especially in the corporate world. A skilled writer is able to quickly, clearly and concisely communicate ideas.

In software development writing is a big part of what I do. From user training documentation, to functional specifications and requirement documentation and even daily email communication, writing is one of the most indispensable skills I possess. When technical documentation is being written, or a communication is being sent out to multiple users, I have to make sure that it is able to be processed and understood. The communication has to be free of syntax or grammatical errors.

·        How to quickly generate ideas

Nothing puts the mind to work like having to come up with a ten-page essay the following day! I once had a final where I was required to write five essays in two hours based on prompts I had never seen until then. As an English major, coming up with what to write about is just as challenging and as important as grammar, syntax, and style. We constantly employ brainstorming techniques like round robin, reverse thinking, stream of consciousness and any other creative means to get us to where we need to be.

In software development, coming up with ideas to solve problems or build solutions is an essential part of our work. You can have all the technical skills in the world, but if you don’t know how to think on your toes you will most likely never get the chance to employ those skills.

·        How to take criticism

In my Freshman year, it was a terrible feeling to get an essay back covered in red slashes or to sit patiently in a circle while each of my classmates told me what they didn’t like about my short story. In later years, I learned to appreciate such criticism and even look forward to it. I knew it was making me a better writer. Unfortunately, I’ve learned that a lot of people in the corporate world do not take criticism well. Most people think their idea is the best idea. The problem is they have not been able to detach their self-worth from their ideas and may view the criticism as a judgement of themselves. English majors learn to distinguish between the two and take advantage of good criticism.

In software development it is necessary to willfully accept the criticism of others. A technical lead may have some ideas to make your code allocate memory more effectively. A business user might have a different opinion on the layout of a page. The important thing in software development is to come up with the best solution, even if it is not yours.

What I borrowed

·        The writing styles of my peers and favorite writers.

Some of my communication requires short, concise, sentences. Yet, others may call for elaborate and descriptive sentences. As an English major, I learned different ways to write the same thing.

In software development, and in the corporate world in general – it is important to not only write clearly, but be able to write for any audience. There is a different style of writing in user training than design documentation or functional specifications. Some messages may need to elicit other feelings that cannot be seen in the words themselves – like urgency, confidence, or even reluctance. Not everyone responds best to the same writing style so it is important to be able to call upon many.

What I abandoned

·        Trying to be like others

There is a fine line between being influenced and copying. It was at times tempting to try to write exactly like others, or about what others write about since so much of an English major’s time is spent reading and writing about the works of others. Doing this masks true potential and covers up an original style that is harder to build but much more effective when it is used. I’ve noticed in the corporate world, many people take their own abilities for granted and would just rather continue doing things the way they have always been done or how others would do it.

To be successful in software development bringing out an original idea requires original thinking. Finding an effective way to do something is much more important than continuing the old way. It is important to actively think about the process being done, and how it can be improved.

Mortgage Loan Officer

What I learned

·        How to sell

Before working as a loan officer, I had generally looked at sales in a stereotypical light. I imagined a skinny man in a colorful suit, generously applied cologne, and slicked back hair who only cared about one thing: money. I learned that selling is more than that, and its applications are much wider than most would imagine. An employer is sold by a candidate and hires them for the job. A husband sells himself to his wife when reciting his vows, assuring her that he will be there to love her until death. Zig Ziglar, one of the most listened to sales gurus said ‘Selling is not something you do to someone, it’s something you do for someone’. If you believe what you are selling will help someone, there is no reason to feel ashamed.

A developer can create the best solution with all the bells and whistles – but if he or she is not able to sell the benefits of the tool to the end user, or the customer – the tool will never roll out. Many of us unfortunately know the feeling of working on a project for months and months, only to not receive sign-off or buy-in from the business.

What I borrowed

·        The optimism attitude

 “Either you run the day or the day runs you.” – Jim Rohn

There is a mentality held by almost every successful salesperson. It is one of relenting optimism. In sales, you have to live call by call, imagining an easy sale every time. The failures of the day before should not influence how today will go. The best salespeople go to work excited, and excite others. They exude energy and positivity and motivate others. They operate on synergy and know how to use momentum.

In software development it may be hard to see the light at the end of a tunnel during the middle of a seemingly endless and evolving project. Yet everyday has to be given the same energy and creativity of the last – an optimistic person can make a big difference for team moral

What I abandoned

·        The get rich quick mindset

It’s common for sales jobs to highlight their most successful employees’ accomplishments, and my job was no different. At any moment in the break room you could hear the conversations. “Did you hear John makes twenty thousand a month? Can you even imagine?”. There is nothing wrong with trying to motivate employees but unrealistic expectations do more harm than good. Several employees in my hiring group quit a few weeks after they finished training when they realized that the ‘Easy Money’ was not as easy as they were led to believe. The truth was that the employee making twenty thousand a month had been working in the industry for a very long time, attended sales seminars on the weekends and worked ten to twelve hours a day. There may very well be an easy, quick money sales job out there – Let us know when you find it.

Personal Trainer

 What I learned

·        How to track and measure success

A personal trainer is responsible for keeping others accountable. They need to be able to set realistic goals for their clients, goals that are big enough to make an impact and happen quick enough to be motivating. The goals require creativity, and are usually never the same between clients. One client may have a goal of reaching ten pull ups in one minute, another may want to lose inches while another only wants to lose weight. Setting an unrealistic goal that is not accomplished can cause a client to lose interest. I communicated regularly to my clients about their goals and expectations, showing them where they could improve and where they are doing well, treating each client like a project you have to manage.

Executives speak the language of metrics. They want to know the facts and they want to know if the investment in your project was a good idea. Having clearly defined goals and metrics ready at any moment only helps the possibility of a successful project.

What I borrowed

·        The advice of my clients

The best part about working with people is listening to people. Everyone has a story. Everyone has a slightly different motivation. I learned that the best way to get clients to listen to you is to listen to them. Many of my clients enjoyed our time together because they were able to talk to me about their day, their challenges and even share some aspects of their personal lives. I was able to learn a lot from their personal experiences and life lessons. While they gained from my knowledge of exercise and diet, I gained from their knowledge of business, parenthood, or marriage.

What I abandoned

·        Blaming others

As I mentioned previously, people have different motivations. Exercise is not an integral part of their lives like so many personal trainers. While some may disagree, I’ve noticed that most ‘Gym Rats’ have not yet started a family or work in professions that afford them the free time to exercise. Instead of blaming a client for not hitting a goal, or cancelling on a session, I thought “How can I motivate this person”? Is there an expectation I am not meeting?”.

In my current position, while there is plenty of opportunities to cast blame around I’ve tried to instead focus on what I can control and ways I can improve my communication to better manage expectations.

In a Stanford commencement speech, Steve Jobs said “You can’t connect the dots looking forward; you can only connect them looking backwards. So you have to trust that the dots will somehow connect in your future”. As I remain anxious about what the future holds, I trust that as long as I attempt to actively learn from my experiences, they can be made to strengthen my future positions – whatever they may be. I hope that this article gives others who may be anxious about their future career some hope and perspective.

How to Study for The Salesforce Platform Developer I Exam

CloudPic

If you’re like me, the first thing you do when you decide to go for something is to peruse the internet for advice from people that have done it and that is exactly the first thing I did when it came to both my Salesforce Administrator and Salesforce Developer certification. When I was up late after work studying for the Platform Developer I exam, I would catch myself half thinking/half praying ‘God, if I pass this test I promise to help others!’ Part of the reason I’m writing this now is because although I found it difficult to find some of the answers I was looking for, I did find many valuable articles from people who had ‘blazed the trail’ before me. This is my attempt to give back.

I wouldn’t consider myself very technically experienced. I have my Bachelor’s degree in English Literature and up until 2014, I’d never opened up an excel file. I do, however, possess a mindset that wants to solve problems and enjoys thinking through them – if you can keep that mindset, you’re on the way to passing the Developer Exam.

 

1.      Use the Salesforce Study Guide to plan

This is important. My first mistake was quickly veering off track from the study guide and down the rabbit hole of development documentation and YouTube videos of Dreamforce speakers. At one point I was attempting to actually read the entire Apex Development Workbook (now deprecated), making stacks of flash cards about Rest API, asynchronous callouts, and memory allocation limits. If you don’t know what most of that is, don’t worry you won’t need to for this exam. Use the Salesforce Study Guide, and what’s on the Salesforce Study Guide as the foundation of your studying. Download the guide here.

     Begin by reading the study guide over and over until you know what is in and out of the scope of the exam. Next, write down each section of the exam in order from least familiar to most familiar. Draw a line dividing the top half of the list from the bottom and apply an 80/20 rule – plan to spend 80% of your time studying in the top half (the less familiar) and 20% of your time on the remainder.

2.      Take the Developer Beginner Trail from Trailhead

Besides experience, Trailhead is the best resource out there for learning Salesforce. If you are unfamiliar with Trailhead, it’s a series of guided learning paths for business users to developers where you can earn badges, track progress and plan your learning curriculum. If you have not yet signed up, do yourself a favor and do it now! https://trailhead.salesforce.com/en/trails. You will need a developer org if you want to follow along with most of the training. You can get one here.

3.      Track by Comprehension, Not by Time

Remember, quality over quantity! I would avoid planning in time chunks. Just because more time is spent studying, does not mean more is learned. Focus on what specific thing you want to know when you’re finished with a study session. For example, looking at section five of the Study Guide you might take ‘Describe how to use basic SOSL, SOQL, and DML statements when working with objects in Apex’ under the Logic and Process Automation and decide to learn the how to write three types of SOQL statements in one session and the limitations of SOSL statements in another. The best part about doing this is that you will hopefully leave every session feeling accomplished

4.      Utilize Different Methods of Learning

Spend time in Salesforce Documentation reading, Trailhead and YouTube learning, and a development org doing! I know I have learned something when I can explain it and when I can think of ways to use it. Take what you want to learn – Read about it, watch someone do it, and finally do it yourself.

5.      Know Why and When

Most of the exam consists of scenario based questions. You’ll never pass the exam if you only know terms and their definitions. After reading and learning about a functionality, I ask myself why I would need it and when I would use it. Why should one use process builder over a workflow? Come up for a scenario or use case for both!

6.      Utilize Salesforce Training

If your company has premier support, you have access to a hub of instructor led training videos! Navigate to ‘Help & Training’ in your org and look for the training section. Don’t sweat it if you do not have premier support, there is still plenty of other information out there.

7.      Salesforce Ben

Salesforceben.com is an awesome resource that I have used for both of my certification. There is a great article about the Platform Developer I certification here: http://www.salesforceben.com/platform-developer-certification-guide-tips/. They give an awesome breakdown of the exam.

8.      Answer and Ask Questions in the Support Forums

Even if you’re not an expert in Salesforce Development yet, try to help others with their problems. It is a great way to receive use cases and scenarios that can provide you with experience and hands on learning! You probably won’t receive the vote for the ‘Best Answer’ all the time, but it begins the process of actively thinking about how to implement development solutions .

9.      Don’t Burn Yourself Out

No need to pull an all-nighter! Give yourself plenty of time, you can only take in so much at a once. If you have accomplished your ‘learning goal’ for the session, take the rest of the day off! Go outside and enjoy some nature.

 

I hope this article has provided some good advice you can utilize to prepare for the Platform Developer I and other Salesforce exams. Good luck, you’ll do great!