Move from Tasks to Strategy
Learning Objectives
After completing this unit, you’ll be able to:
- Differentiate strategic thinking from task thinking.
- Explain the value of strategic Salesforce administration.
Explore Admin Tasks and Admin Strategy
In the previous unit, you learned about task thinking (We need to build a thing!) and strategic thinking (Does that thing really solve the business issue?). Let’s dive into this concept further to see how this applies to Salesforce admins.
Moving from task thinking to strategic thinking is a mindset shift from just doing the work to evaluating the work and considering the business outcome. Let’s break this down into three levels.
Level 1: Task |
Mindset: I need to build this automation because my manager asked for it. Focus: You focus on the how. How do I configure this flow? How do I write this validation rule? Value/Risk: AI is getting good at this level. If you stay here, you are competing with a machine. |
Level 2: Operation |
Mindset: How do I make this task faster or better? Focus: You look for ways to streamline. Maybe you create a template so you don't have to build from scratch every time. Value/Risk: This is better, but it’s still focused on the work itself, not the business result. |
Level 3: Strategy |
Mindset: Should we be doing this in the first place? Focus: This is first principles thinking—a way you can break down a problem to its core to discover the root cause. You look at the request and ask if it actually solves a business problem or if it’s just a legacy process that no longer makes sense. Value/Risk: This is where you become a consultant for your company. You guide the business toward the right solution. Uncovering value and impact might take more time, but as you deliver strong solutions, you build more trust with your stakeholders. |
Make Impact
Imagine a new VP of Operations asks to mass-delete 1,000 unused fields to improve system performance and simplify the database. In the knowledge economy, you might immediately focus on the technical requirements and how to get the job done quickly.
You might ask about:
- The timeframe to complete the task
- If there is something on AppExchange you can use
- Whether there’s a fast way to perform a mass-delete operation
You use a bulk tool to find and delete the fields, and mark the task complete. System performance improves slightly. However, some months later, another team finds a critical, long-running report is now broken because some of those deleted fields were part of a complex historical trend calculation. The simple task-based fix created a complex, high-impact problem.
In the wisdom economy, you look for the pattern and the underlying context instead. You realize that deleting the fields is just a simple technical solution, not a strategic one.
To find the root of the issue, you ask different questions.
- Who requested these fields, and when were they last used?
- What business processes were these fields designed to support?
- Is there any downstream automation, custom code, or reporting that references these fields, even if the fields appear empty?
- Before we delete, do we have a governance process in place to ensure fields are documented, reviewed, and retired responsibly?
- How can we structure the object(s) to be more flexible and prevent field sprawl in the future?
As you investigate further, you realize the underlying issue was about data quality, system health, and lack of governance. Instead of just performing the deletion task, you partner with the VP to create a system-wide data governance process and policy. You work with stakeholders on what fields are necessary to keep, what can be safely deleted, and long-term plans to migrate toward better data capture and reporting. You don’t just close a ticket, you solve a problem that has a bigger impact on your business.
Compare Knowledge and Wisdom
Here’s a handy table that compares two approaches when tackling the same request.
Task Focus |
Strategy and Impact Focus |
|
|---|---|---|
Primary Goal |
Complete the ticket and execute the request efficiently. |
Solve the underlying business problem and drive value. |
Mindset |
How? (How do I accomplish the task?) |
Why? (Why do we need this? Should we do this?) |
Key Questions |
Focus on tools, timing, and criteria. |
Focus on business impact, user experience, and long-term value. |
The Action |
Do exactly what was requested (mass deletion). |
Diagnose the need, analyze the options, and prescribe the right solution (a phased approach toward better data governance). |
The Result |
A completed task, but potentially a broken system or unhappy users. |
A comprehensive solution that improves how the business operates and helps the company grow. |
Put It Into Practice Today
You don’t become strategic after 3, 5, or even 10 years as a Salesforce admin—you become strategic the first time you ask why instead of how. We crafted the scenarios in this badge to show you examples, taking care to capture common use cases to help inspire ways you can apply strategic thinking in your job today.
Drive Business Value
The scenario in this unit is just one example of shifting from task to strategy and impact focus. In the next unit, you dive into how to apply this approach into your daily routine.