The way I run an implementation
Discovery and design workshops with your stakeholders turn requirements into a functional design and a real backlog in Azure DevOps. Configuration happens in your sprint cadence, visible and reviewable. Key-user training and documentation close the loop, so the platform lives on without depending on me.
- Discovery and design workshops
- Functional design and a prioritized Azure DevOps backlog
- Configuration across Sales, Customer Service, D365 Field Service and Project Operations
- Key-user training and go-live support
Standard-first architecture
As a PL-600-certified solution architect I make the design decisions before they get expensive: what stays standard, what genuinely needs customisation, and what belongs in a different system entirely. Standard-first is not dogma. It is the difference between a platform you can upgrade and one you renovate every two years. Regulated and complex environments are familiar ground.
Implementation questions
Do you take on full implementations or specific phases?
Both. Lead consultant across the whole journey, or focused on a phase: design, fit/gap, a specific module, or getting a stalled project moving again.
What does standard-first mean in practice?
Configuration before customisation, and customisation only where the business case is real. Your platform stays maintainable, upgradeable and understandable for the next consultant, including the one after me.
Do you work in our Azure DevOps process?
Yes. Backlog, sprints and release management in your environment, so progress is visible to your team, not hidden in mine.