Use Flow To Track & Quantify Your Admin Automation Success

By Nana Gregg

At the end of the year, are you able to show how the work you are doing as a Salesforce Admin has impacted the business? To show hard metrics, you need things like time saved because of automations, mishaps averted due to cleaner data, streamlined processes and more?

One of the things I think every Salesforce Admin (and Developer and Business Analyst and Architect) can be more proactive about, is quantifying the work they are doing. Using our own tool to show the awesomeness we are bringing to the business. And show us when our automations are being used as expected.

In this article, we’ll explore how you can use a simple Flow to track and measure the success of your Salesforce Admin automation and quantify your work. Let’s get started!

Good Change

When our internal customers come to us with a requirement, it is usually because something is not working: something they need to do their job that we can help with. It may be a report, a new field to enable better reporting, or a change to improve a process.

Years ago, I was able to partake in Kaizen training at a manufacturing plant where I worked, then a few years later, I got to go through a Lean Six Sigma Green Belt program. If you’ve ever looked into these programs, you know they focus on process improvement which includes things like building efficiency, reducing waste, improving quality and making jobs more fulfilling. 

This sounds a lot like the job we undertake as Salesforce Admins as we manage our Salesforce platforms.

The word kaizen is a term taken from two Japanese words that literally mean “good change.” 

When I think of the declarative tools we now have at our disposal to affect good change for our users and companies I get excited. But how do we know a change is good? How do we know if we are creating efficiency, reducing waste, improving quality or making a job more fulfilling?

Measure All The Things!

When you think about the automations or flows that you have created to streamline a process, do you ever stop to think how much time was actually saved? Then take that to another level and multiply that times with how often the process is repeated/run?

My platform owner and I decided to do just that and build it in as a part of every automation. We wanted to be sure that there was a way to quantify the work we were doing. We made it simple and repeatable and used our own tools to measure everything.

What it Took

One custom object. One auto-launched flow.

We called the object Automation Analytics (a mouthful, I know). I like auto-generating the Record Name with a number AA-{00000000} or something similar. It’s got an Owner field already as well as the Created Date/Time field. 

You really only need to add 2 extra custom fields: Automation Name (where you will pass in what you want to call this automation for reporting later) and Time Saved (where for each automation you will pass in as an input value a number that represents the minutes saved by this automation). 

You could add other values you want to analyze, such as which department this is attributed to or even who built it. The sky’s the limit here.

Next up, you create a simple auto-launched Flow.

Create 2 Variables for Automation Name and Time Saved (and any other field you created that you want to set upon entry into the flow) and be sure to mark them as Available for Input – this will make the variables available to populate from the Process Builder or Flow that is calling the new Automation flow.

Then a simple Record Create where you set the values of the Automation Analytic record you are creating with your input variables.

When you save, give it a good name and don’t forget your description! Then click the Advanced link and choose to run this flow in System Context without Sharing – this ensures that the record can be created, regardless of the user who triggers it.

Badabing badaboom! You can now call this Flow at the end of any other Flow or as an Action in Process Builder and generate Automation Analytic records every time one of your automations is used.

Time is Money!

The hardest part of this is probably getting to that ‘Time Saved’ number. So take out your stopwatch and have a little ‘Time Study’ party – this could involve timing the original process yourself or timing a user doing it. This way you’ll be able to quantify how much time it took vs how much time the new process takes. Some things will be easy to time, some will be a little harder and may require educated guesses.

After using the system for a few years, we added a Flow to make creating a Project (and all the ancillary records needed) easier. In addition to just making the process quicker (went from about 11-14 minutes with no interruption to 3-4 minutes), we were also able to default fields from other objects to eliminate data entry errors. 

You’ll want to quantify eliminating errors in your time saved as well. For example, the actual time saved was 8-10 minutes, but if we include the time spent fixing errors, I would estimate it at maybe 10 minutes total for each new project created using the Flow.

Another example is when we wanted to purchase a tool to implement a process for creating Folders and Folder Structures in our document management tool. We wanted to use an integration tool that cost a small amount per month, so that when a record was created in Salesforce, we could send an outbound message to the tool to automate folder creations in the ‘right way’ for our company, then bring back in the URL of the new folder to populate it onto the Salesforce record. 

This was a Net New process that didn’t exist before. So we simulated someone doing it manually (notified them of the new record, they go to the tool, manually create the folders and folder structure and then populate the record) and used that number as time saved. Turn that time saved into dollars and you can now justify the cost of the tool you are using for the integration.

Summary – Celebrate your successes!

Here’s where you create some reports, throw them on a dashboard and show off the amazing work you are doing. 

Not only can you see the fruits of your labor, but you might also identify areas where people aren’t using the cool automations that you are building (wait, what?) – yes, it does happen.

You may notice a trend in the people using them (based on the Automation Analytics record owner) or that they aren’t being used at all, which will give you a chance to ask the best question – why? Find out if it’s a technical problem, a training issue or an “I’ve always done it this way!” issue. Then adjust as needed. 

Not all automations blow it out of the ballpark, but when they do, you can really be an unsung hero. Tracking things that you build, quantifying the results and ensuring that people (management) are seeing those results can shine a spotlight on the work you are doing.

LucidChart Link:

The Author

Nana Gregg

Started as a Salesforce Admin in 2007. Managed a few orgs, built a few flows, spoken at a few conferences. Salesforce MVP Hall of Fame member, currently working as a Solution Architect.


    Mary Butlin
    November 17, 2021 6:55 pm
    I love the idea of using this flow to measure impact! What a great idea, thanks for sharing it.
    Sean Hughes
    November 17, 2021 9:21 pm
    This is really cool! Thank you for the post and overview here. I was curious about strategies for determining the "Time Saved" value. I agree that this is probably both the hardest- and most important- part of this solution, but do you have any resources or best practices for formulating this value? For example, a Time Study could be biased if it is run by those who developed the solution and are very familiar with the new process, whereas if an end user was the subject in a Time Study, you may run into higher times (lower or even negative Time Saved) from just using a new process (early on, at least). Have you see successful strategies for mitigating some of the inaccuracies and bias that will inevitably creep into this metric? Obviously a measure is better than nothing but would be curious to hear ideas around how to keep it relevant.
    Christine Marshall
    November 18, 2021 10:25 am
    Thanks for reading! We love this nifty idea to track your success!
    Nana Gregg
    November 18, 2021 2:46 pm
    Awesome! Hope you get some use out of it! Thanks for reading!
    Nana Gregg
    November 18, 2021 2:52 pm
    Hey Sean - great questions! When I took my Kaizen and Six Sigma training, we learned how to do time studies. Here is a great resource with some suggestions and advice: Also, I would suggest you take a S.W.A.G. approach - a sophisticated wild guess - by timing the original process, maybe add or take-away a bit here or there to accomodate for knowns - getting better quality data is something you can't 'time' - but if you have bad data, it takes time to resolve from other people - so I'd argue it is time saved. It doesn't have to be perfect - even just having a count of how many times your automation ran can tell a story - are people using the things you built? Are they not? Are there certain people using it and certain people not? Can show you who may or may not need training or some extra hand-holding. Hope this helps! Thanks so much for reading and engaging!
    Steve Fischer
    December 15, 2021 4:42 am
    Cool trick. I have not only done this before but I've also attached results to my resume when on the job hunt. Here's something else you can do with this. Add a text field for flow errors and now put this subflow on your fault paths. Map the flow error field on the object to {!$Flow.FaultMessage} and viola! Now you have metrics on which flows are failing and why.
    Jason spencer
    May 13, 2022 2:18 pm
    You are a genius Nana! Not only does it demonstrate our value to the exec’s that approve our budgets but it’s simple enough for non-IT people to understand and re-tell your story. Love it. Thank you for sharing Nana
    Jason spencer
    May 13, 2022 2:19 pm
    You are a genius Nana! Not only does it demonstrate our value to the exec’s that approve our budgets but it’s simple enough for non-IT people to understand and re-tell your story. Thank you for sharing Nana
    May 22, 2022 8:10 am
    This is quite awesome!

Leave a Reply