Enterprise Automation Services
Insights

Field notes from the edge of enterprise IT

Practical writing on automation, platform engineering, and the organisational shifts that make them stick.

Looking back: what you have built
/7 min read

Looking back: what you have built

A recap of the 6Ws methodology and how to keep using it: not as a one-off workshop, but as the quiet logic behind your planning, architecture, and delivery.

MethodologyReflectionProduct Thinking
The 6Ws in practice: a timesheet and expense app
/7 min read

The 6Ws in practice: a timesheet and expense app

A real-world walk-through of the 6Ws applied end to end: a timesheet and expense tracking application for a distributed consultancy.

MethodologyCase StudyDelivery
When: planning, estimation, and prioritisation
/7 min read

When: planning, estimation, and prioritisation

The When is where software planning meets project management. Time, effort, budget, and value, coordinated so delivery becomes predictable, visible, and measurable.

MethodologyDeliveryEstimation
Where: the hosting strategy
/7 min read

Where: the hosting strategy

Where defines how and where the software runs. Reliability, cost, scale, security, and developer experience all meet at this layer.

MethodologyDevOpsInfrastructure
How: technical design as a story
/7 min read

How: technical design as a story

A good How chapter reads like a guided tour. It introduces the actors, describes the conditions, and shows how each piece fits together so the reader trusts the system is going to work.

MethodologyArchitectureTechnical Design
Why: the business benefit
/7 min read

Why: the business benefit

If Who is the audience and What is the story, Why is the reason the story needs to be told. Without it, engineering becomes activity without impact.

MethodologyProduct StrategyROI
What: outcomes and actions
/7 min read

What: outcomes and actions

Once you know who the software is for, the next question is what they need to do with it. This is where ideas become stories and stories become working software.

MethodologyProduct ThinkingRequirements
Who: the actors and users of the system
/7 min read

Who: the actors and users of the system

Every system exists to serve someone. Skip the Who and you will ship features nobody asked for. Here is how to define it properly.

MethodologyProduct ThinkingUser Research
The 6Ws: a thinking scaffold for software that matters
/7 min read

The 6Ws: a thinking scaffold for software that matters

Before the sprint planning, before the architecture diagrams, before the estimates, six questions decide whether the software you're about to build is worth building at all.

MethodologySoftware StrategyProduct Thinking

Want this kind of thinking applied to your systems?

Our consultants bring the same rigour to client work as they do to the writing on this page.

Start a Conversation