Skip to main content

AI Adoption: a practical 6-week plan

By

 Giving people AI tools is the easy part. Getting them to use those tools every day is the hard part.

Too many companies buy licences, announce the tool, then expect adoption to happen by magic. People are busy, they don’t have time to learn, and often they don’t know where to start or what “good” looks like for their role. If you want real adoption, learning must happen in the flow of work: short, practical, role-focused and most importantly, hands-on.

The goal

Make people confident in using AI tools for daily work—not just for demos or toy examples.

The plan (6 weeks, minimal overhead)

Week 0: Sponsor & plan (30–60 min). Get a leader to agree to protected learning time and pick a handful of real use cases. Leadership backing is small but crucial.
Week 1: Role-based awareness (60–90 min). Run short sessions for each role: developers, QA, product, PM, support and show three concrete examples for the role. Keep it practical: real tasks, not abstract slides.
Weeks 2–4: Study groups and mini-challenges. Form groups of 6–8 people for weekly 60–90 minute meetings. Share prompts, run small exercises and solve one real task with the tool. Tiny homework, real problems.
Week 3: Embedded coaching (2–4 hours). Bring an early adopter or coach to sit with the team and work inside their actual tools (IDE, spreadsheet, ticketing system). Show how the AI fits the exact workflow. This hands-on approach beats slide decks.
Week 5: Train the champions. Prepare 3–5 champions to coach other teams. Run a short “how to teach” session, give them a simple learning playbook, and assign small missions to spread the practice.
Week 6: Review & next steps. Collect a few role-based success stories, measure quick wins and plan recurring refreshers.

What actually moves the needle

Short, role-specific sessions that show real tasks; small study groups that create a weekly habit and peer learning; embedded coaching where someone works with the team inside their tools for a few hours; a small champions network that can scale locally; and protected time from leaders so people can practice. None of this is fancy; it’s about creating space and connection between the tool and the daily workflow.

How to measure quick wins

To measure quick wins, identify three to five specific examples of the tool being used in actual workflows for each role within two weeks. Track the number of champions trained and the count of embedded coaching sessions completed. Collect at least one detailed story from a team member describing how the tool saved time or improved output in their regular tasks. Aim for concrete, role-specific outcomes that demonstrate tangible impact.

AI adoption isn’t just about technology. Give people time, show them how to use tools for real work, and let them practice. That’s how licenses deliver value.

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

By
In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more