ARTICLE · DYNAMICS 365 CRM · IMPLEMENTATION

Requirements analysis in a CRM project: listening well, asking the right questions

In short: the success of a CRM implementation rarely depends on technology, and much more on whether we understood what the business really needs. The requested feature is not the need: behind an “exportable list” there is often a missing report, and behind “it should work like today” a legitimate worry about change. Good requirements analysis starts from the standard process (fit-to-standard), listens carefully, asks targeted questions and summarises decisions briefly, starting with the answer.

Why does a CRM project depend on requirements analysis?

A CRM touches daily work: sales, customer service and management all work in it. If the analysis misunderstands a process, the error is inherited by development, testing and rollout, and the later it surfaces, the more expensive it is to fix. Typical misunderstandings:

  • A solution instead of a need: “we need a button that exports to Excel” — the real need is a management report that works better as a Dynamics 365 report or dashboard.
  • A copy of the old system: people ask for familiar steps, not the outcome, and the old workarounds move into the new system.
  • The missing exception: everyone can describe 90% of the process; the remaining 10% (cancelled orders, partner channels, foreign-currency quotes) only surfaces with targeted questions.
  • The wrong person talks: the manager describes how it should work, while the people doing the work do it differently.

Fit-to-standard: starting from the standard process

Microsoft’s Dynamics 365 implementation guidance (Success by Design) recommends that analysis does not start from a blank page but from the system’s standard processes: in workshops we first show how Dynamics 365 handles the business process, and only then look for the differences (fit-gap analysis). For each requirement we record whether the standard covers it (fit) or development is needed (gap), plus its priority and complexity.

This has two benefits: less custom development, which would otherwise need testing at every twice-yearly update, and users see the real system in the workshop rather than an imagined screen.

Active listening: understand first, solve later

Carl Rogers and Richard Farson described active listening in 1957: the listener attends to the total meaning, both the content and the feeling behind it, and reflects it back. In a requirements workshop this comes down to a few simple habits:

Reflectingrepeat what you heard in your own words: “If I understand correctly, a quote currently has to be entered twice, once in the CRM and once in invoicing.”
Summarisingat the end of each topic, in two or three sentences, which the participants confirm or correct.
Silencewait for the answer after a question; the important addition often comes in the second sentence.
Solutions laterno screen design in the workshop; as long as the problem is unclear, a proposed solution only narrows the conversation.

The four-sides model: what does the user say, and what do they ask for?

According to Friedemann Schulz von Thun’s communication square (or “four ears” model), every message has four sides: factual content, self-revelation, relationship and appeal. This helps in requirements work because the requirement is often not in the factual content. Our own example: a sales manager says, “In the old system this was one click.”

SideWhat we hear in itWhat we ask back
Factual contentthe old system exported the list in one stepWhich list is exported, how often, and what happens to it afterwards?
Self-revelationworried that the team will become slowerWhich task is the one where speed matters most?
Relationshipfeels the project did not ask the teamWhich sales reps should join the next workshop?
Appealit must not be worse than todayWhat is the acceptance criterion: how many steps, how much time?

If we only hear the factual content, we build an export button. If we hear all four, we find the real need, involve the users and get a measurable acceptance criterion.

Which questions work for analysing a CRM process?

Open questions (“How…?”, “What happens if…?”) explore; closed questions (“Always…?”, “Who approves?”) clarify. Instead of “why”, “what is it used for” works better, because it does not ask for justification. A proven set of questions for a CRM process:

  • Who starts the process, and what triggers it (a request for quote, an incoming e-mail, a web form)?
  • Which data does it work with, and where does that data come from (ERP, Excel, another system)?
  • Who approves, above which value or under which condition?
  • What are the exceptions: cancellation, changes, customers coming through partners, other currencies or languages?
  • What is the result, and who uses it next (invoicing, reporting, customer service)?
  • How do we know it works: which metric improves, and over what time?

For small and mid-sized companies the same works in a shorter form; the implementation steps are covered in CRM for SMEs.

The Minto pyramid: start the summary with the answer

Barbara Minto’s Pyramid Principle says a written document starts with the main message, followed by grouped supporting arguments, with the details below them. The introduction is often framed as situation – complication – question (SCQ). In a requirements summary for management it looks like this:

  • Recommendation: we implement the sales process with the standard opportunity and quote management of Dynamics 365 Sales; three extensions are needed.
  • Why: the standard covers 80% of the analysed process; the three gaps are foreign-currency pricing, the partner channel and the invoicing integration.
  • Decision needed: should the partner channel go into phase one or phase two?
  • Details: the requirements list, the fit-gap table and the process diagrams in the appendix.
The figures above are illustrative examples of the structure, not data from a specific project.

Every requirement becomes a test case

A requirement is good if it can be verified. So every requirement gets an acceptance criterion (“a quote can be created from the opportunity in three clicks, with line items and price list carried over”), and that becomes the test case. Analysis, development and testing then refer to the same sentence, and the regression suite keeps protecting what matters to the business. From the testing side: test automation and testing.

How do we work?

We start the analysis from the standard Dynamics 365 processes, in workshops with process owners and everyday users, in English, German or Hungarian. The result is a short, decision-ready summary, the fit-gap list and the acceptance criteria. For clients in the DACH region we work as an EU-based nearshore partner.

Details: Microsoft Dynamics 365 consulting.

Frequently asked questions

How long does CRM requirements analysis take?

It depends on the scope: how many business processes, user groups and integrations there are. For a well-defined sales process a few workshops are enough; with several departments and integrations a planned analysis phase is needed. We give a concrete plan after the first call.

What is a fit-gap analysis?

Recording for each requirement whether standard Dynamics 365 functionality covers it (fit) or development, an add-on or a process change is needed (gap). Microsoft’s implementation guidance recommends it after demonstrating the standard process (fit-to-standard).

Who should attend the requirements workshop?

The process owner who can make decisions, and at least one or two users who do the daily work. For integrations, the owner of the connected system too. Management joins for the summary and the decisions.

What is the difference between a requirement and a solution?

A requirement describes what must be achieved (“management sees the value of open quotes every week”), a solution how (“a dashboard in Dynamics 365”). If the analysis records a solution instead of a requirement, the chance of a cheaper standard solution is lost.

Let’s talk about your project.

Tell us what you are planning and we will get back to you within a few days.

Get in touch

Cookie settings

Choose what you consent to. We remember your choice for 6 months; change it any time via “Cookie settings” in the footer.

Privacy notice