Back to Blog
Lean & Execution

Stop Googling on the shopfloor: 10 practical ways to use an AI assistant instead

Julian Zur-Lienen||4 min read
Stop Googling on the shopfloor: 10 practical ways to use an AI assistant instead

You do not have time for ten tabs of search results. Operators do not either. Every minute spent hunting for answers is a minute the line stands still.

An AI assistant works better than search when you talk to it like a person who knows your context. The shift is small. The impact on flow is not.

Use these moves to speed up decisions without adding noise.

10 practical moves

  1. Ask full questions with context Write the whole problem. Include machine, material, constraints, and what you tried. Example: We run a vertical mill on 6082 aluminium, getting chatter at high RPM. Current tool is a 10 mm end mill. What test cuts and parameters would you try first?

  2. Paste snippets. Ask for a summary or pattern Drop three maintenance log entries or a photo of a whiteboard plan. Ask for a short timeline, likely root causes, and two next-step options. Tell it the format you want.

  3. Use follow-ups instead of starting over Keep the same thread. Ask it to adjust for budget, lead time, or a specific supplier spec. Example: Good. Now limit options to under 2,000 EUR and available in two weeks.

  4. Request the output shape you need Say table, checklist, email draft, or one-page brief. Example: Give me a 7-point inspection checklist for shift handover. Then ask it to shorten or expand.

  5. Break complex work into steps Start with a high-level plan. Then drill into the next block. Example: Outline a changeover playbook for SKUs A and B. Now write the operator cue cards for stations 1 to 3.

  6. Ask for assumptions and failure modes Have it state what it is assuming. Then ask how that could be wrong. Example: List the top three ways this setup could fail and how to detect each early.

  7. Use it for clean, fast communication Rough out messages to suppliers, customers, or your team. Example: Draft a clear email asking a supplier for a RoHS compliance letter and material certs. Polite. Precise. No fluff.

  8. Compare trade-offs, not just make a list Ask for pros and cons with a recommendation under your constraints. Example: Compare water-based vs solvent cleaning for stamped parts. Our constraint is footprint and VOC limits.

  9. Pull out standards and references carefully Ask which standard sections apply and where to look. Then check the source. Example: Point me to the clauses in ISO 9001 that govern document control for work instructions.

  10. Keep one thread per topic Park each job, RFQ, or line change in its own chat. The assistant remembers context inside a thread. That reduces repeat typing and keeps decisions traceable.

When to double-check

Treat the assistant like a fast junior. Great at structure and first drafts. Not the final sign-off. Always verify on safety, compliance, money, and irreversible changes. Cross-check technical settings against manuals. Ask for sources if you need to brief an auditor. If it sounds confident but you are unsure, ask it to show reasoning and alternatives.

Why this speeds up flow

Search scatters attention. You click, skim, and switch. A conversation keeps focus on your problem. You get a workable draft in minutes, then improve it. That cuts decision latency and rework. It also reduces meetings, because a clear draft turns debate into edits.

Data privacy and sovereignty matter

Do not paste sensitive drawings, pricing, or payroll into a tool you cannot own and govern. Hosting in the EU is not the same as legal control. Jurisdiction decides who can compel access to your data. Real sovereignty means the provider and the stack are EU based and subject only to EU law. That is the bar we hold ourselves to. If you need an assistant on the shopfloor, make sure your contracts, architecture, and vendor are aligned with EU privacy and sovereignty, not just EU servers.

Make it stick this week

  • Pick one use case with clear value. Shift handover checklists, supplier emails, or changeover plans all work.
  • Define your red lines. What never goes into the tool. What must be verified.
  • Standardize prompts for repeat work. Save them as snippets.
  • Set up a naming convention for threads. One per job or per line change.
  • Do a 30 minute huddle next week. Share what worked and what to adjust.

Want help making an AI assistant safe and useful in your plant, with EU-only data handling and a focus on execution flow? Get in touch.

Sources

  • 23-llm-tips.md