By Bryan Howard, Founder and CEO of Peoplyst
The report gets to the client on Friday because the owner finishes it Thursday night. By Monday, she's behind on the work she set aside to get it done. Her project lead is behind too.
After a few weeks, she decides the team needs to take more ownership. She schedules a meeting. Everyone agrees. The following Thursday, she's back at her desk.
Before deciding this is an ownership problem, look at what keeps sending the work back to her.
At Peoplyst, we use People, Leaders, Systems, and Execution to investigate recurring business problems. These Four Drivers show where the work breaks down and what is contributing to it.
Business drag is the unnecessary effort created by friction, confusion, and resistance. Our Results Alignment Method uses the Four Drivers to locate that drag, clarify what the work requires, and align people and systems around it. Then we test a change and check the result.
You can use the same approach. Start with one problem that keeps coming back and a recent example of what happened.
The Four Drivers of Better Business Results
The Four Drivers give owners and leaders a practical way to investigate a problem before committing time and money to a solution.
| Driver | What it covers | The question to ask |
|---|---|---|
| People | Capability, capacity, role clarity, and the support people need to contribute. | Can the people doing the work realistically produce the result? |
| Leaders | Priorities, decisions, expectations, coaching, and what leaders reinforce. | Are leadership decisions helping people do the work? |
| Systems | Processes, tools, policies, information, and handoffs. | Does the way work moves support the result? |
| Execution | Ownership, delivery, measurement, follow-through, and adjustment. | Are commitments becoming completed work that produces the intended result? |
One problem can involve all four. A missed delivery might begin with an overloaded employee, a promise made without checking capacity, and information that arrives too late. A progress review held the day before the deadline leaves little time to respond.
Where the Four Drivers came from
I've served as both a Chief People Officer and a Chief Operating Officer. Staffing decisions affect what a business can deliver. Operating decisions affect what employees are being asked to carry. I've had responsibility for both.
That experience shapes the Four Drivers we use at Peoplyst. The framework lets us examine how those responsibilities affect each other.
A request for training, for example, gives us several questions to investigate. What do people need to do differently? Have they learned how? Do they have time to do it? What happens when they follow the process and a manager tells them to skip a step?
Why the Four Drivers apply in every business
Every business has work to do, decisions to make, a way of doing the work, and commitments to fulfill. Those functions exist whether the business has one person or several thousand.
A solo consultant makes promises to clients, manages available time, uses tools to deliver the work, and checks whether the client received what was agreed. A company with twenty locations distributes those responsibilities across many people. The connections become harder to see as the business grows.
The evidence will differ by industry. A manufacturer might trace a defective order through production. A bank might follow a loan application that waited several days for missing information. Both can examine who was equipped to do the work, which decisions shaped it, how it moved, and when someone checked the result.
Market conditions, customer demand, and financing also affect performance. Include those realities in the investigation. The Four Drivers help you examine how your business is equipped to respond.
How to examine each driver
People and the ability to do the work
Start by comparing what the work requires with what the person has available.
A capable employee can have more work than the week will hold. A new employee can complete orientation and still be unsure what acceptable work looks like. A role can carry responsibility for a result without the information needed to produce it.
Ask someone to show you a recent piece of work. Where did they need help? What interrupted them? Which decisions required somebody else's approval?
If you suspect a skill gap, look at a work sample or watch the task being performed. Then check the conditions around it. Someone who can do the work during a quiet demonstration may struggle when five competing requests arrive at once.
Training is useful when people need knowledge or practice. A workload problem requires a decision about the work, staffing, or commitments. Adding a course to an already impossible week gives the employee another thing to finish.
Start here: Compare the work assigned with the time, capability, and support actually available.
Leaders and the decisions that shape performance
Leadership shows up in ordinary choices. A manager accepts a rush request. An owner reverses a decision. Two department heads give different instructions about what comes first.
Look at the last time priorities collided. Who decided what would move? Did the people affected hear about the change? Were they allowed to adjust an existing commitment?
Also examine what happens when someone acts independently. If the owner routinely takes the work back or changes decisions without explaining why, people learn to wait for approval.
Make the boundaries clear. A supervisor should know which decisions they can make, when to consult someone, and what requires escalation. Leaders then need to support reasonable decisions made within those boundaries.
Start here: Find one recurring decision that keeps waiting and clarify who can make it.
Systems and the way work moves
Systems include the process, information, and rules people use to get work done. Software is part of that picture. So are approval requirements and the handoff between sales and delivery.
Follow one request from arrival to completion. Pay attention to waiting time. A task that takes twenty minutes to perform can spend three days waiting for someone to approve it.
Look for information entered twice, conflicting versions, and work returned because something was missing. Ask about the spreadsheet beside the official system. What does it let people do that the official process doesn't support?
That answer helps define what needs to change. You might need better technology, a clearer handoff, or an agreement about what must be ready before work begins.
Check what an approval protects before removing it. A faster process still needs to produce accurate work and manage the risks that matter.
Start here: Trace one recent request and identify where it waited or had to be redone.
Execution and the follow-through that produces results
Execution connects an agreement to what happens afterward.
A team can leave a meeting with a clear plan and discover a week later that a dependency has stalled the work. The person maintaining the tracker may have no authority to resolve it. Meanwhile, the status stays green because nobody has missed the final deadline yet.
Name the person responsible for the result and the decisions they can make. Agree on evidence you can inspect while there is still time to act. That might be a draft, a completed customer order, or a sample of cases handled under a new process.
“I'm working on it” gives you very little to inspect. Seeing the work helps you decide whether someone needs support or the plan needs to change.
When you introduce an improvement, check whether people use it and whether it helps. Publishing a checklist proves that a checklist exists. You still need to know what happened on the next eligible piece of work.
Start here: Choose a checkpoint that shows progress early enough to influence the outcome.
Business drag makes the connections visible
To find business drag, look for unnecessary effort around the useful work.
Friction shows up when a routine task requires repeated follow-ups or avoidable rework. Confusion appears when people disagree about the priority, the owner, or what finished work should look like. Resistance appears when a change meets hesitation, workarounds, or refusal.
Each gives you something to investigate. Resistance, for example, can tell you that a new process makes a customer's experience worse, that people haven't learned how to use it, or that a leader continues rewarding the old behavior. Ask what is happening before deciding what it means.
Drag becomes especially easy to miss when capable people absorb it. They stay late, chase missing information, and repair the handoff. The customer receives the work, so the cost disappears into somebody's calendar.
Count that cost. Include time spent rescuing work, correcting errors, and restarting tasks after interruptions. Otherwise, your performance measures can make an exhausting process look dependable.
A business performance problem seen through all four drivers
Maya and Ben are fictional characters from our Four Drivers working guide. Maya owns a professional services firm, and Ben leads client projects.
On Thursday afternoon, she's asking about a report due Friday.
“I'm waiting on a few things,” Ben says.
They finish it together that evening. After several weeks of the same routine, Maya asks for help.
“I need people who take ownership. I can't keep finishing everybody's work.”
The investigation starts with the last report and the commitments that led to it.
Ben had about thirty hours available for project delivery after client calls and other responsibilities. His assigned projects needed roughly forty. Evening work had become part of the firm's capacity plan without anyone calling it that.
The delivery dates reveal another problem.
Maya had accepted a rush request on Tuesday. She expected Ben to work out what needed to move. Ben understood that every existing deadline still applied.
Nobody had decided which commitment would change.
The missing information creates another problem. One correction arrived in an email, another in a text to Maya. Ben couldn't tell which version to use. The firm had promised a delivery date before confirming that the work was ready to begin.
They also look at when progress is reviewed.
Maya usually asks for an update when she starts worrying about the deadline.
“Thursday,” Ben says.
Across the four drivers, they can now see a connected explanation: a capacity gap, an unresolved leadership tradeoff, scattered information, and a review that discovers trouble too late.
They choose one first change. Before Maya confirms a date for a new report, she and Ben will check the time available against the work already promised. She will decide what changes when a rush request arrives.
For the first review, they record whether they used the check, which decisions it affected, and what happened to delivery, quality, and evening rescue work. They keep the information check and an earlier draft review as possible next changes.
Ben can now make the workload visible before a promise is made, and Maya can decide which commitments the firm can realistically keep.
How to diagnose a recurring problem in your business
You can begin with a focused conversation and a few recent examples. Include the people doing the work and someone who can make the relevant decisions.
Describe the problem in observable terms
Write down what happened and what you needed to happen.
“Our managers need accountability” leaves too much open to interpretation. A usable description would be: “Three customer issues waited for the owner this week, although the supervisors had the information needed to resolve them.”
Add the consequence. How long did customers wait? What other work stopped? That helps you judge whether this is the problem to address first.
Follow one recent example
Ask the person involved to walk you through it. Look at the request, the handoff, and the finished work. Find out what they knew at each point and what they were waiting for.
Keep a short record of what you know, what you suspect, and what you still need to check. An explanation can sound convincing long before you have evidence for it.
Examine the example through all four drivers
Use the questions in the table near the beginning of this article and look for connections between the answers.
If an employee lacked time, find out how the work was assigned. If a handoff was incomplete, find out who defined the requirements and when anyone noticed. Several conditions may contribute to the same result.
Compare the example with a time the work went well. What was different? That comparison can help you identify a useful change.
Choose one change and make it usable
Choose a change supported by what you observed. Keep the first test small enough to manage and adjust. If the evidence is thin, gather another example before selecting a solution.
Agree on who owns the test, which work it covers, and what support it needs. Explain the new approach to everyone affected, including the person receiving the work.
Use this sentence to make the agreement specific:
“For ___, we will try ___ because ___. ___ owns the test. On ___, we will review ___ and decide what happens next.”
Review the result and make the next decision
Record the starting point before changing the process so you have something to compare. Choose a review date that fits the frequency of the work. Two weeks can provide useful evidence for a daily process. A quarterly activity needs a different window.
Check whether the change was used, what happened to the result, and whether it created problems elsewhere. Include exceptions. A faster turnaround means little if customers receive incomplete work.
If people didn't use the change, find out what prevented them. If they used it and the result didn't improve, revisit your explanation. Continue, adjust, expand, or stop based on what the evidence supports.
How Peoplyst uses the Four Drivers with clients
With clients, the Results Alignment Method starts with the business result that needs to improve. We examine the work with the people closest to it and agree on what to change first.
The work that follows depends on what we find. It might involve workforce planning or role clarity, manager development and coaching, a workflow improvement, or clearer ownership and progress reviews. Often, a useful solution connects several of these.
Our First Onsite case study describes what connected support can look like. Before the program, more than half of the company's new hires were quitting within six months. Exit surveys showed that they felt disconnected from the business and unclear about their roles.
The response combined onboarding planners and learning resources in three languages with mentoring and role-specific coaching. New employees received preparation, while managers had a more consistent way to support them.
In the case study, Leah Pearson, identified as First Onsite's Director of Global Talent Management, reported stronger new-hire engagement and motivation and less onboarding pressure on managers. The case study does not publish a post-program turnover rate. It shows why an onboarding problem can require changes to both employee preparation and the way support is organized.
We also agree on how much of the work you want Peoplyst to carry. With Guide You, your team leads and we provide expertise and feedback. With Done With You, we build and implement alongside your team. With Done For You, we lead or complete the agreed work and involve you in the decisions that need your authority.
Whichever level fits, the review stays connected to the business result. We want to know whether the new approach is being used and what it is changing for the people relying on the work.
Start with the Four Drivers working guide
Download The Four Drivers of Better Business Results and use it with your team to investigate one recurring problem. The free working guide includes the full Maya and Ben example, investigation questions, and reusable worksheets for planning and reviewing a change.
Download the free Four Drivers working guide
Need a quicker first step? The free Peoplyst Results Alignment Check uses twelve questions to help you identify what to examine next. Use that feedback to focus your review of the actual work.
Prefer help with diagnosis or implementation? Book a free 15-minute review or call 904-404-5434. Bring a recent example and tell us what you've already tried.
Bryan Howard is the founder and CEO of Peoplyst and a former Chief Operating Officer and Chief People Officer. His experience across people and operations shapes how he helps business owners examine recurring problems and improve the work behind their results. Peoplyst supports clients across People, Leaders, Systems, and Execution.