KHAKSAHamidreza Khaksa
If AI Stopped Tomorrow, Could Your Organization

If AI Stopped Tomorrow, Could Your Organization

The article is based on a personal experience where an AI assistant failed to produce a useful business-case document, forcing the author to return to older files and rely on skills that had once been routine. That experience raised an important question: Are we simply using AI, or are we slowly becoming dependent on it? The main concern is that frequent use of AI may gradually weaken practical skills such as writing, analysis, summarizing, problem solving, and recognizing mistakes. At an organizational level, this can become an operational risk if AI tools become unavailable, change in quality, become more expensive, or can no longer be used because of security or policy reasons. The article also highlights that organizational knowledge should not exist only inside prompts, chat histories, or personal AI workflows. Important knowledge should remain documented and owned by the organization. The key principle is simple: The human starts, AI helps, and the human finishes. The final message is: We should use AI to work better, not so much that we can no longer work without it.

# If AI Stopped Tomorrow, Could Your Organization Still Work?

About three weeks ago, I had to spend some time working on a business case.

As usual, the first thing I did was call on my personal assistant for finance and investment. I wrote what I thought was a pretty good prompt and expected to get a reasonably structured result, make a few changes, and move forward.

But this time, the result was different.

After a recent update in GPT Customs, the output was so scattered, inconsistent, and far from the structure I needed that it was almost impossible to use.

I changed the prompt several times, tried a different approach, and added more explanation to guide the system. Still, the result was not close enough to what I needed for a proper and professional file.

In the end, I had to go back to my old archive, find previous examples, review the structure again, and rebuild the final file myself. It took much more time than I expected.

The task itself was not the main issue. Years before these tools existed, we used to do the same work ourselves.

What really caught my attention was how I felt while doing it.

I realized that something that used to be a normal part of my skill set was now taking me more time than I expected without the help of AI. For some parts, I had to go back to older files to remember the right structure. And a few times, my first thought was:

**“Why can’t the assistant just do this part for me?”**

That was the point when I asked myself a serious question:

**Are we using AI, or are we slowly becoming dependent on it?**

My main takeaway from this experience was not simply that one version of a model had changed or become less useful.

The bigger issue was realizing that constant use of AI assistants can slowly weaken some of our practical skills without us noticing.

And maybe more importantly, it can create a level of dependence that is not always necessary.

This experience made me look at the subject more seriously.

Not because I am against AI. I still believe these tools are one of the biggest opportunities for improving productivity in organizations.

But I now look at them more from the point of view of keeping people and organizations able to work independently.

This article is really a summary of that experience.

## There is a very thin line between “getting help” and “becoming dependent”

There is nothing wrong with a professional using AI to improve a report.

In many cases, it is a very reasonable thing to do. I do the same myself.

I use AI for early analysis, structuring ideas, looking at different scenarios, rewriting, and sometimes finding points I may have missed.

All of that can be very useful.

But my recent experience showed me that the line between using AI and depending on it is much thinner than we may think.

At first, we use AI to improve a piece of text.

Then we use it to write the first draft.

Later, we ask it to build the whole structure of a report.

And after some time, we may find that doing the same task without AI has become harder and slower, even though it used to be part of our normal work.

This usually does not happen suddenly.

It happens slowly, almost without us noticing.

In one case, AI makes us more capable.

In the other, AI starts replacing part of our capability.

And I think that difference matters a lot.

## Today’s productivity should not reduce tomorrow’s ability

Of course managers welcome higher productivity. I use AI for the same reason.

If something that used to take two hours can now be done in thirty minutes, it makes no sense to ignore that benefit.

But my recent experience reminded me that speed is not the only thing we should measure.

We should also ask ourselves:

**What are we gaining, and what might we slowly be losing?**

If professionals stop doing their own analysis, if managers stop reading the full report because AI has already summarized it, and if every document, presentation, or report is handed over to an assistant, some of the skills we spent years building may slowly become weaker.

And this is not only about writing.

It can affect analysis, summarizing, reasoning, problem solving, spotting contradictions, and even recognizing a wrong answer.

I felt some of this myself while working on that business case.

The AI tool had not disappeared. It was still available.

But because the output was not useful, I suddenly had to rely again on skills that I had gradually handed over to the assistant over the past months.

## Personal dependence can become organizational dependence

The issue becomes more serious when the same thing happens not to one person, but across an organization.

Imagine a department that uses AI for a large part of its emails, reports, analysis, and documentation.

At first, this looks positive.

Work becomes faster. Workload is reduced. In some cases, the first version of the output may even look better.

But then we need to ask the same question at an organizational level:

**What happens if the tool no longer gives the same quality of output tomorrow?**

What if the service is unavailable?

What if the provider changes its policy?

What if the cost becomes much higher?

What if the organization has to stop using the tool because of security, legal, or internal policy reasons?

Can the work still continue?

If the answer is no, then we are no longer talking only about a productivity tool.

We are talking about operational dependence.

After this experience, I think one of the best exercises for managers is to ask a very simple question:

**If all AI tools became unavailable for one week, what would happen in your organization?**

Which activities would stop?

Which reports would no longer be prepared?

Which employees would struggle with normal tasks?

Which processes have no backup method?

And maybe the most important question:

**Which skills do we think we still have, but in reality, we have not used them for a long time?**

In my view, the answers to these questions show much more about real AI dependence than the number of AI users or the number of tools the organization has bought or developed.

## AI should not become the hidden memory of the organization

There is another issue that is slowly appearing in many organizations.

Employees are building their own prompts, methods, and personal chat histories for daily work.

Someone may know exactly what to ask an AI tool to produce a weekly report or a specific type of analysis.

That may be very efficient.

But there is an important question:

**Does the organization know this process too?**

If that person leaves tomorrow, does the knowledge stay?

Is the method documented somewhere?

Or does the knowledge only exist in that employee’s head and inside their AI chat history?

For years, organizations have talked about knowledge management, documentation, and reducing dependence on specific people.

Now we may need to add a new kind of dependence to that list:

**Dependence on AI assistants for organizational knowledge.**

My own experience also reminded me of something else.

Sometimes, because AI produces a fast and professional-looking answer, we naturally trust it more.

But a professional-looking answer is not always a correct answer.

If AI suggests a better way to write an email, the risk is usually limited.

But if it suggests which supplier to choose, whether an investment is good, how to read a contract, or how to judge an employee’s performance, the situation is different.

AI can suggest.

It can create different options.

It can show us things we may have missed.

But the responsibility for the final decision is still ours.

A manager or specialist should be able to explain why a decision was made.

## The model I am trying to return to

After this experience, I set a simple rule for myself:

**The human starts, AI helps, and the human finishes.**

Before asking AI, I should first understand the problem myself.

I should have a basic structure in mind.

I should know what kind of result I am looking for.

Then I can use AI for speed, ideas, analysis, review, or creating a first draft.

And in the end, I should go back, review the output myself, and make the final decision.

It may sound like a small difference, but I think it is an important one.

It shows whether AI is still our assistant, or whether we have slowly become the operator of AI.

**We should use AI to work better, not so much that we can no longer work without it.**
← All articles