{"id":21067,"date":"2026-10-15T11:27:47","date_gmt":"2026-10-15T11:27:47","guid":{"rendered":"https:\/\/greyson.eu\/?post_type=glossary&p=21067"},"modified":"2026-10-15T11:28:50","modified_gmt":"2026-10-15T11:28:50","slug":"change-management","status":"publish","type":"glossary","link":"https:\/\/greyson.eu\/cs\/glossary\/change-management\/","title":{"rendered":"Change management"},"content":{"rendered":"

Change management: Kompletn\u00ed pr\u016fvodce pro IT mana\u017eery a l\u00eddry digit\u00e1ln\u00ed transformace<\/h1>\n

Change management je strukturovan\u00e1 discipl\u00edna, kter\u00e1 organizaci i lidi v n\u00ed prov\u00e1z\u00ed z aktu\u00e1ln\u00edho stavu do \u017e\u00e1douc\u00edho budouc\u00edho stavu. Zahrnuje pl\u00e1nov\u00e1n\u00ed, komunikaci, \u0161kolen\u00ed a ukotven\u00ed zm\u011bny, kter\u00e9 jsou pot\u0159eba, aby se nov\u00e9 technologie, procesy nebo struktury skute\u010dn\u011b p\u0159ijaly a p\u0159inesly zam\u00fd\u0161lenou hodnotu. Pro CTO, IT mana\u017eery a vedouc\u00ed digit\u00e1ln\u00ed transformace rozhoduje change management o tom, zda migrace platformy, zaveden\u00ed ERP nebo transformace DevOps p\u0159inese obchodn\u00ed v\u00fdsledky, nebo uv\u00e1zne na odporu a p\u0159epracov\u00e1n\u00ed.<\/p>\n

Co je change management a odkud discipl\u00edna poch\u00e1z\u00ed?<\/h2>\n

Change management je proces \u0159\u00edzen\u00ed organiza\u010dn\u00ed zm\u011bny od prvn\u00ed my\u0161lenky a p\u0159\u00edpravy p\u0159es implementaci a\u017e po jej\u00ed uzav\u0159en\u00ed. Pojem ozna\u010duje jak mana\u017eerskou praxi, tak oblast v\u00fdzkumu. Jeho intelektu\u00e1ln\u00ed ko\u0159eny sahaj\u00ed do behavior\u00e1ln\u00ed v\u011bdy \u010dty\u0159ic\u00e1t\u00fdch let 20. stolet\u00ed, kdy psycholog Kurt Lewin navrhl t\u0159\u00edkrokov\u00fd model rozmrazen\u00ed, zm\u011bny a op\u011btovn\u00e9ho zmrazen\u00ed skupinov\u00e9ho chov\u00e1n\u00ed. Lewinova pr\u00e1ce polo\u017eila kl\u00ed\u010dov\u00fd p\u0159edpoklad: aby zm\u011bna obst\u00e1la, je t\u0159eba pohnout nejen syst\u00e9my, ale p\u0159edev\u0161\u00edm lidmi.<\/p>\n

Discipl\u00edna dozr\u00e1vala i v druh\u00e9 polovin\u011b 20. stolet\u00ed. Mana\u017eer\u0161t\u00ed konzultanti Thomas J. Peters a Robert H. Waterman, jejich\u017e pr\u00e1ce o organiza\u010dn\u00ed excelenci pozd\u011bji poslou\u017eila jako z\u00e1klad modelu McKinsey 7-S, uk\u00e1zali, \u017ee strategie a struktura samy o sob\u011b nevysv\u011btluj\u00ed, pro\u010d organizace p\u0159i zm\u011bn\u00e1ch usp\u011bj\u00ed nebo sel\u017eou. Profesor Harvardovy univerzity John Kotter formalizoval v devades\u00e1t\u00fdch letech osmikrokov\u00fd proces, kter\u00fd vych\u00e1zel ze spole\u010dn\u00fdch faktor\u016f \u00fasp\u011bchu \u0159ady vedouc\u00edch zm\u011bn. B\u011bhem zhruba posledn\u00edch dvaceti p\u011bti let se change management d\u00edky v\u00fdzkumem podlo\u017een\u00e9 praxi stal uzn\u00e1vanou profes\u00ed s certifikacemi, n\u00e1stroji a modely schopnost\u00ed pro podniky.<\/p>\n

Pro\u010d pojem nese dva v\u00fdznamy<\/h3>\n

V praxi se v\u00fdraz \u201echange management\u201c pou\u017e\u00edv\u00e1 ve dvou \u010d\u00e1ste\u010dn\u011b se p\u0159ekr\u00fdvaj\u00edc\u00edch v\u00fdznamech. Prvn\u00edm je organiza\u010dn\u00ed change management<\/em>, kter\u00fd se zam\u011b\u0159uje na lidskou str\u00e1nku zm\u011bny: pov\u011bdom\u00ed, zapojen\u00ed, dovednosti a p\u0159ijet\u00ed. Druh\u00fdm je IT change management<\/em>, praxe \u0159\u00edzen\u00ed IT slu\u017eeb, kter\u00e1 ur\u010duje, jak se zm\u011bny produk\u010dn\u00edch syst\u00e9m\u016f posuzuj\u00ed, schvaluj\u00ed a nasazuj\u00ed. R\u00e1mec IT Infrastructure Library (ITIL) 4 tyto v\u00fdznamy v\u00fdslovn\u011b odli\u0161uje. ITIL definuje organiza\u010dn\u00ed change management jako praxi zaji\u0161t\u011bn\u00ed hladk\u00e9 a \u00fasp\u011b\u0161n\u00e9 implementace zm\u011bn a dosa\u017een\u00ed trval\u00fdch p\u0159\u00ednos\u016f \u0159\u00edzen\u00edm lidsk\u00fdch aspekt\u016f zm\u011bny. \u0158\u00edzen\u00ed IT zm\u011bn pova\u017euje za samostatnou praxi zam\u011b\u0159enou na hodnocen\u00ed rizik a pl\u00e1nov\u00e1n\u00ed. Pro podnikov\u00e9 l\u00eddry jsou relevantn\u00ed oba v\u00fdznamy a tento \u010dl\u00e1nek se jim v\u011bnuje ob\u011bma.<\/p>\n

Co se pova\u017euje za organiza\u010dn\u00ed zm\u011bnu?<\/h3>\n

Organiza\u010dn\u00ed zm\u011bnou se rozum\u00ed ka\u017ed\u00e1 v\u00fdznamn\u00e1 \u00faprava zp\u016fsobu, jak\u00fdm firma funguje. M\u016f\u017ee se t\u00fdkat firemn\u00ed kultury, intern\u00edch proces\u016f, technologi\u00ed a infrastruktury, reportingov\u00e9 hierarchie nebo tr\u017en\u00edho postaven\u00ed. Harvard Business School rozli\u0161uje adaptivn\u00ed zm\u011bnu, kter\u00e1 je mal\u00e1, postupn\u00e1 a iterativn\u00ed, a transforma\u010dn\u00ed zm\u011bnu, kter\u00e1 je rozs\u00e1hlej\u0161\u00ed a \u010dasto z\u00e1sadn\u00ed. P\u0159ijmout \u010dlena t\u00fdmu, kter\u00fd zvl\u00e1dne rostouc\u00ed popt\u00e1vku, je adaptivn\u00ed zm\u011bna. Migrace j\u00e1drov\u00e9ho bankovn\u00edho syst\u00e9mu do cloudu nebo vstup na nov\u00fd n\u00e1rodn\u00ed trh je zm\u011bna transforma\u010dn\u00ed. Change management plat\u00ed pro ob\u011b, ale hloubka p\u0159\u00edpravy, sponzorstv\u00ed a \u0159\u00edzen\u00ed by m\u011bla r\u016fst s rozsahem zm\u011bny.<\/p>\n

Jak change management funguje v praxi?<\/h2>\n

Change management p\u016fsob\u00ed tak, \u017ee sou\u010dasn\u011b \u0159e\u0161\u00ed t\u0159i vz\u00e1jemn\u011b z\u00e1visl\u00e9 oblasti: lidi, jejich\u017e chov\u00e1n\u00ed se mus\u00ed zm\u011bnit, procesy, kter\u00e9 ur\u010duj\u00ed, jak se pr\u00e1ce vykon\u00e1v\u00e1, a technologie, kter\u00e1 nov\u00e9 zp\u016fsoby pr\u00e1ce umo\u017e\u0148uje, nebo omezuje. \u010castou chybou je ch\u00e1pat zm\u011bnu jako zaveden\u00ed technologie s p\u0159ipojen\u00fdm komunika\u010dn\u00edm pl\u00e1nem. Prosci, jeden z nejroz\u0161\u00ed\u0159en\u011bj\u0161\u00edch poskytovatel\u016f metodik, v\u00fdslovn\u011b varuje, \u017ee \u0159\u00edzen\u00ed zm\u011bny se \u010dasto redukuje na komunika\u010dn\u00ed pl\u00e1n, kter\u00fd jen ozn\u00e1m\u00ed, \u017ee n\u011bco p\u0159ich\u00e1z\u00ed. T\u00edm se vynech\u00e1 skute\u010dn\u00e1 pr\u00e1ce, tedy podpora lid\u00ed v jejich individu\u00e1ln\u00edch p\u0159echodech.<\/p>\n

Mechanismus lze popsat jako posloupnost navazuj\u00edc\u00edch \u010dinnost\u00ed: identifikovat rozd\u00edl mezi sou\u010dasn\u00fdm a \u017e\u00e1douc\u00edm stavem, posoudit dopad na lidi a syst\u00e9my, navrhnout z\u00e1sah, p\u0159ipravit a vybavit dot\u010den\u00e9 lidi, zm\u011bnu nasadit, ukotvit ji a m\u011b\u0159it, zda k p\u0159ijet\u00ed do\u0161lo. Ka\u017ed\u00e1 f\u00e1ze produkuje v\u00fdstupy, nap\u0159\u00edklad popis mezery, anal\u00fdzu dopad\u016f, mapu zainteresovan\u00fdch stran nebo p\u0159ehled adopce, kter\u00e9 vstupuj\u00ed do dal\u0161\u00ed f\u00e1ze.<\/p>\n

Kl\u00ed\u010dov\u00e9 f\u00e1ze procesu change managementu<\/h3>\n

V\u011bt\u0161ina vysp\u011bl\u00fdch r\u00e1mc\u016f se shoduje na podobn\u00e9 sad\u011b f\u00e1z\u00ed. N\u00e1sleduj\u00edc\u00ed tabulka porovn\u00e1v\u00e1, jak t\u0159i \u0161iroce citovan\u00e9 zdroje popisuj\u00ed \u017eivotn\u00ed cyklus, aby ho IT l\u00edd\u0159i mohli p\u0159en\u00e9st na sv\u016fj vlastn\u00ed model dod\u00e1vky.<\/p>\n\n\n\n\n\n\n\n\n\n
F\u00e1ze<\/th>\nHarvard Business School (5 krok\u016f)<\/th>\nModel digit\u00e1ln\u00ed zm\u011bny od IBM<\/th>\nPraktick\u00fd c\u00edl<\/th>\n<\/tr>\n<\/thead>\n
Identifikace pot\u0159eby<\/td>\nIdentifikovat v\u00fdkonnostn\u00ed nebo p\u0159\u00edle\u017eitostn\u00ed mezery<\/td>\nP\u0159\u00edprava: v\u00fdzkum, rozhovory a anal\u00fdza historick\u00fdch dat<\/td>\nOv\u011b\u0159it, \u017ee zm\u011bna \u0159e\u0161\u00ed skute\u010dnou a m\u011b\u0159itelnou mezeru<\/td>\n<\/tr>\n
Anal\u00fdza p\u0159\u00ed\u010din<\/td>\nDiagnostikovat ko\u0159enov\u00e9 p\u0159\u00ed\u010diny a strategickou nesoulad<\/td>\nObjevov\u00e1n\u00ed: hodnocen\u00ed dopad\u016f a pl\u00e1n cesty<\/td>\nPochopit, co brzd\u00ed postup, d\u0159\u00edve ne\u017e se navrhne \u0159e\u0161en\u00ed<\/td>\n<\/tr>\n
N\u00e1vrh a realizace<\/td>\nNavrhnout a realizovat zm\u011bnu po etap\u00e1ch<\/td>\nDod\u00e1n\u00ed: nasazen\u00ed postup\u016f, m\u011b\u0159en\u00ed v\u00fdsledk\u016f, \u0161kolen\u00ed u\u017eivatel\u016f<\/td>\nImplementovat v kontrolovan\u00fdch kroc\u00edch se zp\u011btnou vazbou<\/td>\n<\/tr>\n
P\u0159ipravenost<\/td>\n\u0158e\u0161it kulturn\u00ed p\u0159ipravenost a odpor<\/td>\nP\u0159echod: za\u0161kolen\u00ed, podpora a m\u011b\u0159en\u00ed p\u0159ijet\u00ed<\/td>\nPosunout lidi od pov\u011bdom\u00ed k aktivn\u00edmu pou\u017e\u00edv\u00e1n\u00ed<\/td>\n<\/tr>\n
Ukotven\u00ed<\/td>\nPos\u00edlit normy a odm\u011bny<\/td>\nRealizace a udr\u017een\u00ed: zplnomocn\u011bn\u00ed a pr\u016fb\u011b\u017en\u00e9 m\u011b\u0159en\u00ed<\/td>\nUkotvit zm\u011bnu tak, aby po spu\u0161t\u011bn\u00ed nezanikla<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Smyslem t\u00e9to posloupnosti nen\u00ed striktn\u00ed dodr\u017eov\u00e1n\u00ed. L\u00edd\u0159i zm\u011bn by se m\u011bli vracet zp\u011bt, kdy\u017e metriky p\u0159ijet\u00ed uk\u00e1\u017eou probl\u00e9m. IBM v\u00fdslovn\u011b doporu\u010duje p\u0159i ne\u00fasp\u011bchu transformace vr\u00e1tit se k f\u00e1z\u00edm objevov\u00e1n\u00ed a dod\u00e1n\u00ed a ch\u00e1pat \u017eivotn\u00ed cyklus jako cyklick\u00fd, nikoli line\u00e1rn\u00ed.<\/p>\n

Co zm\u011bnu udr\u017e\u00ed: p\u0159ijet\u00ed jako m\u011b\u0159\u00edtko \u00fasp\u011bchu<\/h3>\n

Nejd\u016fle\u017eit\u011bj\u0161\u00ed praktick\u00fd poznatek zn\u00ed: zm\u011bna nen\u00ed \u00fasp\u011b\u0161n\u00e1 ve chv\u00edli, kdy je nasazena. Je \u00fasp\u011b\u0161n\u00e1, kdy\u017e ji lid\u00e9 pou\u017e\u00edvaj\u00ed tak, jak byla zam\u00fd\u0161lena. V\u00fdzkum spole\u010dnosti Prosci, zalo\u017een\u00fd na pr\u016fzkumech mezi praktiky za v\u00edce ne\u017e dv\u011b desetilet\u00ed, uv\u00e1d\u00ed, \u017ee projekty s v\u00fdbornou \u0159\u00edzenou zm\u011bnou maj\u00ed 7x vy\u0161\u0161\u00ed pravd\u011bpodobnost spln\u011bn\u00ed c\u00edl\u016f, 4,6x vy\u0161\u0161\u00ed pravd\u011bpodobnost dodr\u017een\u00ed term\u00ednu a 1,4x vy\u0161\u0161\u00ed pravd\u011bpodobnost dodr\u017een\u00ed rozpo\u010dtu ve srovn\u00e1n\u00ed s projekty se slab\u00fdm change managementem. Harvardsk\u00e9 podklady odkazuj\u00ed na zji\u0161t\u011bn\u00ed Gartneru, podle n\u011bho\u017e jen 32 procent l\u00eddr\u016f v jejich posledn\u00ed iniciativ\u011b dos\u00e1hlo zdrav\u00e9ho p\u0159ijet\u00ed zam\u011bstnanci. Pro CTO je tato mezera mezi nasazen\u00edm a p\u0159ijet\u00edm m\u00edstem, kde se v\u011bt\u0161ina p\u0159\u00ednosu bu\u010f z\u00edsk\u00e1, nebo ztrat\u00ed.<\/p>\n

Kter\u00e9 modely \u0159\u00edzen\u00ed zm\u011bn by m\u011bli podnikov\u00ed l\u00edd\u0159i pou\u017e\u00edvat?<\/h2>\n

V podnikov\u00e9m prost\u0159ed\u00ed se vyu\u010duje a uplat\u0148uje n\u011bkolik model\u016f. \u017d\u00e1dn\u00fd nen\u00ed univerz\u00e1ln\u011b nad\u0159azen\u00fd. Ka\u017ed\u00fd nab\u00edz\u00ed jin\u00fd pohled: n\u011bkter\u00e9 popisuj\u00ed, jak lid\u00e9 p\u0159echod pro\u017e\u00edvaj\u00ed, jin\u00e9, jak by l\u00edd\u0159i m\u011bli \u0159adit kroky, a dal\u0161\u00ed, jak vz\u00e1jemn\u011b prov\u00e1zan\u00e9 faktory ovliv\u0148uj\u00ed schopnost organizace se m\u011bnit. Nej\u00fa\u010dinn\u011bj\u0161\u00ed l\u00edd\u0159i vol\u00ed model podle typu zm\u011bny, zralosti organizace a c\u00edlov\u00e9 skupiny.<\/p>\n

Lewin, Kotter a Bridges: po\u0159ad\u00ed a p\u0159echod<\/h3>\n

Lewin\u016fv model \u201erozmrazen\u00ed \u2013 zm\u011bna \u2013 zmrazen\u00ed\u201c je nejstar\u0161\u00ed a nejjednodu\u0161\u0161\u00ed. Jeho metafora p\u0159irovn\u00e1v\u00e1 organizaci k ledov\u00e9 kostce: lze ji p\u0159etvo\u0159it, ani\u017e praskne, pokud led nejprve rozpust\u00edme, nalijeme do nov\u00e9ho tvaru a znovu zmraz\u00edme. Z\u016fst\u00e1v\u00e1 u\u017eite\u010dn\u00fdm p\u0159ipomenut\u00edm, \u017ee na po\u0159ad\u00ed krok\u016f z\u00e1le\u017e\u00ed. Kotter\u016fv osmikrokov\u00fd proces tuto logiku p\u0159ev\u00e1d\u00ed do ak\u010dn\u00edho pl\u00e1nu, kter\u00fd za\u010d\u00edn\u00e1 vytvo\u0159en\u00edm pocitu nal\u00e9havosti a sestaven\u00edm vedouc\u00ed koalice a kon\u010d\u00ed upevn\u011bn\u00edm zm\u011bny. Model p\u0159echodu Williama Bridgese p\u0159esouv\u00e1 pozornost od samotn\u00e9 zm\u011bny k psychologick\u00e9mu p\u0159echodu, kter\u00fdm lid\u00e9 proch\u00e1zej\u00ed. Popisuje konce, neutr\u00e1ln\u00ed z\u00f3nu nejistoty a nov\u00e9 za\u010d\u00e1tky. Bridges\u016fv model je zvl\u00e1\u0161\u0165 cenn\u00fd, kdy\u017e zm\u011bna ru\u0161\u00ed role nebo zn\u00e1m\u00e9 rutiny, proto\u017ee vysv\u011btluje, pro\u010d produktivita \u010dasto klesne d\u0159\u00edv, ne\u017e se zotav\u00ed.<\/p>\n

ADKAR a metodika Prosci: individu\u00e1ln\u00ed p\u0159ijet\u00ed<\/h3>\n

Model ADKAR, sou\u010d\u00e1st metodiky Prosci, se zam\u011b\u0159uje na jednotlivce, nikoli na organizaci. Jeho p\u011bt stavebn\u00edch kamen\u016f jsou pov\u011bdom\u00ed o pot\u0159eb\u011b zm\u011bny, touha se zapojit a zm\u011bnu podpo\u0159it, znalost toho, jak se zm\u011bnit, schopnost osvojit si nov\u00e9 dovednosti a chov\u00e1n\u00ed a pos\u00edlen\u00ed, kter\u00e9 zm\u011bnu udr\u017e\u00ed. ADKAR je diagnostick\u00fd n\u00e1stroj: l\u00eddr zm\u011bny dok\u00e1\u017ee zjistit, kter\u00fd prvek u dan\u00e9 skupiny chyb\u00ed, a zac\u00edlit z\u00e1sah. N\u00edzk\u00e9 sk\u00f3re v oblasti Desire vy\u017eaduje zapojen\u00ed sponzor\u016f a jasn\u00e9 vysv\u011btlen\u00ed osobn\u00edho p\u0159\u00ednosu, n\u00edzk\u00e9 sk\u00f3re v oblasti Ability naopak praktick\u00fd n\u00e1cvik a kou\u010dink. Metodika Prosci d\u00e1le zahrnuje Prosci Change Triangle, kter\u00fd stav\u00ed sponzorstv\u00ed, \u0159\u00edzen\u00ed projekt\u016f a change management jako vz\u00e1jemn\u011b z\u00e1visl\u00e9 hnac\u00ed s\u00edly \u00fasp\u011bchu.<\/p>\n

McKinsey 7-S a ITIL: organiza\u010dn\u00ed a provozn\u00ed r\u00e1mce<\/h3>\n

Model McKinsey 7-S popisuje sedm vz\u00e1jemn\u011b z\u00e1visl\u00fdch prvk\u016f: sd\u00edlen\u00e9 hodnoty, dovednosti, zam\u011bstnance, strategii, strukturu, styl \u0159\u00edzen\u00ed a syst\u00e9my. Je neju\u017eite\u010dn\u011bj\u0161\u00ed p\u0159i diagnostice toho, pro\u010d strategick\u00e1 iniciativa nenabrala tempo, proto\u017ee ukazuje, \u017ee zm\u011bna jednoho prvku, nap\u0159\u00edklad nov\u00e9 strategie, nebude \u00fasp\u011b\u0161n\u00e1, pokud z\u016fstanou beze zm\u011bny struktura a syst\u00e9my. ITIL je naproti tomu provozn\u00ed r\u00e1mec pro \u0159\u00edzen\u00ed IT slu\u017eeb. Jeho praxe change enablement \u0159\u00edd\u00ed, jak se IT zm\u011bny autorizuj\u00ed a nasazuj\u00ed, a je nejroz\u0161\u00ed\u0159en\u011bj\u0161\u00edm referen\u010dn\u00edm r\u00e1mcem pro t\u00fdmy IT provozu.<\/p>\n

Srovn\u00e1n\u00ed hlavn\u00edch model\u016f<\/h3>\n\n\n\n\n\n\n\n\n\n\n
Model<\/th>\nP\u016fvod<\/th>\nHlavn\u00ed zam\u011b\u0159en\u00ed<\/th>\nNejvhodn\u011bj\u0161\u00ed pro<\/th>\n<\/tr>\n<\/thead>\n
Lewinovo rozmrazen\u00ed \u2013 zm\u011bna \u2013 zmrazen\u00ed<\/td>\nKurt Lewin, 40. l\u00e9ta 20. stolet\u00ed<\/td>\nEtapov\u00fd p\u0159echod chov\u00e1n\u00ed skupiny<\/td>\nVysv\u011btlen\u00ed, pro\u010d je t\u0159eba zm\u011bnu \u010dasov\u011b \u0159adit a ukotvit<\/td>\n<\/tr>\n
Kotter\u016fv osmikrokov\u00fd proces<\/td>\nJohn Kotter, Harvard, 90. l\u00e9ta<\/td>\nVeden\u00ed a po\u0159ad\u00ed krok\u016f<\/td>\nVelk\u00e9 transformace veden\u00e9 skupinou sponzor\u016f<\/td>\n<\/tr>\n
Bridges\u016fv model p\u0159echodu<\/td>\nWilliam Bridges<\/td>\nPsychologick\u00e1 reakce na zm\u011bnu<\/td>\nZm\u011bny, kter\u00e9 ru\u0161\u00ed role nebo zn\u00e1m\u00e9 rutiny<\/td>\n<\/tr>\n
ADKAR<\/td>\nProsci<\/td>\nIndividu\u00e1ln\u00ed p\u0159ijet\u00ed<\/td>\nDiagnostika p\u0159ipravenosti a c\u00edlen\u00fd kou\u010dink<\/td>\n<\/tr>\n
McKinsey 7-S<\/td>\nMcKinsey, vych\u00e1z\u00ed z prac\u00ed 70. a 80. let<\/td>\nVz\u00e1jemn\u011b z\u00e1visl\u00e9 organiza\u010dn\u00ed prvky<\/td>\nDiagnostika, pro\u010d strategick\u00e1 zm\u011bna uv\u00e1zla<\/td>\n<\/tr>\n
ITIL change enablement<\/td>\nAxelos (ITIL 4)<\/td>\nAutorizace a riziko IT zm\u011bn<\/td>\n\u0158\u00edzen\u00ed produk\u010dn\u00edch zm\u011bn v IT provozu<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\u010c\u00edm se change management li\u0161\u00ed od \u0159\u00edzen\u00ed projekt\u016f a \u0159\u00edzen\u00ed IT zm\u011bn?<\/h2>\n

Change management se \u010dasto zam\u011b\u0148uje s \u0159\u00edzen\u00edm projekt\u016f a s \u0159\u00edzen\u00edm IT zm\u011bn. Tyto t\u0159i discipl\u00edny se vz\u00e1jemn\u011b dopl\u0148uj\u00ed a selh\u00e1vaj\u00ed r\u016fzn\u00fdmi zp\u016fsoby, pokud je jedna pova\u017eov\u00e1na za druhou. \u0158\u00edzen\u00ed projektu odpov\u00edd\u00e1 za rozsah, harmonogram, rozpo\u010det a dod\u00e1n\u00ed technick\u00e9ho \u0159e\u0161en\u00ed. Change management odpov\u00edd\u00e1 za lidskou str\u00e1nku: zda u\u017eivatel\u00e9 zm\u011bnu ch\u00e1pou, jsou ochotni ji p\u0159ijmout, v\u011bd\u00ed, jak ji pou\u017e\u00edvat, a jsou podporov\u00e1ni, aby ji udr\u017eeli. \u0158\u00edzen\u00ed IT zm\u011bn, v ITIL 4 ozna\u010dovan\u00e9 jako change enablement, odpov\u00edd\u00e1 za governance \u00faprav produk\u010dn\u00edch slu\u017eeb, v\u010detn\u011b hodnocen\u00ed rizik, schvalov\u00e1n\u00ed a pl\u00e1nov\u00e1n\u00ed.<\/p>\n

Rozd\u00edl je d\u016fle\u017eit\u00fd, proto\u017ee projekt m\u016f\u017ee b\u00fdt dod\u00e1n v\u010das a v rozpo\u010dtu, zat\u00edmco firma v\u00fdsledek nep\u0159ijme. Naopak dob\u0159e p\u0159ijat\u00e1 zm\u011bna m\u016f\u017ee b\u00fdt \u0161patn\u011b \u0159\u00edzena, pokud se IT zm\u011bny nekontroluj\u00ed. Prosci popisuje vztah jako dv\u011b kl\u00ed\u010dov\u00e9 role pro \u00fasp\u011bch zm\u011bny: \u0159\u00edzen\u00ed projektu se soust\u0159ed\u00ed na technickou str\u00e1nku, change management na lidskou str\u00e1nku.<\/p>\n\n\n\n\n\n\n\n\n
Dimenze<\/th>\n\u0158\u00edzen\u00ed projektu<\/th>\nChange management<\/th>\n\u0158\u00edzen\u00ed IT zm\u011bn (change enablement)<\/th>\n<\/tr>\n<\/thead>\n
Hlavn\u00ed ot\u00e1zka<\/td>\nJe \u0159e\u0161en\u00ed dod\u00e1no podle pl\u00e1nu?<\/td>\nJsou lid\u00e9 p\u0159ipraveni, ochotni a schopni je p\u0159ijmout?<\/td>\nJe tato \u00faprava bezpe\u010dn\u00e1 pro nasazen\u00ed do produkce?<\/td>\n<\/tr>\n
Hlavn\u00ed v\u00fdstupy<\/td>\nPl\u00e1n, harmonogram, rozpo\u010det, rozsah a dod\u00e1vky<\/td>\nAnal\u00fdza dopad\u016f, pl\u00e1n zainteresovan\u00fdch stran, \u0161kolen\u00ed a ukotven\u00ed<\/td>\n\u017d\u00e1dosti o zm\u011bnu, hodnocen\u00ed rizik, schv\u00e1len\u00ed a z\u00e1znamy o uzav\u0159en\u00ed<\/td>\n<\/tr>\n
Typick\u00fd odpov\u011bdn\u00fd<\/td>\nVedouc\u00ed projektu nebo programu<\/td>\nMana\u017eer zm\u011bny nebo praktik change managementu<\/td>\nMana\u017eer zm\u011bny, CAB nebo ur\u010den\u00e1 autorita pro zm\u011bny<\/td>\n<\/tr>\n
Ukazatel \u00fasp\u011bchu<\/td>\nDodan\u00fd rozsah, \u010das a n\u00e1klady<\/td>\nP\u0159ijet\u00ed a zdatnost<\/td>\nM\u00e9n\u011b incident\u016f a ne\u00fasp\u011b\u0161n\u00fdch zm\u011bn<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Co je IT change management a jak se zm\u011bny klasifikuj\u00ed?<\/h2>\n

IT change management je praxe pl\u00e1nov\u00e1n\u00ed, schvalov\u00e1n\u00ed a nasazov\u00e1n\u00ed zm\u011bn IT slu\u017eeb s minim\u00e1ln\u00edm rizikem a naru\u0161en\u00edm. Spole\u010dnost Atlassian ji popisuje jako praxi navr\u017eenou tak, aby minimalizovala naru\u0161en\u00ed IT slu\u017eeb p\u0159i prov\u00e1d\u011bn\u00ed zm\u011bn na kritick\u00fdch syst\u00e9mech. Zm\u011bnou je v tomto kontextu jak\u00e9koli p\u0159id\u00e1n\u00ed, \u00faprava nebo odebr\u00e1n\u00ed n\u011b\u010deho, co m\u016f\u017ee m\u00edt p\u0159\u00edm\u00fd nebo nep\u0159\u00edm\u00fd vliv na slu\u017eby. Pat\u0159\u00ed sem infrastruktura, aplikace, konfigurace a st\u00e1le \u010dast\u011bji i k\u00f3d a pipeline.<\/p>\n

Praxe vznik\u00e1 proto, \u017ee organizace \u010del\u00ed dv\u011bma protich\u016fdn\u00fdm o\u010dek\u00e1v\u00e1n\u00edm. Pot\u0159ebuj\u00ed stabiln\u00ed a spolehliv\u00e9 slu\u017eby, kter\u00e9 udr\u017e\u00ed u\u017eivatele produktivn\u00ed, a z\u00e1rove\u0148 \u010dast\u00e9 aktualizace, aby reagovaly na m\u011bn\u00edc\u00ed se po\u017eadavky na bezpe\u010dnost, n\u00e1klady a obchodn\u00ed model. Selh\u00e1n\u00ed v kter\u00e9mkoli sm\u011bru je drah\u00e9. Gartner odhadl, \u017ee v\u00fdpadek m\u016f\u017ee firmu st\u00e1t v\u00edce ne\u017e 300 000 dolar\u016f za hodinu, u webov\u00fdch slu\u017eeb i v\u00fdrazn\u011b v\u00edce. Dob\u0159e \u0159\u00edzen\u00fd change management tento konflikt \u0159e\u0161\u00ed t\u00edm, \u017ee zm\u011bny \u010din\u00ed dostate\u010dn\u011b bezpe\u010dn\u00fdmi na to, aby byly \u010dast\u00e9.<\/p>\n

Standardn\u00ed, b\u011b\u017en\u00e9 a havarijn\u00ed zm\u011bny<\/h3>\n

ITIL definuje t\u0159i typy zm\u011bn a jejich za\u0159azen\u00ed ur\u010duje, kolik governance ka\u017ed\u00e1 zm\u011bna dostane. Jedin\u00e1 schvalovac\u00ed cesta pro v\u0161echny zm\u011bny je nej\u010dast\u011bj\u0161\u00ed p\u0159\u00ed\u010dinou \u00fazk\u00fdch m\u00edst.<\/p>\n\n\n\n\n\n\n\n
Typ zm\u011bny<\/th>\nDefinice<\/th>\nSchvalovac\u00ed cesta<\/th>\nP\u0159\u00edklad<\/th>\n<\/tr>\n<\/thead>\n
Standardn\u00ed zm\u011bna<\/td>\nN\u00edzk\u00e9 riziko, opakovateln\u00e1 a p\u0159edem schv\u00e1len\u00e1 zm\u011bna podle zdokumentovan\u00e9ho postupu<\/td>\nP\u0159edem schv\u00e1leno; vhodn\u00e9 k automatizaci<\/td>\nP\u0159id\u00e1n\u00ed pam\u011bti nebo \u00falo\u017ei\u0161t\u011b; vytvo\u0159en\u00ed nov\u00e9 instance datab\u00e1ze<\/td>\n<\/tr>\n
B\u011b\u017en\u00e1 zm\u011bna<\/td>\nNenal\u00e9hav\u00e1 zm\u011bna bez p\u0159edem schv\u00e1len\u00e9ho postupu<\/td>\nHodnocen\u00ed rizik, pot\u00e9 CAB nebo ur\u010den\u00e1 autorita podle rizika<\/td>\nP\u0159esun do nov\u00e9ho datov\u00e9ho centra; upgrade syst\u00e9mu pro spr\u00e1vu obsahu<\/td>\n<\/tr>\n
Havarijn\u00ed zm\u011bna<\/td>\nNutn\u00e1 okam\u017eit\u011b k obnoven\u00ed slu\u017eby nebo \u0159e\u0161en\u00ed bezpe\u010dnostn\u00ed hrozby<\/td>\nZrychlen\u00e9 schv\u00e1len\u00ed s dodate\u010dn\u00fdm p\u0159ezkumem<\/td>\nNasazen\u00ed kritick\u00e9 bezpe\u010dnostn\u00ed z\u00e1platy; \u0159e\u0161en\u00ed z\u00e1va\u017en\u00e9ho v\u00fdpadku<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Je change advisory board je\u0161t\u011b funk\u010dn\u00ed?<\/h3>\n

Change advisory board (CAB) je skupina, kter\u00e1 posuzuje riziko navrhovan\u00fdch zm\u011bn a schvaluje je, nebo zam\u00edt\u00e1. V tradi\u010dn\u00edch IT organizac\u00edch se CAB pravideln\u011b sch\u00e1z\u00ed, aby pro\u0161lo v\u0161echny nadch\u00e1zej\u00edc\u00ed zm\u011bny, a podle pot\u0159eby p\u0159iz\u00fdv\u00e1 odborn\u00edky. CAB poskytuje cennou kontrolu rizik, zejm\u00e9na u zm\u011bn s velk\u00fdm dopadem, jako je p\u0159epnut\u00ed datov\u00e9ho centra. Pokud v\u0161ak jeho \u010dlenov\u00e9 jsou daleko od m\u011bn\u011bn\u00fdch syst\u00e9m\u016f, st\u00e1v\u00e1 se \u00fazk\u00fdm hrdlem, kter\u00e9 zpomaluje dod\u00e1vky, ani\u017e zvy\u0161uje bezpe\u010dnost.<\/p>\n

Modern\u00ed praxe omezuje p\u0159ezkum CAB na nejrizikov\u011bj\u0161\u00ed a strategicky nejd\u016fle\u017eit\u011bj\u0161\u00ed zm\u011bny. ITIL 4 doporu\u010duje decentralizovat pravomoc schvalovat zm\u011bny na \u00farove\u0148 obchodn\u00edch stakeholder\u016f a koleg\u016f, zat\u00edmco automatizace, virtu\u00e1ln\u00ed kontroln\u00ed seznamy a peer review zvl\u00e1daj\u00ed zm\u011bny s ni\u017e\u0161\u00edm rizikem. CAB se tak st\u00e1v\u00e1 poradn\u00edm org\u00e1nem, kter\u00fd sleduje trendy a koordinuje t\u00fdmy, a nikoli br\u00e1nou, kterou mus\u00ed proj\u00edt ka\u017ed\u00e1 zm\u011bna.<\/p>\n

Jak aplikovat change management v podnikov\u00e9 IT a digit\u00e1ln\u00edch projektech?<\/h2>\n

Podnikov\u00fd change management je nejviditeln\u011bj\u0161\u00ed u velk\u00fdch technologick\u00fdch program\u016f: zaveden\u00ed ERP, migrace do cloudu, v\u00fdm\u011bna CRM, modernizace datov\u00fdch platforem a zav\u00e1d\u011bn\u00ed DevOps. V ka\u017ed\u00e9m z t\u011bchto p\u0159\u00edpad\u016f je technologii nejsnaz\u0161\u00ed definovat. Obt\u00ed\u017en\u00e9 je zm\u011bnit, jak lid\u00e9 pl\u00e1nuj\u00ed, rozhoduj\u00ed, p\u0159ed\u00e1vaj\u00ed pr\u00e1ci a m\u011b\u0159\u00ed v\u00fdkon.<\/p>\n

Vezm\u011bme zaveden\u00ed ERP nap\u0159\u00ed\u010d n\u011bkolika dce\u0159in\u00fdmi spole\u010dnostmi. Projektov\u00fd t\u00fdm m\u016f\u017ee dodat funk\u010dn\u00ed syst\u00e9m v\u010das, a p\u0159esto finan\u010dn\u00ed odd\u011blen\u00ed d\u00e1l vedou paraleln\u00ed tabulky, proto\u017ee nev\u011b\u0159\u00ed nov\u00e9 logice reportingu. P\u0159\u00edstup zam\u011b\u0159en\u00fd na zm\u011bnu by tyto stakeholdery identifikoval v\u010das, zapojil je do n\u00e1vrhov\u00fdch rozhodnut\u00ed, definoval standardy zdatnosti pro ka\u017edou roli a propojil ukotven\u00ed s hodnocen\u00edm v\u00fdkonu. V\u00fdsledkem je p\u0159ijet\u00ed, nikoli jen spu\u0161t\u011bn\u00ed.<\/p>\n

Stejn\u00e1 logika plat\u00ed pro DevOps a \u0159\u00edzen\u00ed releas\u016f. Atlassian upozor\u0148uje, \u017ee tradi\u010dn\u00ed release management m\u016f\u017ee agiln\u00edm t\u00fdm\u016fm p\u016fsobit t\u0159en\u00ed a \u017ee modern\u00ed praxe sm\u011b\u0159uje k integraci, automatizaci a kontinu\u00e1ln\u00edmu doru\u010dov\u00e1n\u00ed. P\u0159echod na tento model je zm\u011bnou rol\u00ed, odpov\u011bdnost\u00ed a zodpov\u011bdnosti, nikoli jen n\u00e1stroj\u016f. T\u00fdmy mus\u00ed ch\u00e1pat princip \u201ekdo stav\u00ed, ten provozuje\u201c, v\u011b\u0159it automatizovan\u00fdm kontrol\u00e1m a p\u0159ijmout nov\u00e9 formy dohledu.<\/p>\n

Hodnocen\u00ed p\u0159ipravenosti a odporu<\/h3>\n

P\u0159ed spu\u0161t\u011bn\u00edm zm\u011bny by l\u00edd\u0159i m\u011bli posoudit p\u0159ipravenost organizace: s\u00edlu sponzorstv\u00ed, zku\u0161enosti se zm\u011bnami, kapacitu kl\u00ed\u010dov\u00fdch t\u00fdm\u016f a m\u00edru, v jak\u00e9 zm\u011bna koliduje se st\u00e1vaj\u00edc\u00edmi pob\u00eddkami. Odpor je z\u0159\u00eddka iracion\u00e1ln\u00ed. Obvykle signalizuje nejasn\u00fd p\u0159\u00ednos, nedostate\u010dn\u00e9 zapojen\u00ed nebo konkuren\u010dn\u00ed priority. Harvardsk\u00fd kurz Leading Change doporu\u010duje k jeho \u0159e\u0161en\u00ed model LEASH s p\u011bti p\u00e1\u010dkami: jedn\u00e1n\u00ed veden\u00ed, zapojen\u00ed zam\u011bstnanc\u016f, slad\u011bn\u00e9 odm\u011bny, sign\u00e1ly, p\u0159\u00edb\u011bhy a symboly a slad\u011bn\u00ed HR syst\u00e9m\u016f. Model LEASH vn\u00edm\u00e1 odpor jako \u00falohu n\u00e1vrhu, kterou mohou l\u00edd\u0159i ovlivnit konzistentn\u00edm chov\u00e1n\u00edm a posilov\u00e1n\u00edm.<\/p>\n

Praktick\u00e9 jsou pro IT l\u00eddry i Harvardsk\u00e9 doporu\u010den\u00ed k popisu mezery. Dobr\u00fd popis mezery m\u00e1 \u010dty\u0159i vlastnosti: jasnou odpov\u011bdnost, vymezen\u00fd \u010das a rozsah, smyslupln\u00fd p\u0159\u00ednos a m\u011b\u0159iteln\u00e1 krit\u00e9ria \u00fasp\u011bchu. Zm\u011bna, kter\u00e1 tyto testy neobstoj\u00ed, \u010dasto nebude udr\u017eena.<\/p>\n

Pokud va\u0161e organizace p\u0159ipravuje v\u00fdznamn\u00fd technologick\u00fd p\u0159echod, m\u016f\u017ee v\u00e1m konzulta\u010dn\u00ed t\u00fdm Greyson<\/a> pomoci posoudit p\u0159ipravenost, navrhnout pl\u00e1n zm\u011bny a sladit IT governance s lidskou str\u00e1nkou realizace.<\/p>\n

Jak\u00e9 jsou nej\u010dast\u011bj\u0161\u00ed myln\u00e9 p\u0159edstavy o change managementu?<\/h2>\n

N\u011bkolik myln\u00fdch p\u0159edstav pravideln\u011b podkop\u00e1v\u00e1 zm\u011bnov\u00e9 programy. Prvn\u00ed je p\u0159esv\u011bd\u010den\u00ed, \u017ee komunikace je change management. Ozn\u00e1men\u00ed informuj\u00ed, ale lidi nep\u0159ipravuj\u00ed, nevybavuj\u00ed ani nepodporuj\u00ed. Druhou je p\u0159edstava, \u017ee samotn\u00e9 sponzorstv\u00ed veden\u00ed zaru\u010d\u00ed p\u0159ijet\u00ed. IBM ve sv\u00fdch doporu\u010den\u00edch k osv\u011bd\u010den\u00fdm postup\u016fm v\u00fdslovn\u011b uv\u00e1d\u00ed, \u017ee p\u0159ijet\u00ed zam\u011bstnanci je stejn\u011b d\u016fle\u017eit\u00e9 jako sponzorstv\u00ed veden\u00ed, proto\u017ee p\u0159ijet\u00ed vznik\u00e1 v ka\u017edodenn\u00ed pr\u00e1ci, nikoli v zasedac\u00edch m\u00edstnostech. T\u0159et\u00ed p\u0159edpoklad zn\u00ed, \u017ee schv\u00e1len\u00fd pl\u00e1n zm\u011bny by se m\u011bl prov\u00e9st bez \u00faprav. \u00da\u010dinn\u00ed l\u00edd\u0159i zm\u011bn s pl\u00e1nem zach\u00e1zej\u00ed jako s p\u0159izp\u016fsobiteln\u00fdm a upravuj\u00ed jej podle dat o p\u0159ijet\u00ed.<\/p>\n

\u010ctvrt\u00e1 myln\u00e1 p\u0159edstava se t\u00fdk\u00e1 p\u0159\u00edmo IT. Mnoho organizac\u00ed p\u0159edpokl\u00e1d\u00e1, \u017ee p\u0159\u00edsn\u011bj\u0161\u00ed \u0159\u00edzen\u00ed zm\u011bn sni\u017euje riziko. V praxi nadm\u011brn\u00e9 procesy \u010dasto vedou t\u00fdmy k obch\u00e1zen\u00ed governance a vznikaj\u00ed nezaznamenan\u00e9 zm\u011bny, kter\u00e9 jsou skute\u010dnou p\u0159\u00ed\u010dinou incident\u016f. Atlassian zast\u00e1v\u00e1 n\u00e1zor, \u017ee change management m\u00e1 b\u00fdt jednoduch\u00fd a zalo\u017een\u00fd na riziku, s c\u00edlem m\u00e9n\u011b incident\u016f a men\u0161\u00ed z\u00e1t\u011b\u017ee t\u00fdm\u016f, nikoli v\u00edce pap\u00edrov\u00e1n\u00ed. P\u00e1t\u00e1 myln\u00e1 p\u0159edstava \u0159\u00edk\u00e1, \u017ee change management je jednor\u00e1zov\u00e1 aktivita. Ukotven\u00ed, tedy posilov\u00e1n\u00ed, m\u011b\u0159en\u00ed a p\u0159ed\u00e1v\u00e1n\u00ed znalost\u00ed nov\u00fdm koleg\u016fm, je jeho ned\u00edlnou sou\u010d\u00e1st\u00ed.<\/p>\n

Jak\u00e1 je budoucnost change managementu v digit\u00e1ln\u00ed \u00e9\u0159e?<\/h2>\n

Budoucnost change managementu formuj\u00ed t\u0159i s\u00edly: tempo zm\u011bn, rostouc\u00ed v\u00fdznam datov\u011b podlo\u017een\u00fdch rozhodnut\u00ed a roz\u0161i\u0159ov\u00e1n\u00ed um\u011bl\u00e9 inteligence do technologi\u00ed i do n\u00e1vrhu pr\u00e1ce. Organizace dnes \u010del\u00ed \u010dast\u011bj\u0161\u00edm a slo\u017eit\u011bj\u0161\u00edm zm\u011bn\u00e1m ne\u017e d\u0159\u00edve, a proto je opakovateln\u00e1 schopnost zm\u011bny cenn\u011bj\u0161\u00ed ne\u017e jednotliv\u00e9 projekty zm\u011bny. Prosci to popisuje jako enterprise change management, tedy systematick\u00e9 nasazen\u00ed dovednost\u00ed, n\u00e1stroj\u016f a proces\u016f pro zm\u011bnu nap\u0159\u00ed\u010d organizac\u00ed, tak\u017ee kapacita na zm\u011bnu se buduje, nikoli improvizuje.<\/p>\n

Agiln\u00ed, iterativn\u00ed a datov\u011b \u0159\u00edzen\u00e1 zm\u011bna<\/h3>\n

IBM tvrd\u00ed, \u017ee digit\u00e1ln\u00ed change management by m\u011bl b\u00fdt agiln\u00ed a iterativn\u00ed a vyu\u017e\u00edvat design thinking k navrhov\u00e1n\u00ed empati\u010dt\u011bj\u0161\u00edch cest zm\u011bny. Jeho t\u0159i hnac\u00ed s\u00edly, personalizovan\u00e9, zes\u00edlen\u00e9 a m\u011b\u0159iteln\u00e9, odr\u00e1\u017eej\u00ed p\u0159echod od jednor\u00e1zov\u00e9 komunikace ke kontinu\u00e1ln\u00edmu zapojen\u00ed s jasn\u00fdmi metrikami. Kl\u00ed\u010dov\u00e9 ukazatele v\u00fdkonu a m\u011b\u0159en\u00ed p\u0159ijet\u00ed ukazuj\u00ed l\u00eddr\u016fm, kde zm\u011bna funguje a kde pot\u0159ebuje podporu. Tento p\u0159\u00edstup dob\u0159e zapad\u00e1 do dod\u00e1vkov\u00fdch model\u016f, kter\u00e9 mnoho podnik\u016f ji\u017e pou\u017e\u00edv\u00e1, a usnad\u0148uje integraci zm\u011bny do sprintov\u00fdch reviz\u00ed, release cykl\u016f a programov\u00e9ho \u0159\u00edzen\u00ed.<\/p>\n

Zm\u011bna podpo\u0159en\u00e1 AI a automatizovan\u00e1 governance<\/h3>\n

Automatizace m\u011bn\u00ed governance IT zm\u011bn. Atlassian uv\u00e1d\u00ed, \u017ee n\u011bkter\u00e9 organizace mohou automatizovat a\u017e 70 procent standardn\u00edch zm\u011bn, a uvolnit tak t\u00fdmy pro b\u011b\u017en\u00e9 a havarijn\u00ed pr\u00e1ce. AI p\u0159id\u00e1v\u00e1 dal\u0161\u00ed mo\u017enosti: prediktivn\u00ed anal\u00fdzu rizika zm\u011bn na z\u00e1klad\u011b historick\u00fdch incident\u016f, automatizovan\u00e9 hodnocen\u00ed dopad\u016f a personalizovan\u00e9 vzd\u011bl\u00e1vac\u00ed cesty pro zam\u011bstnance, kte\u0159\u00ed se p\u0159izp\u016fsobuj\u00ed nov\u00fdm syst\u00e9m\u016fm. Lidsk\u00fd rozm\u011br v\u0161ak z\u016fst\u00e1v\u00e1 rozhoduj\u00edc\u00ed. Technologie m\u016f\u017ee zm\u011bnu urychlit, p\u0159ijet\u00ed ale st\u00e1le z\u00e1vis\u00ed na d\u016fv\u011b\u0159e, dovednostech a chov\u00e1n\u00ed veden\u00ed. Organizace, kter\u00e9 automatizuj\u00ed governanci bez investic do lidsk\u00e9 str\u00e1nky, z\u00edskaj\u00ed rychlej\u0161\u00ed nasazen\u00ed a pomalej\u0161\u00ed p\u0159ijet\u00ed.<\/p>\n

Trval\u00e9 ponau\u010den\u00ed pro podnikov\u00e9 l\u00eddry zn\u00ed: change management je schopnost, nikoli f\u00e1ze projektu. Organizace, kter\u00e9 ji buduj\u00ed z\u00e1m\u011brn\u011b, s jasn\u00fdmi modely, m\u011b\u0159iteln\u00fdmi c\u00edli p\u0159ijet\u00ed, governance zalo\u017eenou na riziku a viditeln\u00fdm sponzorstv\u00edm, budou l\u00e9pe p\u0159ipraveny zvl\u00e1dnout kontinu\u00e1ln\u00ed zm\u011bnu, kterou digit\u00e1ln\u00ed transformace vy\u017eaduje.<\/p>\n

Na co se IT mana\u017ee\u0159i nej\u010dast\u011bji ptaj\u00ed ohledn\u011b change managementu?<\/h2>\n

Co je change management jednodu\u0161e \u0159e\u010deno?<\/h3>\n

Change management je strukturovan\u00fd p\u0159\u00edstup, jak p\u0159esunout lidi a organizace z dosavadn\u00edho zp\u016fsobu pr\u00e1ce do nov\u00e9ho. P\u0159ipravuje lidi na zm\u011bnu, prov\u00e1z\u00ed je p\u0159echodem a zm\u011bnu ukotvuje, aby vydr\u017eela. V IT se tento pojem nav\u00edc pou\u017e\u00edv\u00e1 pro proces governance, kter\u00fd \u0159\u00edd\u00ed, jak se schvaluj\u00ed a nasazuj\u00ed zm\u011bny syst\u00e9m\u016f.<\/p>\n

Jak\u00e9 jsou hlavn\u00ed kroky procesu change managementu?<\/h3>\n

V\u011bt\u0161ina r\u00e1mc\u016f sleduje p\u011bt hrub\u00fdch f\u00e1z\u00ed: identifikovat v\u00fdkonnostn\u00ed nebo p\u0159\u00edle\u017eitostn\u00ed mezeru, diagnostikovat ko\u0159enov\u00e9 p\u0159\u00ed\u010diny, navrhnout a realizovat zm\u011bnu po etap\u00e1ch, \u0159e\u0161it kulturn\u00ed p\u0159ipravenost a odpor a zm\u011bnu udr\u017eet pomoc\u00ed posilov\u00e1n\u00ed a m\u011b\u0159en\u00ed. Posloupnost by se m\u011bla ch\u00e1pat iterativn\u011b, a kdy\u017e data o p\u0159ijet\u00ed uk\u00e1\u017eou probl\u00e9m, l\u00edd\u0159i se vracej\u00ed k d\u0159\u00edv\u011bj\u0161\u00edm f\u00e1z\u00edm.<\/p>\n

\u010c\u00edm se change management li\u0161\u00ed od \u0159\u00edzen\u00ed projekt\u016f?<\/h3>\n

\u0158\u00edzen\u00ed projektu dod\u00e1v\u00e1 technick\u00e9 \u0159e\u0161en\u00ed v r\u00e1mci rozsahu, harmonogramu a rozpo\u010dtu. Change management zaji\u0161\u0165uje, \u017ee lid\u00e9 toto \u0159e\u0161en\u00ed p\u0159ijmou a efektivn\u011b pou\u017e\u00edvaj\u00ed. Projekt m\u016f\u017ee splnit v\u0161echny dodac\u00ed c\u00edle a p\u0159esto selhat, pokud firma v\u00fdsledek nep\u0159ijme, proto jsou v podnikov\u00fdch programech pot\u0159eba ob\u011b discipl\u00edny.<\/p>\n

Jak\u00e9 existuj\u00ed typy IT zm\u011bn?<\/h3>\n

ITIL definuje t\u0159i typy: standardn\u00ed zm\u011bny, kter\u00e9 jsou n\u00edzkorizikov\u00e9 a p\u0159edem schv\u00e1len\u00e9; b\u011b\u017en\u00e9 zm\u011bny, kter\u00e9 vy\u017eaduj\u00ed hodnocen\u00ed rizik a schv\u00e1len\u00ed; a havarijn\u00ed zm\u011bny, kter\u00e9 mus\u00ed b\u00fdt provedeny rychle k obnoven\u00ed slu\u017eby nebo \u0159e\u0161en\u00ed bezpe\u010dnostn\u00ed hrozby. Spr\u00e1vn\u00e9 za\u0159azen\u00ed zm\u011bn umo\u017e\u0148uje p\u0159im\u011b\u0159enou governance.<\/p>\n

Co je change advisory board?<\/h3>\n

Change advisory board je skupina, kter\u00e1 posuzuje a schvaluje navrhovan\u00e9 IT zm\u011bny podle rizika. Nejv\u00edce p\u0159\u00ednosn\u00fd je u zm\u011bn s velk\u00fdm dopadem. Mnoho organizac\u00ed dnes p\u0159ezkum CAB omezuje na tyto p\u0159\u00edpady a u zm\u011bn s ni\u017e\u0161\u00edm rizikem vyu\u017e\u00edv\u00e1 peer review a automatizaci, aby se vyhnula zbyte\u010dn\u00fdm zpo\u017ed\u011bn\u00edm.<\/p>\n

Co je model ADKAR?<\/h3>\n

ADKAR je model zm\u011bny pro jednotlivce, vyvinut\u00fd v r\u00e1mci metodiky Prosci. Ur\u010duje p\u011bt v\u00fdsledk\u016f, kter\u00fdch mus\u00ed jedinec dos\u00e1hnout, aby zm\u011bna usp\u011bla: pov\u011bdom\u00ed o pot\u0159eb\u011b zm\u011bny, touha se zapojit, znalost toho, jak se zm\u011bnit, schopnost osvojit si nov\u00e9 dovednosti a chov\u00e1n\u00ed a pos\u00edlen\u00ed, kter\u00e9 zm\u011bnu udr\u017e\u00ed. Slou\u017e\u00ed k diagnostice, kde je pot\u0159eba podpora.<\/p>\n

Pro\u010d change management selh\u00e1v\u00e1?<\/h3>\n

Nej\u010dast\u011bj\u0161\u00edmi p\u0159\u00ed\u010dinami jsou slab\u00e9 sponzorstv\u00ed veden\u00ed, nedostate\u010dn\u00e9 zapojen\u00ed zam\u011bstnanc\u016f, nejasn\u00fd p\u0159\u00ednos, komunikace omezen\u00e1 na ozn\u00e1men\u00ed a governance procesy, kter\u00e9 jsou p\u0159\u00edli\u0161 pomal\u00e9 nebo p\u0159\u00edli\u0161 tuh\u00e9. Selh\u00e1n\u00ed jsou \u010dast\u00e9 tak\u00e9 tehdy, kdy\u017e organizace m\u011b\u0159\u00ed nasazen\u00ed m\u00edsto p\u0159ijet\u00ed.<\/p>\n

Jak m\u011b\u0159it \u00fasp\u011bch change managementu?<\/h3>\n

M\u011b\u0159te p\u0159ijet\u00ed a zdatnost, nejen dod\u00e1n\u00ed. U\u017eite\u010dn\u00e9 ukazatele jsou m\u00edra vyu\u017e\u00edv\u00e1n\u00ed nov\u00fdch syst\u00e9m\u016f, pokles obch\u00e1zen\u00ed postup\u016f, doba do dosa\u017een\u00ed zdatnosti, po\u010det incident\u016f souvisej\u00edc\u00edch se zm\u011bnou, pln\u011bn\u00ed harmonogramu a rozpo\u010dtu a zapojen\u00ed zam\u011bstnanc\u016f. Kl\u00ed\u010dov\u00e9 ukazatele v\u00fdkonu by se m\u011bly definovat je\u0161t\u011b p\u0159ed zah\u00e1jen\u00edm zm\u011bny, aby bylo mo\u017en\u00e9 sledovat pokrok pr\u016fb\u011b\u017en\u011b.<\/p>\n","protected":false},"excerpt":{"rendered":"

Change management: Kompletn\u00ed pr\u016fvodce pro IT mana\u017eery a l\u00eddry digit\u00e1ln\u00ed transformace Change management je strukturovan\u00e1 discipl\u00edna, kter\u00e1 organizaci i lidi v n\u00ed prov\u00e1z\u00ed z aktu\u00e1ln\u00edho stavu do \u017e\u00e1douc\u00edho budouc\u00edho stavu. Zahrnuje pl\u00e1nov\u00e1n\u00ed, komunikaci, \u0161kolen\u00ed a ukotven\u00ed zm\u011bny, kter\u00e9 jsou pot\u0159eba, aby se nov\u00e9 technologie, procesy nebo struktury skute\u010dn\u011b p\u0159ijaly a p\u0159inesly zam\u00fd\u0161lenou hodnotu. Pro CTO, […]<\/p>\n","protected":false},"author":7,"featured_media":0,"parent":0,"template":"","glossary-cat":[],"class_list":["post-21067","glossary","type-glossary","status-publish","hentry"],"yoast_head":"\nChange management - Greyson<\/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:\/\/greyson.eu\/cs\/glossary\/change-management\/\" \/>\n<meta property=\"og:locale\" content=\"cs_CZ\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Change management - Greyson\" \/>\n<meta property=\"og:description\" content=\"Change management: Kompletn\u00ed pr\u016fvodce pro IT mana\u017eery a l\u00eddry digit\u00e1ln\u00ed transformace Change management je strukturovan\u00e1 discipl\u00edna, kter\u00e1 organizaci i lidi v n\u00ed prov\u00e1z\u00ed z aktu\u00e1ln\u00edho stavu do \u017e\u00e1douc\u00edho budouc\u00edho stavu. Zahrnuje pl\u00e1nov\u00e1n\u00ed, komunikaci, \u0161kolen\u00ed a ukotven\u00ed zm\u011bny, kter\u00e9 jsou pot\u0159eba, aby se nov\u00e9 technologie, procesy nebo struktury skute\u010dn\u011b p\u0159ijaly a p\u0159inesly zam\u00fd\u0161lenou hodnotu. Pro CTO, […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/greyson.eu\/cs\/glossary\/change-management\/\" \/>\n<meta property=\"og:site_name\" content=\"Greyson\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-15T11:28:50+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Odhadovan\u00e1 doba \u010dten\u00ed\" \/>\n\t<meta name=\"twitter:data1\" content=\"18 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/greyson.eu\/cs\/glossary\/change-management\/\",\"url\":\"https:\/\/greyson.eu\/cs\/glossary\/change-management\/\",\"name\":\"Change management - Greyson\",\"isPartOf\":{\"@id\":\"https:\/\/greyson.eu\/cs\/#website\"},\"datePublished\":\"2026-10-15T11:27:47+00:00\",\"dateModified\":\"2026-10-15T11:28:50+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/greyson.eu\/cs\/glossary\/change-management\/#breadcrumb\"},\"inLanguage\":\"cs\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/greyson.eu\/cs\/glossary\/change-management\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/greyson.eu\/cs\/glossary\/change-management\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Domovsk\u00e1 str\u00e1nka\",\"item\":\"https:\/\/greyson.eu\/cs\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Glossary Terms\",\"item\":\"https:\/\/greyson.eu\/cs\/glossary\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Change management\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/greyson.eu\/cs\/#website\",\"url\":\"https:\/\/greyson.eu\/cs\/\",\"name\":\"Greyson\",\"description\":\"Let\u2019s make future GREYT together\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/greyson.eu\/cs\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"cs\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Change management - Greyson","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:\/\/greyson.eu\/cs\/glossary\/change-management\/","og_locale":"cs_CZ","og_type":"article","og_title":"Change management - Greyson","og_description":"Change management: Kompletn\u00ed pr\u016fvodce pro IT mana\u017eery a l\u00eddry digit\u00e1ln\u00ed transformace Change management je strukturovan\u00e1 discipl\u00edna, kter\u00e1 organizaci i lidi v n\u00ed prov\u00e1z\u00ed z aktu\u00e1ln\u00edho stavu do \u017e\u00e1douc\u00edho budouc\u00edho stavu. Zahrnuje pl\u00e1nov\u00e1n\u00ed, komunikaci, \u0161kolen\u00ed a ukotven\u00ed zm\u011bny, kter\u00e9 jsou pot\u0159eba, aby se nov\u00e9 technologie, procesy nebo struktury skute\u010dn\u011b p\u0159ijaly a p\u0159inesly zam\u00fd\u0161lenou hodnotu. Pro CTO, […]","og_url":"https:\/\/greyson.eu\/cs\/glossary\/change-management\/","og_site_name":"Greyson","article_modified_time":"2026-10-15T11:28:50+00:00","twitter_card":"summary_large_image","twitter_misc":{"Odhadovan\u00e1 doba \u010dten\u00ed":"18 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/greyson.eu\/cs\/glossary\/change-management\/","url":"https:\/\/greyson.eu\/cs\/glossary\/change-management\/","name":"Change management - Greyson","isPartOf":{"@id":"https:\/\/greyson.eu\/cs\/#website"},"datePublished":"2026-10-15T11:27:47+00:00","dateModified":"2026-10-15T11:28:50+00:00","breadcrumb":{"@id":"https:\/\/greyson.eu\/cs\/glossary\/change-management\/#breadcrumb"},"inLanguage":"cs","potentialAction":[{"@type":"ReadAction","target":["https:\/\/greyson.eu\/cs\/glossary\/change-management\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/greyson.eu\/cs\/glossary\/change-management\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Domovsk\u00e1 str\u00e1nka","item":"https:\/\/greyson.eu\/cs\/"},{"@type":"ListItem","position":2,"name":"Glossary Terms","item":"https:\/\/greyson.eu\/cs\/glossary\/"},{"@type":"ListItem","position":3,"name":"Change management"}]},{"@type":"WebSite","@id":"https:\/\/greyson.eu\/cs\/#website","url":"https:\/\/greyson.eu\/cs\/","name":"Greyson","description":"Let\u2019s make future GREYT together","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/greyson.eu\/cs\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"cs"}]}},"related_terms":"","external_url":"","internal_reference_id":"","_links":{"self":[{"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary\/21067","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/types\/glossary"}],"author":[{"embeddable":true,"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/users\/7"}],"version-history":[{"count":1,"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary\/21067\/revisions"}],"predecessor-version":[{"id":21068,"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary\/21067\/revisions\/21068"}],"wp:attachment":[{"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/media?parent=21067"}],"wp:term":[{"taxonomy":"glossary-cat","embeddable":true,"href":"https:\/\/greyson.eu\/cs\/wp-json\/wp\/v2\/glossary-cat?post=21067"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}