Success by Design for Business Central: A Right-Sized Guide
Success by Design Was Shaped by Large, Complex Projects. Here's How to Right-Size It for Business Central.
Search for "Business Central implementation Success by Design" and you'll find plenty of explanations of Microsoft's five-phase methodology: Discover, Initiate, Implement, Prepare, and Operate.
Those explanations are useful, but they often leave out the question that matters most to a Business Central buyer:
How much of the framework does your project actually need?
A 30-user, single-entity Business Central implementation with standard functionality does not have the same risk profile as a multi-country deployment involving complex integrations, extensive extensions, multiple legal entities, and hundreds of users.
That does not mean a smaller Business Central project should ignore Success by Design. It means the framework should be applied proportionately.
The goal is not to perform fewer quality checks for the sake of speed. The goal is to put the greatest governance effort where the project has the greatest risk.
What Is Success by Design?
Success by Design is Microsoft's implementation guidance for Dynamics 365 projects. It was developed from Microsoft's experience with large numbers of customer implementations and provides structured guidance for identifying architectural, functional, technical, data, and operational risks before they become expensive problems.
The framework is organized around five phases:
- Discover — establish the business context, objectives, scope, solution requirements, and major risks.
- Initiate — establish the implementation approach, solution direction, governance, and project foundations.
- Implement — configure, extend, integrate, migrate, and validate the solution.
- Prepare — get the organization, users, data, processes, and technology ready for deployment.
- Operate — stabilize the solution and establish the processes needed to run and continuously improve it.
The important point is that Success by Design is guidance, not a substitute for your partner's delivery methodology. A Business Central partner can use agile, waterfall, or a hybrid delivery approach while incorporating the principles and reviews that make sense for the project.
Microsoft also makes clear that following Success by Design does not guarantee project success. Its purpose is to help implementation teams identify and address risks systematically rather than discovering them late in the project.
That distinction matters when applying the framework to Business Central.
Why Applying Enterprise-Level Governance to Every BC Project Can Add Unnecessary Cost
There are two mistakes a Business Central customer can make.
The first is under-governance: treating a smaller project as simple enough to skip architecture, data, integration, security, testing, and cutover discipline.
The second is over-governance: applying every review, document, meeting, and control at the same intensity regardless of project size or complexity.
Both create problems.
If you skip important design validation, a seemingly small decision about data structure, integrations, dimensions, extensions, or security can become expensive to correct later.
But if a 30-user implementation with standard Business Central functionality is subjected to the same governance burden as a large, multi-country transformation, the additional documentation and review effort may add project cost and calendar time without creating equivalent risk reduction.
The better approach is risk-based governance.
Ask:
- How many legal entities are involved?
- How many countries and currencies are involved?
- How complex is the data migration?
- How many integrations are required?
- How much custom development or extension work is planned?
- Are there complex warehouse or manufacturing processes?
- Are multiple external systems business-critical?
- Are Copilot capabilities or AI agents part of the solution?
- How much change will users experience?
- What happens to the business if a particular integration or process fails?
The answers should determine the depth of your implementation governance.
A Right-Sized Approach to Each Success by Design Phase
1. Discover: Keep the Business Context, Scale the Documentation
Discover should not be treated as paperwork.
This is where the implementation team establishes what the business is trying to achieve, which processes matter most, what systems are being replaced, and where the major risks are.
For a smaller Business Central implementation, the documentation can be concise, but the questions should remain rigorous.
At minimum, establish:
- Business objectives and measurable outcomes
- Current systems and processes
- Business Central scope
- Key integrations
- Data migration requirements
- Reporting requirements
- Security and approval requirements
- Country, tax, and localization requirements
- Major customisation or extension requirements
- Project constraints and dependencies
The objective is simple: do not start configuring Business Central until everyone agrees on what problem the implementation is supposed to solve.
2. Initiate: Establish the Architecture Before Building
Initiate is where assumptions become an implementation direction.
For a straightforward single-entity Business Central project, this does not necessarily require an enormous architecture document.
It does require clarity around:
- Business Central configuration
- Extensions and customisations
- Integration architecture
- Data migration approach
- Reporting and analytics
- Security and permissions
- Environments
- Testing strategy
- Deployment approach
- Ownership and decision-making
This is also the point at which AI capabilities should enter the conversation if they are part of the project.
If the customer plans to use Copilot capabilities or agent-based automation, define the intended use cases, data access, human oversight, permissions, and boundaries before those capabilities become embedded in business processes.
3. Implement: Review the Areas That Actually Carry Risk
This is where right-sizing becomes particularly valuable.
Not every Business Central project needs the same level of specialist review across every workstream.
A standard financial implementation with limited integrations may require relatively straightforward validation.
A project involving:
- A custom warehouse integration
- Complex manufacturing
- Multiple legal entities
- Significant extensions
- External e-commerce platforms
- Third-party logistics systems
- Complex consolidation
- High-volume data migration
deserves deeper technical and functional review.
The principle is:
Do not remove governance. Target it.
If the solution blueprint identifies a high-risk integration, review that integration deeply.
If data migration is the greatest risk, put more review effort into data mapping, cleansing, reconciliation, mock migrations, and cutover.
If custom extensions are business-critical, validate their architecture, dependencies, upgradeability, and testing approach.
This is more valuable than applying identical governance to every part of the project.
A Practical Business Central Success by Design Decision Matrix
| Business Central project profile | Recommended governance approach |
| 20–50 users, single entity, mostly standard functionality | Core design and readiness reviews with lightweight project governance |
| Multiple legal entities | Deeper solution architecture and targeted functional reviews |
| Multi-country implementation | Stronger localization, data, security, testing, and deployment governance |
| Complex integrations | Focused technical and integration reviews |
| Significant extensions/custom development | Additional architecture, testing, and upgradeability validation |
| Complex manufacturing or warehousing | Targeted functional and operational reviews |
| High-risk data migration | Stronger data profiling, cleansing, mock migration, and reconciliation controls |
| Copilot or AI-agent-enabled processes | Explicit AI scope, permissions, human oversight, validation, and monitoring |
| Large or multi-region rollout | More comprehensive governance across affected workstreams |
Go-live preparation is where a theoretically successful implementation can still fail operationally.
The question is not simply:
"Is Business Central configured?"
It is:
"Can the business operate successfully from day one?"
For a smaller implementation, the readiness process may be shorter than for a multi-country rollout, but it should still cover the essentials:
- Data migration completed and reconciled
- Users and permissions validated
- Critical processes tested
- Integrations tested
- Reports validated
- Opening balances confirmed
- Training completed
- Support ownership established
- Cutover responsibilities assigned
- Business continuity and fallback procedures understood
The size of the checklist can change.
The quality of the decision should not.
5. Operate: The Phase Business Central Customers Should Take More Seriously
Many implementation discussions treat Operate as the final stabilization period after go-live.
For Business Central customers, that is too narrow.
Business Central operates within Microsoft's continuous update model. Microsoft delivers two major release waves each year, and customers need to account for changes to functionality, extensions, integrations, and customisations as the platform evolves.
That means the relationship with your implementation partner should not effectively end at go-live.
Your Operate model should answer:
- Who monitors upcoming Business Central updates?
- Who evaluates their impact?
- Who tests critical extensions and integrations?
- Who owns regression testing?
- Who handles issues discovered after an update?
- What is the escalation process?
- Which customisations need special attention?
- How are users informed about material changes?
- How are new Business Central capabilities evaluated?
This is especially important for organisations that rely on third-party extensions or integrations.
The implementation is not the end of the Business Central lifecycle.
It is the beginning of operating and continuously improving the platform.
The AI-First Layer: What Changes When Your BC Project Includes Copilot or Agents?
Business Central is increasingly becoming part of Microsoft's broader AI strategy, with Copilot capabilities and agent-based functionality changing how users interact with ERP processes.
That creates another dimension of implementation risk.
Traditional ERP governance asks:
What should the system do?
AI-enabled ERP projects also need to ask:
What should the AI be allowed to do?
For a Business Central project involving AI or agents, define the boundaries before deployment.
Consider:
Scope
What process is the AI capability intended to improve?
Permissions
What information can it access, and what actions can it take?
Human oversight
Which decisions require human approval?
Accuracy and validation
How will outputs be checked before they influence financial or operational decisions?
Security
Are the AI capability and connected systems operating within the organisation's security model?
Monitoring
Who reviews performance and exceptions after deployment?
Change management
Do users understand what the AI does, what it does not do, and when they should intervene?
These questions should be integrated into the normal implementation governance rather than treated as an isolated "AI project."
For example, if an agent is being introduced to automate part of an order-to-cash process, its permissions, exception handling, approval boundaries, testing approach, and monitoring should be considered alongside the Business Central process itself.
What Should You Never Right-Size Away?
Right-sizing does not mean cutting the controls that protect the project.
There are several areas where reducing effort to save time can create disproportionate risk.
Data validation
Bad data can undermine an otherwise successful Business Central implementation.
Solution architecture
Poor decisions about integrations, extensions, or customisations can become expensive technical debt.
Security
Permissions and segregation of duties should be validated before users begin processing live transactions.
Testing
Critical end-to-end business processes need to work before go-live.
Cutover
The business needs a controlled transition from the old system to Business Central.
User readiness
Users need to understand how their actual jobs change, not simply how to navigate screens.
Post-go-live support
The first weeks after launch should have clearly defined ownership and escalation paths.
The principle is simple:
Reduce unnecessary administration, not necessary control.
Does a Smaller Business Central Project Need Less Success by Design?
Yes — but "less" should mean less unnecessary process, not less discipline.
A 25-user company with standard finance, sales, purchasing, and inventory processes may not need the same governance structure as a 2,000-user international organisation.
But it still needs:
- A clear scope
- A sound solution design
- Validated data
- Appropriate security
- Tested integrations
- User acceptance
- A controlled cutover
- Post-go-live support
The framework should become lighter, not weaker.
Success by Design vs. Your Partner's Implementation Methodology
Success by Design does not have to compete with your implementation partner's methodology.
A mature Business Central partner should be able to combine Microsoft's guidance with its own delivery framework.
For example:
Success by Design provides the risk and quality framework.
The partner's methodology provides the execution model.
That might include agile sprints, workshops, configuration cycles, testing cycles, project governance, change management, and deployment planning.
The important question when evaluating a partner is therefore not:
"Do you use Success by Design?"
A better question is:
"Show me how you apply Success by Design to a project of our size and risk profile."
That answer can tell you much more about the partner's implementation maturity.
Frequently Asked Questions
Is Success by Design required for a Business Central implementation?
Success by Design is Microsoft's implementation guidance and should not be confused with a universal requirement that every Business Central customer follow every review and artifact at the same level. The specific governance and review requirements can depend on the implementation context and Microsoft's applicable guidance or program requirements.
Does Success by Design guarantee that a Business Central project will succeed?
No. Microsoft does not position Success by Design as a guarantee of project success. It is intended to help implementation teams identify risks, make informed decisions, and improve implementation quality.
Which parts of Success by Design matter most for a small Business Central project?
The answer depends on the project's risk profile. At minimum, a small implementation should have disciplined solution design, data validation, testing, security validation, go-live readiness, and post-go-live support. Additional specialist reviews should be added where the solution introduces significant complexity.
Should a Business Central implementation include a Solution Blueprint Review?
A solution blueprint is valuable because it establishes the proposed solution, key assumptions, integrations, risks, and design decisions before significant implementation effort is committed. The depth and formality of that work should be proportionate to the project.
How does Success by Design apply to Business Central projects using Copilot or AI agents?
AI-enabled projects introduce additional considerations around scope, permissions, human oversight, validation, security, responsible use, and ongoing monitoring. These should be incorporated into the overall solution and operational governance rather than treated as an unrelated initiative.
Does Success by Design replace a Business Central implementation methodology?
No. Microsoft's guidance can complement an implementation methodology. Your partner should be able to explain how its delivery process incorporates the relevant Success by Design principles and reviews.
The Real Value of Success by Design Is Not More Documentation
Success by Design should not be measured by the number of documents produced or meetings held.
Its value is measured by the risks identified before they become expensive.
For a smaller Business Central implementation, that may mean a leaner governance model.
For a complex international rollout, it may mean much deeper architecture, testing, integration, data, and operational controls.
Neither approach is inherently better.
The right approach is the one that matches the risk, complexity, and business impact of the project.
That is the principle Business Central buyers should look for when evaluating an implementation partner.
Talk to a Business Central Specialist
If you want a Success by Design approach scaled to your actual Business Central project rather than a one-size-fits-all implementation template, speak with the Dynamics Square team.
We can help assess your scope, integrations, data migration, customisation requirements, AI use cases, and operational needs before recommending the appropriate implementation approach.