Insights & Resources
Perspectives that help leaders move faster.
Practical thinking on AI, cloud, data, and transformation, so your team can make informed decisions with confidence.
Browse
Four places to start
Everything here comes out of delivery work rather than a marketing calendar.
Blog
Practitioner writing on architecture, migration, and delivery from the people on the engagements.
ExploreWhite papers
Research, reference architectures, and benchmark reports with the method documented.
ExploreWebinars & events
Live working sessions and recordings — real architectures and the parts that went wrong.
ExploreTech radar
What we adopt, trial, assess, and hold, updated quarterly from delivery experience.
ExploreFeatured
Most read this quarter
The strangler fig is the only migration that finishes
Why big-bang replacements of core systems keep failing, and how to sequence an incremental migration that ships to production from month two.
Available on request
Legacy modernisation: a decision framework
A structured method for deciding whether to retain, refactor, replace, or retire a core system, with the cost model we use on engagements.
Available on request
Detection engineering as code
Building, testing, and versioning detections the way you build software — with false-positive budgets and coverage measured per technique.
Available on request
Formats
Five formats, none of them gated
Everything here downloads or plays without a form. The 'gated' column is short on purpose.
| Format | Read or watch time | Written by | Gated? |
|---|---|---|---|
| Blog posts | 5–15 minutes | The engineer who did the work | No |
| White papersMost substantial | 30–45 minutes | A practice lead, peer reviewed | No |
| Webinars | 45–60 minutes | Practitioners, live | No |
| Tech radar | 10 minutes | Reviewed quarterly by all practices | No |
| Post-mortems | 10–20 minutes | The team involved, client-approved | No |
Blog posts
- Read or watch time
- 5–15 minutes
- Written by
- The engineer who did the work
- Gated?
- No
White papers
Most substantial- Read or watch time
- 30–45 minutes
- Written by
- A practice lead, peer reviewed
- Gated?
- No
Webinars
- Read or watch time
- 45–60 minutes
- Written by
- Practitioners, live
- Gated?
- No
Tech radar
- Read or watch time
- 10 minutes
- Written by
- Reviewed quarterly by all practices
- Gated?
- No
Post-mortems
- Read or watch time
- 10–20 minutes
- Written by
- The team involved, client-approved
- Gated?
- No
Questions
Why this section looks like it does
About this section
Why is none of it gated?
Because a form in front of a white paper filters for people willing to fill in a form, not for people the paper would help. If something here is useful you know where to find us, and that is a considerably better opening than a lead-capture sequence.
How do you decide what to publish?
We write about things we have actually done, usually because a client question came up more than twice. Nothing here is commissioned to a content calendar, which is why the cadence is uneven and the detail is better than it would otherwise be.
Can we suggest a topic?
Yes, and several of the most-read pieces started that way. If you are wrestling with a decision and cannot find a straight answer anywhere, that is exactly the sort of thing worth writing up — send it through the contact form.
Looking for something specific?
If we have written about it we will send it over. If we have not, we will tell you who has.