Skip to main content

Linnoedge

Linnoedge
AI Training Programs × Role-Based Design

We ran the training.
Nothing changed.

The tool wasn't the problem. The design was.

At one company I worked with, the mandate was straightforward: get the whole team using AI. They ran a full-day session, bought the licenses, handed out the handouts. Three months later, usage had dropped to almost zero.

The training wasn't bad. The design was wrong. Executives, managers, and frontline staff don't have the same AI challenge — and one session can't fix all three.

We're a team based in Ho Chi Minh City that runs its own business on AI every day. We teach what we actually use — in English, Japanese, and Vietnamese.

Book a Free Session → See the Programs
Sound Familiar?

Which of these is your company right now?

These are the three situations I see most often. None of them means AI won't work in your organization — they just mean the design needs to be different for each one.

01

Leadership is pushing AI. The team isn't moving.

"Management keeps saying we need to use AI, but nobody's told us what that actually means for our jobs."

Honest observation

This is a leadership alignment gap, not a technology problem. When executives haven't been trained on what AI can and can't do, they can't set realistic expectations for the team. The frontline takes the pressure and doesn't know where to start.

02

The licenses got bought. Nobody's using them.

"We rolled out the tools across the team. Six months later, two people actually use them."

Honest observation

Buying a tool is not a workflow change. At one company I visited, they had ChatGPT accounts for 40 people. When I asked what they were using it for, most said: "Sometimes to write emails." The tool was there. The workflow design wasn't.

03

Training ran once. Three months later, nothing stuck.

"People used it right after the session. Then gradually drifted back to what they were doing before."

Why it happens

This isn't a motivation problem. When workload spikes, everyone reverts to habit — that's just how people work. If the training didn't specify which task in which workflow gets replaced by AI, there's no new habit to revert to. One-off sessions don't create behavioral change.

The real insight

AI produces averages. That means humans need to be the ones who can say "that's wrong."

A 25-year veteran and a new hire have completely different AI challenges. The veteran's value is knowing when the AI output is off. The new hire's challenge is building judgment before they can evaluate AI at all. Running them through the same session wastes both.

Most vendors will help you get it running. Almost none of them are still in the room six months later when something breaks — or when it works so well it breaks something else.

Training Programs

The right format depends on where you're stuck.

We don't run a course catalog. These are the four situations companies most often bring to us — and the format we propose for each. What's below is a starting point — depth and number of sessions are tuned to your situation. Not sure which fits? Start with a 30-minute call — I'll ask what's actually happening and we'll figure it out together.

Situation A
A

You want the whole company using AI — but every level is at a different temperature

Leadership is pushing, managers are hedging, the frontline doesn't know what's expected. That mismatch isn't unusual — it's the state I see most often when a company first calls us.

Each level gets different content. Leadership gets AI decision-making frameworks. Managers get team adoption design. Frontline gets workflow-specific prompts they can use the next morning. Each layer builds on the previous one.

Executives & Leadership
"This isn't a technology decision. It's a workflow design decision."
Managers
"80% of management overhead can be systematized. The other 20% is where you earn your role."
Senior Staff & Specialists
"You're not replacing your experience with AI. You're using your experience to evaluate AI."
New Hires
"AI accelerates thinking — it doesn't replace the thinking you still need to build."
The format we propose AI Training by Seniority Level — 60–120 min per session, from ¥50,000 (~$330 USD). The session ends with a defined "what changes tomorrow" for each participant — not just a list of tools.
Situation B
B

The licenses got bought. Now you need a team that can build AI into the actual workflow

"Knowing how to use AI" and "having it built into the workflow" are separated by more distance than one training day can cover. That's why this format runs as a six-session series, team by team.

"Visualize before you build" — describing the output before prompting. This is the habit that separates people who get useful AI output from people who get generic AI output. Sessions 1–3 cover prompt design and output evaluation. Sessions 4–6 cover workflow integration.

Led by Shin (Uchida Shin, COO) — someone who runs his own daily operations on AI systems, not slides about AI systems.

The format we propose AI Practical Skills Program "Visualize to Realize" — 6 sessions, team format. Follow-up checkpoints at 30 and 90 days available. Pricing after the first call — it depends on team size and situation.
Situation C
C

Before the team moves, you want to run AI yourself

"Using AI" and "running AI agents" are different things. The first is Q&A. The second means the system is gathering information, organizing it, and preparing decision inputs while you're doing something else.

Two sessions per month, 1-on-1 with SHOGO. We start from how I've built agents for my own management workflows, then redesign them around your specific decision processes. Not theory — we build and run it together.

The format we propose CEO AI Agent Coaching — 2× per month, 1 executive. Pricing on inquiry.
Situation D
D

Your team works across Japanese and Vietnamese — and AI adoption keeps stalling in between

For Japanese companies with Vietnamese staff, or Vietnamese companies working with Japanese clients. At one engagement I ran in Ho Chi Minh City, half the room was Vietnamese engineers, half Japanese managers. The AI collaboration gaps between them weren't language — they were workflow assumptions. We run sessions that surface those gaps explicitly.

Delivery available on-site in Ho Chi Minh City and Tokyo. Japanese SMBs may also be eligible for up to 75% subsidy via Japanese government training programs (人材開発支援助成金) — ask us.

The format we propose Bilingual Team Training — on-site in Ho Chi Minh City or Tokyo, or live online. English / Japanese / Vietnamese. Pricing on inquiry.
Whatever the entry point, the goal is the same — not "now you know," but a team that moves the next morning. Which format fits, we'll figure out in the conversation.

The Difference

Training with workflow design vs. training without it

Both are called "AI training." One month later, the results are completely different.

Common pattern

Training without workflow design

  • Same content for every seniority level
  • Ends with "try it yourself" — no defined next actions
  • Not mapped to any specific workflow
  • Leadership hasn't been aligned — team doesn't know what's expected
  • 80% of participants revert to old habits within 90 days
Continued usage at 90 days 20%
Linnoedge method

Training with workflow design

  • Content designed separately for each seniority level
  • Session ends with agreed "what changes tomorrow" per participant
  • Specific workflow moments identified before training ends
  • Executive alignment built before frontline training starts
  • Follow-up checkpoints at 30 and 90 days available
Teams that integrate into workflow High
Our Instructors

Not a training company. A team that runs on AI.

Everyone who delivers our training uses AI in their own work every day — not as a demonstration, but as infrastructure. Japanese, English, and Vietnamese delivery available. On-site in Ho Chi Minh City and Tokyo.

Shogo Harada CEO

Shogo Harada

Representative Director · Ho Chi Minh City

Ho Chi Minh City-based. I lead a Japanese-Vietnamese team and run the business on AI — not occasionally, but as the actual infrastructure. My approach always starts with "why use AI" as the decision framework, not the tools themselves. I can say that because I got it wrong in my own company first.

Come to this thinking of it as a business conversation, not a training session.

Japanese English
Shin Uchida COO

Shin Uchida

Chief Operating Officer

Shin runs the Practical Skills Program. He designed the "Visualize to Realize" curriculum from the actual friction points he hit when rolling out AI inside our own operations.

He's the person I trust to sit with a team that's never used AI seriously and get them to a usable state in six sessions.

Japanese English
Nguyen Dang CTO

Nguyen Dang

CTO · Ho Chi Minh City

Dang covers the technical integration side — when a team's AI questions cross into "how does this actually connect to our systems," he's the one in the room.

Particularly valuable for engineering teams and for Vietnamese-language delivery in mixed Japanese-Vietnamese organizations.

Vietnamese English
The Path Forward

Training can be the end. Or it can be the beginning.

Most companies just need the training and nothing else — that's a complete engagement. But at some companies, the training session surfaces a workflow problem that turns out to be a systems problem. When that happens, we have the development capacity to build it.

A dedicated development team in Ho Chi Minh City — senior engineers who have shipped AI integrations for clients in Japan and Southeast Asia, with a PM who speaks both the technical side and the business side. Engineer rates run roughly half of an equivalent Tokyo team — about 35% lower in total cost once ramp-up and communication overhead are counted. The difference: we don't hand off and disappear. QA checkpoint before anything touches your production environment. Ongoing support from month one of go-live.

01

30-min call

We hear what's actually happening

→
02

Program design

Built around your team's actual workflow

→
03

Training

Each level gets different content

→
04

Follow-up

30 & 90-day check-ins (optional)

FAQ

Frequently Asked Questions

Q How large can the training group be?

No hard upper limit. We've run sessions for teams of 5 and for groups of 60+. For groups above 100, we recommend splitting into sessions by seniority level — which is what we'd likely suggest anyway. The standard per-session target is under 25 for interactive depth.

Q Do you deliver training online or on-site?

Both. We're based in Ho Chi Minh City — on-site delivery in Vietnam is straightforward. We travel to Japan (Tokyo and surrounding areas) for multi-session engagements that justify the logistics. Online delivery works well for ongoing programs and for organizations with distributed teams.

Q What languages do you train in?

Japanese, English, and Vietnamese — sometimes in the same session for mixed teams. For Japanese companies operating in Vietnam with local staff, we run bilingual sessions that bridge the gap explicitly, not just linguistically but in terms of working-culture assumptions about AI.

Q Is the content customized or do you use a standard curriculum?

Every engagement is custom-built. Before any session, we ask about the tools you're already using, the specific workflows you want to change, and the AI maturity level of each participant group. A pharmaceutical company's workflow challenges look nothing like a manufacturing company's — and the training shouldn't either.

Q What happens after the training ends?

To prevent the pattern of "used it right after the session, then gradually drifted back" — we recommend designing follow-up in from the start, not as an afterthought. Optional check-in sessions at 30 and 90 days are available. For the CEO coaching program, it's an ongoing relationship by design — two sessions per month, content evolving as your AI infrastructure does. If training surfaces a workflow problem that needs development, our HCM-based team can build it at roughly half the engineer rate — about 35% lower in total cost — of equivalent Tokyo development.

Measure first

Before you reach out, measure where you stand

Reaching out cold can feel like a big step. So before that, two free tools to see — right here — whether now is the right time for you, and how much your cost would change. Bring the result to a 30-minute session, and the conversation moves a lot faster.

Readiness check / about 90 seconds

Is now the right time for you?

Answer eight questions and we score your readiness, then send back three specific recommendations from your answers. Not “you should do this” — “here’s what to do, in your situation.”

Check your readiness → Cost calculator / instant

How much would your cost change?

Enter your team size and budget, and see how the next 12 months change — right here, with the reasoning behind the numbers laid out.

Calculate your cost →
Start Here

Whether training is the right next step,
we'll only know once we talk.

Maybe you're not sure which tier-based program fits — or whether your team needs training at all yet. Either is fine. In 30 minutes I'll ask what's actually happening in your organization, and we'll figure out the realistic next step together. No deck. We talk first.

“If training isn't what you need,
I'll tell you directly.”
1
Book a 30-min session. No prep needed. Just tell me where your team is getting stuck with AI right now.
2
We talk through the situation and sort out the starting point — which tier needs what, or whether the gap is something training won't fix.
3
If it fits, we shape the concrete next step. If it doesn't, I'll say so — and we'll think through a better way together.
Book a Free Session Send a Message
Shogo Harada, CEO, Linnoedge
Who You're Talking To
Shogo Harada
CEO, Linnoedge — Ho Chi Minh City

I run my own company the way I tell clients to run theirs — AI in every workflow, not as a side project, but as the actual operating model. Almost no hour of my workday happens without AI in some part of it.

So when I train a team, I'm not teaching from a slide deck about AI potential. I'm sharing what I've already tried, where it broke, and what actually held up day to day.

WORKS

Teams built with this model.

Data Engineering SaaS

3,200+

Regulated Gaming Data Platform — Japan Market

Every morning, three hours of someone's day disappeared.

Read the case

Pharma & Healthcare

4mo

Patient & Physician Management System — Pharma Enterprise

The workflow that ran the operation wasn't in the spec.

Read the case
AI solutions consulting All case studies