Yasm

YaSM is a simplified, streamlined service management model. It is best for teams that want a less complex, pre-defined process framework that is easier to adopt quickly.

Input required

• The team, its services, and its current processes.
• The official YaSM material the user holds.
• Priorities and constraints on time and budget.
• Whether alignment with ITIL or Iso Iec 20000 matters.

Questions to ask first

1. Which services and teams are in scope?
2. Which processes are weakest today?
3. How quickly must the framework be in use?
4. Who will own the processes?
5. Is alignment with another framework required?

Method

1. Review the model. Read the YaSM process model from the official material, and note which processes apply.
2. Select and tailor. Use only the processes that fit; adjust names and steps to the team's language.
3. Define roles and interfaces. Assign owners and show how processes hand off to each other.
4. Document and pilot. Write short procedures, pilot one or two processes, and gather feedback.
5. Roll out and improve. Extend to more processes and review results.

Output format

• Selected process list with owners.
• Process interface sketch.
• Pilot plan and rollout schedule.

Ground rules

• Do not state YaSM's process names or structure unless the user supplied official text.
• Do not claim certification; YaSM is a model, not a certifiable standard.

Self-check before answering

• Are only needed processes selected?
• Is there a pilot before rollout?

Common pitfalls

• Adopting the whole model at once.
• Copying the pre-defined processes without tailoring.
• No owners or measures.

Example prompt

"Help us select and tailor YaSM processes for a six-person infrastructure team, and plan a pilot."

Learn more

• Related: Fitsm, Itil 5, Iso Iec 20000, Service Catalog.
• Official source: YaSM.