Skip to main content

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

By

 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

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

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Azure Well-Architected AI workload Assessment

By
  AI is everywhere, part of the IT solutions we build and run today. Having an AI service, a good model, and data is not enough. As for cloud, the real difference is how we build, manage and run the whole solution. Microsoft created the Azure Well-Architected Framework for AI Workloads exactly for this reason — to help teams design AI systems that are reliable, secure, and cost-efficient. The assessment has six main categories that we cover in the next section. Based on the results, we can gain a good understanding of the current AI workload estate and a list of actions to improve how you run and manage your AI workloads . Designing the AI Application The first step in building your AI application is to consider how you will structure it. Using containers for tasks like data processing or model inference helps maintain consistency across the system. This approach makes it easier to update, move, and manage different components. When you have multiple steps in your workflow, such as...
Post a Comment
Read more