Guides
Blueprints we actually use on engagements — diagnostic agendas, architecture checklists and cost models. No email wall.
Browse guidesInsights
Field notes, not thought leadership
Written by the people doing the delivery, usually because something went wrong and we worked out why. Guides, teardowns, recorded sessions and a glossary that avoids vendor language.
MWRKJT
Delivery leads online — talk to a human, not a botMonthlyThe Signal newsletter
PractitionerWritten
NoGated PDFs
Latest
Recent writing
Playbook
The six-week AI use case: how to pick one that survives contact with production
Most pilots fail on selection, not engineering. A checklist for choosing the first one.
Read Field noteWhy the semantic layer is the cheapest governance you will ever buy
Agreeing what revenue means costs a fortnight. Not agreeing costs a headcount a year.
Read TeardownWhat actually breaks when a mid-market team moves to a lakehouse
Five failure modes we have hit, and what we would do differently on each.
Read GuideA pricing model for data platform cost that finance will accept
How to attribute warehouse spend to a team, a product and a decision.
Read Field noteRetrieval quality is the whole game in RAG
Model choice matters far less than chunking, metadata and evaluation.
Read PlaybookRunning a two-week data diagnostic that produces a decision
The agenda, the interviews and the deliverable we use on every engagement.
ReadAlso here
Guides, sessions and a glossary
Webinars
Recorded working sessions and architecture teardowns, run by delivery leads rather than marketing.
Watch sessionsGlossary
Plain-English definitions of the terms vendors use loosely — lakehouse, semantic layer, agentic, observability.
Open glossaryNext step
Prefer a conversation to a newsletter?
Thirty minutes with a delivery lead. Bring the problem you keep postponing.