From Requirements to Context: The New Role of the Analyst in the Era of AI-Driven Development

In a world where code is written “by vibe”, context is the only scarce resource. And the analyst is the one responsible for it.

Code has become inexpensive. LLMs generate services, APIs, and schemas faster than a team can align on terminology. Development increasingly happens “by vibe” — and at that moment, requirements stop protecting us from mistakes.

Projects fail not because of the code and not because of user stories. They fail because of incorrect context: blurred boundaries, mixed domains, inconsistent language, and unexamined assumptions. And this is the analyst’s direct area of responsibility.

In this talk, we will discuss vibe analytics — the ability to work with uncertainty, maintain a coherent domain model, and stop attractive but risky solutions proposed by AI. We will show why the analyst no longer “collects requirements”, but designs context: the boundaries, language, and assumptions within which a team can make decisions.

Code can be rewritten. A mistake in context cannot.