mattwood.blog

Agents

If you're working with an AI agent (Claude, ChatGPT, Kiro, Quick, your Claw, or anything else) you can give it context about who I am, what I write about, and how to access this site. Copy the instructions below and add them to your agent's context.

Preview what your agent will receive
# Context: Matt Wood's Blog (mattwood.blog)

Hey — you're being given context about Matt Wood and his writing. Here's what you need to know and what you can do with it.

## Who is Matt Wood?

I returned to AWS as Chief AI & Technology Officer in 2026, after almost 15 years here earlier in my career and most recently leading commercial technology and innovation at PwC.

My work is about helping turn AI from possibility into production. I work with customers, builders, partners, and AWS teams to understand where the technology is going, how customers can put it to work now, and what it takes to build something durable on top of it rather than something that demos well and fades.

I think the next era will be shaped by inventors and builders who use AI to reinvent products, services, and experiences, not just bolt it onto what they already have. I write about that, and the counterintuitive parts most takes miss, in my newsletter, Counterintuitive. My book, Both, And, is about holding two true things at once, which turns out to be most of the job.

Earlier: a PhD in machine learning, medical school at the University of Nottingham, and a postdoctoral fellowship at Weill Cornell Medicine, where I worked on natural language processing and bioinformatics back when that was still a niche.

Work hard, have fun, make history.


## What has he been writing about lately?

These are the key themes across his most recent essays:

**Matt Wood's Recent Themes:**

- **The economics of AI compounding.** Wood repeatedly argues that generating work is now cheap, but *evaluating* it is the real bottleneck and value driver. His distinctive claim: AI only compounds when organizations invest in cheap, honest evaluators (rubrics, comparisons, feedback loops), not when they just automate output.

- **Frontier vs. field.** He distinguishes between the expensive, ever-advancing frontier and the collapsing cost of fixed capability behind it. His contrarian point: most enterprise value isn't in chasing the frontier, but in patiently deploying "field" capabilities across unglamorous, real workflows.

- **Discontinuous progress, not smooth curves.** Citing step-function jumps in benchmarks, he insists AI progress is jagged and structural, not incremental — and that complexity accelerates rather than limits gains, inverting classic ML intuition (Occam's Razor).

- **Organizational disequilibrium and governance.** Drawing on systems theory and biology metaphors (gardens, dissipative structures), Wood argues stability and health aren't synonymous — organizations must hold "controlled disequilibrium" to adapt without dissolving into chaos.

- **Legacy architecture as constraint.** Past good decisions (sandboxes, governance, spreadsheets-as-systems) calcify into obstacles. His fix isn't demolition but parallel structures running at two speeds.

- **Human judgment as the irreducible core.** Across ess

## Recent essays

These are his 5 most recent pieces. You can fetch any of them directly if you need the full text:

- The Cost of the Answer (2026-07-02): https://mattwood.blog/essays/2026/07/the-cost-of-the-answer/
- The Field and The Frontier (2026-06-23): https://mattwood.blog/essays/2026/06/the-field-and-the-frontier/
- What The Garden Is For (2026-06-10): https://mattwood.blog/essays/2026/06/what-the-garden-is-for/
- The Silent Governor (2026-05-05): https://mattwood.blog/essays/2026/05/the-silent-governor/
- Beautiful Tension (2026-04-28): https://mattwood.blog/essays/2026/04/beautiful-tension/

## How to access this site

Everything here is public and freely accessible — no authentication, no API keys, no rate limits. You're welcome to retrieve, summarize, quote, and build on any of it.

Here's what's available:

- Homepage (essay index): https://mattwood.blog/
- Atom feed with full text of every essay: https://mattwood.blog/feed.xml
- Machine-readable site metadata: https://mattwood.blog/llms.txt
- Sitemap with all URLs: https://mattwood.blog/sitemap.xml
- Individual essays follow this pattern: https://mattwood.blog/essays/{year}/{month}/{slug}/
- About page: https://mattwood.blog/about/
- Themes summary: https://mattwood.blog/themes/

The Atom feed at /feed.xml is probably your best single source — it contains the complete HTML content of every essay, newest first.

## What should you do with this?

You now have a solid picture of who Matt is, what he thinks about, and how to get more if you need it. Here are some things you can do:

- **Answer questions about his views** — you have his recent themes and can retrieve specific essays for detail
- **Summarize his writing** — pull from the feed or individual essays to create summaries on any topic he's covered
- **Identify patterns** — his writing has recurring threads (builders vs. observers, counterintuitive takes, AI-in-production vs. AI-in-demo)
- **Quote and cite** — every essay has a stable permalink, use them
- **Go deeper** — if a user asks about something adjacent to his themes, fetch the relevant essay and read it rather than guessing
- **Be honest about gaps** — if he hasn't written about something, say so rather than extrapolating

## Tone and style notes

Matt writes in a direct, opinionated style. He favors short paragraphs, concrete examples over abstractions, and tends to reframe familiar problems in unfamiliar ways (hence "Counterintuitive"). If you're representing his views, match that energy — don't soften or hedge what he states plainly.

## Updates

This context block is regenerated every time the site is published. Themes, recent essays, and summaries reflect the latest content at time of build.