Welcome — and why this site exists
What this site is, the thesis behind it, and the four kinds of pieces you'll find here.
This site documents one thesis: the BA/SA role as a separate function is on a 5-7 year clock.
Product managers will absorb most of it. AI agents will absorb the rest. I’ve worked as a business and system analyst for 14 years across retail (Metro, MediaMarkt, Leroy Merlin), banking (Alfa-Bank), and a stretch in iGaming. I’ve watched specifications I once wrote by hand get drafted by AI agents inside an hour. I’ve watched product managers absorb requirements work that used to need a dedicated BA. The change is happening, and it’s not abnormal — roles dissolve. DBAs became SREs. Webmasters became frontend engineers. The shape changes, the craft survives in different hands.
I document the transition along four pillars.
- The Shift — observations on how the role is changing. Job listing data. Org chart shifts. Predictions with timeframes, not vibes. The SA System Design Cycle documents one specific shift in long form: senior BAs now design systems.
- Proof — concrete AI experiments on real BA/SA work. Methodology, results, null findings. The Lab is where most of the experiments live.
- Craft That Endures — the part that doesn’t automate. System thinking. Integration design. Judgment calls.
- Career Navigation — practical guidance for peers in the same transition. What to learn now, where to pivot, what the market is signalling.
Long-form pieces typically land here first. Shorter notes and observations go to LinkedIn. The Medium cycle continues at medium.com/@alekseywzor.
If the transition this site documents matters to you and you want to discuss it — the channels are the channels.