Still Asking “Where Are We At With This?” You Have a Visibility Problem
There's a question I hear constantly in business operations:
“Where are we at with this?”
Where are we at with that project?
Did that estimate go out?
Did anyone follow up with that customer?
Is that job finished?
Are we waiting on the client?
Did those materials get ordered?
How many hours do we have into that job?
Has anyone reviewed this?
Every business needs to ask questions.
But if management spends a large part of the day tracking down the answers, there's probably a bigger issue.
You don't necessarily have a communication problem.
You may have a visibility problem.
How Long Does It Take to Get an Answer?
Here's a simple test.
Ask someone on your team:
“What's the status of Project X?”
What happens next?
Can they look at one system and tell you?
Or do they need to:
Check their email.
Open a spreadsheet.
Look through text messages.
Ask another employee.
Check a project management system.
Call someone in the field.
Then come back to you?
If it takes five different places to answer one basic operational question, the information exists.
It just isn't visible.
Information and Visibility Aren't the Same Thing
Most companies have plenty of information.
The problem is where that information lives.
Part of the project is in someone's inbox.
Another part is in a spreadsheet.
The latest update is in a text message.
The hours are somewhere else.
Photos are on someone's phone.
The customer conversation is in another system.
Technically, everything is there.
But management can't see the complete picture.
That's the difference between having information and having operational visibility.
What Should You Be Able to See?
The answer depends on your business.
But imagine opening one dashboard and immediately seeing:
Projects
Not Started
In Progress
Waiting on Customer
Waiting on Materials
Needs Review
Complete
Estimates
Needs Estimate
Estimate in Progress
Submitted
Needs Follow-Up
Won
Lost
Jobs
Scheduled
In Progress
Additional Work Required
Complete
Ready to Invoice
Team
Hours by Employee
Hours by Job
Overdue Tasks
Work Due This Week
Leads
New
Contacted
Needs Quote
Follow-Up Due
Approved
Closed
Now management isn't asking employees to create the picture.
The system is showing it.
Good Visibility Changes Management
When information is difficult to access, managers become information collectors.
They spend time asking:
“Did this happen?”
“Who has this?”
“When is this due?”
“What's holding this up?”
“Did anyone contact them?”
But when the operation provides visibility, the questions change.
Now management can ask:
Why are five projects stuck at this stage?
Why are we consistently exceeding estimated hours on this type of work?
Why are leads sitting too long before follow-up?
Why are estimates taking longer this month?
Those are much more valuable questions.
You're no longer trying to figure out what's happening.
You're improving why it's happening.
Dashboards Should Help You Make Decisions
A dashboard isn't useful simply because it looks impressive on a screen.
I've seen plenty of dashboards full of charts that don't help anyone make a decision.
The better question is:
What does management need to know in order to act?
If an estimate is overdue, someone needs to know.
If a project has exceeded its expected hours, someone may need to investigate.
If a customer hasn't responded, someone may need to follow up.
If work is complete but hasn't been invoiced, someone needs to see it.
If an employee is overloaded, management should know before deadlines start getting missed.
A useful dashboard doesn't just display information.
It draws attention to what needs action.
But the Dashboard Is the Last Step
There's something important here.
You can't build good visibility on bad information.
Before creating dashboards, you need to determine:
What should be tracked?
Who enters it?
When is it entered?
Where does it come from?
What statuses actually matter?
What does “complete” mean?
What should happen when something changes?
That's why simply buying dashboard software doesn't solve an operational problem.
The process underneath it still matters.
Stop Creating Reports People Could Already Have
Here's another sign of a visibility problem.
Every Friday, someone spends hours gathering information so management can understand what happened that week.
They pull numbers from one system.
Update a spreadsheet.
Check another report.
Calculate totals.
Ask employees for missing information.
Then create the weekly report.
And next Friday?
They do it all over again.
Ask:
Could the system already know this?
If employees are recording their time against jobs throughout the week, weekly hours shouldn't necessarily require someone to manually calculate them.
If project statuses are being maintained, someone shouldn't need to create a separate list of open projects.
If lead follow-up dates are being recorded, someone shouldn't have to manually search for who needs to be contacted.
Collect the information as part of the normal workflow.
Then let the system organize it.
One Source of Truth Doesn't Always Mean One Piece of Software
This is another misconception.
Operational visibility doesn't necessarily mean forcing your entire company into one platform.
Your estimating team might still use Excel.
Accounting might use accounting software.
Your sales team might use a CRM.
Field employees might use a custom app.
Your project team might use monday.com.
That's okay.
The goal isn't necessarily:
One tool for everything.
The goal is:
The right information gets to the right place.
Sometimes the best operational system is a group of tools that work together.
Try the 10-Minute Test
Give yourself ten minutes.
Without asking another employee, can you determine:
What's overdue?
What's waiting on a customer?
What's waiting internally?
Which projects need attention?
Which jobs require additional work?
Which estimates need follow-up?
What work was completed this week?
Where your team's time went?
What's coming next?
If you can, you probably have pretty good operational visibility.
If gathering those answers takes half the day?
That's worth examining.
