BA Academy — self-paced module
By the end of this module, you will be able to:
The Business Analyst is one of the most accessible entry points into professional Salesforce work. It does not require a computer science degree, years of coding experience, or an expensive bootcamp. What it requires is a set of skills many people already have in some form: listening carefully, asking good questions, organizing information, writing clearly, and helping groups of people understand each other. This course exists to take those raw abilities and shape them into a professional, hireable skill set, one that supports remote work from anywhere, including right here in Puna.
Every module in this course is written at full depth. You can learn everything here on your own, at your own pace, in any order. Live sessions add community, real war stories, and hands-on practice, but nothing is held back from these pages. Start here, and go as far as you want.
People often use these terms interchangeably, but it helps to separate the process from the person.
Business analysis (the process) is a systematic analysis of business processes and needs. Its focus is understanding how a business currently works, where its problems and opportunities are, and what it is trying to achieve within the scope of a project. The work involves mapping current-state and future-state business processes, gathering requirements, analyzing data, and proposing improvements. Its tools are process models, requirements documents, and data analysis. Its outcome is a clear understanding of business processes and their impact on efficiency, profitability, or performance.
The Business Analyst (the role) is the person responsible for doing that analysis. A BA gathers requirements, analyzes data, and recommends improvements. Critically, the BA acts as a bridge between stakeholders: the business people who have needs, and the technical people who build solutions. The BA engages with stakeholders, documents requirements, and ensures the delivered solution actually meets the business need. The outcome of the BA's work is insight, documentation, and recommendations that improve business performance.
Here is another way to see it. Business analysis is a skill set that many roles use: admins, architects, and consultants all do some business analysis. The Business Analyst is the role that specializes in it. Every project, no matter how small, needs business analysis, whether or not someone holds the formal BA title.
In practice, a BA does these things:
...in order to inform these things:
Notice the shape of that list: the first half is investigation, the second half is judgment. A BA is not just a collector of facts. The facts exist to support recommendations and decisions.
The Salesforce Business Analyst is a project-based, business-improvement role. Salesforce BAs help guide businesses to improve their processes and efficiency in Salesforce, the world's leading Customer Relationship Management (CRM) platform (you will learn much more about the platform itself in Module 2). They elicit, document, and analyze requirements around business challenges, then help produce data-driven solutions.
Think of the Salesforce BA as an interpreter. Business stakeholders speak the language of sales targets, patient care, student enrollment, or donor relationships. Technical teams speak the language of objects, fields, flows, and integrations. The BA is the go-to person for translation between these two worlds, making sure everyone works together toward the best result.
A short story makes this concrete. Imagine a solar-equipment company where the Vice President of International Sales needs to see his team's quarterly forecast and adjust the numbers for individual sales reps when he has better information than they do. That sounds like a small request. But he is focused on selling, does not know how to configure the system, and does not realize his "simple" request touches forecast settings, permissions, and reporting. He needs someone who understands both the technology and the business process, someone who can recommend the right solution and see it through. That someone is the Business Analyst. BAs are, in the words of one Trailhead module, the "fix-it people of the business world."
The change a BA enables can be large (converting an acquired company's entire financial system into Salesforce), small (enabling forecast adjustments for one sales team), or anywhere in between (improving a single business process). Whatever the scale, if the change involves improving a process or system to help an organization meet its goals, a BA can steer the project in the right direction.
Across nearly every project, a Salesforce BA:
The word "conduit" deserves emphasis. On a typical Salesforce project team, the BA sits between the client on one side and the delivery team on the other: the Project Manager (PM) who runs the schedule and budget, the Solution Architect (SA) who designs the overall solution, the Technical Architect (TA) and Developers who build the complex parts, and Quality Assurance (QA) who verify the build. Information flows through the BA constantly, in both directions. When that flow is clear and steady, projects go well. When it clogs, projects drift.
Because the BA sits at the center of communication, relationship management is part of the job description, not a side effect. Strong BAs:
Do not worry if some of those terms are new. Each one gets its own module later in the course. The point for now is the pattern: a BA's job is woven through every other role's job. You are the connective tissue.
BA work spans the whole project lifecycle. It helps to group the activities into four clusters.
Two threads run through all four clusters. Some of this work is collaborative (crafting user stories, aligning with architects, contributing to solution documentation) and some is client-facing (leading workshops, eliciting requirements, delivering training). A BA moves between those two modes many times a day.
One honest note: no two projects use their BA identically. On one project you may lead discovery workshops solo; on another you may support a senior consultant and focus on documentation. The role flexes. What stays constant is the mission: understand the need, translate it faithfully, and protect the quality of the outcome.
Students in this course often aim at both BA and Admin roles, and this course deliberately bridges the two (Module 8 is the explicit bridge point). Here is the cleanest way to distinguish them.
Salesforce administration is an operational role. Admins are the resident Salesforce experts inside an organization. They set up users, configure security and access, create and maintain objects and fields, manage data, build reports and dashboards, create automations, manage releases and org health, and train users. Their work is continuous: the org needs care every day, forever.
Salesforce business analysis is a project-based role. BAs are brought in to change something: implement a new cloud, redesign a process, fix a broken workflow. They elicit and document requirements, write user stories, analyze data, facilitate solutions, manage projects, and solve issues during testing. When the project ends, the BA moves to the next project.
| Salesforce Admin | Salesforce BA | |
|---|---|---|
| Role type | Operational, ongoing | Project-based |
| Core focus | Keep the org healthy and users productive | Guide a specific business improvement from idea to adoption |
| Typical tasks | User setup, security, objects and fields, data management, automations, reports, releases, training | Requirements elicitation and documentation, user stories, process analysis, project facilitation, testing support, training materials |
| Key qualities | Empathetic, confident, encouraging | Data-driven, action-oriented, solution-oriented |
In smaller organizations, one person often wears both hats: the admin does the business analysis, or the BA does light administration. The skills reinforce each other, which is exactly why this course teaches both tracks.
The source curriculum names a dozen core skills. Rather than a laundry list, here they are grouped into the three clusters Salesforce's own BA training uses, with the individual skills inside each.
Skills: active listening, engaging with all levels of stakeholders.
To make informed recommendations, BAs gather information, lots of it, from every level of an organization. Discovery is one of the most important steps in the BA process, and doing it well is a skill in itself. Active listening means absorbing what people say (and notice what they do not say) rather than waiting for your turn to talk. Great BAs are described as intellectually curious, with "voracious appetites for learning": they are very good listeners who absorb information like sponges. Module 3 is devoted entirely to this skill set.
Skills: analytical thinking, critical thinking, creative thinking, systems thinking, expert judgment, problem-solving.
Once information is gathered, the BA spends real effort making sense of it. Critical and creative thinking break information into smaller, assessable parts and examine problems from multiple perspectives. Systems thinking sees how a change in one place ripples through the whole. Expert judgment, built over time from deep understanding of an organization and industry, helps evaluate alternative solutions. Problem-solving ties them together: distinguishing relevant detail from trivia and formulating solutions that hold up.
Skills: effective communication, professional writing, professional presentation, change management advocacy.
By some estimates, 80 percent or more of a BA's time involves communication in some form. That includes clear writing (requirements no one can misread), engaging presentation (findings people actually absorb), and the confidence to communicate problems and solutions to leaders at every level, backed by strong data. BAs help improve everyone's productivity by breaking down barriers to communication. Change management advocacy means the BA does not just design change but champions it, helping people understand why it matters (Module 15).
Be encouraged by this list rather than intimidated. Nobody arrives with all twelve skills polished. The role progression below exists precisely because these skills grow with practice.
Four misconceptions come up constantly. Clearing them up now will sharpen your understanding of the role and serve you well in interviews.
"BAs need to be super technical." No. A BA needs a solid working understanding of the Salesforce platform, its capabilities, and its limitations, enough to keep recommendations realistic. The deeply technical work belongs to admins, developers, and architects. (That said, the more platform fluency you build, the more valuable you become, which is why this course includes real Salesforce depth.)
"BAs shouldn't touch configuration." This is a matter of team choice, not a rule. If a BA has the skills and bandwidth to help with configuration while overseeing the solution, most teams welcome the extra hands. Many BAs grow into admin-capable hybrids, and this course is built to support exactly that growth.
"BAs are only needed after a project kicks off." Backwards, in fact. BAs are most valuable at the very beginning, building the initial understanding of needs and scope that everything else rests on. Analysis comes before architecture, and architecture comes before build.
"BAs only do requirements." Requirements are a big part of the job, but as the four activity clusters above show, BAs facilitate, test, train, manage change, and support launches too.
Knowing the boundaries of your role protects you and your projects.
You do not need to master specific software before starting, but you should recognize the categories of tools working BAs touch daily. Exact tools vary by employer; the categories do not.
If you are comfortable with email, spreadsheets, and shared documents today, you have a real head start. The rest is learnable, and this course points you to hands-on practice for the Salesforce pieces.
The BA role has a well-worn growth path. Titles vary by company, but the shape is consistent:
Module 18 returns to this ladder in detail, including which skills are considered core at each stage and how the BA path connects to Admin, Scrum Master, and other Salesforce careers. For now, the takeaway is simple: this is a role you can enter at the ground floor and grow in for a decade.
One habit separates good BAs from great ones, and you can begin practicing it immediately: establish measurable benchmarks, and seek feedback relentlessly.
When a customer wants to change how they do business, learn what matters to them and turn it into something quantifiable. How many minutes does it take a sales rep to produce and email a quote? How often do service agents need a repeat visit? Run those benchmarks on the existing process before you change anything. After the solution lands, run them again. The delta is your proof of value: for the customer's return on investment, and, candidly, for your own resume.
And in everything you produce (documents, presentations, solutions, test cases), invite feedback. Hand your requirements to someone who was not in the room and see if they make sense. Ask testers to narrate their thoughts aloud. Feedback can be uncomfortable; it is also the cheapest professional development you will ever get.
8 questions. Answer at your own pace, then check the explanation for each.
Nice work. Review any question again using the menu (top right), or move on.
Continue to Module 2: The Salesforce Platform for BAs (Clouds + AI Overview) →