If you want a smart factory, start by getting comfortable asking dumb questions.
Not “dumb” like careless. Dumb like simple. The kind of question you might avoid because you think you should already know the answer.
After years working across plants, labs, and production lines, one pattern keeps repeating. The biggest breakthroughs rarely start with advanced tech. They start with someone asking, “Why do we do it this way?” or “What problem are we actually solving?”
That sounds basic. It is. It is also where most projects go wrong.
Why Dumb Questions Matter More Than Technology
When you walk into a plant, everything has a story. Every spreadsheet, every SCADA screen, every workaround.
The problem is. Most of those stories are no longer questioned.
People are busy. The line must keep running. And over time, assumptions turn into “truth.”
Asking simple questions does two things:
- It exposes hidden assumptions.
- It gives others permission to question things that don’t make sense.
That is usually the real start of transformation. Not the solution. Not the architecture. The conversation.
The Questions That Actually Save IIoT Projects
Over time, I started treating a few “dumb questions” like a checklist. They sound obvious. They save months.
1) What problem are we actually solving?
This is where most teams think they are aligned. They are not.
Example:
“We need real-time data.”
For what?
- Reduce downtime?
- Improve batch release?
- Remove manual logbooks?
- Feed analytics?
- Support compliance?
These are different problems. They need different data, different latency, different validation.
If you cannot explain the problem in one sentence that both a technician and QA understand, you are not ready to build anything.
2) What is the source of truth?
In manufacturing, there is never just one truth.
- The PLC says the pump is running.
- The SCADA shows it running.
- The historian trend confirms it.
- The operator says it stopped 10 minutes ago.
- The work order says it is under repair.
Which one wins. When. And why.
This becomes critical when you build OEE, dashboards, genealogy, or automated alerts.
A simple rule that works in practice:
- Control truth stays in control systems.
- Operational truth lives in MES or workflows.
- Analytical truth needs lineage and explanation.
If you skip this, you build a solution that moves data well but nobody trusts.
3) Who will use this on a bad day?
Most demos happen on good days.
Real manufacturing happens on bad days.
Ask:
- Who is on call at 2:00 AM?
- What happens when the network is unstable?
- What if a sensor is stuck?
- What about changeover, cleaning, or manual mode?
- What about audit week?
If the system only works when everything is perfect, it is not a real solution. It is a demo.
4) What is the smallest useful slice?
Here is an opinion.
Big-bang “enterprise solutions” fail more often than people admit. Not because of the technology. Because value comes too late.
A better approach:
- One line.
- A few critical assets.
- A small set of meaningful data points.
- One workflow that removes manual effort.
Then you scale the pattern. Not the slides.
5) What can we safely ignore?
Every plant has thousands of signals.
Most are not needed for the first outcome.
If you ingest everything “just in case,” you pay in cost, complexity, and troubleshooting.
A better question:
“What is the minimum data needed to explain a stop, slowdown, or quality issue without guessing?”
That set is usually much smaller than people expect.
6) What does “done” look like?
Not “go live.” Not “solution deployed.”
Done means measurable outcomes:
- Troubleshooting is faster.
- Manual work is reduced.
- Batch traceability is quicker.
- Data is consistent across sites.
If there is no clear before and after, the work will drift.
Why These Questions Feel Uncomfortable
People do not like basic questions.
- They feel exposed.
- They think they should know the answer.
- They are proud of their expertise.
But if you stay curious and respectful, something interesting happens.
Someone eventually says, “Actually, I was wondering the same thing.”
That is when progress starts.
Final Thought
Smart manufacturing is not magic. It is discipline.
- Discipline to define problems clearly.
- Discipline to agree on truth.
- Discipline to start small.
- Discipline to ignore what does not matter.
Technology helps. A lot.
But if you skip the basics, you will automate confusion and digitize waste.
If you feel awkward asking simple questions in a room full of experts, that is normal.
It still happens to me.
But the plants that move forward are the ones where someone is willing to say:
“Can we pause for a minute. What are we actually trying to do here.”
Leave a Comment