This is the fourth in our series exploring key insights on implementation methodologies for Microsoft Dynamics 365.
Leveraging Microsoft’s Framework for Project Success
Microsoft Success by Design (SBD) is a critical framework that complements whichever implementation methodology you choose. Success by Design gives more details on how we should specifically manage certain activities related to Dynamics projects.
The framework isn’t a replacement for Agile, Waterfall, or hybrid approaches—it’s designed to work alongside them, providing Microsoft-specific best practices and guardrails based on thousands of implementation experiences.
The Evolution from Sure Step to Success by Design
Microsoft introduced the Sure Step methodology about 15-16 years ago, which served the Dynamics community well for many years. However, Microsoft more recently kind of stepped back, left Sure Step out there, but not proactively improving the methodology.
While Microsoft mentioned “Sure Step 365” as a potential evolution, that it hasn’t been widely published. Instead, Microsoft pivoted to Success by Design—a more flexible framework that provides guidance without prescribing a rigid methodology.
Core Phases of Success by Design
Success by Design organizes the implementation journey into four key phases:
1. Initiate
This phase focuses on establishing the foundation for project success:
- Executive alignment on vision and objectives
- Governance structure and steering committee formation
- High-level scoping and business case validation
- Team mobilization and role definition
If we skip steps here, we tend to fall short in our downstream activities.
2. Implement
The bulk of the project work occurs during this phase:
- Detailed solution design and architecture
- System configuration based on requirements
- Custom development where necessary
- Iterative build and unit testing
Success by Design accommodates both sequential and iterative activities during implementation, supporting his recommended hybrid approach.
3. Prepare
This critical phase ensures readiness for production:
- End-to-end integration testing
- User acceptance testing (UAT)
- Performance and security validation
- Training and change management rollout
- Go-live planning and rehearsals
Many projects rush through this phase, leading to problematic launches. Success by Design provides specific checkpoints to prevent this.
4. Operate
Post go-live activities focus on sustainable operations:
- Transition to production support
- Performance monitoring and optimization
- User adoption tracking
- Continuous improvement processes
Key Assurance Activities
There are several critical assurance activities that Success by Design emphasizes throughout the project lifecycle:
Blueprint and Risk Reviews
Microsoft gives guidance and Microsoft provides additional support through their Fast Track team. These reviews help identify potential issues early on when they’re less expensive to address.
Security and Performance Testing
With increasing cyber threats and user expectations for system performance, Success by Design mandates specific security assessments and performance benchmarks at key milestones.
Go-Live Assessments
Microsoft has developed comprehensive go-live readiness checklists based on 3,000 to 4,000 projects that Microsoft got involved with directly or indirectly over the last 5 to 10 years.
Usage Telemetry
Post-implementation monitoring helps ensure the solution delivers expected business value and identifies areas for optimization.
Accessing Success by Design Resources
Success by Design documentation spans over 700 pages. Microsoft maintains also a GitHub repository with free templates, workshops, and guidelines that teams can use immediately. These resources are available without even logging in.
Making Success by Design Work for Your Project
Success by Design should complement, not replace, your chosen methodology. Here are several practical tips:
1. Tailor to Your Roles
Rather than overwhelming team members with the entire 700-page documentation, focus on role-specific guidance. Project managers, solution architects, and functional consultants each have distinct Success by Design elements to master.
2. Combine with Partner Methodologies
Partners are already typically well-versed with Success by Design and often combine it with their own methodologies. The key is ensuring these approaches complement rather than conflict with each other.
3. Leverage Microsoft’s Direct Support
“Microsoft gives us a lot, but Microsoft also does not say, ‘Hey, you have to do it this way,'”. Instead, Success by Design provides flexible guidance while Microsoft’s Fast Track team offers direct support for qualifying projects.
4. Don’t Just Check the Boxes
Success by Design shouldn’t be treated as a compliance exercise. Each checkpoint and review should add real value to your project.
Success by Design for Different Project Types
Success by Design scales appropriately to project complexity:
- Rapid Projects: May use simplified Success by Design elements, focusing on core best practices
- Standard Projects: Implement most Success by Design checkpoints with moderate documentation
- Enterprise Projects: Require full Success by Design implementation with comprehensive reviews
The Bottom Line on Success by Design
Success by Design represents Microsoft’s commitment to helping customers succeed with Dynamics 365 implementations. It’s not about rigid adherence to a methodology, but about applying proven practices that reduce risk and improve outcomes.
The framework provides structure without stifling flexibility—exactly what modern Dynamics 365 projects need. By combining Success by Design with appropriate implementation methodologies, organizations can dramatically improve their chances of joining the successful 20-35% of ERP implementations rather than the failing majority.
In Part 5 of our series, we’ll explore best practices for creating effective project governance and team structures that drive implementation success.
