This video gives a simplified, proven practice I've used for over eight years to help all kinds of businesses to figure out exactly what their company does so they can grow their business easier and more efficiently. This process mapping tutorial will walk you through the core theory of process mapping, which allows you to answer the six key questions of a systemized business, as well as execute it to improve your business workflows.
Process mapping is essentially visual storytelling for your business, turning invisible actions into a simple, clear map that shows you why things matter to the big picture and where things are breaking down. By working through the steps, you'll learn to identify the painful areas of your small business that are worth fixing and figure out the scope by setting a clear start and stop point. The power of process mapping comes from being able to clearly see all of your steps in a workflow, identify where handoffs are causing confusion, and find automation opportunities so you can stop manually applying project templates and focus on the actions that will truly systemize your business.
Here's what this video covers: 00:00 Why process mapping matters 02:30 Pick the painful process 03:32 Set your map’s start and stop points 05:16 The 4 shapes you need to know 07:35 Start mapping: “What happens next?” 09:40 Parallel paths + improvement flags 11:37 Using decisions (diamonds) 14:08 How detailed should your map be? 15:26 Adding swimlanes: people, tools, time, emotions
[ DISCLAIMERS ] Content we publish is sharing information based on our own experience and opinions. We're not your business coach, lawyer, or advisor in any way. We encourage you to do your own research and find a way to Enjoy the Process with your own style and due diligence!
You may notice how our content often includes affiliate links or sponsored content. ProcessDriven may receive compensation for this type of content, which supports the work we do at no cost to you
If you want to systemize your business or your services,
there is no skill more valuable than learning how to process map.
In this video, I'm going to share a simplified version of the practice
I've been using for over eight years to help businesses ranging from
landscapers to lawyers to agencies figure out what their business actually does
so they can do it more efficiently with less stress.
I've taught this so many times that I know you're going to get value out of it.
But before I get into the actual process mapping,
there's some important theory you need to know.
To learn the secret skill,
it starts with understanding how this fits into your actual business.
You see, at the end of the day,
systemizing your business is about being able to answer
these six questions for any given thing in your business.
You know, why are we doing it?
What needs to happen?
Who's doing it?
When's it happening?
How do we do it?
And where do we keep track of all of this stuff?
You see, here at Process Driven, our business is systemizing other businesses.
And we walk folks through these six questions.
And when we're working on a project,
we're always starting with what happens, who is doing it, and when.
These tactical actions are the backbone of any business.
It's the execution arm.
It's what allows you to get stuff done.
Once we get this down, we move on to the how side of the equation,
which is how do we keep track of our methodology?
This is where things like templates and SOPs become very helpful.
Whole videos on that up at the top.
Now, if that all sounds good to you,
and you want to skip all of the roundabout stuff,
use the link in the description to work with my team.
But if you are looking to DIY, when we're working with folks,
we also take care of the where aspect of which technology do we store all this stuff in.
That's the easy part.
But why that last piece?
That is really tricky.
And that's where process mapping, the topic of this video, can really help you.
Process mapping is a form of visual storytelling to tell you,
here is what's going to happen in this otherwise invisible set of actions
that occur inside your business.
When we take things and make them visual,
voila, we can suddenly start to understand why they actually matter to the big picture.
So with all that backstory out of the way,
go ahead and grab a piece of paper or a digital whiteboard or a physical whiteboard.
And for the rest of this video, we're actually going to start process mapping together.
Ready?
I can't hear you.
So let's just say you're ready.
Okay.
So to process map along with me,
I would encourage you to pick one area of your business to process map with me,
because you actually doing it is going to help you remember this
a lot better than me just talking at you.
Although I can keep talking at you if that's what you want.
Some common areas to choose for process mapping are areas that are really valuable,
but also kind of a pain in the ass.
Something about them is not quite working, but you know they are worth fixing.
Common examples would be things like onboarding,
sales processes, how you find vendors, how you update your website if you're an e-commerce shop,
how you handle client change requests if you're a contractor agency,
those kinds of painful areas that really do matter.
That's where we want to focus our energy on.
Once you have identified one of those areas for your business,
you're ready to move on to the next step.
And if you're not paused the video here,
if you're still watching, I assume you haven't paused it.
Bonus points.
If you actually write the process you'll be working on in the comments below.
Okay.
Write it down there.
I'll see you on.
Let's move on to the next step.
Side note.
This is why I love that process-driven works with teams of less than 50 people,
because when you have a smaller company like ours,
you can quickly assess, ah, that's the area that's not working.
You don't need a 14-month evaluation to figure that out.
You just know.
So, awesome.
Now that you have that, let's move on to the next step,
which is figuring out our scope.
You see, process mapping is storytelling.
And just like any story, we need to roughly know where does it begin and where does it end.
We want to keep it short enough to focus on the good stuff,
and not so long that we fall asleep.
So if, for example, the process that is painful for you is sales,
let's start when we have a lead,
and let's end our story when we have a sale or we've somehow closed out that lead.
If for you, the thing that you focused on is fulfillment,
your start is probably going to be when someone becomes a client.
And your stop is probably going to be when that client is off boarded.
If you are focusing on sourcing vendors, it's going to be, hey, we need vendors.
We have a vendor.
If it's sourcing talent, it's we need talent.
Oh, we hired somebody.
You know, you can pick the start and stop,
but the area that you said is needy should be your North Star when deciding
where do we want to focus.
Now, for myself today, when I'm process mapping,
where I'm going to focus on is the actual fulfillment of process-driven new service.
Now, I don't think the service is painful.
However, this service is something I really want to be improving,
and we're going to be scaling up.
So I want to map out all of the steps that happen
from someone becoming a client to when they are off boarded.
Because I know if I can make this amazing,
the product will basically sell itself,
or at least that's my non-marketer point of view.
So this is the journey that I'm going to be focused on process mapping
from someone purchasing to someone becoming a former client
of this guided service specifically.
Now, to start telling the story of how we go from purchased to a former client,
we could start creating hieroglyphics or stick figures telling each step in the process,
but that would take a really long time
and require artistic skill that most of us do not have.
So instead, we are going to rely on basic symbols.
Now, fortunately for us, there are really just four symbols
we need to know in order to create a process map.
I promise you are capable of this, even if you're not a great drawer,
because the main shape we need to know is this one.
Yep, it's a rectangle.
A rectangle in process mapping means a step or an action
where things happen along the journey.
This is our key storytelling device is the rectangle.
The second shape we have is a diamond.
Yes, just like a diamond in a proposal represents a choice you have to make.
Will you say yes or will you say no?
And heartbreak ensues.
A diamond in a process map is a decision-making point
for where things could branch off in multiple directions.
So a decision is what we have for the diamond.
The next shape we need to know is what I like to think of as a folder,
but is technically a predefined process.
We're going to call it a folder for our own sake.
Folder represents a bunch of stuff that's tucked inside.
So for example, if there are so many steps that we're like,
oh my gosh, we're running out of space,
we can put them inside a folder and say,
hey, this folder is where everything related to
how we decide how to script a video goes.
This is a folder that describes everything about how we send an email.
This is a folder that describes everything about how we handle a complaint.
Those are complicated processes,
and maybe we don't want to get fully into them in a given process map.
We can put them in one of these folders and just say,
hey, we'll deal with that later.
We'll expand it somewhere else.
That is our next symbol.
And then the last one is actually already on here.
And that is this guy right here, an arrow.
You already know about this one,
that an arrow is a way to show the flow of traffic,
which step is leading to which decision,
which is leading to which step,
which is leading to which decision.
Now there are in true process mapping,
many, many, many other symbols.
But for the sake of our purposes today,
I don't think they're worth your time to worry about.
Let's just focus on these three plus the arrow makes four.
By the way, if you're enjoying this video,
please do like comment and subscribe.
It actually does make a big difference and it's free.
So thank you so much.
All right, now that we know these symbols
for process mapping, we need to start actually mapping.
And to do this, the process is actually really simple.
Start at the left of your page or the start of your process
and answer the question, what happens first?
In my case, I know I'm starting with a purchase.
So the first action, which I'm gonna just do a square
to represent this here, is that the checkout is complete.
Go ahead and write the first thing that happens
in your process there.
Usually this will be the same as your first step.
Sometimes it'll be a smaller action that is part of that.
Like in this case, purchase involves
a few fields being filled out.
All I'm writing is that the checkout is complete.
Once you have that first step, the next question
and the only question you'll need
for the rest of your process mapping journey
is what happens next?
That's it.
We wanna try to break down every action,
whether automated or human done
to get us from checkout complete to former client.
And as you can imagine, this can take a little while.
That's why when we're working with people at Process Driven,
we don't recommend you do this
for every single thing under the sun.
Old school consultants, unfortunately,
very many of them will say that you must,
you must map out everything.
But Jesus, we don't have time to do that
and still run a business as a small team.
So I recommend this exercise for areas of pain
and for the simpler areas of our business,
we can generally skip over.
But for now, let's go into this.
My example, again, is service fulfillment.
So after checkout is complete, what happens next?
Well, for us, they see a confirmation page.
So client goes, client goes to confirmation page
and then they immediately go to a scheduling page.
And that's pretty much all that they do
in one quick sitting to go through the checkout process
right after they actually do the financial checkout.
At the same time as they are doing that,
we have a step triggering internally.
We have an internal sale confirmation.
And from there, we have an internal step
of applying a template, which is our project template
with all of the steps and tasks
and everything we need to do
to make sure this client feels really happy.
Now, this is actually a great example
of a problem you might have in your process map.
And I want to highlight both of them here
before we keep going.
I have two things happening at the same time.
We've got the client doing this confirmation stuff
and approximately at the same time,
assuming we check our email,
we've got the internal team doing some other actions.
My general rule of thumb,
although this is completely my own preference,
I like to keep those things in line with each other
to show that they're happening at the same time.
If you've got things with a delay,
it can be nice to show the delay.
But personally, I like to have it more like a timeline
where from left to right,
it's telling me the story in the sequence that it happens.
That's just my own personal preference.
The second thing that is happening
as I start to write this out
is probably something that's going to happen to you as well,
which is I am starting to already notice
opportunities for improvement.
Like I'm writing this down and I'm like,
wait, why are we manually applying project templates?
We could automate this.
That is incredibly normal.
But what I want you to do
and what I'm going to force myself to do
is when we are process mapping,
we want to process map status quo.
What is happening today?
If you feel like you might forget it,
you can go ahead and add a little highlight
or a note with your ideas about changes.
But I'd really like us to focus
on just documenting what is currently happening.
And then we can go through some revisions.
Try your best to not map things that aren't actually there.
We're focused on reality.
Now from here in my particular draft,
I'm going to keep asking the same question.
What happens next?
In my case, I have a client start doing some training.
And at the same time,
the internal team is doing call one prep.
So eventually these two paths come back together
when we complete call one.
Now in my process after call one for this service,
we need to start creating the roadmap,
the implementation plan for this client
of exactly what they need to do
to start systemizing their business
based on all the data we have.
But sometimes after this call,
we realize there's still some information missing.
So that gets to our next step of the process,
which is one of those infamous diamonds.
Now, quick pop quiz.
Do you remember what a diamond represents?
Hint, hint.
Yeah, okay.
It's a choice.
It's a decision.
And in this case, the decision is,
do we have enough info
to go ahead and start creating the roadmap?
Now, if yes, we're going to continue on our intended path.
So in this case, yes,
we'll continue into another rectangle
where we start prepping the roadmap,
which is that customized plan
to systemize their unique business.
If no, that's where things get a little interesting
where we're going to have a step away from the norm.
Now, depending on the layout of your software,
I like to sometimes have my no paths go way down
or way up to show that they're kind of in a weird spot.
They're not the normal path.
So in this case, what I'm going to do
is since I don't have a lot of room above,
I'm going to take the no path
and I'm going to go way on down.
And if there is not enough information,
I'm going to reach out with information request
to get additional information from the client.
And I'm also going to take an additional step here
of adding retro note.
Adding a retro note is something we do
in all of our projects,
but for client projects like this,
if we reach the point of having a call
and we're missing information,
that is a process failure.
So we'll have a step here that says,
hey, if something was missing,
add a note to our retrospective that says
for future projects,
we need to request this extra info.
So we are never left in this no path in the future,
but regardless, this is the no path.
And here we go.
Eventually we will come back up to this main path.
We go over here.
And then if we have enough info,
we then continue on to yes.
So you can kind of see how this serpentines together.
We're going to keep adding steps and steps and steps
by asking the question,
what happens next until we arrive at former client?
This is something that will come easier
with more practice,
but I just want to highlight some tips
to get you through this.
If you are new,
as you can tell on my little whiteboard here,
I'm using a digital whiteboard.
That is intentional.
It's because one, my handwriting is messy.
Two, this takes up a lot of space.
When I use my physical whiteboard,
it is fantastic,
but I need to be really thoughtful
in how I use my space
to make sure I don't run out of room
or accidentally wipe it off with my shoulder.
So if you were doing this at home,
I would suggest taking multiple pieces of paper,
using sticky notes or keeping it digital.
So you can infinitely expand as you start mapping
because you're not going to guess
the right distance at first.
The second tip I'll share
is that sometimes people get confused
about how detailed to be on this map.
A good rule of thumb
is to keep each box you see on here
equal to about one task.
A task is something that's done by one person
in one work sitting at one discrete date.
So here they are going to check out
the scheduling page once.
It's not going to take them 10 hours.
It's going to take them 15 minutes by one person.
If there are multiple steps,
like you see right here,
there are multiple steps you're going through.
There'll be multiple actions.
If you are not comfortable
with that definition of task,
I have a whole video on it up here
that I would definitely recommend watching
after you finish this one.
By the way, if you'd like me to go into more detail
of how to process map your service
going step-by-step through each piece,
write the word more in the comments below.
That'll act as a vote to let me know
you want a part two on this.
But for now, let's move on to the next phase,
which is adding additional layers.
Sometimes when we're telling the story
of the actions that happen
in a particular process of our business,
we don't really find the problem.
This isn't common, but sometimes it happens
where you're writing out the steps
and you're like, oh yeah, that's all great.
And yet you still feel like something is missing.
In those cases, in step four here,
we can add layers to our process map
to make the problem areas more obvious.
Adding these additional layers or swim lanes
allows you to see other pieces of information
connected to the process map.
Some examples of what you might add
will be to go through your whole process map
and show which people are involved.
So for example, I might say step one is client,
client, client, client.
This one is Layla.
This one is Bob.
This one is Susie.
This one is Layla.
This one is Layla plus client.
This one, you know what I mean?
I could go through each one.
And what that will help me see
is where there might be challenges with handoffs.
Like for example, right here,
if I have three different people
doing three different things right back to back,
that tends to cause a bit of confusion
and is something I might be able to eliminate.
I have a whole video on different ways
to streamline your process up here,
which includes this one.
Now I would add this people layer in
if I want to explore whether people
might be making my process harder.
Another thing you might want to check is software.
So for example, if I have Kajabi here,
WordPress here, Calendar here,
No Software here, ClickUp here.
You know, if I have all these other tools
and I look at that and I'm like,
that's painful.
I can also see that story
by adding more details like software.
Additional pieces of information,
as if you're not overwhelmed enough,
would be things like how long things take.
So I could write how many minutes
of my time versus client time
does each step take?
So it might take me 60 minutes,
my client, 50 minutes.
Starting to write down how much active time
or how many delays you have in your process
can help you solve challenges around turnaround time
or cost.
Like if you're spending more time on your service
than you're actually making,
this can really help you see that.
And the last example I'll give you
of an additional layer,
which is probably my favorite layer,
is emotions.
So particularly for clients,
going through your process
and figuring out how your client
typically feels in that moment
can be really interesting.
So in this case, checkout.
My client's probably going to feel pretty darn happy
because they just did a thing.
Once they start getting through the confirmation page,
they're going to get less and less happy,
maybe even to the point of feeling like,
oh God, I hate scheduling things.
And then they're going to get to the first call
and they're going to be excited again.
So I might look at this and realize,
hmm, how can I make the lows
a little less low in this process?
How can I spread out the happy face?
How can I make some of the exciting moments
happen earlier?
If you have a service component to your business,
mapping out the emotional experience
can actually be a really good solution
for things like client drop-off
or people ghosting you.
Oh, and I should say,
if this is something you're looking to do
with your clients and you really want
all the advanced strategies around process mapping,
this is one of my favorite books on the subject.
It is a textbook, basically.
It is a lot,
but it will give you a lot of great examples
of different swim lanes you can add.
And the service design blueprinting approach
they teach in here is probably
one of my favorite approaches
to process mapping for practitioners.
If you are a regular business owner,
please ignore this recommendation.
It is overkill for your needs.
For all of us though,
I think it's time we move on to step five,
which is taking this process map we've built
and turning it into actions.
Because the fact is,
even if we create a beautiful process map,
if no one actually knows how to use this
and this doesn't change how we behave,
it's just a form of procrastination.
So we need to connect this back
to the actions that drive our business,
back to those six attributes of a systemized team,
and we need to connect it all together.
The way we do that is by setting up software,
using templates,
making sure that we have our team members
in charge of the key areas
and hiring when we actually need to,
to make sure our whole process
is running smoothly
and getting better every time.
And if you are serious
about systemizing your business today
and not someday,
that's exactly where myself and my team can help.
Work with us in the description below.
Let's get this taken care of
so you can move on to the next chapter
of growing your business to the next level.
Of course, if you'd rather DIY to start out,
I totally respect that.
I would recommend you watch this video
here on the next page,
because if you have all of this stuff down,
but you don't understand
how to create tasks properly,
unfortunately,
this is never gonna translate to action.
So watch this video next,
and until next time,
enjoy the process.