The Question I Ask Every New D365 Client (And Why Their Answer Determines Everything)
After years of D365 project management experience, I’ve learned that most projects fail for the same reason: everyone’s focused on the “how” before they’ve agreed on the “what.”
The technical details. The timeline. The budget. The vendor selection.
All important. All secondary.
Before any of that, I ask every new client the same question:
“What does success look like 90 days after go-live?”
Not at go-live. Not during implementation. 90 days after.
And the answer tells me everything I need to know about whether this project will succeed or become another statistic.
Why Most Consultants Don’t Ask This Question
Big consulting firms skip this question because it’s inconvenient. It forces clarity. It creates accountability. It might reveal that what the client actually needs is different from what generates the highest consulting fees.
They’d rather sell you a $500K implementation with all the bells and whistles than help you figure out what success truly means for your business.
But here’s what I’ve learned: the clearest answers lead to the most successful projects.
The Three Types of Answers I Hear
Over the years, I’ve noticed client answers fall into three categories. Each one tells me something different about the project ahead.
Type 1: “We’ll finally have accurate financial reporting in real-time”
This is a business outcome answer. Specific, measurable, tied to a real problem they’re solving.
When I hear this, I know:
- Leadership is aligned on the actual problem
- There’s a clear way to measure success
- We can work backward from this outcome to define scope
- The project has executive support because they understand the “why”
These projects usually succeed because everyone knows what they’re building toward.
Type 2: “We’ll have D365 fully implemented with all modules configured”
This is a technical completion answer. It describes the work, not the outcome.
When I hear this, I probe deeper: “Okay, but why? What changes for your business?”
Often, there’s confusion. Different stakeholders want different things. IT wants modern technology. Finance wants better reporting. Operations wants efficiency. No one’s connected the dots.
These projects struggle because “done” doesn’t equal “successful.” You can implement every module and still fail to solve the business problem.
Type 3: “I’m not sure—that’s what we’re hiring you to figure out”
This is the honest answer. And honestly? I respect it more than Type 2.
At least they know what they don’t know. We can fix that. We start with discovery:
- What problems are you trying to solve?
- What’s broken today?
- What happens if you do nothing?
- Who benefits from this change?
These projects can succeed if we take time upfront to define success before we start implementing.
What This Question Reveals About Your Project
The answer to “What does success look like 90 days after go-live?” exposes four critical things:
1. Whether leadership is aligned
If the CFO says “better financial reporting” and the COO says “streamlined operations” and the CIO says “cloud migration,” you don’t have one project. You have three competing initiatives pretending to be one.
This misalignment will kill your project. Not immediately—slowly, through scope creep, priority conflicts, and decision paralysis.
2. Whether you’re solving the right problem
I once inherited a “failing” D365 implementation. The project was technically on track, but the client was unhappy.
Why? Because the original scope was designed to solve the problem their previous consultant assumed they had, not the problem they actually had.
The real issue wasn’t system capabilities—it was change management. Their team was resisting the new workflows. But they’d spent $200K on technical customizations that missed the point entirely.
3. Whether your timeline is realistic
If your answer is “We’ll have completely transformed our business processes and everyone will be proficient in the new system,” and your timeline is 90 days to go-live plus 90 days after… we need to talk.
Real transformation takes time. Real user adoption takes time. Real business change takes time.
Unrealistic expectations create doomed projects.
4. Whether you’re set up to measure success
If you can’t articulate what success looks like, you can’t measure whether you achieved it.
Which means you can’t prove ROI. You can’t learn from the project. You can’t identify what worked and what didn’t. You can’t make a compelling case for future investments.
You just spent six figures on something you hope worked.
The Follow-Up Question That Matters Even More
Once I know what success looks like, I ask the follow-up:
“What has to be true for that to happen?”
This is where we get tactical. If success is “accurate real-time financial reporting,” then what has to be true?
- Data migration must be clean (not just complete)
- Chart of accounts must be properly structured
- Users must understand how to post transactions correctly
- Integrations must work reliably
- Month-end close processes must be documented
Now we’re building a real project plan. One that’s connected to business outcomes, not just technical tasks.
What I’ve Learned From Wrong Answers
I’ve seen projects with terrible answers to my question still succeed—but only after we stopped, reset expectations, and redefined success.
I’ve also seen projects with perfect answers fail because success was defined, but no one was held accountable for achieving it.
The question itself isn’t magic. But it forces a conversation that most projects skip. And that conversation is the difference between implementations that check boxes and implementations that transform businesses.
If You’re Planning a D365 Project
Before you sign a contract with any consultant or partner, ask yourself: “What does success look like 90 days after go-live?”
If you can answer clearly and specifically, you’re ahead of 70% of D365 projects.
If you can’t, that’s not a weakness—that’s your starting point. Spend time here. Get alignment. Define outcomes.
Because everything else in D365 project mangement: vendor selection, scope definition, timeline, budget—flows from this answer.
And if your D365 project manager or consultant doesn’t ask this question? That tells you something too.
Ready to Discuss Your D365 Project?
Whether you’re planning a new implementation, rescuing a stalled project, or just want a second opinion on your approach, let’s talk.
I offer free 30-minute discovery calls where we’ll explore:
- What success looks like for your specific situation
- Whether your current plan is set up for success
- How I might be able to help
No pressure. No sales pitch. Just an honest conversation.
I offer free 30-minute discovery sessions to talk through your situation—no sales pressure. Just clarity.
📅 Schedule: Schedule a call
📧 Email: [email protected]