Articles & Observations
Documenting the evolution of the technical analyst. Systemic thinking, architectural blueprints, and career strategy for the modern BSA / SA practitioner.
Selected Case Studies
Axioma — documentation-first transformation
Built product architecture from scratch and formalized requirements engineering. Result: 6× lower defect rate, 2× faster feature delivery, +5% uptime.
Metro — Siebel CRM loyalty rollout across 15 stores
Siebel CRM loyalty rollout: 15 stores, 50,000 B2B users, 150+ change requests, 900+ employees trained, phased go-live.
Alfa-Bank — high-load call-center integration
30+ APIs integrating call-center to core banking (voice + chat). Serving 40M+ customers and 7,000+ agents across 5+ regions.
Latest Articles
-
Why I am writing acceptance criteria four times for the same agent
Gartner predicts 40% of enterprise AI agents will be demoted by 2027. Why I now write acceptance criteria four times for the same agent — one stack per autonomy level.
shift READ ARTICLE → -
The Old Analyst Wrote Reports. The New Analyst Writes Instructions.
AI didn't replace analysts. It replaced what analysts produce. The cognitive work is the same. The artifact is different — and that changes hiring.
shift READ ARTICLE → -
Problem Framing: Clients Don't Know What They're Asking For. The SA's Job Is to Surface It.
Stage 1 of the SA System Design Cycle. The work most analysts skip — and what it costs when an electronics retailer asks Axioma to 'just build e-commerce'.
shift READ ARTICLE → -
The next spec I write has to allow the agent to be wrong
When the system you are specifying can be wrong on purpose, the old acceptance-criteria discipline breaks. Six rough spec classes I now use.
craft READ ARTICLE → -
WebMCP and the e-commerce spec I am not sure I know how to write
Google slipped WebMCP into the Chrome roadmap on Tuesday. The audience for integration specs shifted from a human developer to an agent, and most of what I know how to write goes to the wrong place.
shift READ ARTICLE → -
Discovery: Ask Questions Before You Do Anything
Part 2 of the SA System Design Cycle. Five categories of questions before any architecture, four meta-questions before those, and the antipattern of trusting a verbal answer that nobody verified.
shift READ ARTICLE → -
I Lost Two System Design Interviews in Two Weeks. Here's the Cycle Built From What I Got Wrong.
A four-month cycle on system design, written for analysts who are watching the senior BA role shift under their feet. Eight publications, one OMS case, every two weeks.
shift READ ARTICLE → -
From Requirements Writer to Process Automation Driver
What the Senior BA role actually means in 2026. A few months ago I was helping someone prepare for a Senior BA interview. The job description tells you the role has already moved — most analysts haven't.
shift READ ARTICLE → -
Welcome — and why this site exists
What this site is, the thesis behind it, and the four kinds of pieces you'll find here.
meta READ ARTICLE →