Business problems often reoccur because symptoms are addressed, but the underlying causes remain.
The Five Whys technique helps identify root causes by asking 'why' repeatedly until you find the core issue.
Don't always blame individuals; investigate processes since mistakes can indicate fragile systems.
Support root cause analysis for business with data, observing frequencies and conditions surrounding issues.
Implement targeted improvements, then monitor results to confirm that you fixed a meaningful problem.
Some business problems never really disappear.
A report is late, so someone reminds the employee responsible.
A customer inquiry is missed, so the team is told to pay closer attention.
An invoice contains incorrect information, so accounting fixes it.
The immediate problem gets resolved, but a few weeks later it happens again.
That usually means the symptom was corrected while the underlying cause remained.
Symptoms Are Easier to See
Suppose customer inquiries occasionally go unanswered.
The obvious conclusion might be that employees need to check email more frequently.
But that may not be the actual problem.
Perhaps inquiries are delivered to a shared mailbox nobody owns. Maybe there is no standard definition of who should respond. Perhaps website inquiries go to a single employee who is occasionally unavailable.
Until you understand the cause, it is difficult to create a reliable solution.
Use the Five Whys
The Five Whys is a simple root cause analysis technique frequently associated with Lean problem solving.
The idea is to repeatedly ask why something happened until you move beyond the obvious symptom.
For example:
Problem: A prospect did not receive a follow-up.
Why? The salesperson did not see the inquiry.
Why? The inquiry was sent to a general email address.
Why? Website inquiries are not automatically assigned.
Why? The website is not connected to the CRM.
Why? No formal lead intake process was established when the CRM was implemented.
The original problem appeared to be an employee forgetting something.
The deeper problem was a process design issue.
You Do Not Always Need Five Whys
The number five is not a requirement.
Sometimes two questions reveal the cause. Sometimes seven are necessary.
The objective is simply to continue asking until you identify something that can reasonably explain and prevent the problem.
Be Careful About Blaming People
When the answer to a process problem is "someone needs to be more careful," keep investigating.
People make mistakes. Good processes are designed with that reality in mind.
If a critical activity depends entirely on one employee remembering to perform it at exactly the right time, the process itself may be fragile.
Use Data When Possible
Root cause analysis is stronger when supported by evidence.
Look at when the problem occurs, how often it happens, which customers are affected, and whether certain conditions are consistently present.
This reflects the Analyze stage of Six Sigma's DMAIC approach: Define, Measure, Analyze, Improve, and Control.
The goal is not to make problem solving complicated. It is to avoid spending time fixing the wrong thing.
Fix the Cause, Then Watch the Result
Once you identify a likely root cause, make a targeted improvement and monitor the process.
If the problem disappears or declines substantially, you have evidence that you addressed something meaningful.
If it continues, return to the process and investigate again.
Repeated problems deserve better than repeated reminders.
Lean principles apply to various environments, focusing on activities that create value versus those that waste resources.
Eight common forms of waste include defects, overproduction, waiting, non-utilized talent, transportation, inventory, motion, and extra processing.
Understanding these wastes can help identify specific improvement opportunities in business processes.
When people hear the word Lean, they often picture a manufacturing floor.
But the basic idea behind Lean applies just as well to an office, professional service firm, contractor, or growing small business.
Lean asks a straightforward question:
Which activities create value, and which activities consume resources without creating enough value?
One useful Lean framework identifies eight common forms of waste.
1. Defects
Defects are mistakes that require correction or rework.
In an office environment, that could mean an incorrect proposal, missing customer information, billing errors, duplicate records, or a form that must be resubmitted.
The cost is not limited to correcting the mistake. Errors can create delays and additional communication throughout the process.
2. Overproduction
Overproduction means creating something before it is needed or producing more than is required.
Examples might include reports nobody reads, unnecessary printed materials, duplicate documentation, or preparing detailed work before a customer has approved the project.
3. Waiting
Waiting is one of the easiest wastes to recognize.
Work may sit idle while employees wait for:
approvals
customer information
management decisions
system access
another department
Reducing waiting time can often improve customer response without employees actually working faster.
4. Non-Utilized Talent
This happens when employee knowledge and capabilities are not being used effectively.
A skilled employee spending hours manually compiling spreadsheets is a simple example. Another is failing to involve frontline employees in improving processes they work with every day.
5. Transportation
In service and office environments, transportation can mean unnecessarily moving information between systems, folders, people, or locations.
Downloading a report from one system just to upload it into another is a common digital version of transportation waste.
6. Inventory
Inventory is unfinished work waiting to be processed.
For a service business, that might include unanswered inquiries, proposals waiting for approval, unprocessed invoices, open support tickets, or projects waiting to be scheduled.
7. Motion
Motion refers to unnecessary movement required to perform work.
Digital motion might mean opening five applications to answer one customer question, repeatedly searching for documents, or navigating unnecessarily complicated folder structures.
8. Extra Processing
Extra processing is work performed beyond what the process or customer requires.
Examples include duplicate data entry, unnecessary approvals, overly complicated forms, and maintaining the same information in multiple systems.
Use Waste as a Lens, Not a Checklist
You do not need to inspect every business activity and classify it into a Lean category.
The eight wastes are simply a useful way to look at familiar work differently.
The next time a process feels frustrating, ask what kind of waste may be present.
That question can turn a vague complaint into a specific improvement opportunity.
Start by clearly defining the trigger of the process to understand its flow.
Document what actually happens, not just how it should work, to uncover hidden improvement opportunities.
Identify decision points and handoffs in the process to mitigate delays and improve efficiency.
Question each step in the process; remove unnecessary tasks before attempting to automate.
Finally, define the desired outcome to guide your automation efforts effectively.
Automation can make a good process faster.
It can also make a bad process fail faster.
That is why one of the most important questions to ask before implementing automation is not "What software should we use?"
It is:
How does this process actually work today?
Start With the Trigger
Every process starts somewhere.
A customer submits a form. A purchase order arrives. A project is approved. An invoice becomes due. A service request is received.
Define that trigger clearly.
Then follow the work from beginning to end.
A simple process might look like:
Inquiry received → Qualification → Assignment → Follow-up → Proposal → Outcome recorded
You do not need specialized process mapping software. A whiteboard, piece of paper, or shared document can be enough.
Document What Actually Happens
One of the most common process improvement mistakes is mapping how the process is supposed to work instead of how it really works.
Ask the people performing the work.
You may discover that the documented procedure says one thing while employees have developed several additional steps to keep the process moving.
Those unofficial steps are often where the best improvement opportunities are hiding.
Look for Decisions and Handoffs
As you map the process, identify every point where someone must make a decision.
Examples include:
Is the lead qualified?
Does this require manager approval?
Is inventory available?
Is the information complete?
Has the customer responded?
Also identify handoffs between people and systems.
Handoffs frequently create delays because one person finishes their part but the next person does not know that action is required.
Question Every Step
Once the process is visible, begin asking questions.
Why does this step exist?
Does anyone use this information?
Could this information be collected earlier?
Are we entering the same information twice?
Could one approval replace several?
Does the customer benefit from this step?
This reflects an important Lean principle: remove unnecessary work before trying to make unnecessary work faster.
Simplify Before You Automate
Imagine a process with twelve steps.
After reviewing it, you discover that three steps are no longer necessary and two others can be combined.
You now have a seven-step process.
Automating those seven useful steps is likely to produce a better result than automating all twelve original steps.
Define the Desired Outcome
Finally, define what success should look like.
Perhaps you want every website inquiry entered into your CRM automatically and assigned within five minutes.
Or invoices should be generated within one business day of project completion.
Clear outcomes make technology decisions easier because you are choosing tools to support a defined process rather than hoping a tool will define the process for you.
Map first. Simplify second. Automate third.
That order prevents a surprising amount of wasted effort.
Small tasks can accumulate significant costs; even minor inefficiencies add up over time.
Start measuring the cost of inefficient processes by asking about time spent, frequency, participants, and their hourly rates.
Look beyond labor costs to include errors, missed opportunities, and customer dissatisfaction in your calculations.
Establish baseline measurements to understand current performance before making improvements.
After implementing changes, measure again to quantify the improvement and emphasize the value of efficiency.
A process does not need to look expensive to cost a business money.
Consider a task that takes one employee 20 minutes and happens three times each day.
That is one hour per day.
Over approximately 250 working days, that small task consumes about 250 hours each year.
If the process can be simplified or reduced to a few minutes, the improvement may recover weeks of productive capacity without hiring another employee.
This is why one of the most useful steps in process improvement is learning to measure the problem.
Start With Time
Time is usually the easiest cost to estimate.
Ask four questions:
How long does the process take?
How often does it happen?
How many people are involved?
What is the approximate hourly cost of their time?
You do not need perfect numbers. A reasonable estimate is usually enough to determine whether a problem deserves further attention.
For example, suppose a weekly report requires three hours of administrative work.
Three hours multiplied by 52 weeks equals 156 hours per year.
If the fully loaded labor cost is approximately $35 per hour, that report represents more than $5,000 of annual labor.
If most of that work can be eliminated or automated, the value of improving the process becomes much easier to understand.
Look Beyond Labor Cost
Labor is only one part of the equation.
An inefficient process can also create costs through:
errors and rework
missed sales opportunities
delayed invoices
slow customer response
expedited shipping or rush charges
duplicate software subscriptions
customer dissatisfaction
Some costs are easier to calculate than others, but even approximate numbers provide useful perspective.
Measure the Current State First
Six Sigma uses the concept of establishing a baseline before making improvements. The principle is simple: if you do not understand the current performance of a process, it becomes difficult to prove that your change actually helped.
Depending on the process, useful baseline measurements might include:
minutes per transaction
number of errors per month
average response time
percentage of inquiries receiving follow-up
days between completing work and sending an invoice
number of manual steps
Do Not Chase False Precision
Small businesses rarely need a complicated measurement system for every improvement.
If you know a task takes approximately 15 to 20 minutes, there is little value in spending hours determining whether the exact average is 17 minutes and 42 seconds.
The purpose of measurement is to support a decision.
Is the problem meaningful?
Is the proposed improvement worth pursuing?
Did the result actually get better?
Measure Again After the Change
Once you implement an improvement, repeat the measurement.
If a process previously required 20 minutes and now requires eight, you have recovered 12 minutes every time that process occurs.
Multiply that difference by its frequency and you can estimate the annual value of the improvement.
This simple before-and-after comparison is one of the most important habits a growing business can develop.
It shifts improvement from "this feels better" to "this produced a measurable result."
To give access to Google Search Console, ensure you have owner permission for the property and the provided Google Account email.
Open Google Search Console, navigate to Settings, and select Users and permissions to add Practical Momentum.
Choose the appropriate access level: Full user is typically sufficient for SEO analysis, while Owner access is only needed for specific tasks.
Remember to verify you are adding access to the correct property; organizations may have multiple entries for the same site.
Access to both Google Search Console and GA4 provides a comprehensive view of site performance for SEO projects.
If Practical Momentum is helping with SEO, website visibility, content performance, indexing, or search reporting, we may ask you to provide access to your Google Search Console property.
You do not need to share your Google password. Search Console allows an existing property owner to add another Google Account and control that user's permission level.
This guide explains how to add Practical Momentum securely and how to choose the appropriate access level.
Before You Start
You will need:
Access to the Google Search Console property for the website we are working on.
Owner permission for that Search Console property.
The Google Account email address Practical Momentum provided for your project.
If you are not an owner, you can still use Search Console, but you cannot add other users. In that case, the current property owner will need to complete the steps below.
Open Google Search Console
Go directly to Google Search Console and sign in with the Google Account that manages your website.
Use the property selector near the top of the page to make sure you are working with the correct website property.
How to Add Practical Momentum to Search Console
Open the correct property in Google Search Console.
Click Settings in the left navigation.
Select Users and permissions.
Click Add user.
Enter the Google Account email address Practical Momentum provided to you.
Choose the permission level requested for your project.
Click Add.
Practical Momentum can then confirm that the property is visible and that the assigned permissions are sufficient for the work being performed.
Which Search Console Permission Level Should You Choose?
Search Console uses three main access levels for people who can open a property.
Owner: Has full control of the property, including the ability to add and remove users and change important settings.
Full user: Can view all Search Console data and perform several useful actions. This is usually sufficient for ongoing SEO analysis and optimization work.
Restricted user: Can view most data but has fewer capabilities. This may be appropriate for limited reporting or review work.
For most Practical Momentum SEO engagements, Full user is generally the appropriate level unless we specifically request something different.
Owner access should not be granted simply because a consultant or agency is helping with SEO. We will ask for ownership-level access only when a specific task genuinely requires it.
Make Sure You Choose the Correct Search Console Property
Some organizations have several Search Console properties for the same website. For example, you may see both a domain property and one or more URL-prefix properties.
Whenever possible, use the property that provides the most complete coverage of the website involved in the project. If you are unsure which one is correct, send us the property names you see and we can help you identify the best option.
Why Search Console Access May Be Needed Even When We Already Have GA4
Google Analytics 4 and Google Search Console provide different types of information.
GA4 is primarily focused on what happens after visitors arrive on your website. Search Console focuses on how your site appears and performs in Google Search.
Search Console can provide information such as:
Google Search queries that generated impressions and clicks
click-through rates and average search positions
pages receiving traffic from Google Search
indexing and page discovery issues
sitemap status
URL inspection information
search-related enhancements and technical issues
When SEO or organic search performance is part of the project, having access to both GA4 and Search Console gives us a more complete picture.
What Happens After You Add Access?
Once access is active, Practical Momentum can use Search Console to evaluate organic search performance, identify indexing or visibility issues, review queries and landing pages, monitor technical search signals, and measure whether SEO improvements are producing meaningful results.
Your organization remains in control of the property. An owner can change or remove our access whenever needed.
Security Best Practices
Never send your Google password or multi-factor authentication codes.
Add only the Google Account email address Practical Momentum provided.
Use Full or Restricted access unless Owner access is specifically required.
Confirm that you are adding us to the correct website property.
Review user access periodically and remove access that is no longer needed.
Having Trouble?
If you do not see Users and permissions, you probably are not an owner of that Search Console property. The person who originally verified the website, your web developer, your prior SEO provider, or another administrator may be the current owner.
If you are unsure who owns the property, let us know what you can see in Search Console. We can help determine the most practical next step without asking for your login credentials.
