This is a complete 2027 revision of the "Enterprise Chatbot Adoption Strategy" series originally written in 2021. It incorporates the ChatGPT and LLM revolution, RAG and AI Agent technologies, EU AI Act and regulatory changes, and maritime/shipbuilding industry case studies.
Building AI Consensus in Shipping Companies and Shipyards (this article)
From 2021's Iruda to 2027's LLMs — How has the enterprise AI landscape fundamentally changed?
The 2027 Paradox — AI got easier to use, so why is successful adoption getting harder?
Consensus 2.0 — Expanding the stakeholder map and building an AI Charter
Prologue
In 2021, writing from my experience as a PO/PM working on dialogue systems and NLP, I framed this series around one question: "How do you persuade your organization to adopt a chatbot?" My core message was simple — trigger internal debate first, and let consensus emerge from the friction.
Six years on, the technology has been completely transformed. Yet the single most important truth remains: no AI survives without org-wide buy-in.
1. What ChatGPT's Arrival in 2022 Changed
In 2021, the Iruda chatbot scandal taught us that AI is only as ethical as its data. Then, in November 2022, ChatGPT arrived. That single event moved AI from "the language of research labs" to "the language of the boardroom."
Large Language Models — GPT-4, Claude, Gemini — completely dissolved the old chatbot paradigm. Instead of designing conversation scenarios and training intent classifiers, you can now give an LLM the right instructions and context and it handles the rest.
| Category | 2021 (Legacy Chatbot Era) | 2027 (LLM / Agent Era) |
|---|---|---|
| Core technology | NLU models, intent/entity design | LLM, RAG, AI Agents |
| Development approach | Manual scenario design + utterance training | Prompt engineering + RAG with enterprise data |
| Driver of adoption | IT / AI teams | C-suite + all departments |
| Key risk | Iruda (biased data, privacy breach) | Hallucination, data leaks, EU AI Act |
| Adoption barrier | "We don't understand AI" | "Everyone says do it — but how?" (direction confusion) |
The technical barrier is lower. The organizational barrier is actually higher.
2. Why Most AI Projects Never Make It Past the Pilot
The technical barriers are lower than ever. Yet industry surveys consistently find that most AI projects stall before moving beyond the pilot stage. The reason is never the technology.
Projects that start with "everyone else is doing it" have no KPIs and quickly lose direction. Defining the purpose comes before anything else.
Connecting internal enterprise data to an LLM runs straight into data quality and security issues. Samsung Electronics' 2023 source-code leak via ChatGPT is the cautionary case study.
"AI will take my job" fear and "I don't trust AI" skepticism spread through the organization and quietly kill the project from the inside.
All three failure modes trace back to the same root: moving forward without sufficient upfront discussion and shared understanding.
3. Who Needs to Be in the Room in 2027?
In 2021, consensus-building centered on the AI team + IT + relevant business units. In 2027, that perimeter has expanded significantly. Three functions that must be included from day one:
The EU AI Act is rolling out in phases from 2026. South Korea enacted its AI Basic Act in 2025. Customer service, HR/recruiting, and financial AI now carry regulatory risk that must be reviewed at kickoff — not after the fact.
LLM API-based deployments route enterprise data through external servers. Security teams must be at the table before the first API key is provisioned — not called in after a breach.
McKinsey's 2025 report estimates that LLMs could automate roughly 30% of current work activities. HR must communicate upskilling plans and role redesigns alongside the AI rollout — not as an afterthought.
4. How to Start the Debate in 2027 — Three Methods
In 2021, I recommended sparking debate through internal message boards and team channels. The core philosophy — building consensus from the bottom up — still holds. The methods need an upgrade.
Experience beats explanation. Let executives and frontline staff actually use ChatGPT, Claude, or a company-specific RAG chatbot. The moment someone asks "which part of my work could this handle?" — the debate has begun.
Invite business units to submit "work problems they'd like AI to solve." This approach — used by SK Group and Hyundai Motor in 2025 — both surfaces real AI demand and turns employees into active participants in the change rather than passive recipients.
Selling only the upside creates backlash. Put hallucination, data leaks, regulatory exposure, and job impact on the table openly. Organizations that debate the risks together tend to own the solutions together too.
5. Build an AI Charter
The one thing leading enterprise AI adopters in 2027 have in common: they establish an AI Charter — a written document codifying "how and on what principles our organization will use AI." Microsoft, Google, and Samsung have published public AI responsibility principles; internal employee guidelines follow the same logic.
| Element | What It Defines |
|---|---|
| Purpose of AI use | Which tasks AI will handle; which decisions always require a human |
| Data principles | What data may be fed to AI; what is prohibited (PII, trade secrets, etc.) |
| Verification standards | How AI outputs are reviewed and approved before acting on them |
| Accountability | Who bears responsibility when AI produces an error |
| Employee protection | Training and role-transition support when AI changes job scope |
The process of writing the charter is itself the consensus-building exercise.
6. Who Must Be in the Room at a Shipowner or Shipyard
In most industries, the stakeholders for an AI project sit in the same building. In shipping they do not. The organization is split between ship and shore, the people who run the vessel rotate on contracts, and the way the two halves talk to each other is already defined by the ISM Code. Any AI that changes how work is done on board touches the Safety Management System (SMS) — so consensus has to cross the ship–shore line, not just the org chart.
| Role | Why they must be involved | The question they will ask |
|---|---|---|
| Designated Person Ashore (DPA) | The ISM Code link between the ship and top management. If AI changes a shipboard procedure, the SMS changes. | “Which SMS procedures change, and who approves the revision?” |
| Master & Chief Engineer | The ISM Code gives the Master overriding authority on safety and pollution prevention. AI advice must never appear to override it. | “Can I ignore the AI without having to justify it to the office?” |
| Technical & Marine Superintendents | They own the data AI will consume — noon reports, planned maintenance history, defect and inspection reports. | “Is our maintenance data clean enough to trust an AI answer?” |
| Company Security Officer / Fleet IT & OT security | AI that connects to vessel systems changes the cyber risk picture the SMS must address under IMO Resolution MSC.428(98). On ships contracted from July 2024, IACS UR E26 also requires those connections to fit the zone and conduit design. | “Does this create a new conduit into the ship network?” |
| Classification society & flag liaison | If AI touches a computer-based system in UR E26/E27 scope, or influences a safety decision, class should hear about it early — not at the survey. | “Is this a change to an approved system?” |
| Crewing / HR and seafarer representatives | A rotating, multinational workforce learns new tools during short handovers. Training has to fit crew-change cycles. | “Who trains the next crew, and in which language?” |
In a shipyard the map changes but the principle holds: design, production planning, QA/QC, the owner’s site team and the class surveyor all touch the same deliverables.
The shipyard version deserves one extra line. AI that reads drawings, specifications or vendor documents is working on contract deliverables and on information that belongs to the owner, the yard and the makers under the shipbuilding contract. Legal has to be in the room before the first document is uploaded — not after.
7. Adapting the Three Debate Methods for Ship and Shore
The three methods from Section 3 still work, but each needs a maritime adjustment:
Hold the demo at the training centre during officer briefings, or on board during a superintendent visit in port. Use a real (anonymized) noon report or PSC checklist rather than a generic office example; a Chief Engineer will judge the tool by whether it understands their paperwork.
Ask vessels to submit the recurring tasks that cost them the most time — PSC inspection preparation, bunker documentation, maintenance reporting. Ship-side submissions surface use cases that shore teams never see, and give crews ownership of the change.
Put the maritime-specific risks on the table: an AI quoting a SOLAS regulation that does not exist, vessel data leaving over the satellite link to an external AI provider, and who carries liability when AI-assisted advice goes wrong under a charter party.
8. Maritime Additions to the AI Charter
The five charter elements in Section 5 apply as they are. A shipowner or shipyard should add the following six, because they answer questions that general enterprise charters never ask:
| Element | What it defines |
|---|---|
| Master’s authority | AI output on board is advisory. The Master’s overriding authority under the ISM Code is never delegated to a system. |
| Ship–shore data boundary | Which vessel data may leave the ship over satellite, to which providers, and under which contract terms. |
| SMS integration | AI-supported procedures are written into the SMS as controlled documents and covered by internal audits. |
| Cyber scope | Any AI component that connects to onboard networks is recorded in the cyber asset inventory and assessed under the company’s cyber risk management (MSC-FAL.1/Circ.3). On UR E26 ships, it is assessed against the zones and conduits. |
| Degraded mode | What the crew does when the AI service or the satellite link is unavailable — the vessel must operate safely without it. |
| Regulatory references | AI may draft, but any citation of SOLAS, MARPOL, class rules or flag requirements is checked against the official text before it is used. |
If an element cannot be agreed between the DPA, the Masters and the CSO, the project is not ready.
"Companies that treat AI projects as a technology team problem fail. Companies that treat them as an organization-wide change management problem succeed."
The AI of 2027 is more powerful, faster, and more accessible than ever. That's precisely why agreement on how to use it must happen sooner and go deeper. In Part 2, we'll look at how to choose AI service channels and design customer touchpoints in the LLM era.
Building AI Consensus in Shipping Companies and Shipyards (this article)
⚓ Join the ShipPaulJobs Community
Join →
Comments
Post a Comment