Operational Systems FAQs

You will receive a reply within one business day to schedule a 30-minute fit conversation. After the call, you receive a short written summary within two business days: whether the problem is a fit, the recommended starting point, and what that step would involve. There is no obligation. If it is not a fit, I will say so.

No. The assessment exists because symptoms and causes are often different. Bring the friction, not a predetermined solution. The work begins by following how the process actually operates and separating the visible symptom from the system creating it.

We select a defined workflow or operating area and follow the work as it actually happens. The assessment looks at intake, ownership, information flow, decisions, handoffs, tools, workarounds, quality controls, visibility, and risk. You receive a current-state map, findings, and a prioritized roadmap, delivered in writing and walked through in a readout session.

Every engagement is scoped and priced in writing before work begins. The assessment is a fixed fee. Redesign and adoption work is quoted as a fixed fee or in defined phases. Price depends on the number of workflows, teams, and systems involved, the depth of documentation, and how much implementation support you want.

Typically 2 to 4 weeks for an assessment, 4 to 8 weeks to redesign one critical workflow, and 4 to 12 weeks for playbook and adoption work, including a pilot. The written scope states the timeline and what could extend it.

For an assessment, typically about one hour a week from a sponsor and a 45 to 60 minute interview with each of four to eight people. Redesign and adoption work asks more of the people who do the work, and the written scope lists it in advance.

I am based in Charlotte, North Carolina, and work with clients across the U.S. and internationally. Some work can be done remotely. On-site sessions are available when the work benefits from them and are agreed in the scope. Travel for on-site work outside the Charlotte area: for on-site work more than 50 miles from Uptown Charlotte, North Carolina, the client is responsible for travel expenses, including airfare, rental cars, and accommodations. These expenses will be estimated and approved in advance, with payment due before travel is booked.

No. The work helps leadership and internal teams see the operating problem clearly, build the missing structure, and improve how existing people and tools work together. Internal owners remain essential because the objective is a system the organization can maintain.

Only when the workflow supports the need. A new platform should solve a defined operating requirement. It should not become a substitute for clarifying the process, ownership, information, decisions, controls, and adoption requirements the tool is expected to support. I do not resell software or accept referral fees.

Yes. Implementation and adoption support can pilot the redesigned process, refine documentation, align stakeholders, support tool configuration, establish operating checkpoints, and transfer ownership internally.

You will be clearly notified in writing. The findings and roadmap are yours to use with any provider or internal team. However, if you require an external vendor to execute the recommendations, vendor management can be scoped as a separate engagement.

The objective is to create a system that is transferable, teachable, and maintainable by internal owners. Outside support may continue where it creates value, but dependency is not the design intent.

Yes. Operational information shared during an engagement is used only for that engagement.