by Christopher Chagnon
Date Published March 2, 2026 - Last Updated March 2, 2026

“No coding. Just vibes.”

Vibe coding started as a joke. Developers described applications in plain language and let AI make it work. If the result was not quite right, they refined it, focusing on “the what” more than “the how.”

What is Vibe Coding?

Vibe coding is an “emerging software development practice that uses AI to generate functional code from natural language prompts, accelerating development, and making app building more accessible, especially for those with limited programming experience,” according to Google Cloud.

The workflow can be simplified to: Describe => Generate => Validate => Refine

A typical exchange might look like this:

Describe: “Create an app that allows a user to make a list of to-dos and mark them as completed.”
Generate: The AI outputs code.
Validate: You run the code and click around in the app.
Refine: You enter additional prompts such as:

• “Completed items should move to the bottom.”
• “Use React.”
• “No, the current version.”
• “Use React 20. Not 17.”

What appears chaotic is actually the process working as intended. It reinforces familiar lessons: be specific, include explicit requirements and state not only what you want but what you do not want.

“You can’t automate what you haven’t defined” is often repeated. With vibe coding, the goal is not automation. The goal is momentum. That same mindset applies to ITSM.

From Vibe Code to VibeTSM

VibeTSM is not about writing code. It is about designing processes, documents and structures that support complex service environments. In VibeTSM, AI accelerates the creation and refinement of ITSM artifacts.

The same Describe, Generate, Validate, Refine model applies:

Describe: “Create an SOP for incident response for a new call center process.”
Generate: The AI outputs a draft document.
Validate: Review the output.
Refine: Enter additional prompts such as:

• “Account for follow-the-sun.”
• “Consider multi-tier escalations.”

Finding a vibe in ITSM gives you a starting point. When rolling out a change or implementing a process, the hardest part is getting something on the page. Within minutes, you have a structured document to review. It will not be perfect, and may contain generic language or unnecessary detail, but it is a starting point.

That shift matters. Stakeholders react more effectively to a draft than to an abstract idea. With a starting point, iterations move faster and alignment comes sooner.

Your Favorite Consultant

Like vibe coding, VibeTSM has risks. Hallucinations, mistakes and inconsistencies are real. The key is to treat AI like a consultant. Use it as a sounding board and a starting point. Ask for specific artifacts and supplement work you have already begun. Tell it which ITSM tools, frameworks and technologies you use.

AI can surface best practices, highlight how your processes differ and point to common approaches across the industry. It should inform judgment; not replace it.

Where This Approach Delivers Value

Process Design

When designing a new support workflow, AI becomes a fast-brainstorming partner. It can generate escalation paths, tier definitions and process maps.

Sometimes, the result feels technically sound, but disconnected from real-world behavior. Even so, it provides a framework to refine instead of starting from nothing.

CMDB and Field Design

AI performs well when creating structured data definitions. It can suggest attribute lists, data types, required flags and help text. This saves time documenting information teams already understand, but have never been formally captured.

The risk is overdesign. It is easy to accept every suggested field. Strong governance requires deciding which data drives decisions and which data only increases maintenance.

Communication Drafting

We often need to communicate the same change to different audiences. AI can draft an executive summary, a manager-level announcement and analyst instructions in minutes.

The tone usually requires editing. Language can feel overly polished or generic. With refinement and an editorial eye, it reduces the friction of getting messages out during transitions.

From Vibes to Value

The endless void of the blank page has long slowed process improvement in service management. Generative AI reduces that friction. What determines the outcome is how deliberately we use it. VibeTSM is not about replacing rigor with vibes; it is about pairing structured ideation with experienced judgment so we can move faster without sacrificing quality.

Tag(s): IT service management, supportworld

Related:

More from Christopher Chagnon :

    No articles were found.

Comments: