✦ THE PROBLEM
The system can be technically correct and still make the work harder.
Organizations rarely set out to build cumbersome systems. They accumulate them. A policy gets added to solve one problem. A spreadsheet fills a gap in the HRIS. A workaround becomes the process. Before long, people are spending more time navigating the system than the system is saving them.
The problem may show up in payroll, benefits, compliance, performance management, job architecture, or everyday employee processes. But fixing the individual symptom without looking at how the pieces connect often creates one more workaround.
I help identify where the friction actually lives, what still serves a purpose, what no longer does, and how the pieces can work together more clearly.
.
✦ WHAT IT CAN LOOK LIKE
The system works. The workarounds work harder.
It shows up as spreadsheets built around the HRIS, policies interpreted differently depending on who answers the question, payroll processes that depend on one person remembering the exceptions, or job descriptions that stopped describing the jobs years ago.
Sometimes every individual piece technically works. The friction lives between them. Information gets entered twice, employees learn which process to bypass, managers create their own systems, and capable people quietly compensate for problems the organization has stopped noticing.
✦ WHAT I CAN HELP CHANGE
The goal isn't more process. It's a system people can actually use.
I help organizations make the infrastructure behind the work clearer, more useful, and easier to maintain. That can mean rethinking policies, HRIS implementation and payroll workflows, job architecture, performance management, benefits administration, compliance practices, or the handoffs between them.
Sometimes the answer is better technology. Sometimes it's a better process, clearer ownership, fewer steps, or retiring something that no longer earns the effort it requires. The point isn't to add sophistication for its own sake. It's to build systems that support the people doing the work instead of asking them to compensate for the system.
✦ WHEN THIS WORK IS USEFUL
The work evolved. The systems supporting it didn't.
This work is especially useful when growth, new technology, regulatory requirements, acquisitions, leadership changes, or years of accumulated workarounds have outpaced the systems underneath the work. What once made sense may now require too many steps, too much explanation, or too much institutional memory to keep functioning.
It can also help when no single process looks broken, but employees keep finding friction between them. The clues are often ordinary: repeated questions, duplicate entry, inconsistent answers, manual fixes, missed handoffs, or one person who somehow knows how everything actually works.
✦ HOW I APPROACH IT
Start with how the work actually gets done, not how the process says it gets done.
I start with the work itself: what triggers the process, who touches it, where information comes from, where it goes next, and what people have learned to do when the formal process doesn't quite work. The workaround is often evidence, not noise.
From there, I look at the system as a whole. Technology, policy, ownership, handoffs, compliance requirements, and employee experience all matter. The recommendation might involve redesigning a workflow, clarifying responsibility, configuring or implementing technology, simplifying a policy, or eliminating a step that no longer earns its place.
If the system is creating more work than it solves, start with the friction.
You don’t need to know what the solution is before we talk.
Start with what’s happening, and we’ll figure out what actually needs to change.