{"id":9679,"date":"2026-06-01T13:28:07","date_gmt":"2026-06-01T13:28:07","guid":{"rendered":"https:\/\/nilex.se\/nicht-kategorisiert\/change-management-itil-4\/"},"modified":"2026-06-01T13:28:07","modified_gmt":"2026-06-01T13:28:07","slug":"change-management-itil-4","status":"publish","type":"post","link":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/","title":{"rendered":"Change Management i ITIL 4 \u2013 best practice och f\u00f6r\u00e4ndringstyper"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Okontrollerade f\u00f6r\u00e4ndringar \u00e4r en av de vanligaste orsakerna till IT-incidenter i produktion. Change Management \u2013 eller Change Enablement som ITIL 4 numera ben\u00e4mner praktiken \u2013 \u00e4r det strukturella svaret: ett ramverk f\u00f6r att godk\u00e4nna, schemal\u00e4gga och genomf\u00f6ra f\u00f6r\u00e4ndringar med minimal st\u00f6rning p\u00e5 tj\u00e4nsteleveransen. Den h\u00e4r guiden g\u00e5r igenom vad ITIL 4 definierar som Change Enablement, vilka f\u00f6r\u00e4ndringstyper som finns, hur godk\u00e4nnandeprocessen fungerar i praktiken och vilka arbetsmetoder som faktiskt minskar risken f\u00f6r produktionsst\u00f6rningar.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">Vad \u00e4r Change Enablement i ITIL 4?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">I ITIL 3 kallades praktiken Change Management. I ITIL 4 heter den officiellt Change Enablement \u2013 en namnf\u00f6r\u00e4ndring som signalerar en f\u00f6rskjutning i syns\u00e4tt: fokus \u00e4r inte l\u00e4ngre enbart kontroll, utan att m\u00f6jligg\u00f6ra f\u00f6r\u00e4ndringar snabbt och s\u00e4kert. ITIL 4 definierar syftet som att maximera antalet lyckade IT- och produktf\u00f6r\u00e4ndringar genom att s\u00e4kerst\u00e4lla att risker bed\u00f6ms korrekt, att f\u00f6r\u00e4ndringar auktoriseras och att f\u00f6r\u00e4ndringsschemat hanteras aktivt.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">Praktiken t\u00e4cker alla typer av f\u00f6r\u00e4ndringar som p\u00e5verkar en organisations tj\u00e4nster: konfigurationsf\u00f6r\u00e4ndringar, releaser, patchning, infrastrukturjusteringar och applikationsuppdateringar. Allt som kan st\u00f6ra en tj\u00e4nst om det genomf\u00f6rs fel faller inom ramen. I praktiken anv\u00e4nds termen Change Management fortfarande brett \u2013 i verktyg, processdokumentation och i branschen generellt \u2013 och i den h\u00e4r guiden anv\u00e4nds b\u00e5da begreppen parallellt.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">De tre f\u00f6r\u00e4ndringstyperna i ITIL 4<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">ITIL 4 definierar tre f\u00f6r\u00e4ndringstyper med olika godk\u00e4nnandefl\u00f6den. Klassificeringen \u00e4r central: fel typ p\u00e5 en f\u00f6r\u00e4ndring inneb\u00e4r antingen on\u00f6dig byr\u00e5krati eller otillr\u00e4cklig riskhantering.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Typ<\/strong><\/td><td><strong>Beskrivning<\/strong><\/td><td><strong>Godk\u00e4nnandeprocess<\/strong><\/td><td><strong>Exempel<\/strong><\/td><\/tr><tr><td>Standard change<\/td><td>L\u00e5grisig, v\u00e4ldefinierad f\u00f6r\u00e4ndring med k\u00e4nt utfall och etablerat genomf\u00f6randef\u00f6rfarande<\/td><td>Pre-auktoriserad \u2013 kr\u00e4ver inget aktivt CAB-beslut<\/td><td>L\u00f6senords\u00e5terst\u00e4llning, standardinstallation, rutinm\u00e4ssig patchning av testad uppdatering<\/td><\/tr><tr><td>Normal change<\/td><td>F\u00f6r\u00e4ndring som kr\u00e4ver individuell bed\u00f6mning och formell auktorisering innan genomf\u00f6rande<\/td><td>Granskning av Change Authority eller CAB beroende p\u00e5 riskniv\u00e5<\/td><td>Ny applikation i produktion, infrastrukturuppgradering, integrationsf\u00f6r\u00e4ndring<\/td><\/tr><tr><td>Emergency change<\/td><td>M\u00e5ste implementeras omedelbart f\u00f6r att l\u00f6sa en allvarlig incident eller kritisk s\u00e4kerhetsbrist<\/td><td>F\u00f6renklat godk\u00e4nnandefl\u00f6de \u2013 auktoriseras av utsedd person, dokumenteras fullst\u00e4ndigt i efterhand<\/td><td>Patchning av aktivt utnyttjad s\u00e4kerhetsbrist, akut konfigurations\u00e5tg\u00e4rd vid p\u00e5g\u00e5ende incident<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Standard changes \u00e4r pre-auktoriserade och kr\u00e4ver inget aktivt beslut per tillf\u00e4lle. Syftet \u00e4r att eliminera administrativt overhead f\u00f6r rutinm\u00e4ssiga l\u00e5griskf\u00f6r\u00e4ndringar. Normal changes genomg\u00e5r en formell riskbed\u00f6mning och auktoriseras av en Change Authority \u2013 antingen en individ eller ett Change Advisory Board beroende p\u00e5 f\u00f6r\u00e4ndringens komplexitet och riskniv\u00e5. Emergency changes \u00e4r undantaget: n\u00e4r en kritisk incident kr\u00e4ver en omedelbar system\u00e5tg\u00e4rd genomf\u00f6rs f\u00f6r\u00e4ndringen med ett f\u00f6renklat godk\u00e4nnandefl\u00f6de, men ska dokumenteras fullst\u00e4ndigt och granskas p\u00e5 n\u00e4stkommande ordinarie CAB.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Change Authority och CAB<\/h2>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">En av de praktiska fr\u00e5gorna i ITIL 4 \u00e4r vem som auktoriserar f\u00f6r\u00e4ndringar. ITIL 4 introducerade begreppet Change Authority som en mer flexibel modell \u00e4n det tidigare CAB-centrerade syns\u00e4ttet i ITIL 3.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Change Authority \u00e4r den person eller grupp som auktoriserar en specifik typ av f\u00f6r\u00e4ndring. Auktoritetsniv\u00e5n ska vara proportionell mot riskens storlek och aff\u00e4rsp\u00e5verkan:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>L\u00e5grisiga normala f\u00f6r\u00e4ndringar: Change Manager eller linjechefen f\u00f6r ansvarigt team<\/li>\n\n\n\n<li>Medelrisiga f\u00f6r\u00e4ndringar: Change Advisory Board (CAB) \u2013 ett r\u00e5dgivande organ med representanter fr\u00e5n IT-drift, development, verksamhet och vid behov externa leverant\u00f6rer<\/li>\n\n\n\n<li>H\u00f6griskiga och aff\u00e4rskritiska f\u00f6r\u00e4ndringar: IT-ledning eller styrgrupp beroende p\u00e5 organisation<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">CAB \u00e4r i ITIL 4 ett verktyg \u2013 inte ett obligatoriskt processteg f\u00f6r alla f\u00f6r\u00e4ndringar. Organisationer som historiskt kallat in CAB till varje f\u00f6r\u00e4ndring har ofta skapat en flaskhals som bromsar legitim l\u00e5grisig f\u00f6r\u00e4ndring och minskar processens trov\u00e4rdighet. ITIL 4:s rekommendation \u00e4r att CAB anv\u00e4nds selektivt f\u00f6r komplexa eller h\u00f6griskiga f\u00f6r\u00e4ndringar d\u00e4r ett bredare perspektiv faktiskt tillf\u00f6r v\u00e4rde i riskbed\u00f6mningen.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Change-processen steg f\u00f6r steg<\/h2>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">Ett normalt change-fl\u00f6de i en ITIL 4-baserad organisation genomf\u00f6rs i f\u00f6ljande steg:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Change Request registreras. Alla f\u00f6r\u00e4ndringar initieras via en formell Change Request (CR) i \u00e4rendehanteringssystemet. CR:n ska inneh\u00e5lla beskrivning, motivering, ber\u00f6rd CI i CMDB, riskbed\u00f6mning, \u00e5terst\u00e4llningsplan och f\u00f6reslaget implementationsf\u00f6nster.<\/li>\n\n\n\n<li>Initial granskning. Change Manager granskar att CR:n \u00e4r fullst\u00e4ndig och klassificerar f\u00f6r\u00e4ndringstypen. Ofullst\u00e4ndiga CR:er returneras med specificerade kompletteringskrav.<\/li>\n\n\n\n<li>Riskbed\u00f6mning. F\u00f6r normala f\u00f6r\u00e4ndringar g\u00f6rs en formell riskbed\u00f6mning. Bed\u00f6mningen tar h\u00e4nsyn till sannolikhet f\u00f6r st\u00f6rning, p\u00e5verkade tj\u00e4nster och CI:er, historik fr\u00e5n liknande f\u00f6r\u00e4ndringar och rollback-m\u00f6jligheter.<\/li>\n\n\n\n<li>Auktorisering. Beroende p\u00e5 riskniv\u00e5 auktoriseras f\u00f6r\u00e4ndringen av Change Manager, CAB eller eskaleras till IT-ledning. Beslutet dokumenteras i CR:n.<\/li>\n\n\n\n<li>Schemal\u00e4ggning. Godk\u00e4nda f\u00f6r\u00e4ndringar schemal\u00e4ggs i en Forward Schedule of Changes (FSC). H\u00e4nsyn tas till andra planerade f\u00f6r\u00e4ndringar, kritiska aff\u00e4rsperioder och kapacitet hos implementationsteamet.<\/li>\n\n\n\n<li>Implementation. F\u00f6r\u00e4ndringen genomf\u00f6rs enligt plan. Avvikelser fr\u00e5n planerat genomf\u00f6rande dokumenteras direkt i CR:n.<\/li>\n\n\n\n<li>Granskning och st\u00e4ngning. Efter implementation granskas utfallet: levererade f\u00f6r\u00e4ndringen det avsedda resultatet, uppstod incidenter och vad kan f\u00f6rb\u00e4ttras? Erfarenheterna dokumenteras och anv\u00e4nds f\u00f6r att kalibrera framtida riskbed\u00f6mningar.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">Best practices f\u00f6r Change Enablement<\/h2>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">De organisationer som lyckas med Change Enablement enligt ITIL 4 har ett antal gemensamma arbetsmetoder:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pre-auktorisera rutinm\u00e4ssiga standard changes. En organisation som l\u00e5ter servicedesken hantera l\u00e5grisiga f\u00f6r\u00e4ndringar utan CAB-godk\u00e4nnande frig\u00f6r kapacitet f\u00f6r genuint komplexa f\u00f6r\u00e4ndringar och minskar genomloppstiden f\u00f6r rutinarbete.<\/li>\n\n\n\n<li>Koppla varje change request till CMDB. Utan koppling till konfigurationsdatabasen \u00e4r det om\u00f6jligt att bed\u00f6ma p\u00e5verkan korrekt. Varje CR ska referera till ber\u00f6rda Configuration Items och systemrelationer.<\/li>\n\n\n\n<li>M\u00e4t change success rate kontinuerligt. Andelen f\u00f6r\u00e4ndringar som genomf\u00f6rs utan efterf\u00f6ljande incident \u00e4r det prim\u00e4ra KPI:t f\u00f6r Change Enablement. Realistiska m\u00e5lniv\u00e5er f\u00f6r mogna organisationer \u00e4r 95 % och upp\u00e5t.<\/li>\n\n\n\n<li>H\u00e5ll CAB fokuserat. Ett CAB-m\u00f6te som granskar 40 f\u00f6r\u00e4ndringar per vecka \u00e4r ett granskningsm\u00f6te i teorin och ett st\u00e4mpelm\u00f6te i praktiken. Begr\u00e4nsa CAB till komplexa och h\u00f6griskiga f\u00f6r\u00e4ndringar d\u00e4r bredare perspektiv faktiskt tillf\u00f6r v\u00e4rde.<\/li>\n\n\n\n<li>Dokumentera emergency changes fullst\u00e4ndigt. Det \u00e4r h\u00e4r sp\u00e5rbarheten ofta brister. Emergency changes ska granskas p\u00e5 n\u00e4stkommande ordinarie CAB och erfarenheterna ska in i problemhanteringsprocessen.<\/li>\n\n\n\n<li>Integrera change och release. I ITIL 4 hanteras Change Enablement och Release Management som separata men t\u00e4tt kopplade praktiker. En release utan godk\u00e4nd CR \u00e4r en okontrollerad f\u00f6r\u00e4ndring oavsett hur den tekniska kvaliteten ser ut.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Vanliga fallgropar<\/h2>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">F\u00f6ljande m\u00f6nster \u00e5terkommer i organisationer d\u00e4r Change Enablement inte fungerar som avsett:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CAB som formalitet. Om CAB-m\u00f6ten konsekvent godk\u00e4nner alla f\u00f6r\u00e4ndringar utan substantiell diskussion har processen blivit ceremoniel, inte kontrollerande. Det \u00e4r ett tecken p\u00e5 att fel f\u00f6r\u00e4ndringar eskaleras till CAB, inte att CAB-formatet \u00e4r fel.<\/li>\n\n\n\n<li>Change-fatigue. Alltf\u00f6r rigor\u00f6s process f\u00f6r l\u00e5grisiga f\u00f6r\u00e4ndringar skapar incitament att kringg\u00e5 processen. Resultatet \u00e4r Shadow Changes \u2013 f\u00f6r\u00e4ndringar som genomf\u00f6rs utan registrering \u2013 vilket \u00e4r v\u00e4rre ur risksynpunkt \u00e4n avsaknaden av en formell process.<\/li>\n\n\n\n<li>Saknad post-implementation review. Change-processen f\u00f6rb\u00e4ttras av strukturerad uppf\u00f6ljning efter varje genomf\u00f6rd f\u00f6r\u00e4ndring. Utan den upprepas samma riskbed\u00f6mningsmisstag i n\u00e4sta cycle.<\/li>\n\n\n\n<li>Manuell schemal\u00e4ggning. Forward Schedule of Changes i ett kalkylblad synligg\u00f6r inte konflikter och beroenden mellan parallella f\u00f6r\u00e4ndringar. Schemal\u00e4ggning ska hanteras i \u00e4rendehanteringssystemet med automatisk konfliktindikering.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Change Management i Nilex Service Platform<\/h2>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">I Nilex Service Platform (NSP) implementeras Change Enablement som en konfigurerad arbetsprocess: change requests registreras, klassificeras och routas automatiskt baserat p\u00e5 f\u00f6r\u00e4ndringstyp och riskniv\u00e5. Standard changes pre-auktoriseras med direkt routing till implementationsteamet. Normala och komplexa f\u00f6r\u00e4ndringar routas till definierade Change Authorities eller ett CAB-granskningsfl\u00f6de med inbyggt godk\u00e4nnandessteg och revisionssp\u00e5r.<\/p>\n\n\n\n<div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">NSP kopplar varje change request mot CMDB, vilket inneb\u00e4r att p\u00e5verkansanalysen \u2013 vilka tj\u00e4nster, system och beroenden som ber\u00f6rs \u2013 \u00e4r direkt tillg\u00e4nglig i \u00e4rendet utan manuell s\u00f6kning. Forward Schedule of Changes visualiseras i en kalendervy med automatisk konfliktindikering. Post-implementation reviews och change success rate rapporteras i standarddashboardar utan konfigurationstill\u00e4gg.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Vill du se hur ett change-fl\u00f6de konfigureras konkret i NSP? Boka en genomg\u00e5ng med en av v\u00e5ra konsulter.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Okontrollerade f\u00f6r\u00e4ndringar \u00e4r en av de vanligaste orsakerna till IT-incidenter i produktion. Change Management \u2013 eller Change Enablement som ITIL 4 numera ben\u00e4mner praktiken \u2013 \u00e4r det strukturella svaret: ett ramverk f\u00f6r att godk\u00e4nna, schemal\u00e4gga och genomf\u00f6ra f\u00f6r\u00e4ndringar med minimal st\u00f6rning p\u00e5 tj\u00e4nsteleveransen. Den h\u00e4r guiden g\u00e5r igenom vad ITIL 4 definierar som Change Enablement, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":9680,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[181],"tags":[],"class_list":["post-9679","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-e-guider-de"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.6 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Change Management i ITIL 4 \u2013 best practice och f\u00f6r\u00e4ndringstyper | Nilex<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/\" \/>\n<meta property=\"og:locale\" content=\"de_DE\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Change Management i ITIL 4 \u2013 best practice och f\u00f6r\u00e4ndringstyper | Nilex\" \/>\n<meta property=\"og:description\" content=\"Okontrollerade f\u00f6r\u00e4ndringar \u00e4r en av de vanligaste orsakerna till IT-incidenter i produktion. Change Management \u2013 eller Change Enablement som ITIL 4 numera ben\u00e4mner praktiken \u2013 \u00e4r det strukturella svaret: ett ramverk f\u00f6r att godk\u00e4nna, schemal\u00e4gga och genomf\u00f6ra f\u00f6r\u00e4ndringar med minimal st\u00f6rning p\u00e5 tj\u00e4nsteleveransen. Den h\u00e4r guiden g\u00e5r igenom vad ITIL 4 definierar som Change Enablement, [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/\" \/>\n<meta property=\"og:site_name\" content=\"Nilex\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-01T13:28:07+00:00\" \/>\n<meta name=\"author\" content=\"nilex_admin\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"nilex_admin\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7\u00a0Minuten\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Change Management i ITIL 4 \u2013 best practice och f\u00f6r\u00e4ndringstyper | Nilex","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/","og_locale":"de_DE","og_type":"article","og_title":"Change Management i ITIL 4 \u2013 best practice och f\u00f6r\u00e4ndringstyper | Nilex","og_description":"Okontrollerade f\u00f6r\u00e4ndringar \u00e4r en av de vanligaste orsakerna till IT-incidenter i produktion. Change Management \u2013 eller Change Enablement som ITIL 4 numera ben\u00e4mner praktiken \u2013 \u00e4r det strukturella svaret: ett ramverk f\u00f6r att godk\u00e4nna, schemal\u00e4gga och genomf\u00f6ra f\u00f6r\u00e4ndringar med minimal st\u00f6rning p\u00e5 tj\u00e4nsteleveransen. Den h\u00e4r guiden g\u00e5r igenom vad ITIL 4 definierar som Change Enablement, [&hellip;]","og_url":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/","og_site_name":"Nilex","article_published_time":"2026-06-01T13:28:07+00:00","author":"nilex_admin","twitter_card":"summary_large_image","twitter_misc":{"Written by":"nilex_admin","Est. reading time":"7\u00a0Minuten"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/#article","isPartOf":{"@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/"},"author":{"name":"nilex_admin","@id":"https:\/\/nilex.se\/de\/#\/schema\/person\/2f40d971d740db14580101a64f44c6f1"},"headline":"Change Management i ITIL 4 \u2013 best practice och f\u00f6r\u00e4ndringstyper","datePublished":"2026-06-01T13:28:07+00:00","mainEntityOfPage":{"@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/"},"wordCount":1465,"publisher":{"@id":"https:\/\/nilex.se\/de\/#organization"},"image":{"@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/#primaryimage"},"thumbnailUrl":"https:\/\/nilex.se\/wp-content\/uploads\/2026\/03\/1.png","articleSection":["E-guider"],"inLanguage":"de"},{"@type":"WebPage","@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/","url":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/","name":"Change Management i ITIL 4 \u2013 best practice och f\u00f6r\u00e4ndringstyper | Nilex","isPartOf":{"@id":"https:\/\/nilex.se\/de\/#website"},"primaryImageOfPage":{"@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/#primaryimage"},"image":{"@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/#primaryimage"},"thumbnailUrl":"https:\/\/nilex.se\/wp-content\/uploads\/2026\/03\/1.png","datePublished":"2026-06-01T13:28:07+00:00","breadcrumb":{"@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/#breadcrumb"},"inLanguage":"de","potentialAction":[{"@type":"ReadAction","target":["https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/"]}]},{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/#primaryimage","url":"https:\/\/nilex.se\/wp-content\/uploads\/2026\/03\/1.png","contentUrl":"https:\/\/nilex.se\/wp-content\/uploads\/2026\/03\/1.png","width":1800,"height":1199},{"@type":"BreadcrumbList","@id":"https:\/\/nilex.se\/de\/e-guider-de\/change-management-itil-4\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Hem","item":"https:\/\/nilex.se\/de\/"},{"@type":"ListItem","position":2,"name":"Change Management i ITIL 4 \u2013 best practice och f\u00f6r\u00e4ndringstyper"}]},{"@type":"WebSite","@id":"https:\/\/nilex.se\/de\/#website","url":"https:\/\/nilex.se\/de\/","name":"Nilex","description":"\u00c4rendehanteringssystem som f\u00f6rvandlar din organisation med automatisk \u00e4rendeprioritering","publisher":{"@id":"https:\/\/nilex.se\/de\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/nilex.se\/de\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"de"},{"@type":"Organization","@id":"https:\/\/nilex.se\/de\/#organization","name":"Nilex","url":"https:\/\/nilex.se\/de\/","logo":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/nilex.se\/de\/#\/schema\/logo\/image\/","url":"https:\/\/new.nilex.se\/wp-content\/uploads\/2025\/06\/logo_nilex.svg","contentUrl":"https:\/\/new.nilex.se\/wp-content\/uploads\/2025\/06\/logo_nilex.svg","width":149,"height":25,"caption":"Nilex"},"image":{"@id":"https:\/\/nilex.se\/de\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/nilex.se\/de\/#\/schema\/person\/2f40d971d740db14580101a64f44c6f1","name":"nilex_admin","image":{"@type":"ImageObject","inLanguage":"de","@id":"https:\/\/secure.gravatar.com\/avatar\/1e15ff7dec39b2c16dc9c192a9b2240c4bf677fee8346ac0bbd267521712623d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1e15ff7dec39b2c16dc9c192a9b2240c4bf677fee8346ac0bbd267521712623d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1e15ff7dec39b2c16dc9c192a9b2240c4bf677fee8346ac0bbd267521712623d?s=96&d=mm&r=g","caption":"nilex_admin"},"sameAs":["https:\/\/new.nilex.se"],"url":"https:\/\/nilex.se\/de\/author\/nilex_admin\/"}]}},"_links":{"self":[{"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/posts\/9679","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/comments?post=9679"}],"version-history":[{"count":0,"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/posts\/9679\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/media\/9680"}],"wp:attachment":[{"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/media?parent=9679"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/categories?post=9679"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nilex.se\/de\/wp-json\/wp\/v2\/tags?post=9679"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}