Every SAP consultant gets assessed on what they know and what they build. Certifications confirm module knowledge, and project history confirms delivery capability. What neither measures is the quality of the questions asked before the configuration began, during deployment and afterwards.

Knowing how to ask the right types of question in SAP consulting is a discipline that can be developed and those that are able to tend to produce consistently better outcomes, hold client relationships longer, and move into advisory roles faster.

SAP’s certification programs name client engagement questioning as a distinct competency, separate from technical and functional knowledge, but as much of SAP consulting requires deliberate and structured questions, the role of questioning as a skill is undervalued.

This means effective questioning is a skill that can be developed as an SAP consultant, in order to improve planning and delivery, and that it can also be leveraged as a means of differentiation in the SAP talent market. 

The Cost of Poor Questioning

The consequences of inadequate questioning become apparent as scope creep, rework cycles, UAT defect volumes that exceed projections, and post-go-live adoption rates that fall short.

Each of those outcomes has a root cause, and a significant proportion of those root causes trace back to requirements accepted at face value, undisclosed integration dependencies, or change readiness gaps that discovery processes did not reveal.

Requirements gathered without sufficiently probing questions may consist primarily of inherited assumptions rather than genuine business needs.

A client’s subject matter experts describe the process they know: which is often the process that accumulated over years of workarounds, legacy system constraints, and undocumented exceptions.

The consultant who accepts that description without questioning the assumptions underneath it will design a solution for a process that the business would benefit from reconsidering.

The consultant who asks why the process works that way, and what would break if it changed, is doing something qualitatively different, and producing a design that is more likely to adequately serve business operations.

Change management failures follow a similar pattern. Resistance to a new system is a surprise only to the project team that never asked the questions that would have made it clear.

Smart consultants use well-designed questions to understand what business users require and how best to ensure adoption of a new SAP system.

The Mechanics of a Well-Designed Question

An effective question is a carefully designed speech act. It predetermines the type of information it can return, and the choice of the right type of question for the right scenario should precede the formulation of any specific question.

Open questions generate context and bring to light what the respondent considers important.

Closed questions confirm specific facts.

Probing questions test whether an answer is complete.

Clarifying questions establish whether the consultant’s understanding matches the respondent’s intent.

Hypothetical questions reveal how a stakeholder thinks about future states without committing them to a position.

Each type belongs in specific contexts, and deploying them without that awareness produces answers that are technically responsive but practically incomplete.

Questions also differ in the type of dialogue they propose. A question that retrieves information instigates a different conversation from one that invites argument, or one that elicits an explanation of causes.

Knowing which type of dialogue a specific situation requires is a prerequisite for asking the right question.

Every question also contains a presupposition: an embedded assumption that must be true for the question to make sense.

In requirements gathering, unexamined presuppositions create false consensus. The client answers the question as posed (without correcting the assumption underneath it) and the consultant records a requirement that was never actually validated. Stripping presuppositions out of questions before asking them is one of the most productive questioning habits an SAP consultant can develop.

What is applied here is sometimes referred to as Socratic questioning. It targets underlying assumptions and fundamental design logic, and it can be used to reveal assumptions, in the formulation of questions, but also in the operating assumptions of users, and other stakeholders in SAP environments. Frequently, this is used in a logical chain: establishing shared observations, then proceeding to clarify further.

In a fit-to-standard workshop, the most productive question is often the one that asks why the process was designed the way it was, and whether the reason for that design still holds.

One further mechanic deserves mention because it is consistently underused: the pause. Maintaining a pause after someone initially answers allows the respondent to think further, and this reliably produces more complete information as more relevant information occurs to them. One should never interrogate, but experienced questioners use this frequently to elicit more nuanced answers. 

What You Need to Know to Ask the Right Question

The mechanics of questioning described above are tools. Their effectiveness depends entirely on what knowledge the consultant brings to the conversation. Domain knowledge and questioning skill are interdependent. Neither substitutes for the other, and both need deliberate development.

A well-constructed question asked without sufficient SAP landscape knowledge will produce a well-constructed answer the consultant cannot evaluate. Understanding how deployment models, integration architectures, and customization positions determine what a client’s answers mean is the minimum context required to ask credible discovery questions, and to recognise when an answer warrants further investigation.

Industry knowledge operates the same way. Process-level questions only produce actionable answers when the consultant understands the business context well enough to assess whether a response is standard for the sector or exceptional. A consultant without manufacturing exposure cannot reliably judge whether a client’s production planning assumptions are conventional or worth investigating further.

Before any client conversation, the most productive question a consultant can ask is what they themselves do not know yet. They need to know enough about the subject under discussion to ask the right questions, and if they cannot prepare sufficiently insightful questions, then someone else with the right knowledge needs to be given the task.

Questioning Across the Full Program

Questioning is not purely an activity for discovery, and knowing which type of question belongs at which stage is itself a professional skill.

Pre-engagement conversations carry the highest stakes of the entire program because the expectations set here determine what the delivery team will later be measured against. 

Questions at this stage are simultaneously diagnostic and commercial. They establish strategic intent, political landscape, realistic budget commitment, and the scope of what the client is actually prepared to undertake. This is the stage where the consultant who arrives prepared, having researched the client’s industry, existing landscape, and likely pressure points, asks questions that define the engagement.

The Discover and Prepare phases seek evidence. Governance questions, on who holds final decision authority, what scope is explicitly excluded, and where budget assumptions rest on optimistic projections rather than documented commitments, must be answered with evidence before any project charter is signed.

Organizational readiness for change is also relevant here, and consultants must ask questions that reveal whether the people side of the program has received the same planning attention as the technical side.

Fit-to-standard workshops in the Explore phase introduce the most intellectually demanding questioning task in a functional consultant’s repertoire. The central discipline is distinguishing a truly functional gap from a perceived one, which requires demonstrating SAP standard functionality first, and then asking questions that test whether the client’s process really cannot be served by it (meaning some extension or customization may be required). This phase also reveals the use of shadow systems: the spreadsheets, and informal workarounds operating alongside the documented process that represent undisclosed requirements not already captured in any scope document.

In the Realize phase, questions are more diagnostic. Integration testing requires questions that establish whether all interface scenarios (including error handling, partial processing, and edge-case data conditions) have been covered. UAT introduces a specific questioning challenge: distinguishing a genuine system defect from a change management issue, where a user reports something as wrong because the new process differs from the familiar one rather than because the system is misconfigured. Getting that diagnosis right determines whether the correct response is a configuration fix or a training intervention.

Go-live readiness questions carry the most direct professional responsibility in the program. They must be based on documented evidence, and the consultant’s obligation is to raise concerns clearly when that evidence is absent or insufficient. Through hypercare, the defining diagnostic question is whether the organization is learning the system or building workarounds around it, and that answer needs direct conversation with users.

During the Run phase, the relevant questions are no longer about whether the system functions correctly but whether the investment is producing the value the business case projected, and where the gap exists if it is not. These conversations require an evaluative and strategic mindset and they are often the conversations that define whether a client relationship extends beyond the current program.

Questioning, across all of these contexts, is the mechanism that keeps a consultant calibrated to the client’s reality at every stage. The nature of the questioning changes continuously, but it never stops being the primary instrument through which a consultant understands what is true.

Why Consistent Questioning Boosts Careers

The consultants who command the strongest rates, sustain the longest client relationships, and move into architecture and advisory roles are distinguished by the quality of the questions they ask when decisions are getting made.

The trusted advisor relationship (where a client returns to a specific consultant for strategic direction), is built through insightful questioning over time to yield context-specific advice. 

Clients who feel genuinely heard and accurately understood return for more advice. The source of that trust (along with positive outcomes from previous engagements) is the experience of being asked the right questions: of having a consultant demonstrate through their questions that they understand the business, the stakes, and what the client has not yet thought to say.

Career progression in SAP consulting follows the same logic. Junior consultants are evaluated on technical execution. Senior consultants are evaluated on judgement. That judgement is expressed mainly through the questions asked in design reviews, steering committees, change conversations, and pre-sales engagements. The move from module specialist to cross-functional advisor, and the T-shaped or π-shaped profile that architecture and strategic roles require, depends on the ability to ask credible questions outside a primary domain. A questioning framework that has been deliberately developed transfers across industries, modules, and client contexts.

The practice that produces this development is straightforward but consistently neglected: after each workshop, discovery session, or stakeholder interview, reviewing what the questions produced, which ones failed to surface what was needed, and what could have been asked differently to provide more detailed or more actionable information.

The Questions Are Changing

As intelligence embeds across S/4HANA and SAP BTP: through Joule, embedded AI in core processes, and AI-assisted analytics, the question agenda for SAP consultants is expanding into new territory.

The questions that now matter in client conversations include which business problems are genuinely suited to AI-assisted resolution, whether the data quality and governance structures exist to support the ambitions being discussed, and whether users will trust AI-generated outputs enough to act on them.

These are not technical questions in the conventional sense. They are discovery questions, change readiness questions, or strategic alignment questions, and they require exactly the kind of disciplined, assumption-testing, context-aware questioning this article has described. The consultants developing that capability now are preparing for the next wave of SAP transformation with the skill that will determine how well it lands.

Consultants who are able to develop their ability to evaluate systems and organizations and recommend optimal changes to improve the business performance of their clients’ processes are obliged to rely on their powers of questioning. 

If you want to excel in an SAP consulting career, it is extremely useful to be aware of the way in which you ask questions, and how you can do that more effectively.

The question now is: how much do you want to improve?

If you are an SAP professional looking for a new role in the SAP ecosystem our team of dedicated recruitment consultants can match you with your ideal employer and negotiate a competitive compensation package for your extremely valuable skills, so join our exclusive community at IgniteSAP.