Understanding the Duvall Framework for Business Process Maturity
The Duvall Curve is a process maturity model that maps how IT and business operations evolve through four distinct stages: ad hoc, repeatable, defined, and managed. It was originally developed within the ITIL community to help organizations understand where their service processes sit and what improvements are realistically achievable at each phase. Most companies start at stage one, where work gets done by heroics and tribal knowledge, then slowly climb toward stage four, where metrics drive continuous improvement. Before you start mapping anything, you need to honestly assess which stage your core processes actually occupy. I have watched too many teams skip this step and immediately try to implement full-service level agreements and automated reporting dashboards for processes that are still being figured out on the fly. That mismatch between maturity level and tooling investment is the single biggest reason these initiatives stall out within six months. Start by listing your critical business processes—the ones that, if they broke, would cause revenue to drop or compliance to fail. For each one, ask three questions: Is it documented? Can two different people execute it with the same outcome? Are the results measured against a baseline?
If the answer to all three is no, you are firmly in the ad hoc stage. If documentation exists but people ignore it, you are in the repeatable stage. If documentation is followed consistently and results are tracked, you have reached the defined stage. Managed is when you use those metrics to forecast and optimize proactively rather than reactively.
What Changes at Each Stage
The practical shift between stages is not about buying new software. It is about changing who is accountable for process outcomes. In the ad hoc stage, individual contributors own results. By the defined stage, process owners exist with clear authority to enforce standards. The managed stage requires that those process owners have access to data systems that give them visibility into performance trends over time. I spent two years helping a mid-market logistics company move from repeatable to defined. The breakthrough was not a new tool. It was getting their VP of Operations to stop treating the standard operating procedure document as a suggestion and start making promotion decisions based on whether people followed it. Process ownership without accountability is just a Google Doc.
Get the Full Details
Implementation Steps That Actually Work
Pick one high-impact process to start with. Do not attempt a company-wide rollout. A single process gives you a controlled environment to practice the discipline of documentation, measurement, and review before scaling. Map the current state as it actually works, not as it should work. This is uncomfortable because you have to write down the messy reality, but fixing a process you do not understand is waste. Then define the target state. Write it in plain language. A flowchart alone will not work because most of your people do not read them. Pair the visual map with written acceptance criteria for each step. What does done look like? What inputs are required? What is the expected output? After that, establish a measurement cadence. Every process needs at least one leading indicator and one lagging indicator. Leading indicators predict problems before they happen. Lagging indicators tell you what already went wrong. For a customer onboarding process, a leading indicator might be time from contract signature to first training session scheduled. A lagging indicator might be first-contact resolution rate after go-live.
Common Pitfalls and How to Avoid Them
The biggest mistake I see is treating the Duvall model as linear and permanent. Once you reach the defined stage, you do not stay there forever. Processes decay. Staff turnover changes how work actually gets done. You need to schedule a process health review every ninety days minimum, and more frequently for critical functions. I learned this the hard way when our change management process looked perfect on paper for eighteen months, then completely fell apart after a reorganization we had not accounted for in the documentation. Another pitfall is over-investing in measurement before the process is stable. If your workflow changes weekly, spending two weeks building a dashboard to track it is a poor return on time. Get the process consistent first, then instrument it.
When the Duvall Model Falls Short
The framework assumes a certain level of organizational stability. It works well in established companies with defined roles. It struggles in early-stage startups where the business model itself is shifting every quarter. In those environments, the effort required to maintain process documentation can slow experimentation more than it improves consistency. For those cases, lightweight process mapping using a shared kanban board or a simple runbook document often delivers better results than a formal maturity model exercise. There is also a cost ceiling. Moving from defined to managed requires data infrastructure that most mid-size companies do not have and cannot justify until they have enough process volume to make automation worthwhile. If you are processing fewer than a hundred transactions per week through a given workflow, the managed stage is probably not cost-effective to pursue yet.
A Practical Checklist
Document your current process state honestly, with acceptance criteria for every major step. Identify one process owner per critical workflow. Establish at least one leading and one lagging metric per process. Schedule a recurring review cadence. Resist the urge to automate before you can articulate the process in plain language. Measure the same way for at least one full quarter before declaring success or failure. Expect to revise documentation after significant staffing or tooling changes. The Duvall framework is not a product you install. It is a lens for understanding where your operational discipline stands and what kind of effort is needed to move forward. Treat it that way and it will serve you. Treat it as a certification checklist and you will produce a pile of outdated documentation and feel like you wasted your time.
