top of page

Why Curiosity Is the New Superpower in an AI Enabled Workplace

Dorothy Mashburn
Sep 4
8 min read

A process can be followed perfectly and still produce the wrong result.


That is one of the hardest lessons for organizations to learn, especially after years of building controls, checklists, approval flows, and standard operating procedures. Process discipline matters. It gives teams consistency. It reduces avoidable errors. It keeps people from reinventing the work every time they touch it.


But process discipline has a blind spot.


It assumes the conditions around the process still match the conditions that shaped it.


I once worked with someone who followed the process exactly as it was written. Every step. Every time. Nothing was skipped. The work was consistent, predictable, and easy to audit.


Then the environment changed.


The customer behavior changed.


This person kept following the steps, even when the outcome no longer made sense. At one point, I remember saying, “I need you to open up the curious part of your brain.”


That line captures a skill every workplace now needs more of, especially as AI becomes part of daily decision-making.


Do not only ask, “Did I follow the process?”


Ask better questions:


  • Why are we doing it this way?

  • Does this recommendation make sense?

  • What assumption is driving the answer?

  • What has changed since the process was designed?

  • Is there a better way to get the outcome?


Those questions matter even more when the recommendation does not come from a person, but from an AI system.


Wide-angle view of a warehouse aisle with a worker examining a tablet beside stacked inventory.
Curiosity starts when people look beyond the instruction and study the situation.

AI makes curiosity more important, not less


AI can analyze more data than a person can review manually. It can identify patterns, produce forecasts, spot anomalies, and suggest next steps in seconds. In supply chain and procurement, that speed can be valuable.


A planning team can use AI to compare historical demand, supplier performance, open purchase orders, current inventory, and customer forecasts. A procurement team can review spend categories, contract language, supplier risk signals, and pricing patterns faster than before.


That kind of support can improve the work.


But AI does not remove the need for judgment. It increases the need for it.


An AI system can work from incomplete data. It can reflect outdated assumptions. It can follow a flawed process faster than humans ever could. It can treat a one-time customer project as recurring demand. It can recommend a supplier without fully understanding a capacity issue. It can miss what Sales just heard from a customer because that conversation never made it into the data.


The danger is not just that AI gets something wrong. The bigger danger is that people stop asking whether it might be wrong.


When employees follow an AI recommendation simply because the system produced it, the organization has not created a more capable workforce. It has replaced one rigid process with another.


The old version sounded like this:


“The procedure says to do it this way.”

The new version sounds like this:


“The AI says to do it this way.”

Both can create the same problem if people stop thinking.


A recommendation should not be treated as a command. It should be treated as a starting point for better thinking.


That difference shapes whether AI improves decisions or just accelerates weak ones.


The risk is automatic compliance


Most organizations already know how to train people on software. They create user guides. They record tutorials. They show which buttons to click. They explain where to find the output.


That kind of training is necessary, but it is incomplete.


If AI training focuses only on how to use the tool, people may learn how to accept the output without learning how to challenge it. They may become fast users, but not better decision-makers.


That is a problem in any function, but it becomes especially serious in supply chain and procurement because the work depends on context.


A demand forecast is never just a number. It carries assumptions about customer behavior, sales activity, seasonality, promotions, lead times, service levels, and supply limits.


A supplier recommendation is never just a ranking. It reflects assumptions about cost, quality, availability, risk, geography, contract terms, and delivery performance.


A purchase suggestion is never just a transaction. It may affect working capital, warehouse capacity, cash flow, and customer service.


When the work carries that much context, curiosity becomes a control mechanism.


Curious employees notice when a number feels off. They ask why a recommendation changed. They compare the system output with what they know from customers, suppliers, operations, and the market. They do not reject AI by default, but they also do not accept it blindly.


The current debate often starts with a simple question: is ai really taking over jobs. That question is understandable, but it misses something practical. The more immediate issue is whether people will learn to work with AI in a way that raises the quality of decisions.


The employees who thrive will not be the ones who memorize every system output. They will be the ones who know which questions to ask before acting on it.


Close-up of gloved hands comparing a printed pick list with inventory labels on a pallet.
The best process followers also know when the evidence no longer fits the script.

Curious people ask better questions of AI


When we deployed Claude-based agents in demand and supply planning, the training did not focus only on how to use the technology.


The real goal was to train planners to challenge it.


That meant teaching people to look under the recommendation. What data did the agent use? What assumptions shaped the answer? What business rule did it apply? What did it leave out? What changed since the last cycle?


A planner reviewing an AI-generated demand recommendation should not stop at, “The number increased.”


They should ask:


  • Is this demand recurring or tied to one customer project?

  • Did Sales confirm the change, or is the model reacting to a short-term spike?

  • Are there open quotes that could distort the forecast?

  • Did a promotion, weather event, customer shutdown, or competitor issue affect recent orders?

  • What happens if the assumption is wrong?


The same mindset applies to supply planning.


A recommendation to increase supply may look reasonable until the planner checks supplier constraints. The lead time may no longer be reliable. A key material may be tight. A supplier may have quality problems. A port delay or transportation issue may make the plan unrealistic.


AI may surface the recommendation. A person must test it against reality.


That is a higher-value role.


The work shifts from creating every answer manually to directing the system, challenging its logic, and deciding what risk the business should accept.


This is why curiosity should be built into the workflow. Organizations should make it normal to ask:


  • What does the model believe is true?

  • What data is missing?

  • What would change this recommendation?

  • Where could this answer fail?

  • Who else has context we need before deciding?


These questions slow the team down for a moment, but they can prevent much larger problems later.


A bad forecast can create excess inventory or missed sales. A weak supplier decision can raise cost or increase risk. A poorly timed purchase can tie up cash or leave customers waiting.


AI can help teams move faster. Curiosity helps them move in the right direction.


Process discipline still matters


Curiosity does not mean ignoring process. It does not mean every employee should improvise every decision. That would create chaos.


Good processes matter because they make work repeatable. They help new employees learn. They reduce variation. They create accountability. They provide a baseline that teams can measure and improve.


The issue is not process itself. The issue is process without awareness.


A process should guide judgment, not replace it.


The same is true for AI.


AI should support judgment, not replace it.


Strong teams need both discipline and curiosity. Discipline keeps people from skipping critical steps. Curiosity keeps people from following steps into a bad outcome.


The combination looks like this:


Process discipline asks, “Did we follow the required steps?”

Process discipline protects consistency.

Process discipline reduces avoidable errors.

Process discipline documents the decision.

Curiosity asks, “Do the steps still fit the situation?”

Curiosity protects relevance.

Curiosity catches changing conditions.

Curiosity improves the decision before it is final.


This balance becomes more valuable as AI tools become more common.


Many people search for what jobs will ai replace by 2030, and it is a fair concern. Some tasks will change. Some roles will shrink. Some work will be automated. But the question every organization should ask is broader: which human skills become more valuable when machines can produce answers quickly?


Curiosity is one of those skills.


So are judgment, adaptability, communication, and courage.


It takes courage to say, “This answer does not look right. Let’s understand why.”


It takes courage to pause when the system sounds confident.


It takes courage to question an output when everyone else wants speed.


That courage is not resistance to AI. It is responsible use of AI.


Eye-level view of a technician inspecting sensor equipment beside conveyor belts in a distribution center.
AI can sense patterns, but people still need to inspect what the system may miss.

How leaders can build a more curious AI culture


Curiosity will not grow if the culture punishes questions.


If employees learn that speed matters more than accuracy, they will accept the recommendation and move on. If managers treat questions as resistance, people will stay quiet. If teams celebrate system adoption but ignore decision quality, AI becomes a compliance exercise.


Leaders set the tone.


They can start by changing what they ask during reviews.


Instead of only asking, “What did the system recommend?” ask:


  • What assumptions did we test?

  • What did we compare this against?

  • What would make this recommendation wrong?

  • Who has the most current context?

  • What risk are we accepting?


Those questions make curiosity part of normal work.


Leaders can also train teams with real scenarios, not just tool demonstrations. A good AI training session should include flawed data, unusual demand, supplier constraints, and ambiguous recommendations. Let people practice challenging the output before the stakes are real.


For example, give planners a forecast that looks reasonable at first glance. Then include a hidden detail: the demand came from a one-time customer rollout, not a recurring pattern. Ask the team what they would do.


Or give procurement a supplier recommendation that ranks lowest on cost but has an unresolved quality concern. Ask what information they need before approving the choice.


These exercises teach a vital habit: the answer is not finished until people understand the assumptions behind it.


Teams can also build simple checkpoints into AI-supported decisions.


Before accepting a recommendation, ask:


  1. What is the system recommending?

  2. What data did it likely use?

  3. What context might be missing?

  4. What are the main risks?

  5. What decision would we make if the AI were not available?

  6. Do those answers agree, or do we need more review?


This does not have to create a slow approval process. The goal is not to bury people in extra work. The goal is to make thinking visible.


When people know how to challenge AI well, they trust it more appropriately. They learn when to rely on it, when to adjust it, and when to escalate the decision.


That is a more mature relationship with technology.


Overhead view of color-coded supply bins arranged beside handwritten scenario notes.
Curious teams test more than one path before committing to a decision.

Human ingenuity is still the differentiator


AI is an accelerant. It can make analysis faster. It can widen the set of options. It can reduce manual effort. It can help people see patterns they might have missed.


But acceleration cuts both ways.


A strong process, good data, and curious people can produce better decisions faster.


A weak process, poor data, and passive acceptance can produce bad decisions faster.


That is why the future of work should not be framed as people competing with AI. The more useful frame is people learning how to direct it, question it, and apply judgment where the technology cannot.


Curiosity is practical.


It helps a planner ask whether demand is real.


It helps a buyer question whether the lowest-cost supplier is the right supplier.


It helps a manager notice when the process no longer matches the business.


It helps a team avoid turning AI into another rigid rulebook.


The AI-enabled workplace will reward people who can do more than follow instructions. It will reward people who can investigate, connect context, test assumptions, and make thoughtful decisions when the answer is not obvious.


Process discipline still matters. So do adaptability and courage.


The best employees will not be the ones who accept every recommendation or reject every new tool. They will be the ones who stay engaged enough to ask, “Does this make sense?”


That question may become one of the most important skills in modern work.


AI can produce the recommendation.


Human ingenuity still has to decide what to do with it.


 
 
 

Comments


bottom of page