Skip to main content

Building capabilities that deliver: When have you built a capability?

 When building capabilities (like cloud) across regions, I focused on a core question: what should the organisation deliver as a direct result of this capability?

This question helped align decisions about people, projects and business priorities. Training, certifications, communities and reusable assets all play a role, but the focus remains on delivering outcomes we can stand behind for our customers.
Initially, we introduced a practical tool: an inventory of our cloud experience. We mapped projects, technologies, locations and the people involved. This gave us clear visibility into our expertise, exposed gaps and identified areas where we depended too heavily on a small group of individuals.
With this data, we could make targeted decisions about where to invest next.
Developing people required the same clarity. Training access was only the beginning. Teams needed time, hands-on environments and real opportunities to apply new skills. Feedback from our programs highlighted these constraints and allowed us to refine our approach.
Linking capability development with delivery is essential. Projects generate valuable experience, but making that experience reusable for other teams requires effort: documenting decisions, clarifying limitations and maintaining assets. This depends on clear ownership and sufficient capacity.
Customer engagements provided direct feedback and surfaced new requirements. Presales highlighted where our evidence was insufficient. Delivery clarified what we could commit to with confidence and under which conditions.
My responsibility was to connect these signals and translate them into decisions: which skills to develop, which services to strengthen, where to focus our expertise and which activities to discontinue.
This remains my approach to assessing a capability. Can we identify a customer need, assemble the right team and deliver? Does each experience improve the next engagement? Can the work continue if people or structures change?
When this cycle operates consistently and ownership is clear across teams, the capability is established.

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