BLOG / ANALYSIS & METHODS

Technical subjects.
Answers you can decide on.

Content for executives, IT departments, product leads and the teams that build and operate their digital tools.

20 articles

Blog & analysis

Technical leadership and team gathered around a product trajectory
Teams & leadership

CTO, squad or expert reinforcement: which model should you choose?

Three ways of working together, three ways of splitting responsibility. How to pick the one that matches what you are actually missing.

Read the article ↗
Technical team coordinating a production incident response
Emergency & continuity

Production incident: what to prepare before you call

A short brief can save an hour on an incident. Here is what it contains — and what it must never contain.

Read the article ↗
Continuity architecture and recovery environment
Cloud & DevOps

RTO and RPO: asking the right business questions before the architecture

Two numbers decide your continuity architecture. They are defined with the business, not in an infrastructure spreadsheet.

Read the article ↗
Path connecting search, content and conversion
SEO & performance

Preparing a rebuild: the SEO decision checklist

Most traffic losses after a rebuild come from decisions taken too late. Here are the ones to settle during framing.

Read the article ↗
Operations dashboard measuring the impact of a service outage
Emergency & continuity

What does an hour of downtime really cost?

A simple calculation is enough to settle a continuity budget. You just have to count what matters, and only once.

Read the article ↗
Backup infrastructure and controlled restore environment
Cloud & DevOps

An untested restore does not exist

Backups all succeed, until the day you try to restore. What a drill reveals, and how to run one without risk.

Read the article ↗
Containerised architecture spread across several environments
Cloud & DevOps

Migrating to Kubernetes without stopping the business

A successful migration is invisible. It is prepared environment by environment, switched in stages, and always keeps a way back.

Read the article ↗
Existing system analysed then transformed into a modern architecture
Teams & leadership

Technical debt: measure it before raising it with management

Debt you cannot quantify stays a complaint. Translated into risk, delay and cost, it becomes a decision.

Read the article ↗
Match between a technical assignment and a screened expert
Teams & leadership

Hiring or bringing in an expert: what lead time really changes

Between a three-month hire and reinforcement within days, the difference is not only the calendar: it changes what you can hand over.

Read the article ↗
Private infrastructure dedicated to training and running AI models
AI & automation

Private AI: what “sovereign” means technically

The word covers four very different requirements. Telling them apart avoids paying for a constraint you do not have — or forgetting one that matters.

Read the article ↗
Chain connecting internal documents to a conversational assistant
AI & automation

RAG: why your answers are wrong, and how to fix it

When a document assistant gets things wrong, the model is rarely to blame. The problem almost always sits before it.

Read the article ↗
Business process combining automated processing and human validation
AI & automation

Automating a process: where humans must stay in the loop

Automating what is repetitive is easy. Deciding what stays validated by a person is the real design work.

Read the article ↗
Web performance measurement across a browsing journey
SEO & performance

Core Web Vitals: the three projects that actually move the needle

Many optimisations cost a lot and change nothing. Three projects concentrate most of the measurable gain.

Read the article ↗
Mapping plan between old and new addresses of a website
SEO & performance

URL migration: the redirect plan that avoids the collapse

Changing addresses is a routine and brutal operation. What makes it safe fits in four rules and one mapping file.

Read the article ↗
Business application connecting users, software components, APIs and data
Development

A fast website starts with less code

Before optimising loading, ask what needs to exist at all. Most pages ship an application in order to display text.

Read the article ↗
Technical team analysing an existing application estate
Development

Taking over an existing project: the ten entry checks

Before writing the first line, ten checks say whether the takeover is feasible, expensive, or impossible as things stand.

Read the article ↗
Diagram of exchanges between a business API and its partner integrations
Development

APIs: evolving without breaking your integrations

A published API is a contract. Evolving it takes fewer versions than discipline about what is guaranteed.

Read the article ↗
Security team analysing a compromise before remediation
Security

Incident response: collect the evidence before cleaning up

Cleaning a compromised server without looking for the entry point guarantees a repeat. The order of the steps matters more than their speed.

Read the article ↗
Server infrastructure protected by network filtering and a reverse proxy
Security

Hardening an exposed server: the minimal list that changes everything

Reducing the exposed surface costs little and removes most attempts. Six measures, in order, and one frequent trap.

Read the article ↗
Paid acquisition setup and conversion tracking
Acquisition

Paid search: connecting media budget to genuinely useful enquiries

An ad account optimised on the wrong conversions spends efficiently for a useless result.

Read the article ↗
Analyses drawn from our assignments. They describe methods and trade-offs, never an identifiable client.

Let’s talk about what is blocking you.

An emergency, a profile to find or a project to structure: let’s start with your need.

Talk to RGAIX