Microsoft MVP | MCT | Solution Architect | AI-Ready ERP & CRM Copilot & Agentic Business Applications

At DMR, our Microsoft Dynamics 365 and Power Platform consultancy, we are constantly exploring ways to improve not only the solutions we deliver, but also how our teams think, collaborate, and learn.

Recently, we started a small internal initiative within our team. What began as a simple book club quickly evolved into something broader — a culture club where we discuss books, podcasts, articles, and ideas related to technology, teamwork, and personal development.

But the purpose was never only professional development.

We wanted to create a small space inside the company where colleagues could connect more naturally, get to know each other beyond project meetings, and occasionally step away from the constant rhythm of deadlines, sprint planning, and Go-Live discussions.

Sometimes the topic might be a technology book.
Sometimes it might be a novel, a podcast, or even a discussion about sociology, psychology, or personal interests.

The goal is simple: to create a moment where the team can pause, think differently, and talk about ideas that are not always directly related to the next project deliverable.

During one of these early sessions, we also found ourselves discussing something many people have noticed lately: why reading habits seem to be declining in the modern digital world. With endless short-form content, notifications, and fast information streams competing for our attention, deep reading has become increasingly rare — yet perhaps more valuable than ever.

For our first book, we chose a modern classic: Atomic Habits by James Clear.

At first glance, it might seem like an unusual choice for a consulting team working on Dynamics 365 ERP, CRM, and Power Platform solutions. The book is typically positioned as a personal development guide, focusing on habits such as exercising more, eating healthier, or becoming more productive.

But as we started discussing it together, something interesting happened.

Our conversations quickly moved beyond personal productivity. We began to see strong parallels between Clear’s principles and the world we operate in every day: enterprise software projects, solution architecture, and cross-functional consulting teams.

Because while we build systems using sophisticated platforms like Dynamics 365, Azure, and the Power Platform, our success ultimately depends on something much more human: the habits of the teams behind those systems.

Beyond Go-Live: The “System” Behind Successful Business Application Projects

One of James Clear’s core ideas is that we should focus on systems, not goals. This idea resonated strongly with our team discussions.

In the world of enterprise projects—whether it’s Dynamics 365 ERP implementations, CRM transformations, or Power Platform solutions—teams often become obsessed with a single milestone: the Go-Live date.

Anyone who has spent time in large ERP or CRM projects knows how quickly everything starts revolving around that single date.

That date becomes the focal point of the entire project. Sometimes it becomes the only thing anyone talks about for months.  Everything is measured against it. But when we focus only on that finish line, we sometimes overlook the daily habits and working systems that actually make a successful delivery possible.

A goal is a target; a system is the set of repeatable processes, behaviors, and operating practices that lead you there. As James Clear writes:

“Goals are about the results you want to achieve. Systems are about the processes that lead to those results.”

n consulting teams like ours at DMR, the “system” is not just the software we build. It is the way we work together every day.

It’s how we design solutions.
It’s how we review code and configurations.
It’s how we document architecture and decisions.
It’s our QA and testing practices.
It’s how we communicate with stakeholders during sprint reviews.
It’s the habit of running honest retrospectives and improving the next iteration.

These habits apply across ERP implementations, CRM transformations, automation initiatives, and Power Platform projects alike.

If the goal is a successful digital transformation project—but the daily working system includes rushed documentation, skipped reviews, unclear design decisions, or weak testing practices—then the goal becomes difficult to achieve.

High-performing consulting teams are not the ones who work late nights right before Go-Live.

They are the teams with strong systems—teams that build quality through consistent habits, structured processes, and disciplined collaboration every single day.

The Compound Interest of a Better PR Template

Clear’s powerful central thesis is about the compounding effect of tiny changes. He famously uses the mathematical example of improving by 1% every day for a year. You end up not 3.65 times better, but 37 times better.

This idea of small improvements compounding over time is precisely how a tech team builds a high-quality product. Think about it in terms of daily dev practices:

• A better code review template. Imagine a slight change that encourages a simple checklist. The habit of always checking for security vulnerabilities or for proper exception handling. That one small habit might prevent one critical bug a month.
• A “documentation first” habit. What if the team made it a strict rule to write the user story and a high-level documentation outline before writing any code? That small habit reduces ambiguity and leads to better quality.
• Standardizing Power Automate naming conventions. It seems trivial. But having hundreds of flows and logic apps with consistent naming (Scope-Action-Target) saves thousands of hours in debugging and knowledge transfer for everyone on the team over the course of a project.

These aren’t dramatic “transformative” changes. They are “atomic” habits—small, simple actions. But when practiced consistently by an entire team for weeks, months, or years, their positive effect on code quality, technical debt, and team efficiency is exponential.

Culture is the Sum of Our Daily Handshakes

We also spent a lot of time discussing team culture. It’s a word that is overused and under-defined. Organizational culture is often framed as a set of values or a mission statement. James Clear helps us look at it differently. He writes, “Every action you take is a vote for the type of person you wish to become.”

We can apply this directly to a technology team: your team culture is the sum of your daily team habits.

A “culture of transparency” isn’t created by a town hall speech; it’s built when it’s a standard habit for a consultant to raise their hand and say, “This functional requirement is more complex than we thought,” during the grooming session, rather than burying that complexity until the end of the sprint.

A “culture of collaboration” is built when it’s a team habit for developers to actively look for ways to help a peer who’s stuck, to pair-program on a difficult problem without being asked, or to leave constructive, teaching-oriented comments in a code review instead of just an “Approved.”

If you want a great team culture, don’t write a new values statement. Identify the specific, observable habits you want to see, and then design your environment to encourage them.

Making the Learning Habit Mandatory in an AI World

For a company specializing in the Microsoft ecosystem, the concept of a learning culture is not optional; it’s an absolute necessity. In our experience, teams that stop learning for even a year quickly fall behind in the Microsoft ecosystem. Dynamics 365, the Power Platform, Azure AI Services—these platforms are evolving at a breakneck pace. What was best practice 18 months ago might be legacy today.

Atomic Habits gives us a framework for making learning… well, atomic. A learning habit isn’t an “all-day training workshop” once a quarter. A learning habit is:

• The Friday “Show-and-Tell”: A 30-minute block on Friday afternoon where one team member does a quick demo of a new feature they discovered in the latest Microsoft release wave.
• The “One-New-Thing” Daily Slack Post: A simple habit where team members share one useful blog post, article, or piece of documentation they read that day.
• A dedicated “Learning Hour” on the calendar: Blocking out time for Microsoft Learn modules that is non-negotiable.

By focusing on these regular, tiny habits of learning, the team’s knowledgebase remains fresh and their skills stay on the cutting edge.

The Environment of Software Development

Finally, we reflected on the power of the environment. James Clear shows that we are profoundly influenced by our surroundings. In a tech team, that “environment” is our physical workspace, but also our digital, process, and tool-based environment.

• Make it obvious: If you want developers to follow a certain branching strategy, make the guidelines a pinned message in the relevant chat channel.
• Make it easy: Use automation to reduce friction. Set up GitHub or Azure DevOps pipelines to automatically check code formatting and run unit tests on every pull request. Don’t rely on the “willpower” of a developer to remember to run tests manually. Build it into the system so that not doing it is impossible.
• Make it satisfying: The feeling of seeing a automated deployment complete, or of seeing a piece of clean, elegant documentation get checked in, is a tiny reward that reinforces the habit.

Conclusion: Digital Transformation Starts with Team Habits

One of the most important insights from our discussions in the DMR culture club is that successful technology projects are rarely the result of a single breakthrough moment.

They are the result of consistent, small habits practiced by teams over time.

Writing clear documentation. Reviewing code carefully. Sharing new knowledge with colleagues. Raising risks early during sprint discussions. Continuously improving processes instead of accepting “good enough.” Individually, these behaviors may seem small.

But over the course of months and years, they compound — shaping the quality of the architecture, the maintainability of the solution, and the overall success of the project.

This is especially true in the Microsoft Business Applications ecosystem, where we work across Dynamics 365 ERP, CRM, and Power Platform solutions. The technology is evolving rapidly with innovations in AI, Copilot, automation, and data platforms. In such a fast-moving landscape, strong team habits become one of the most reliable sources of stability and excellence.

Technology will continue to change. Platforms will evolve. Tools will improve. AI will automate more and more tasks. But the core of successful projects will still depend on how teams work together every day.

At DMR, this realization is exactly why we started our culture club — a small space where our teams can step back from project deadlines and reflect on how we work and how we improve together.

Because in the end, great digital transformation is not built only through technology.

It is built through people, culture, and habits.

Digital transformation doesn’t happen in a single Go-Live moment.
It happens one small habit at a time.

Fatih Demirci

www.fatihdemirci.net