This video is part of Inteq Group's broader video series designed to give practitioners and business leaders deep insights into strategy, strategy execution, business process management, process reengineering, digital transformation, and business systems analysis. In this particular video, the focus is on one of the most common questions Inteq receives from clients and colleagues: When we talk about reengineering, what are the kinds of things we can actually do inside our organization?
.png?height=200&name=BPR-360-Framework%20(1).png)
This video provides a six-step framework for executing BPR - whether the work is incremental process improvement or full-scale transformational reengineering - along with the "secret sauce" that makes the difference between a one-time initiative and a sustainable, ongoing program of improvement.
Before getting into the six steps, it helps to be clear about the distinction between Business Process Reengineering (BPR) and Business Process Management (BPM) - because the line between them is grayer than many people think.
Business Process Management tends to focus on incremental change to existing processes. It operates within the current process footprint, improving upon it over time without fundamentally redesigning it. BPM is the ongoing, business-as-usual engine of continuous improvement.
Business Process Reengineering is more aggressive. It uses the current state as baseline context - but it isn't constrained by that baseline. BPR asks: what do our processes need to look like to achieve our strategy? It is willing to radically change the underlying process model when the situation demands it. BPR is more directly linked to organizational strategy and tends to be more transformational in nature.
These approaches are not incompatible. In practice, most organizations move through a cycle: a BPR initiative delivers the transformational changes needed to reach a new operating model, then BPM takes over to continuously refine and improve within that new model. The Inteq BPR framework supports both approaches - and the six steps below apply to both.
Every BPR or BPM initiative starts in the same place: map the current state.
Map out the work activities, roles, reporting relationships, and workflows that make up the existing process. This is good solid business process mapping - understanding what is actually happening today before deciding what needs to change.
There is sometimes resistance to spending time on current state analysis, particularly in reengineering engagements where the instinct is to jump straight to the future. That instinct is understandable but mistaken. In almost every engagement, the honest answer is that the organization doesn't fully understand its own current state - not at the level of detail needed to make informed decisions. Deep current state mapping is the foundation. Without it, every subsequent step is built on assumptions that may not hold.
This is true whether the initiative is incremental BPM or transformational BPR. Start where you are. Build on that starting point.
With the current state documented, the next step is analysis: look for gaps, root causes, and opportunities - and connect them to organizational strategy.
The analysis is always oriented around two core dimensions:
These are not in tension. It is possible to increase the value proposition while simultaneously becoming more efficient. That combination - doing more valuable things in more economical ways - is the goal.
A useful framework for conducting this analysis is the five essential business analysis questions:
With the analysis in hand, Step 3 builds the opportunity inventory: identify, analyze, and validate the specific changes that would address the gaps and root causes surfaced in Step 2.
This includes both the operationally focused improvements from Questions 2 and 3 - the incremental, within-footprint changes - and the more forward-facing, strategic opportunities from Questions 4 and 5. The latter category, in particular, needs to be evaluated against organizational strategy. Process improvements that align directly to strategic objectives tend to be the most transformational and the highest priority.
At this stage, the full opportunity inventory is likely to be large - far more items than any organization can realistically tackle at once. Step 3 is about building that complete picture before Step 4 forces the hard prioritization decisions.
Step 4 is where the work gets concrete. With a full opportunity inventory in hand, the task is to shortlist, design, and operationalize.
Shortlisting. Every engagement will surface more opportunities than time, budget, and capacity allow. The shortlisting exercise identifies which opportunities - given the organization's constraints - will have the greatest impact on operational effectiveness and efficiency. This might mean taking thirty of a hundred and fifty identified opportunities and building a phased roadmap around them.
Future state mapping. Once the shortlist is established, model the future state. Create process maps that show what the process will look like as changes are implemented - not just the end state, but the intermediate states as well. What does the process look like in thirty days? Sixty? Ninety? Six months out? A year? These time-slice maps provide the visual foundation for leadership dialogue, build organizational support, and often surface connections and dependencies that weren't visible before.
Operationalizing. This is the step that is most frequently overlooked - and the omission is one of the most common sources of implementation failure. Before any change can actually be implemented, it has to be built out: new workflows and procedures designed, technology functionality developed and tested, people trained. Do not attempt to do this on the fly. Build it out, test it, and then implement. Organizations that skip this step pay for it later.
Step 5 is the operationalization step made explicit: the organization actually constructs the components required to enable the future state.
This includes designing new workflows and procedures, developing or enhancing application functionality, testing those changes in a controlled environment, and resolving issues before go-live. Each of the shortlisted opportunities needs to be built out and validated before implementation begins. This step sounds straightforward, but it is consistently underinvested in. Get ahead of it. Build, test, and be ready before moving forward.
Step 6 is classic implementation - planned, sequenced, and managed.
Key considerations:
Sequencing and dependencies. Of the twenty or thirty things being implemented, which ones have dependencies? Which need to be in place before others can follow? Map those dependencies and sequence the implementation accordingly.
Change management. The process design can be technically excellent, but people have to engage with it. Change management is the people side of this work: communicating what's changing and why, equipping people to operate in the new model, and managing the transition. It is not optional. Even a well-designed process will fail to deliver its value if adoption is poor.
Performance metrics. Define what success looks like before implementation, not after. What metrics will indicate that the process changes are delivering the intended improvements in effectiveness and efficiency? How will those metrics be captured? Getting this in place before go-live is essential to being able to evaluate results and make adjustments.
The six steps above are a framework for a BPR initiative - but the real secret sauce is what happens after the initial implementation is complete.
The most common mistake organizations make is treating BPR as a one-time event. They identify a set of opportunities, implement thirty or forty of them, and then declare success and move on. The process gradually drifts back toward business as usual, and a few years later the organization finds itself in the same position: processes that have fallen behind, a gap between where things are and where they need to be, and another reengineering initiative required to close it.
The alternative is to build a permanent structure for ongoing process improvement - and the centerpiece of that structure is the opportunity backlog.
What the opportunity backlog is. It is a living list of identified process improvement and transformation opportunities. At any point in time, it contains the items currently in implementation, the items shortlisted for near-term implementation, and the longer-term opportunities that have been identified but not yet scheduled. Think of it as a prioritized, dynamic queue.
Grooming the backlog. Grooming means continuously reviewing and updating the backlog: reprioritizing as business conditions change, adding new opportunities as they are identified, retiring opportunities that are no longer relevant, and ensuring the most important items are always surfacing to the top. As implemented items close out and free up resources, the next set of opportunities can move forward.
Separating strategic from operational. The backlog should always distinguish between two types of opportunities: the transformational, strategically-linked BPR initiatives and the ongoing, incremental BPM improvements. Both matter - but for different reasons and on different timelines. The strategic transformational items should be explicitly tracked against organizational strategy. The operational improvement items should be continuously flowing through the improvement pipeline.
The intake mechanism. For the backlog to stay current, the organization needs a formal mechanism for capturing new opportunities as they emerge. This means creating outreach channels - a business relationship management function that actively engages stakeholders, subject matter experts, and customers; internal submission mechanisms like forms or designated email addresses; and a culture that treats process improvement as an ongoing responsibility, not a periodic event. The intake mechanism ensures that what the business is learning in real time finds its way into the improvement pipeline.
The Inteq BPR framework reflects a view that BPR and BPM are not competing approaches - they are two phases of the same lifecycle.
Organizations start with a BPR initiative to make the transformational changes required to reach a new operating model. That might mean rethinking how the business engages customers, automating processes that were previously manual, realigning organizational structure around new workflows, or implementing capabilities that didn't previously exist.
Once those transformational changes are made, the organization moves into a BPM phase: ongoing, incremental improvement within the new operating model. Continuous refinement, continuous grooming of the backlog, continuous adaptation to changes in the business environment.
And when the business environment shifts significantly enough - when strategy changes, when new competitive pressures emerge, when new technology fundamentally changes what's possible - the cycle begins again with a new BPR initiative.
The key is not to let either phase collapse. Don't get so focused on the transformational work that incremental improvements stop flowing. And don't let the comfort of incremental improvement prevent the organization from making the transformational changes that strategy requires.
Both are important. Both can happen simultaneously. That's the secret sauce.
Inteq Group offers management consulting services and a full suite of training programs in business process management, business process reengineering, business systems analysis, digital transformation, agentic AI, and organizational change management.
To explore Inteq's training courses or consulting services, visit inteqgroup.com.
