Skip to main content

Building capabilities that deliver: Start with the experience you already have

 When we started developing our cloud capability, one of the first things I wanted to understand was what experience we already had.

People across different locations had worked on cloud projects, solved difficult problems and learned things that could help other teams. Finding this information took effort. It was spread across teams, locations and systems. Each group collected information for its own needs. Sales needed customer references. Delivery teams knew the technical details. Regional leaders looked at people and availability. Communities followed skills and certifications.

Everyone had part of the picture. We needed to bring these parts together in one place.One of our working tools was an inventory connecting projects, technologies, locations and the people involved. The important part was agreeing what information we needed and how others would use it.

A technology name alone tells you very little. I wanted to know what the team had delivered, the constraints they had faced and who could explain the decisions. This gave us a better starting point when discussing a new opportunity. We needed a way to connect a challenge to a person, knowing to who to go when there are questions. It also helped us decide where to invest.

For example, experience needed by one team might already exist in another region. Connecting the teams could be the first step. In another area, several projects might depend on the same person. There, developing more people would become a priority.

These situations require different decisions. Before asking for a training budget, recruiting or building an accelerator, I want to understand the gap we are trying to close.

Keeping the information useful is another challenge. Someone needs to own it. Teams need to understand why contributing matters. Project descriptions need updating, and the people listed may have moved to other roles.

This becomes especially important when we use the information in a customer conversation. We need confidence that the experience is relevant and that the people behind it can still support us.

I see this visibility as a practical foundation for growing a capability. It helps us draw on our experience and make better decisions about what to build next.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

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...

Can User Technical Profile Influence AI Architecture Decisions?

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...

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

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...