• 7 min read •By Tiago Marques

AI Rumination: How Overthinking with LLMs Steals Brain Power and Decision Quality

Note: “AI rumination” is not a formally recognized construct in clinical psychology or psychiatry. Here, the term is used informally to describe a pattern of rumination and reassurance-seeking that can be amplified by AI-generated output. It is not a diagnostic label.

Why I Call It AI Rumination

There’s a familiar mental pattern where a thought doesn’t resolve. You go over it again, slightly differently each time, expecting that the next pass will unlock something new.

In psychology, this is called rumination: a repetitive, difficult-to-disengage form of thinking that doesn’t converge on an outcome.

Large language models interact with this pattern in a particular way. They don’t close the loop—they expand it. Every prompt generates more plausible explanations and angles that feel like progress without actually resolving anything. The result is a feedback loop that increases cognitive load and prolongs indecision.

I am not naming AI rumination as a clinical category, but rather as a shorthand for a pattern that becomes easier to understand once you’ve experienced it.

When the Loop Took Over

The Bandmate

A former bandmate stopped appearing at rehearsals for months—no explanation, no messages, just silence.

I kept replaying past conversations, trying to figure out what had gone wrong. The question became a loop: “What did I do wrong? Nothing, right?” Instead of letting the uncertainty sit, I kept feeding it into an AI chatbot, looking for reassurance that I hadn’t missed something obvious.

When I finally confronted him, the response was abrupt. I ended the band and cut ties on the spot. The lack of communication had felt like the central issue, and in the moment, I felt justified in reacting strongly.

With distance, though, I can see how much rumination had amplified the intensity of my response. There was no clear alignment between that reaction and any rational or strategic goal for preserving the three years we had invested in the band.

Later, I learned he had been planning to leave town and simply hadn’t communicated it. With that context, my reaction feels disproportionate in hindsight. The band could likely have continued with a replacement, and the friendship might have been preserved. People move on from projects all the time.

The Architecture Decision

In a previous team, I respectfuly disagreed with the engineering manager about a core data modeling approach, that would shape years of data pipelines and reports to come.

I had (and still have) a strong belief that the Ralph Kimball methodology represents one of the most robust approaches to data warehousing. With that framing, I turned to an LLM and asked it to take on the role of a “grumpy Kimball purist” and argue against the alternative.

It did exactly that. The argument was clean, confident, and hard to refute. I revisited it multiple times, refining prompts and strengthening the case. I reinforced my prior knowledge of Kimball practices, and my assumptions that it was the absolute best fit.

What I didn’t account for in AI prompting were the surrounding constraints: the team’s skill set, management direction, and my colleague’s experience managing different systems and tools. The solution that moved forward wasn’t what I would have chosen. It wasn’t theoretically optimal, but it was good enough to meet most of the company’s reporting needs.

There’s also a structural reality in team environments: not every decision is yours to make. Influence has boundaries. If you’re not part of the final decision-making process, responsibility doesn’t fully sit with you either. That doesn’t mean disengaging or withholding input. It means recognizing where your role ends. If things don’t work out, your understanding doesn’t disappear, but neither does the distribution of accountability.

Looking back, the issue was that I used AI to ruminate on a position that had already formed, rather than to test its limits or understand the trade-offs more fully, and I ended up wasting time in the process. I lost count of how many times I revisited the approach, repeatedly stress-testing it in my head and with prompts, even guesstimating the amount of money potentially wasted on storage and compute.

In this particular case, the worst outcome of my rumination was definitely cynicism. I found myself internally expecting the alternative to fail, as if that would validate my original view or prove my worth. In that frame, it becomes easy to mentally split approaches into “how we do things here” versus “the right way”, even when reality is more constrained and less absolute.

Seeing the Loop in Action

The mechanisms behind it are well understood and some individuals may be more prone than others.

  • Intolerance of uncertainty: ambiguity is uncomfortable, so the mind keeps searching for resolution
  • Reassurance-seeking: asking for confirmation even when no new information is available
  • Cognitive biases: especially confirmation bias and the illusion of explanatory depth
  • Metacognitive beliefs: the assumption that continued analysis will eventually produce certainty

With AI, most questions return an answer that is coherent, structured, and convincing. Over time, it becomes harder to recognize when you’re actually learning versus just circling the same idea from different angles.

You spend more time reviewing generated arguments than moving forward. Decisions stretch longer than they should. Confidence starts to come from how persuasive an answer sounds, rather than how well it reflects reality.

When nothing feels resolved, the instinct is to try again: rephrase the prompt, explore another angle, generate a stronger argument. The loop repeats.

That pattern doesn’t always stay contained. It can show up in team discussions as well—bringing increasingly refined questions or critiques about decisions that have already been explored. The intention is usually to improve outcomes, but the effect is often different. When repeated without new information or clear alternatives, constant questioning tends to create friction without changing direction. Conversations slow down, alignment becomes harder, and the signal-to-noise ratio drops.

Over time, this can start to affect trust. What feels like careful analysis on one side can be experienced as churn on the other. Teams may become less responsive, not necessarily because the questions are invalid, but because they don’t appear to lead anywhere actionable.

Reflection vs. Rumination

Not all repeated thinking is a problem.

Reflection is usually anchored to something: evidence, a decision, a next step. It tends to move toward closure.

Rumination feels different. It repeats without resolving. The question shifts slightly each time, but the underlying uncertainty stays intact.

The system tends to align with the framing you give it. Not perfectly, but enough that it reinforces the direction you’re already leaning toward.

This is functionally similar to reassurance loops seen in anxiety-related patterns. The act of asking provides temporary relief, but it doesn’t resolve the underlying uncertainty.

The important distinction is that this is a behavioral pattern, not a clinical condition. The similarity is structural, not diagnostic.

Interrupting the Loop

In practice, a few things tend to help:

  • Deciding in advance how long you’ll explore a question before acting
  • Writing down what would actually change your mind before asking the model
  • Bringing another person into the conversation, especially when you notice you’re looking for agreement rather than information

The shift is subtle but important: from generating more interpretations to testing reality.

On Adversarial Prompting

Using AI to explore worst-case scenarios can be useful in a controlled context.

But when used as a personal check, it tends to amplify negativity, giving disproportionate weight to unlikely negative outcomes.

Over time, that can skew perception in a way that reinforces the loop rather than breaking it.

Where AI Actually Helps

None of this means AI-driven iteration is inherently problematic.

Used well, it can:

  • expand the solution space
  • accelerate learning
  • generate hypotheses that can be tested

When It Becomes a Problem

There isn’t a clean boundary, but certain signals tend to show up together:

  • You keep revisiting the same question without getting closer to a decision
  • The process increases tension instead of reducing it
  • You delay acting because you feel like you’re “almost there”

At that point, the issue is usually difficulty tolerating the uncertainty that remains.

Like most cognitive patterns, this one is easier to recognize in hindsight than in the moment.

Parting Thought

AI reflects what you bring into it. When used deliberately, it can sharpen thinking. When used to resolve uncertainty that can’t be resolved through more analysis, it tends to do the opposite.

Recognizing that difference is less about discipline and more about awareness. Once you see the rumination pattern, it becomes easier to step out of it.

Tiago Marques
Written by

Tiago Marques

Principal Data Analytics Engineer specializing in cloud data platforms, Databricks, Kimball dimensional modeling, and reliable BI architectures.