Technology

New technology is putting training creation into the hands of employees and subject experts. Meanwhile, the global corporate e-learning market is heading towards US$335 billion. The market is forecast to more than triple in size this decade as employers face growing pressure to continuously reskill their workforces. However, this surge in demand is also exposing a fundamental problem.

The narrative about Africa’s technological future often relies on the narrow assumption that the continent must “catch up” with global innovation. However, this framing misses a critical point: Africa has never simply consumed technology. We adapt it, reshape it, and increasingly originate it. This is the essence of Africanisation: designing and deploying technology to respond directly to the continent’s cultural nuances, economic realities, and local challenges.

The traditional office social fabric is undergoing a profound psychological shift. Instead of walking down the corridor to bounce ideas off a colleague or venting to a teammate over coffee, workers increasingly turn to Artificial Intelligence (AI). They use it as their primary workplace confidant, sounding board, and creative partner.

A cyberattack does not end when malicious activity has been contained. For the affected business, that is usually when the most expensive phase begins. When an attacker breaches a system, the problem quickly extends beyond IT. Systems may go offline while staff try to keep the business running. Customers demand answers, and the business may need to meet regulatory obligations. All these activities cost money, often when revenue is already under pressure.

With the growing use of Artificial Intelligence (AI) and its integration into corporate systems, a key question arises: can a company be held responsible for misleading statements made by its AI chatbot to a customer? This issue arose in Moffatt vs Air Canada, a case concerning a refund for a bereavement fare. Although a Canadian small-claims tribunal decided the case in 2024, its ruling does not bind South African courts.

Enterprises love to call themselves Application Programming Interface (API)-first. However, almost none are ready for what is about to start calling those APIs. According to Postman's 2025 State of the API Report, 82% of organisations now describe themselves as API-first. It's a comfortable number to cite in a strategy deck. However, that number becomes far less comfortable when we ask what “API-first” was actually built to withstand.

When farmers take a photo of unfamiliar spots on a crop and ask a question on their phone, they’re not thinking about digital systems or models. Instead, they are looking for reassurance, guidance, and something they can act on before the problem spreads. Moments like these are becoming increasingly common as technology becomes a first stop for information and decision-making. This shift extends from the field to the clinic and the classroom. Yet whether that farmer gets a useful answer still often comes down to one simple factor: language.

When a financial institution moves Jira, Confluence, or Jira Service Management into the cloud, part of the operational burden shifts to the provider. Atlassian runs the platform and maintains the underlying infrastructure. Meanwhile, the customer gains the service capabilities that come with software as a service (SaaS). However, moving to the cloud does not eliminate the institution’s responsibility to manage technology risks and meet regulatory requirements.

Twenty years ago, PC procurement was pretty straightforward. Business leaders would evaluate hardware specifications and then set off to compare vendors. This process was generally rooted in a single, simple transaction. It was one and done. Fast-forward to now, and this is no longer the case.

Backup, disaster recovery, and operational resilience are often used interchangeably in boardroom conversations. However, they are three distinct disciplines. Each carries its own risk if organisations leave it unaddressed. Organisations that conflate the three are frequently the ones caught out when ransomware strikes.