There is a particular kind of exhaustion that comes not from too much work, but from being structurally removed from work that you know matters.
A lot of business analysts are feeling that right now. And I want to name it clearly, because it is not being talked about enough.
Ideas are bypassing BAs entirely. A business leader has an idea, and instead of going through any kind of structured intake or analysis, they walk directly to a developer or a development team and say “can you build this?” The developer spins up an AI coding tool, and within days, sometimes hours, there is a working prototype. The BA never got a call. Nobody asked whether this was the right problem to solve, whether it aligned with strategic priorities, whether there were downstream impacts that needed to be analyzed. The build just started.
Or developers themselves are having the ideas. They see something AI could do, they build it, and they bring it to the business as a finished thing. Again, no BA in the loop. No intake. No analysis of whether the thing that was built was the thing that was needed.
The intake process, which has always been imperfect and often frustrating, is now in many organizations functionally broken. And BAs are sitting in this strange no-man’s land where they are still nominally responsible for ensuring good analysis happens on projects, but they are being structurally bypassed before they ever have the chance to do it.
That is exhausting in a specific way that is hard to describe to someone who has not experienced it. It is not the exhaustion of too many meetings or too much documentation. It is the exhaustion of irrelevance. Of watching things go wrong in predictable ways that you could have helped prevent, and having no entry point to do anything about it.
If that is where you are, I want you to know: this is real, it is not your fault, and there are things you can do about it.
Why Intake Is Breaking Down
Understanding why this is happening does not fix it, but it does help you respond more effectively than if you are just reacting to the frustration.
The primary driver is speed. AI tools have so dramatically compressed the time from idea to prototype that the traditional intake process, which was designed for a world where building was slow and expensive, now feels like an unreasonable tax on momentum. If a developer can have a working prototype in two days, a two-week intake and discovery process feels absurd to the business leaders and developers driving the work.
They are not wrong that the old intake process is too slow for the current environment. Where they are wrong is in concluding that no intake process is better than a slow one. Because what they are trading for speed is the quality of the problems they are solving. Ideas that skip intake often skip the questions that would reveal whether the idea is worth building, whether it is the highest priority, whether it will cause downstream problems, and whether there is a simpler solution that would achieve the same goal. Those questions do not become less important because building got faster. They become more important, because the cost of building the wrong thing at AI speed is higher than ever.
The second driver is a perception gap. Many business leaders and developers do not fully understand what happens during a good intake and analysis process, so they do not know what they are losing by skipping it. They see documentation and process. They do not see the problem clarification, the assumption surfacing, the stakeholder alignment, and the strategic prioritization that good intake produces. Making that value visible is partly a communication challenge and partly a demonstration challenge.
Tip 1: Create a Fast, Lightweight Intake Presence That Fits the New Speed
The worst response to intake being bypassed is to advocate for the intake process you used to have. That process is not coming back, and advocating for it positions you as an obstacle to the speed that the organization has decided it wants.
The right response is to create an intake presence that fits the current environment. Not a two-week discovery phase. A focused, fast, high-value touchpoint that can happen before or in the very early stages of a build, that takes an hour instead of a week, and that produces something immediately useful.
What does that look like in practice? It looks like a one-page problem brief: the problem statement, the evidence that supports prioritizing it, the connection to strategic goals, and the initial definition of what success looks like. It looks like a thirty-minute conversation with the business leader and the developer before the first line of code gets written, focused on three questions: what problem are we solving, how will we know it is solved, and what do we know about the constraints?
That is not a requirements phase. It is a lightweight analytical entry point. It takes almost no time compared to what it prevents. And it gives the BA something to orient the rest of the work against, even if the work is moving fast.
The key is making this a standing offer that is easy to say yes to. Not “we need to do proper intake before this moves forward,” which sounds like a brake. But “I can do a thirty-minute problem brief with you that will make the build faster and more likely to land right, when can we do that?” Different posture entirely.
Tip 2: Get Upstream by Building Relationships With the People Who Have Ideas
The structural problem with intake being bypassed is that the BA is not in the relationship where ideas originate. Ideas come from business leaders, business users, and developers. If BAs are not visible and present to those people before ideas become builds, they will keep getting bypassed.
The practical response is to invest in the relationships that put you upstream of where decisions are happening. Not in a political way, but in a genuine “I want to understand what you are working on and what you need” way.
Spend time with business leaders whose domains you support. Not just on active projects, but in regular conversations about what they are seeing, what problems they are trying to solve, and what opportunities they are thinking about. When you are present in those conversations regularly, you become a natural first call when an idea starts to form, rather than someone who gets looped in after the build has already started.
Do the same with developers. Understand what they are building, what AI tools they are using, and where they are running into questions about whether what they are building is aligned with what the business actually needs. Position yourself as a resource who can help answer those questions quickly, not as a process gatekeeper who needs to be notified and consulted before anything moves.
The goal is to become part of the natural flow of ideas-to-decisions, rather than an external process that flow has to pass through. That shift is relational before it is structural, and it starts with investing in the conversations that put you where ideas are forming.
Tip 3: Make the Cost of Skipping You Visible, Without Making It a Fight
The most sustainable solution to intake being bypassed is for the organization to recognize, from its own experience, that skipping the analysis step is expensive. That recognition does not happen automatically. It requires BAs to make the cost visible in a way that is factual and specific, not defensive.
When a project lands in trouble because nobody defined the problem clearly before building, document it. Not as a grievance, but as a case study. What was the cost of the rework? What was the impact on the team? What question, if it had been asked early, would have prevented it? Bring that information to the right people, framed as a learning, not as “I told you so.”
When you are called in late to validate something that has already been built, do the research: surface the gaps, quantify the risk, and name specifically what earlier involvement would have caught. That information, delivered consistently and without drama, builds an evidence base for why intake matters.
Over time, that evidence base changes the conversation from “intake is a process we follow” to “intake is how we avoid expensive mistakes.” That is a much more compelling argument, and it is one you build through demonstration rather than advocacy.
This takes patience. The first case study does not change minds. The third or fourth one starts to. The goal is to build a track record that makes the value of analytical involvement self-evident to the people who are currently bypassing it.
On the Burnout Itself
I want to come back to the emotional reality of this for a moment, because the practical tips are not enough on their own.
The burnout that comes from being structurally bypassed is real, and it deserves acknowledgment. It is demoralizing to be an expert in something and be repeatedly excluded from the conversations where that expertise would matter. It is exhausting to watch preventable problems happen and have no entry point to prevent them. It is discouraging to feel like your role is shrinking while the work you care about is accelerating.
If you are in that place, the most important thing to do first is name it clearly to yourself. This is not a personal failure. It is an organizational dysfunction, driven by speed, perception gaps, and structural patterns that are bigger than any individual BA. You did not cause it, and you cannot fix it alone.
What you can do is refuse to let it make you passive. The BAs who are navigating this moment best are the ones who are proactively building the relationships, the lightweight processes, and the evidence base that gradually change how they are seen and where they are involved. It is slow work. It is sometimes frustrating work. But it is available to you, starting with decisions you can make today.
You have not been left behind permanently. You are in a moment that requires a strategic response. And strategic responses, made consistently over time, change outcomes.
Get Equipped to Lead in a Fast-Moving Environment
My Maven course series is built for BAs who are navigating this exact moment: fast-moving AI-driven delivery, broken intake processes, and the challenge of staying relevant and valuable in an environment that was not designed with the BA role in mind.
You will get practical frameworks, real-world scenarios, and a community of peers working through the same challenges.
Visit www.maven.com/angela-wick to explore current courses and upcoming cohorts.
The intake process is broken. You can help fix it. Let us talk about how.