Leadership: Build Future Capability Before It Is Urgently Needed

One of the clearest differences between ordinary management and exceptional leadership is the ability to prepare an organisation for challenges and opportunities that have not yet fully arrived.

Most organisations begin recruiting, reskilling or investing only after capability gaps have become visible. A major client asks for expertise the organisation does not possess. A new technology disrupts an established service. Regulation creates an urgent compliance requirement. Competitors launch a new proposition. Delivery teams become overloaded because demand has grown faster than the available workforce.

At that point, leaders are forced to react.

They must recruit quickly, pay a premium for scarce talent, depend heavily on contractors, form rushed partnerships or attempt to retrain people while simultaneously delivering critical work. The organisation may eventually build the required capability, but it often does so under pressure, at greater cost and with considerable execution risk.

Exceptional leaders take a different approach.

They identify the capabilities that are likely to become strategically important over the next three to five years and begin developing them before demand becomes urgent. They create the people, partnerships, intellectual property, operating models and career pathways that will allow the organisation to respond when the market shifts.

This is not simply workforce planning. It is strategic capability building.

It requires leaders to answer difficult questions:

• Which market changes are temporary, and which are structural?
• Which capabilities will become essential to clients, regulators and the organisation itself?
• What should be built internally?
• What should be acquired?
• Where should the organisation partner?
• Which existing employees can be reskilled?
• How long will it take for a new capability to become commercially productive?
• How much should the organisation invest before demand is fully proven?
• How can the organisation avoid chasing every emerging trend?

The purpose is not to predict the future perfectly. No leader can do that.

The purpose is to build an organisation that is better prepared than its competitors.

---

1. Why organisations usually build capability too late​

Many organisations recognise the importance of talent and capability, but their systems encourage short-term decision-making.

Business units are often measured on current-year revenue, utilisation, margin and delivery performance. Hiring decisions may require a confirmed business case. Training budgets are frequently cut when utilisation falls. Emerging capabilities may not have an established revenue pipeline. Leaders may hesitate to invest in teams that cannot immediately be allocated to billable work.

As a result, capability investment is delayed until demand is undeniable.

By then, several problems emerge.

Talent becomes expensive​

When an entire market begins searching for the same specialists, salary expectations rise, notice periods lengthen and retention becomes more difficult.

For example, once demand for AI security, model risk, responsible AI or agentic-system engineering becomes widespread, organisations may find themselves competing for a very small pool of experienced people.

Delivery quality becomes inconsistent​

Organisations may respond to capability gaps by assigning work to people who have adjacent but insufficient expertise. This can create weak architecture, poor controls, delivery delays or unsuitable recommendations.

The organisation becomes dependent on contractors​

Contractors can be valuable, especially for short-term specialist needs. However, overdependence can prevent knowledge from remaining inside the organisation. It may also create higher costs, weaker continuity and limited intellectual-property development.

Commercial opportunities are missed​

An organisation may identify an attractive opportunity but lack the credible team, case studies or delivery capacity required to pursue it. By the time the capability has been assembled, competitors may already hold the market position.

Existing employees lose confidence​

Employees may see the market changing but feel that the organisation is not investing in their development. High performers may leave to join companies that appear better prepared for the future.

Leaders are forced into rushed decisions​

When capability becomes urgent, leaders may make acquisitions, partnerships or hiring decisions without sufficient diligence. The result may be poor cultural fit, duplicated capability, high integration costs or unclear accountability.

Building capability early reduces these risks.

---

2. What future capability really means​

Future capability is broader than hiring people with new technical skills.

A capability exists only when the organisation can repeatedly use a combination of people, processes, technology, knowledge and governance to produce a valuable outcome.

For example, employing several AI engineers does not mean an organisation has an enterprise AI solution-engineering capability.

A mature capability may also require:

• Solution architects.
• Data engineers.
• Product managers.
• Security specialists.
• Responsible AI professionals.
• Industry experts.
• Commercial leaders.
• Change and adoption specialists.
• Delivery methodologies.
• Reference architectures.
• Reusable components.
• Quality standards.
• Governance processes.
• Technology partnerships.
• Training programmes.
• Career pathways.
• Communities of practice.
• Case studies and demonstrators.
• A clear route to market.

Leaders must therefore avoid treating capability building as a recruitment exercise.

It is an organisational design challenge.

---

3. Start with a three-to-five-year capability horizon​

Exceptional leaders regularly examine how the organisation’s market, clients, workforce and technology environment may evolve over the next three to five years.

The horizon must be long enough to allow meaningful preparation but close enough to support practical investment decisions.

A capability foresight process should consider several dimensions.

Market demand​

Leaders should study how client priorities are changing.

Questions may include:

• What problems are becoming more urgent for clients?
• Which budgets are increasing?
• Which services are becoming commoditised?
• Where are clients building internal capability?
• Which services are moving toward managed or outcome-based models?
• What new risks are boards discussing?
• Which client functions are likely to be transformed by technology?

Technology change​

Leaders should assess technologies that may alter products, services, operating models or workforce requirements.

The objective is not to invest in every new tool. It is to understand which technologies may create lasting organisational consequences.

Questions may include:

• Which technologies are moving from experimentation to enterprise adoption?
• Which technologies may change the economics of existing services?
• Which technologies will require new assurance, security or governance capabilities?
• What infrastructure will be needed?
• Which skills are likely to become scarce?
• Which current roles may change significantly?

Regulatory development​

New regulation can create substantial capability requirements.

For example, evolving rules relating to artificial intelligence, data privacy, sustainability reporting, operational resilience, cybersecurity and digital platforms may create demand for advisory, implementation and assurance services.

Leaders should ask:

• Which regulations are likely to affect clients in the next three to five years?
• Which industries will be affected first?
• What evidence, controls or reporting will organisations need?
• What new professional services may emerge?
• Which capabilities must be independent from implementation teams?

Industry transformation​

Technology affects industries differently.

The capability required to support AI adoption in financial services may differ from the capability required in healthcare, government, manufacturing, retail or energy.

Leaders should therefore examine:

• Industry-specific operating models.
• Data availability.
• Regulatory constraints.
• Technology maturity.
• Customer expectations.
• Workforce characteristics.
• Capital-investment cycles.
• Competitive pressures.

Workforce change​

Future capability planning must also consider how work itself will change.

Leaders should ask:

• Which roles will become more important?
• Which existing roles will be augmented by technology?
• Which tasks may become automated?
• Which human capabilities will become more valuable?
• Where will multidisciplinary teams be required?
• Which career models may no longer be attractive?
• How will younger employees expect to learn and progress?

The output should be a future capability map that identifies the capabilities the organisation may need, why they matter, when demand may emerge and how difficult they will be to build.

---

4. Distinguish structural change from temporary demand​

One of the most important leadership responsibilities is separating short-lived enthusiasm from long-term market change.

Not every emerging trend justifies building a permanent capability.

A sudden increase in client interest may be driven by media attention, temporary regulatory uncertainty or vendor marketing. If leaders respond to every trend by creating teams, appointing heads of capability and launching propositions, the organisation will become fragmented and expensive.

Exceptional leaders look for evidence of structural change.

Structural change usually has several characteristics.

It changes client economics​

A structural shift affects how clients make money, manage cost, allocate capital or compete.

For example, AI may become structurally important when it changes the cost of customer service, software development, compliance monitoring, decision support or content production.

It changes operating models​

A structural shift affects how work is organised and delivered.

Agentic systems, for example, may become structurally important if organisations begin redesigning processes around autonomous or semi-autonomous digital workers rather than using AI only as an employee-assistance tool.

It creates lasting risk or regulatory requirements​

A capability becomes more likely to endure when regulators, boards or professional bodies expect organisations to maintain formal controls, governance or evidence.

AI assurance may become a structural capability because organisations will need continuing confidence in model behaviour, data usage, oversight, fairness, security and compliance.

It changes client buying behaviour​

A shift may be structural when clients begin purchasing ongoing services rather than one-off projects.

Technology-enabled managed services are an example. Clients may increasingly purchase continuous monitoring, compliance operations, data-management services or AI-enabled business processes rather than standalone advisory engagements.

It attracts sustained investment​

Leaders should look for evidence that governments, major technology providers, investors and large enterprises are making long-term commitments.

It affects multiple service lines or functions​

A structural shift usually extends beyond a single isolated use case. It may influence strategy, operations, risk, technology, people and finance.

Leaders can use these indicators to score emerging capabilities against:

• Market durability.
• Strategic relevance.
• Revenue potential.
• Client urgency.
• Regulatory significance.
• Talent scarcity.
• Competitive differentiation.
• Ability to reuse the capability.
• Alignment with the organisation’s existing strengths.

This reduces the risk of investing heavily in temporary demand.

---

5. Identify the capabilities that will matter most​

The following capability areas illustrate the kinds of investments leaders may need to consider.

AI solution engineering​

AI solution engineering connects business problems with practical, secure and scalable AI systems.

The capability goes beyond model development. It includes:

• Business-problem framing.
• Use-case prioritisation.
• AI and non-AI option assessment.
• Solution architecture.
• Data design.
• Model and platform selection.
• Integration with enterprise systems.
• Security and privacy controls.
• Evaluation and testing.
• Human oversight.
• Deployment and observability.
• Cost management.
• Adoption and change.
• Benefit measurement.

Organisations that wait until demand becomes urgent may discover that they have data scientists but lack people who can shape complete enterprise solutions.

Building the capability early may involve:

• Defining an AI solution-engineering role family.
• Creating reference architectures.
• Developing cloud-specific implementation patterns.
• Building demonstrators.
• Training architects and engineers in AI risk.
• Teaching technical specialists commercial and executive communication.
• Creating reusable discovery and solution-shaping methods.

AI assurance​

As organisations use AI in increasingly important decisions, they will need confidence that systems are reliable, explainable, controlled and compliant.

AI assurance may include:

• Model validation.
• Data-quality assessment.
• Fairness and bias testing.
• Explainability evaluation.
• Robustness testing.
• Security testing.
• Governance assessment.
• Documentation review.
• Human-oversight evaluation.
• Regulatory-readiness assessment.
• Continuous monitoring.
• Independent assurance reporting.

Building this capability requires more than technical testing. It may require professionals with backgrounds in audit, risk, statistics, law, cybersecurity, data science and industry regulation.

Leaders must also consider independence. The team assuring an AI system may need to remain separate from the team that designed or implemented it.

AI security​

AI introduces security risks that differ from traditional application security.

Future capability may need to cover:

• Prompt injection.
• Data leakage.
• Model theft.
• Training-data poisoning.
• Insecure model integration.
• Excessive agent permissions.
• Tool misuse.
• Supply-chain vulnerabilities.
• Adversarial examples.
• Unsafe autonomous actions.
• Identity and access control.
• Model-provider risk.
• AI red teaming.
• Runtime monitoring.
• Incident response.

Building an AI security capability may require close coordination between cybersecurity, AI engineering, cloud, data, privacy and risk teams.

The organisation should not wait for a major AI incident before developing this expertise.

Data-product management​

Many organisations have large amounts of data but struggle to turn it into reusable, trusted products.

Data-product management treats data as a product with defined users, quality standards, ownership, service levels and lifecycle management.

The capability may include:

• User-needs discovery.
• Data-domain ownership.
• Product roadmaps.
• Data contracts.
• Quality measurement.
• Metadata and lineage.
• Access models.
• Platform integration.
• Usage analytics.
• Cost allocation.
• Product retirement.

This capability will become increasingly important as organisations develop AI systems that depend on reliable and accessible enterprise data.

Quantum readiness​

Quantum computing may not create immediate commercial demand in every industry, but certain organisations should begin preparing early.

Quantum readiness may involve:

• Identifying business problems where quantum methods could eventually matter.
• Understanding likely industry impact.
• Monitoring hardware and algorithm development.
• Assessing cryptographic exposure.
• Planning post-quantum cryptography.
• Developing small research teams.
• Building relationships with universities and technology providers.
• Educating boards without overstating maturity.

The objective is not to build a large quantum team prematurely. It is to ensure that the organisation can recognise meaningful developments and respond intelligently.

Sustainability analytics​

Clients face increasing pressure to measure, manage and report environmental and social impact.

Sustainability analytics may include:

• Carbon-accounting data.
• Climate-risk modelling.
• Supply-chain emissions.
• Energy-usage optimisation.
• Scenario analysis.
• Sustainability reporting.
• Nature and biodiversity data.
• Transition planning.
• Regulatory disclosure.
• Assurance of sustainability information.

This capability may require professionals who understand data, finance, regulation, climate science, operations and assurance.

Digital regulation​

The digital economy is becoming increasingly regulated.

Organisations may require capability relating to:

• Artificial-intelligence regulation.
• Data protection.
• Digital operational resilience.
• Online safety.
• Platform regulation.
• Cybersecurity requirements.
• Digital competition.
• Algorithmic accountability.
• Cross-border data transfer.
• Digital identity.
• Technology procurement.

A strong digital-regulation capability combines legal interpretation with practical implementation. Clients do not only need to understand new rules; they need to redesign processes, systems, controls and evidence.

Agentic systems​

Agentic systems can plan, make decisions, use tools and perform sequences of actions with varying levels of autonomy.

Building capability in this area may require:

• Agent architecture.
• Tool and workflow orchestration.
• Permission design.
• Memory and context management.
• Human approval.
• Multi-agent coordination.
• Evaluation.
• Security controls.
• Failure handling.
• Observability.
• Cost management.
• Accountability design.

Agentic systems may create significant operational value, but they also introduce new forms of risk. Organisations that develop this capability early can create safer and more commercially viable solutions.

Industry cloud​

Industry-cloud capability combines cloud platforms with sector-specific data models, workflows, controls and applications.

It may include:

• Industry reference architectures.
• Preconfigured regulatory controls.
• Sector-specific data models.
• Reusable process components.
• Integration patterns.
• Cloud marketplaces.
• Industry partnerships.
• Managed platforms.
• Accelerators and demonstrators.

Industry cloud can reduce implementation time and differentiate an organisation from competitors offering generic technology services.

Technology-enabled managed services​

Many professional and technology organisations are moving from project-based delivery toward recurring services supported by technology, data and automation.

Examples may include:

• Continuous compliance monitoring.
• AI-enabled customer operations.
• Managed cybersecurity.
• Data-quality operations.
• Regulatory reporting.
• Finance-process services.
• Model monitoring.
• Fraud detection.
• Procurement analytics.
• Sustainability reporting.

Building managed-service capability requires different skills from traditional consulting.

The organisation may need:

• Product management.
• Service operations.
• Service-level management.
• Platform engineering.
• Automation.
• Customer success.
• Commercial pricing.
• Capacity planning.
• 24-hour support.
• Incident management.
• Continuous improvement.
• Long-term risk ownership.

Leaders must begin developing these capabilities well before launching large managed-service propositions.

---

6. Build specialist teams before demand becomes obvious​

Creating a specialist team early can give the organisation a significant advantage.

However, the team should be deliberately designed.

A common mistake is creating a large central team without a clear purpose, commercial model or connection to the wider organisation. The result may be an expensive group that produces research and prototypes but struggles to influence client delivery.

An early specialist team should have a focused mandate.

For example:

• Build market understanding.
• Develop initial propositions.
• Support strategic opportunities.
• Create reusable assets.
• Establish delivery standards.
• Train the wider organisation.
• Build partner relationships.
• Produce demonstrators.
• Develop early client case studies.
• Identify talent requirements.
• Test commercial models.

The team may begin as a small multidisciplinary group rather than a large department.

It could include:

• A capability leader.
• A solution architect.
• A technical specialist.
• An industry expert.
• A product or proposition lead.
• A risk or assurance specialist.
• A commercial lead.

The team should have measurable objectives, such as:

• Number of priority propositions developed.
• Strategic opportunities supported.
• Reusable assets created.
• Employees trained.
• Partnerships established.
• External market recognition.
• Revenue influenced.
• Client pilots converted into scaled delivery.

Leaders should review the team regularly and expand it only when evidence supports further investment.

---

7. Decide what to build, buy, partner or borrow​

Not every capability should be developed entirely inside the organisation.

Exceptional leaders evaluate several routes.

Build​

The organisation should build internally when the capability:

• Is central to long-term differentiation.
• Depends heavily on organisational knowledge.
• Requires close integration with existing teams.
• Is likely to generate sustained demand.
• Involves sensitive client or internal information.
• Creates reusable intellectual property.
• Supports multiple service lines or markets.

Building provides control and long-term value, but it can take time.

Buy​

Acquiring a specialist business may be appropriate when:

• The capability is urgently required.
• Talent is difficult to recruit individually.
• The target has established intellectual property.
• The business has strong client relationships.
• The organisation needs market credibility.
• The capability would take too long to develop internally.

However, acquisition is not a substitute for strategy.

Leaders must assess:

• Cultural compatibility.
• Talent-retention risk.
• Integration requirements.
• Client overlap.
• Technology compatibility.
• Brand implications.
• Independence or regulatory concerns.
• Whether the capability can scale.
• Whether value depends on a small number of individuals.

A small acquisition can accelerate capability, but poorly managed integration can destroy the value that was acquired.

Partner​

Technology alliances, research partnerships and delivery partnerships can provide access to expertise without requiring full ownership.

Partnerships may be useful when:

• Technology changes rapidly.
• A platform provider has unique capabilities.
• Joint market development is possible.
• The organisation needs access to specialist tools.
• Client solutions require several ecosystems.
• Neither party can succeed alone.

Strong alliances require more than signing an agreement.

They need:

• Clear strategic objectives.
• Joint propositions.
• Named executive sponsors.
• Shared account planning.
• Technical enablement.
• Commercial agreements.
• Training.
• Co-investment.
• Pipeline tracking.
• Delivery governance.
• Conflict management.

The organisation should avoid collecting partnerships that exist mainly for marketing purposes.

Borrow​

For emerging or uncertain areas, temporary access to capability may be appropriate.

This may include:

• Contractors.
• Visiting researchers.
• Secondments.
• Academic advisers.
• Specialist subcontractors.
• Joint ventures.
• Global-network experts.

Borrowing capability can help the organisation test demand before making a larger commitment.

However, leaders should ensure that knowledge is transferred to permanent teams.

---

8. Acquire small specialist businesses carefully​

Acquiring a specialist business can rapidly provide talent, technology, intellectual property and market reputation.

For example, an organisation may acquire a small company specialising in:

• AI red teaming.
• Model assurance.
• Sustainability data.
• Cloud security.
• Data-product design.
• Digital regulation.
• Industry-specific analytics.
• Managed AI operations.

The acquisition thesis should be explicit.

Leaders must explain:

• What capability is being acquired?
• Why can it not be built quickly enough internally?
• How will the acquired team strengthen the wider organisation?
• Which clients and markets will benefit?
• How will the acquired capability scale?
• What will remain independent?
• How will key people be retained?
• What integration will occur in the first 100 days?
• How will success be measured?

The greatest risk is often not the acquisition price. It is the loss of specialist talent after the transaction.

Small innovative firms may operate differently from large organisations. Their employees may value autonomy, speed, technical depth and entrepreneurial culture. Excessive bureaucracy can cause them to leave.

Exceptional leaders therefore protect what made the acquired business valuable while connecting it to the resources, clients and scale of the larger organisation.

---

9. Develop alliances with technology companies​

Technology companies can help organisations build future capability faster.

Potential partners may include:

• Cloud providers.
• AI model providers.
• Data-platform companies.
• Cybersecurity firms.
• Enterprise-software vendors.
• Semiconductor companies.
• Start-ups.
• Industry-platform providers.

A future-focused alliance should create value in several ways.

Capability development​

Partners can provide training, certifications, technical support, sandbox environments and early access to products.

Proposition development​

The organisation and partner can jointly build industry propositions, reference architectures and accelerators.

Market access​

Joint events, campaigns and account planning can create client opportunities.

Innovation​

Partners may provide access to research, product roadmaps and technical experts.

Delivery capacity​

The organisation can develop implementation and managed-service capability around the partner’s platform.

However, leaders must preserve strategic independence.

They should avoid becoming so dependent on one provider that the organisation cannot offer objective advice or support clients operating across multiple platforms.

---

10. Create university partnerships​

Universities are valuable sources of research, talent and long-term capability.

A strong university partnership can include:

• Joint research.
• Sponsored doctoral projects.
• Student placements.
• Graduate recruitment.
• Executive education.
• Innovation laboratories.
• Shared datasets.
• Industry challenges.
• Technical seminars.
• Visiting professorships.
• Joint publications.
• Commercialisation of research.

Leaders should choose partners based on strategic relevance rather than reputation alone.

A university may be valuable because it has specialist strength in:

• Machine learning.
• Cybersecurity.
• Quantum computing.
• Robotics.
• Climate science.
• Human-computer interaction.
• Digital ethics.
• Public policy.
• Healthcare technology.
• Advanced manufacturing.

The partnership should have clear outcomes.

For example:

• Develop a pipeline of 20 specialist graduates per year.
• Produce research on trusted agentic systems.
• Create a prototype for sustainability-data assurance.
• Establish a joint laboratory.
• Publish an annual market report.
• Develop a conversion programme for non-technical professionals.

University partnerships work best when they connect research with real organisational and client problems.

---

11. Sponsor research and innovation​

Future capability often begins with research.

However, research should not become disconnected from strategic need.

Exceptional leaders create a balanced innovation portfolio.

Horizon-one innovation​

Improvements that can be applied to current services or operations.

Examples include:

• Automating proposal creation.
• Improving knowledge search.
• Reducing AI inference cost.
• Strengthening data quality.
• Creating reusable delivery components.

Horizon-two innovation​

Capabilities likely to create commercial value within one to three years.

Examples include:

• AI assurance methods.
• Agentic workflow platforms.
• Industry-specific AI accelerators.
• Managed model-monitoring services.
• Data-product operating models.

Horizon-three innovation​

Longer-term areas where timing and commercial value remain uncertain.

Examples include:

• Quantum applications.
• Advanced autonomous systems.
• New forms of digital identity.
• Synthetic-data ecosystems.
• Emerging human-machine interfaces.

Leaders should define how research progresses.

A useful pathway may be:

1. Research question.
2. Concept paper.
3. Small experiment.
4. Demonstrator.
5. Client pilot.
6. Reusable solution.
7. Scaled proposition.
8. Managed service or established capability.

Each stage should have criteria for continuation, modification or termination.

The organisation should be willing to stop weak ideas. Future capability building requires patience, but it should not protect projects from evidence.

---

12. Develop apprenticeships and conversion programmes​

Relying only on experienced external hires is rarely sustainable.

In fast-growing capability areas, the external market may not contain enough experienced people. Organisations must create their own talent pipelines.

Apprenticeships can provide structured entry routes for people who may not have traditional academic or professional backgrounds.

Conversion programmes can help experienced professionals move from adjacent disciplines.

Examples include:

• Software engineers becoming AI solution engineers.
• Auditors becoming AI assurance specialists.
• Cybersecurity professionals moving into AI security.
• Business analysts becoming data-product managers.
• Lawyers moving into digital-regulation advisory.
• Industry specialists becoming technology-enabled transformation leaders.
• Data analysts becoming sustainability-analytics specialists.

A strong conversion programme should include:

• Initial capability assessment.
• Core technical or professional training.
• Practical assignments.
• Mentoring.
• Supervised client work.
• Formal assessment.
• Community support.
• Certification where relevant.
• A clear destination role.

Leaders should not assume that short online courses create professional capability. People need repeated application, feedback and experience.

---

13. Reskill experienced professionals​

Experienced employees are one of the organisation’s most valuable sources of future capability.

They understand clients, industries, delivery, regulation, commercial models and organisational culture. Their knowledge can be combined with new technical or analytical skills.

Reskilling experienced professionals can be more valuable than hiring only junior technical talent.

For example, a professional with ten years of financial-services risk experience may become a highly effective AI governance or AI assurance leader after targeted technical training.

A reskilling strategy should identify:

• Which current roles are likely to change.
• Which existing skills remain valuable.
• Which new capabilities can be learned.
• Which employees have the motivation and potential to transition.
• How much protected learning time is required.
• What practical experience will be available.
• How compensation and promotion will be affected.
• How previous seniority will translate into the new career path.

A common failure is asking employees to reskill in their spare time while maintaining full delivery targets.

Serious reskilling requires protected time, practical work and leadership support.

---

14. Create new career pathways​

New capabilities cannot grow if the organisation’s career model only recognises traditional roles.

Employees need to understand:

• What roles exist.
• What skills each role requires.
• How progression works.
• How technical expertise is rewarded.
• Whether people can move between technical, commercial and leadership paths.
• How specialist contribution is valued.
• What evidence is required for promotion.
• How compensation compares with the external market.

Future capability may require several career pathways.

Technical specialist pathway​

For people who want to deepen expertise without becoming general managers.

Potential roles may include:

• Principal AI engineer.
• Distinguished architect.
• AI security specialist.
• Quantum research lead.
• Model-risk specialist.
• Data-product architect.

Product and proposition pathway​

For people who translate capability into scalable market offerings.

Potential roles may include:

• AI product manager.
• Managed-service product lead.
• Industry-solution lead.
• Data-product director.
• Proposition owner.

Delivery leadership pathway​

For people who lead complex programmes and multidisciplinary teams.

Commercial leadership pathway​

For people who build markets, shape opportunities and manage strategic accounts.

Risk and assurance pathway​

For professionals focused on governance, validation, compliance and independent assurance.

Employees should be able to move between pathways at different stages of their careers.

Without clear pathways, specialist talent may leave because management is the only visible route to progression.

---

15. Build communities of practice​

Formal teams alone are not enough.

Future capabilities often need to spread across business units, regions and service lines.

A community of practice can connect employees who share an interest or emerging specialism.

An effective community may provide:

• Regular technical sessions.
• Case-study reviews.
• Shared tools and templates.
• Office hours.
• Mentoring.
• Innovation challenges.
• External speakers.
• Research summaries.
• Delivery support.
• Reusable assets.
• Career information.
• Collaboration opportunities.

However, communities should not become passive discussion groups.

They should have clear outputs, such as:

• Published guidance.
• Reference architectures.
• Training modules.
• New propositions.
• Client demonstrators.
• Technical standards.
• Delivery reviews.
• Skills directories.
• Mentoring relationships.

Leaders should sponsor communities while allowing members to shape their content.

---

16. Create capability academies​

A capability academy provides a structured approach to developing future skills at scale.

An academy should be more than a collection of training courses.

It may include:

• Role-based curricula.
• Foundation, practitioner and advanced levels.
• Live instruction.
• Self-paced content.
• Labs and simulations.
• Client scenarios.
• Assessments.
• Certifications.
• Mentoring.
• Apprenticeships.
• Rotations.
• Communities of practice.
• Demonstration projects.
• Leadership development.

For example, an AI solution-engineering academy might include:

Foundation​

• AI fundamentals.
• Data fundamentals.
• Responsible AI.
• Cloud concepts.
• Business-case development.
• Security basics.

Practitioner​

• Use-case discovery.
• Solution architecture.
• Retrieval-augmented generation.
• Agentic workflows.
• Evaluation.
• Integration.
• Deployment.
• Observability.
• Cost management.

Advanced​

• Enterprise architecture.
• Multi-agent systems.
• AI security.
• Regulatory design.
• Complex delivery leadership.
• Commercial proposition development.
• Executive communication.

Participants should complete real work, not only theoretical assessments.

---

17. Connect capability building to commercial strategy​

Future capability must eventually create organisational value.

Leaders should define how each capability will support:

• New revenue.
• Client retention.
• Market differentiation.
• Delivery quality.
• Productivity.
• Risk reduction.
• Reusable intellectual property.
• Managed services.
• Talent attraction.
• Strategic partnerships.

Each capability should have a commercial pathway.

For example, an AI assurance capability may progress through:

1. Internal AI control reviews.
2. Client readiness assessments.
3. Model-validation projects.
4. Regulatory assurance services.
5. Continuous monitoring.
6. Industry-specific assurance platforms.
7. Recurring managed assurance services.

Leaders should avoid demanding immediate revenue from every emerging capability. Some investment is necessary before the market develops.

However, there should still be a clear hypothesis explaining how the capability may create value.

---

18. Use a capability investment portfolio​

Future capability should be managed as an investment portfolio.

Not every capability will have the same level of certainty.

A portfolio may include four categories.

Core capabilities​

Capabilities that are already essential and require continuous strengthening.

Examples may include cloud engineering, cybersecurity, data engineering and digital transformation.

Scaling capabilities​

Capabilities with proven demand that require rapid expansion.

Examples may include AI solution engineering, AI security or data-product management.

Emerging capabilities​

Capabilities with strong strategic potential but limited current demand.

Examples may include agentic-system assurance or industry-cloud operations.

Exploratory capabilities​

Capabilities with high uncertainty but potentially significant long-term impact.

Examples may include quantum applications or advanced autonomous systems.

Each category should have different investment expectations.

Core capabilities may be measured through scale, quality and utilisation.

Exploratory capabilities may be measured through learning, partnerships, prototypes and strategic insight.

Applying the same financial expectations to every category will either encourage waste or prevent innovation.

---

19. Establish clear governance​

Future capability investment requires governance because resources are limited and uncertainty is high.

A capability council may include:

• Business leadership.
• Technology leadership.
• Industry leaders.
• Talent leadership.
• Finance.
• Risk and legal.
• Learning and development.
• Innovation.
• Commercial leadership.

The council should review:

• Market evidence.
• Capability maturity.
• Talent supply.
• Financial investment.
• Strategic alignment.
• Partnership options.
• Intellectual property.
• Risks.
• Commercial pipeline.
• Scaling decisions.
• Capabilities to stop or merge.

Every capability should have a senior accountable owner.

That person should be responsible for:

• Capability strategy.
• Talent development.
• Market proposition.
• Partnerships.
• Standards.
• Investment.
• Performance reporting.
• Integration across the organisation.

Ownership should not be symbolic. The leader must have sufficient authority and resources.

---

20. Define a capability maturity model​

A maturity model can help leaders assess progress consistently.

Level 1: Awareness​

The organisation understands that the capability may become important.

Typical characteristics:

• Informal research.
• A small number of interested individuals.
• No formal proposition.
• No dedicated funding.
• Limited external presence.

Level 2: Experimentation​

The organisation begins testing the capability.

Typical characteristics:

• Pilot projects.
• Small training programmes.
• Initial partnerships.
• Demonstrators.
• Early client conversations.

Level 3: Emerging capability​

The organisation creates a defined team and market offering.

Typical characteristics:

• Named leadership.
• Role definitions.
• Initial methodology.
• Early case studies.
• Dedicated investment.
• Growing pipeline.

Level 4: Scaled capability​

The capability operates across multiple teams, clients or industries.

Typical characteristics:

• Repeatable delivery.
• Strong talent pipeline.
• Reusable intellectual property.
• Defined quality standards.
• Material revenue.
• Established partnerships.

Level 5: Market leadership​

The organisation helps define the market.

Typical characteristics:

• Recognised thought leadership.
• Proprietary platforms or methods.
• Strong external reputation.
• Strategic client relationships.
• Ability to attract leading talent.
• Influence on standards or regulation.
• International scale.

The maturity model allows leaders to match investment with evidence.

---

21. Measure more than headcount​

Capability development should not be measured only by the number of people hired or trained.

A balanced scorecard may include several dimensions.

Talent​

• Number of qualified specialists.
• Skills depth.
• Retention.
• Diversity of experience.
• Leadership succession.
• Internal mobility.
• Training completion.
• Practical assessment results.

Market​

• Strategic opportunities supported.
• Client demand.
• Revenue influenced.
• Revenue generated.
• Pipeline quality.
• Client references.
• Market recognition.

Delivery​

• Project quality.
• Time to deploy.
• Reuse of assets.
• Delivery margin.
• Client satisfaction.
• Defect or incident rates.
• Scalability.

Innovation​

• Research produced.
• Prototypes developed.
• Patents or intellectual property.
• University partnerships.
• New propositions.
• Experiments converted into services.

Organisational impact​

• Productivity improvement.
• Risk reduction.
• Employee adoption.
• Cross-service-line collaboration.
• Reduction in contractor dependency.
• Improved talent attraction.

Strategic readiness​

• Ability to respond to major opportunities.
• Coverage of priority industries.
• Capability resilience.
• Succession depth.
• Platform readiness.
• Regulatory preparedness.

The most important question is not how many people attended training.

It is whether the organisation can now perform work that it could not perform before.

---

22. Protect time for learning and development​

Future capability cannot be built through aspiration alone.

Employees need time to learn, experiment, collaborate and apply new skills.

Leaders should establish:

• Protected learning days.
• Reduced utilisation targets during conversion programmes.
• Funded certifications.
• Access to technology environments.
• Mentoring.
• Internal rotations.
• Innovation assignments.
• Participation in research.
• Recognition for knowledge sharing.

Managers must not penalise employees for using approved development time.

When delivery pressure increases, learning is often the first activity to be cancelled. This creates a cycle in which capability remains weak, causing even greater delivery pressure.

Exceptional leaders protect long-term capability even when short-term demands are intense.

---

23. Create real opportunities to apply new skills​

Training without application rarely creates capability.

Employees need opportunities to use new skills in real or realistic contexts.

This may include:

• Internal transformation projects.
• Supervised client assignments.
• Sandboxed experiments.
• Hackathons linked to business problems.
• Rotations into specialist teams.
• Shadowing experienced professionals.
• Research projects.
• Demonstrator development.
• Proposal support.
• Quality reviews.
• Managed-service operations.

Leaders should create an experience ladder.

For example:

1. Complete foundation training.
2. Work through a simulated case.
3. Support an internal project.
4. Shadow a client engagement.
5. Deliver a defined work package.
6. Lead a small engagement.
7. Coach other practitioners.
8. Contribute to standards and intellectual property.

Capability develops through progressive responsibility.

---

24. Retain scarce talent​

Building future capability is difficult. Losing it is easy.

Scarce specialists may leave because of:

• Uncompetitive compensation.
• Limited technical progression.
• Excessive bureaucracy.
• Lack of meaningful work.
• Weak leadership.
• Poor access to tools.
• Unclear career pathways.
• Pressure to become general managers.
• Lack of recognition.
• Isolation from peers.

Retention should therefore include:

• Competitive reward.
• Strong technical leadership.
• Interesting work.
• Access to research and innovation.
• Visible career progression.
• External speaking opportunities.
• Communities of practice.
• Flexible working models.
• Recognition of specialist contribution.
• Protection from unnecessary administration.

Leaders should regularly speak directly with critical talent rather than relying only on annual surveys.

---

25. Avoid common capability-building mistakes​

Chasing every trend​

The organisation creates teams around fashionable topics without evidence of long-term demand.

Hiring without an operating model​

Specialists are recruited, but nobody knows how they will support clients, delivery teams or commercial activity.

Training without application​

Employees complete courses but never use the new skills.

Creating isolated centres​

A central team becomes disconnected from industries, service lines or client accounts.

Measuring attendance rather than capability​

Success is reported through training numbers rather than practical performance.

Ignoring experienced professionals​

The organisation focuses only on graduate recruitment and fails to reskill valuable existing employees.

Overreliance on technology partners​

The organisation becomes a reseller or implementation channel without developing independent expertise.

Failing to create career paths​

Specialists leave because they cannot see how to progress.

Scaling too early​

A large team is created before the value proposition and demand are proven.

Scaling too late​

Leadership waits for certainty and loses the market opportunity.

Protecting weak investments​

Capability initiatives continue because senior leaders sponsored them, even when evidence is poor.

Exceptional leadership requires both commitment and the willingness to change direction.

---

26. A practical capability-building roadmap​

Phase 1: Strategic sensing​

Leaders should:

• Identify market, technology, regulatory and workforce trends.
• Consult clients, employees, partners and researchers.
• Develop future scenarios.
• Create an initial capability map.
• Separate structural trends from temporary demand.

Phase 2: Prioritisation​

For each potential capability, assess:

• Strategic alignment.
• Market durability.
• Client relevance.
• Talent scarcity.
• Investment required.
• Time to maturity.
• Competitive advantage.
• Commercial potential.
• Risk.
• Ability to reuse.

Select a limited number of priority capabilities.

Phase 3: Capability design​

Define:

• Capability purpose.
• Services or outcomes.
• Role families.
• Required skills.
• Operating model.
• Governance.
• Technology.
• Partnerships.
• Learning pathways.
• Commercial model.
• Investment requirements.
• Success measures.

Phase 4: Seed investment​

Create a small initial team.

Develop:

• Research.
• Demonstrators.
• Training.
• Initial methods.
• Reference architectures.
• Partnerships.
• Early client pilots.
• Internal use cases.

Phase 5: Validation​

Test whether:

• Clients recognise the problem.
• The proposition creates value.
• The organisation can deliver effectively.
• The commercial model is viable.
• The capability is differentiated.
• The talent model is sustainable.

Phase 6: Scale​

Expand:

• Recruitment.
• Reskilling.
• Geographic coverage.
• Industry specialisation.
• Partnerships.
• Intellectual property.
• Managed services.
• Marketing.
• Leadership succession.

Phase 7: Institutionalise​

Embed the capability into:

• Strategic planning.
• Account planning.
• Recruitment.
• Learning.
• Quality standards.
• Performance management.
• Technology platforms.
• Risk governance.
• Career pathways.
• Investment processes.

Phase 8: Renew or retire​

Review whether the capability remains strategically relevant.

Leaders should:

• Refresh obsolete skills.
• Merge overlapping teams.
• Retire weak propositions.
• Reallocate investment.
• Identify the next capability horizon.

Capability building is a continuous cycle, not a one-time initiative.

---

27. Questions exceptional leaders ask​

Leaders building future capability should repeatedly ask:

• What will our clients need from us three to five years from now?
• Which current services may decline or become automated?
• Which capabilities will become essential rather than optional?
• Where are competitors investing?
• Where could we establish a position before the market becomes crowded?
• What evidence suggests this change is structural?
• Which capability should we build internally?
• Which capability should we acquire or partner for?
• Which existing employees could transition into new roles?
• What career paths will retain specialist talent?
• How will people gain practical experience?
• What reusable assets should we create?
• What should we test before scaling?
• What would cause us to stop investing?
• How will the capability create client, commercial or organisational value?
• Are we building a collection of individuals or a repeatable organisational capability?
• Who is accountable?
• What decisions must be made now rather than later?

These questions help leadership move from vague interest to disciplined preparation.

---

28. The leadership mindset required​

Building capability before it is urgently needed requires a particular leadership mindset.

Long-term orientation​

The leader must invest beyond the current reporting period.

Strategic courage​

The leader must make decisions before complete certainty exists.

Intellectual discipline​

The leader must distinguish evidence from hype.

Commercial understanding​

The capability must eventually create measurable value.

Talent stewardship​

The leader must treat workforce development as a strategic responsibility.

Organisational influence​

Future capability often requires cooperation across business units, functions and geographies.

Patience​

Some capabilities take years to mature.

Willingness to stop​

Leaders must terminate initiatives when evidence no longer supports them.

Personal curiosity​

The leader must continue learning about technology, regulation, industries and workforce change.

Humility​

Future planning requires recognising uncertainty and listening to specialists.

The objective is not to claim certainty about the future. It is to create intelligent options.

---

Conclusion​

Most organisations wait until a capability gap becomes painful before responding.

They recruit after demand exceeds supply. They develop training after delivery quality declines. They create partnerships after competitors have established stronger ecosystems. They redesign career paths after specialists begin leaving. They invest in governance after an incident or regulatory deadline creates urgency.

Exceptional leaders act earlier.

They identify capabilities that are likely to matter in three to five years. They determine whether changes are temporary or structural. They build small specialist teams, create university and technology partnerships, sponsor research, acquire targeted businesses, reskill experienced professionals and establish new career pathways.

They do not invest blindly. They use evidence, scenarios, maturity models, portfolio governance and measurable outcomes.

They understand that future capability is not merely a collection of technical skills. It is the organisation’s ability to repeatedly combine people, technology, processes, knowledge, partnerships and governance to solve important problems.

The strongest organisations are rarely those that predict every future development correctly.

They are the organisations that begin preparing early, learn faster than competitors and build the capacity to respond when the future arrives.