Software

Sequent Editorial · 4 November 2026

Before you modernise: five questions to ask about your application estate

Application modernisation begins with understanding what each system does and why it matters.

  1. Which business processes depend on it?
  2. What creates the greatest difficulty: cost, reliability, usability or the speed of change?
  3. Which systems and data sources are connected to it?
  4. What does the business expect to change over the coming years?
  5. Who will operate the application after modernisation?

The answers help distinguish between applications that need replacement, targeted improvement, integration or continued maintenance.

A useful roadmap connects technical work with business priorities and operational realities. It also makes dependencies visible before implementation begins.

Data & AI

Sequent Editorial · 21 October 2026

Finding a practical starting point for enterprise AI

An effective AI initiative starts with a defined task.

Identify where people spend time interpreting information, searching for knowledge or preparing routine outputs. Then assess whether the relevant information is available, suitable for use and governed by appropriate access controls.

Begin with a limited pilot. Establish how outputs will be reviewed and how usefulness will be measured. Consider errors, exceptions, running costs and the support the solution will need.

A successful experiment provides evidence for the next decision. That may mean expanding the solution, changing its design or choosing a different approach.

Cloud

Sequent Editorial · 7 October 2026

Cloud migration is also an operating-model decision

Moving workloads changes more than their location.

Organisations need to decide who manages access, monitors performance, reviews costs and responds to incidents. Application dependencies, recovery requirements and internal skills also influence the migration plan.

Establishing these responsibilities early makes the transition easier to manage. It helps teams understand the environment they are building and what will be required to operate it.

Cloud adoption works best when architecture, delivery and ongoing management are planned together.

Experience

Sequent Editorial · 16 September 2026

Why customer experience needs operational design

A digital interface is only one part of a customer’s experience.

Behind a simple request may sit several teams, approval steps and business systems. If these remain disconnected, a redesigned website or application may leave the underlying problem unresolved.

Journey mapping should therefore examine both the customer’s actions and the organisation’s response.

  • Where does information move?
  • Who makes decisions?
  • What causes delays?
  • How are exceptions handled?

Connecting these questions to product design helps organisations improve the complete service.

What comes next for your business?