.png?height=200&name=EB2%20Thumbnail%20(1).png)
Agentic AI is changing the way organizations think about business process transformation. The focus is no longer only on the technical side of AI agents. The technology has become strong and stable enough that the real question is now how organizations use AI agents to create business value, redesign work, and transform the way processes operate.
This is the second briefing in Inteq's agentic AI series. The focus here is identifying high-impact AI agent opportunities inside your business processes: agents that optimize how work gets done across the enterprise. Personal agents are a separate topic.
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?
This video focuses on a foundational challenge that every business analyst and business systems analyst faces: how to move beyond superficial engagement with subject matter experts and get to the deeper, more actionable requirements that actually drive improvement.
The session introduces five essential underlying questions - not a literal script of five things to ask, but a disciplined thought process that shapes how a professional analyst engages stakeholders. Together, these questions provide the foundation for deeply effective requirements elicitation across both incremental and transformational change initiatives.
Getting requirements right is hard. Business requirements, business system requirements - surfacing them accurately and completely is one of the most difficult things a business analyst does. And one of the most common failure modes is analysis that stays too shallow.
When an analyst asks superficial questions, they get superficial answers. They walk away with a bullet list of wishes and gripes - things people said they wanted — rather than a genuine understanding of the underlying rules, workflows, value drivers, and constraints that shape what the business actually needs. The result is requirements that are technically documented but practically incomplete, and deliverables that miss the mark.
The goal is deep engagement: going beyond what stakeholders volunteer to surface the requirements that will truly move the organization forward.
Before getting to the questions themselves, it helps to establish the frame of reference they operate within.
These two words are often used interchangeably, but they are distinct concepts and the distinction matters.
Effectiveness is about creating customer value. It encompasses the quality of outputs, timeliness, service levels, and the overall customer experience. Effectiveness asks: what are the things we can change in our business processes and the systems that support them to create better outcomes for customers?
Efficiency is about delivering effectiveness in the most economical way possible. Once service levels are established - the standards for quality, timeliness, and customer experience - efficiency asks: how can we reduce the cost of meeting those standards without lowering them? Efficiency and cost reduction are related but not the same. Cost reduction means accepting a lower level of effectiveness to reduce cost. Efficiency means maintaining effectiveness at a lower cost. Both are valid objectives, but they are different levers.
A business requirement is anything the organization needs to do as part of its operations. A business system requirement is a business requirement that will be supported through information technology or application software.
A useful illustration: consider two restaurants - a large national chain and a small independent Italian restaurant with ten tables. Both have the same underlying business requirements: take reservations, seat customers, assign servers, take orders, prepare and serve food, generate a check, process payment. Those are universal business requirements for any restaurant operation.
But the solution to the same requirement can look very different. The small independent might handle reservations with a hand-written log - a low-tech, no-tech solution that is entirely appropriate for their scale and economics. The national chain might implement an enterprise reservation management platform integrated with online booking services. Same business requirement, very different business system requirements. Understanding this distinction is foundational to scoping analysis work correctly.
Business analysis work falls into two broad categories, and it is important to approach them differently.
Incremental change is business as usual - improving existing processes, adding functionality to existing systems, updating policies and procedures. These are the things that keep the wheels on. They matter enormously, and most organizations are doing incremental improvement continuously.
Transformational change is driven by strategic initiatives - fundamentally new ways of engaging customers, new product lines, new organizational models, new business capabilities. These are the changes that move the needle. They require more sophisticated analysis and a longer strategic horizon, but they are what allows an organization to grow and prosper in the long run.
Both types of change are important. The five questions address both - but they do so from different angles.
The level of engagement the analyst brings to these questions determines whether the organization gets genuine requirements or just a list of requests. Think of it as the difference between fast food and fine dining.
At a fast-food restaurant, the person taking the order is doing exactly that - taking an order. The interaction is transactional and superficial. What do you want? What size? Can I supersize it? Nothing wrong with that in the right context. But it is a set of hands getting input into a system, not a professional doing analysis.
At a fine dining restaurant, the server brings knowledge, judgment, and genuine engagement to the table. They understand the menu deeply. They ask thoughtful questions, offer suggestions, make connections between what the guest is looking for and what the kitchen can deliver. That's a professional - someone who adds real value through the quality of the engagement itself.
The five questions that follow are really about elevating the conversation with subject matter experts from fast food to fine dining.
These are not five literal questions to read off a list. They are five underlying lines of inquiry - five dimensions of engagement - that a professional analyst works through to deeply understand the current state, identify what should change, and surface what the organization needs to move forward.
The first question establishes the baseline. Before anything can be improved, eliminated, or reimagined, the analyst has to understand what actually happens today - the current state.
There is sometimes resistance to this in practice. Business analysts will occasionally hear, or even say themselves, "We don't need to spend time on current state - we know what we're doing. Let's focus on the future." That's a mistake. In almost every engagement, the honest answer is that the organization doesn't fully know what it's doing. People have a general understanding, but the detailed reality of how work actually flows - the steps, the decision points, the hand-offs, the exceptions - is rarely as well understood as assumed. Deep current state analysis is how that understanding gets established.
The current state baseline also serves as the launching point for everything that follows. Without it, the remaining four questions have no foundation.
With the current state established, the second question turns immediately to elimination: of everything we are currently doing, what should we stop doing?
This is one of the most practically valuable questions in the entire framework. In virtually every organization, there are work activities, procedures, and processes that exist simply because they have always existed - policies that were created ten or fifteen years ago and are no longer relevant, procedures that were put in place for reasons nobody can quite remember, steps that don't add any value in the current environment. Subject matter experts often know exactly what these are and can list them readily when asked directly.
The analyst's role here is not just to capture the list. It is to understand each item, build the case for eliminating it, and help move that case up the line. Most subject matter experts cannot unilaterally decide to stop doing something, even something obviously unnecessary. It typically requires a first-level supervisor or manager to authorize the change - and often that manager wasn't aware the work was being done at all. Getting to that conversation, and enabling that decision, is part of the analyst's job. Stopping the madness before it gets automated is far less expensive than automating unnecessary work and then having to undo it.
This question is primarily about incremental improvement: leaning out the current process before building on it.
After the baseline is established in Question 1 and the unnecessary work is identified for elimination in Question 2, Question 3 focuses on what remains: the activities and processes that need to continue, but that should be done better.
This is the core of incremental improvement work. Given everything the organization legitimately needs to do, what can be done more effectively — at a higher level of quality, timeliness, or customer experience? What can be done more efficiently - at lower cost while maintaining those effectiveness levels? And what business process changes, policy changes, or system functionality changes would enable those improvements?
The lens here is still the existing process - not a new operating model, but an improved version of the current one.
Question 4 marks a turn toward forward-facing analysis. This question asks subject matter experts to look beyond the current state and surface the things they know the organization needs to do - things that would clearly add value - but that they are currently prevented from doing.
The constraints are usually one of a few types: missing functionality in the supporting systems, business policies or procedures that haven't been updated, resource or capacity limitations, or organizational barriers. Subject matter experts almost always have a list of these. They know what they can't do. They know what's holding them back.
The analyst's job is to elicit that list, understand the value each item would create, and frame the conversation around what would need to change — in process, policy, or technology - to make it possible.
This question can surface both incremental and transformational opportunities. Some items on the list are relatively straightforward improvements to existing capabilities. Others point toward fundamentally new ways of operating or engaging customers - things that would move the needle for the organization rather than just optimize the current model.
The fifth question reaches into what can be called the "unknown unknowns" - the things the organization needs to be doing that it hasn't yet identified, but that would create significant value if it knew to do them.
By definition, subject matter experts cannot generate this list on their own. They can only surface what they know. Answering Question 5 requires the analyst to look outside the organization: industry benchmarking, best practice research, competitive analysis, emerging technology and process capabilities, and adjacent industries that have solved similar problems in new ways.
This is typically where transformational opportunities live. It might be a capability that competitors are beginning to build and the organization needs to get ahead of. It might be a blue ocean opportunity - something nobody in the industry is doing yet, but that a careful look at customer needs and market dynamics suggests is coming. It might be an emerging technology application that changes what's operationally possible.
Question 5 demands the most from the analyst in terms of domain knowledge, external research, and strategic thinking. But it is also where some of the highest-value insights come from.
The five questions build on each other in a logical sequence:
Questions 1 through 3 are primarily oriented toward the current state and incremental improvement. Questions 4 and 5 are forward-facing and increasingly transformational.
Used together, these five lines of inquiry give the analyst the framework to deeply engage subject matter experts across the full range of business analysis work - from routine process improvement to strategic transformation.
The real message underneath the five questions is about the quality of the conversation with subject matter experts.
A superficial conversation produces wishes and gripes. A deep one produces actionable requirements - requirements that are understood well enough to be implemented, validated against what the business actually needs, and traceable back to the effectiveness and efficiency objectives that motivated the work in the first place.
The questions to ask when assessing your own organization's business analysis practice:
The consequences of getting this wrong show up in project deliverables that miss the business need, in stakeholder frustration, and in the cumulative cost of rework and misaligned systems. The benefits of getting it right - requirements that are accurate, complete, and actionable - compound over time into genuine competitive advantage.
Inteq Group offers a full suite of training programs and management consulting services in business systems analysis, business process management, business process reengineering, digital transformation, agentic AI, and organizational change management.
To explore Inteq's training course catalog or consulting services, visit inteqgroup.com.
.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.
Ten best practices for business process modeling and mapping that apply across industries, process types, and organizational contexts - drawn from hundreds of current state and future state maps built across virtually every vertical market.
The focus of this video is on one of the most pressing talent challenges organizations face today: how to identify, interview, and onboard truly professional business analysts - and how to tell them apart from candidates who simply look the part.
%5B1%5D.webp?height=200&name=What%20is%20RPA%20Part%201%20(1)%5B1%5D.webp)
