[{"Value":"","Discard":false,"Expires":9999999999}]{"id":7418,"date":"2026-08-11T07:00:01","date_gmt":"2026-08-11T05:00:01","guid":{"rendered":"https:\/\/www.insightsofa.com\/?p=7418"},"modified":"2026-08-09T10:05:49","modified_gmt":"2026-08-09T08:05:49","slug":"jedna-stiznost-je-gesto-deset-stejnych-je-system-ktery-selhava","status":"publish","type":"post","link":"https:\/\/www.insightsofa.com\/cs\/jedna-stiznost-je-gesto-deset-stejnych-je-system-ktery-selhava\/","title":{"rendered":"Jedna st\u00ed\u017enost je gesto, deset stejn\u00fdch je syst\u00e9m, kter\u00fd selh\u00e1v\u00e1"},"content":{"rendered":"

Minul\u00fd t\u00fdden mi kolegyn\u011b z jin\u00e9 firmy psala, \u017ee \u0159e\u0161\u00ed u\u017e pot\u0159et\u00ed za m\u011bs\u00edc tu samou st\u00ed\u017enost od t\u0159\u00ed r\u016fzn\u00fdch z\u00e1kazn\u00edk\u016f. Poka\u017ed\u00e9 ji „vy\u0159e\u0161ili<\/em>„. Poka\u017ed\u00e9 se stejn\u00e1 v\u011bc objevila znovu o p\u00e1r t\u00fddn\u016f pozd\u011bji. Ptala se m\u011b, jestli je to norm\u00e1ln\u00ed. Ano, bohu\u017eel je.<\/p>\n

Tohle je nej\u010dast\u011bj\u0161\u00ed past closed-loop procesu. Firmy si osvoj\u00ed rychlou reakci na jednotlivce a mysl\u00ed si, \u017ee t\u00edm closed-loop kon\u010d\u00ed. Nekon\u010d\u00ed. Teprve tam za\u010d\u00edn\u00e1 ta zaj\u00edmav\u011bj\u0161\u00ed p\u016flka pr\u00e1ce.<\/p>\n

Dv\u011b smy\u010dky, ne jedna<\/h2>\n

Closed-loop feedback (tedy princip, kdy na zp\u011btnou vazbu z\u00e1kazn\u00edka n\u011bkdo skute\u010dn\u011b reaguje, m\u00edsto aby zapadla do tabulky) se v praxi d\u011bl\u00ed na dv\u011b r\u016fzn\u00e9 smy\u010dky. N\u011bkdo jim \u0159\u00edk\u00e1 inner loop a outer loop, jinde se pou\u017e\u00edv\u00e1 pojem mikro a makro \u00farove\u0148. N\u00e1zev je jedno. Podstatn\u00e9 je, \u017ee to jsou dv\u011b odli\u0161n\u00e9 discipl\u00edny s jin\u00fdm vlastn\u00edkem, jin\u00fdm tempem a jin\u00fdm c\u00edlem.<\/p>\n

Vnit\u0159n\u00ed smy\u010dka<\/strong> (inner loop) je o jednom konkr\u00e9tn\u00edm z\u00e1kazn\u00edkovi. P\u0159i\u0161la st\u00ed\u017enost, reklamace, n\u00edzk\u00e9 sk\u00f3re v pr\u016fzkumu. N\u011bkdo se ozve, vy\u0159e\u0161\u00ed situaci, p\u0159\u00edpadn\u011b se omluv\u00ed nebo nab\u00eddne kompenzaci. Tohle mus\u00ed b\u00fdt rychl\u00e9. Hodiny, maxim\u00e1ln\u011b dny. Z\u00e1kazn\u00edka nezaj\u00edm\u00e1 va\u0161e kvart\u00e1ln\u00ed reportov\u00e1n\u00ed, chce v\u011bd\u011bt, jestli se s n\u00edm n\u011bkdo bude bavit jako s \u010dlov\u011bkem.<\/p>\n

Vn\u011bj\u0161\u00ed smy\u010dka<\/strong> (outer loop) je o tom, co se stalo za tou st\u00ed\u017enost\u00ed. Pro\u010d se to v\u016fbec objevilo. Je to izolovan\u00fd p\u0159\u00edpad, nebo syst\u00e9mov\u00fd probl\u00e9m, kter\u00fd se bude opakovat, dokud ho n\u011bkdo neoprav\u00ed na \u00farovni procesu, produktu nebo \u0161kolen\u00ed lid\u00ed. Tohle nemus\u00ed a nem\u00e1 b\u00fdt rychl\u00e9. Tady je pot\u0159eba \u010das na anal\u00fdzu, prioritizaci a \u010dasto i na schv\u00e1len\u00ed rozpo\u010dtu.<\/p>\n

Probl\u00e9m nast\u00e1v\u00e1, kdy\u017e firma um\u00ed jen tu prvn\u00ed smy\u010dku. Vy\u0159e\u0161\u00ed \u010dlov\u011bka, ale nikdy se nevr\u00e1t\u00ed k p\u0159\u00ed\u010din\u011b. Pak se div\u00edte, pro\u010d v\u00e1m po\u0159\u00e1d p\u0159ist\u00e1vaj\u00ed stejn\u00e9 st\u00ed\u017enosti na stejnou v\u011bc, jen s jin\u00fdm jm\u00e9nem z\u00e1kazn\u00edka.<\/p>\n

Kdo co vlastn\u00ed a kdy<\/h2>\n

Tohle je m\u00edsto, kde spousta firem tone. Ne proto, \u017ee by necht\u011bly closed-loop d\u011blat, ale proto\u017ee nikdo p\u0159esn\u011b nev\u00ed, \u010d\u00ed je to pr\u00e1ce a v jak\u00fd moment m\u00e1 zas\u00e1hnout.<\/p>\n

Funguj\u00edc\u00ed rozd\u011blen\u00ed, kter\u00e9 jsem vid\u011bl v praxi opakovan\u011b fungovat, vypad\u00e1 zhruba takhle:<\/strong><\/p>\n

Front-line t\u00fdm (agent, obsluha, prodejce) vlastn\u00ed inner loop. Reaguje jako prvn\u00ed<\/strong>, do 24 a\u017e 48 hodin od podn\u011btu. Jeho \u00fakolem nen\u00ed analyzovat p\u0159\u00ed\u010dinu, ale vy\u0159e\u0161it \u010dlov\u011bka p\u0159ed sebou a zaznamenat, co se stalo<\/strong>, dostate\u010dn\u011b konkr\u00e9tn\u011b, aby to bylo pou\u017eiteln\u00e9 d\u00e1l.<\/p>\n

CX t\u00fdm nebo product owner vlastn\u00ed outer loop. Sb\u00edr\u00e1 sign\u00e1ly z front-line, hled\u00e1 vzorce, rozhoduje, jestli jde o jednor\u00e1zovku nebo trend.<\/strong> Tady se pracuje v t\u00fddnech, ne v hodin\u00e1ch. C\u00edlem nen\u00ed hasit, ale pochopit.<\/p>\n

Veden\u00ed nebo vlastn\u00edk procesu vlastn\u00ed rozhodnut\u00ed o zm\u011bn\u011b. Tohle je \u010dlov\u011bk, kter\u00fd m\u00e1 mand\u00e1t zm\u011bnit proces, p\u0159erozd\u011blit rozpo\u010det nebo p\u0159e\u0161kolit t\u00fdm. Bez n\u011bj outer loop skon\u010d\u00ed jako p\u011bkn\u011b vypln\u011bn\u00e1 tabulka, do kter\u00e9 se nikdy nikdo nevr\u00e1t\u00ed.<\/p>\n

Kl\u00ed\u010dov\u00e1 v\u011bc: tyhle t\u0159i role nesm\u00ed spl\u00fdvat v jednoho \u010dlov\u011bka, kter\u00fd to „m\u00e1 na starosti n\u011bjak cel\u00e9<\/em>„<\/strong>. Vid\u011bl jsem to p\u00e1rkr\u00e1t a v\u017edycky to skon\u010dilo stejn\u011b. Bu\u010f se has\u00ed po\u017e\u00e1ry a na anal\u00fdzu nezbyde \u010das, nebo se analyzuje a z\u00e1kazn\u00edk \u010dek\u00e1 t\u00fdden na odpov\u011b\u010f na ban\u00e1ln\u00ed dotaz.<\/p>\n

Pravidla eskalace, aby insight nezapadl<\/h2>\n

Tohle je bod, kde se rozhoduje, jestli closed-loop funguje, nebo jestli je to jen pojem, kter\u00fd si firma od\u0161krtne v intern\u00ed dokumentaci a nikdy k n\u011bmu nikdo nedohl\u00e9dne. Insighty um\u00edraj\u00ed nej\u010dast\u011bji na jednom m\u00edst\u011b: mezi front-line a t\u00fdmem, kter\u00fd m\u00e1 mand\u00e1t n\u011bco zm\u011bnit. Zp\u011btn\u00e1 vazba se sesb\u00edr\u00e1, zap\u00ed\u0161e do syst\u00e9mu, a tam skon\u010d\u00ed.<\/p>\n

P\u00e1r pravidel, kter\u00e1 tomu re\u00e1ln\u011b pom\u00e1haj\u00ed:<\/strong><\/p>\n

    \n
  1. Definuj pr\u00e1h, ne pocit. Ne\u010dekej, a\u017e si n\u011bkdo „v\u0161imne trendu<\/em>„. Nastav si konkr\u00e9tn\u00ed \u010d\u00edslo, t\u0159eba t\u0159i stejn\u00e9 st\u00ed\u017enosti od r\u016fzn\u00fdch z\u00e1kazn\u00edk\u016f b\u011bhem dvou t\u00fddn\u016f, a v ten moment se automaticky spou\u0161t\u00ed eskalace k outer loop t\u00fdmu. Bez \u010d\u00edsla se spol\u00e9h\u00e1\u0161 na to, \u017ee si toho n\u011bkdo n\u00e1hodou v\u0161imne. Nev\u0161imne.<\/li>\n
  2. P\u0159i\u0159a\u010f vlastn\u00edka do 48 hodin, ne „\u010dasem“. Ka\u017ed\u00fd eskalovan\u00fd insight mus\u00ed m\u00edt jm\u00e9no u sebe, ne odd\u011blen\u00ed. „To \u0159e\u0161\u00ed CX t\u00fdm<\/em>“ je zp\u016fsob, jak se nic nevy\u0159e\u0161\u00ed. „To \u0159e\u0161\u00ed Petra do konce t\u00fddne<\/em>“ je zp\u016fsob, jak se n\u011bco vy\u0159e\u0161\u00ed.<\/li>\n
  3. Nastav SLA i pro outer loop. Lidi si mysl\u00ed, \u017ee SLA (dohodnut\u00e1 lh\u016fta na vy\u0159\u00edzen\u00ed) pat\u0159\u00ed jen k inner loop, k reakci na z\u00e1kazn\u00edka. Outer loop bez term\u00ednu se v praxi odsune na neur\u010dito, proto\u017ee v\u017edycky je n\u011bco nal\u00e9hav\u011bj\u0161\u00edho. Dej si \u010dty\u0159i t\u00fddny na to, aby insight dostal rozhodnut\u00ed, ne \u0159e\u0161en\u00ed, jen rozhodnut\u00ed, jestli se s t\u00edm bude nebo nebude d\u00e1l pracovat.<\/li>\n
  4. Zp\u011btn\u011b informuj front-line. Tohle se skoro v\u017edycky vynech\u00e1v\u00e1 a je to \u0161koda. Kdy\u017e agent nahl\u00e1s\u00ed probl\u00e9m a nikdy se nedozv\u00ed, co se s t\u00edm stalo, p\u0159estane to hl\u00e1sit. Pro\u010d by taky m\u011bl, kdy\u017e to jde do \u010dern\u00e9 d\u00edry. Sta\u010d\u00ed kr\u00e1tk\u00e1 zpr\u00e1va: „D\u00edky za podn\u011bt, upravujeme proces X, d\u00edky tob\u011b jsme si toho v\u0161imli.<\/em>“ Tohle jedno gesto dok\u00e1\u017ee z lhostejn\u00e9ho t\u00fdmu ud\u011blat t\u00fdm, kter\u00fd aktivn\u011b hled\u00e1 probl\u00e9my.<\/li>\n<\/ol>\n

    Jak poznat, \u017ee to funguje<\/h2>\n

    Spousta firem m\u011b\u0159\u00ed closed-loop jenom podle rychlosti reakce na inner loop. Kolik st\u00ed\u017enost\u00ed vy\u0159e\u0161eno, jak rychle, jak\u00e9 sk\u00f3re spokojenosti po vy\u0159e\u0161en\u00ed. To je fajn metrika, ale m\u011b\u0159\u00ed jen p\u016flku syst\u00e9mu.<\/p>\n

    Skute\u010dn\u00e9 fungov\u00e1n\u00ed closed-loop procesu pozn\u00e1\u0161 podle t\u0159\u00ed v\u011bc\u00ed:<\/strong><\/p>\n

    Klesaj\u00edc\u00ed recidiva.<\/strong> Sleduj, jestli se stejn\u00fd typ probl\u00e9mu opakuje u nov\u00fdch z\u00e1kazn\u00edk\u016f m\u011bs\u00edc po m\u011bs\u00edci. Pokud po\u010det nov\u00fdch p\u0159\u00edpad\u016f stejn\u00e9ho probl\u00e9mu kles\u00e1, outer loop d\u011bl\u00e1 svou pr\u00e1ci. Pokud z\u016fst\u00e1v\u00e1 stabiln\u00ed, \u0159e\u0161\u00edte jen symptomy.<\/p>\n

    Rychlost mezi insightem a rozhodnut\u00edm<\/strong>. Ne mezi insightem a implementac\u00ed, proto\u017ee implementace m\u016f\u017ee trvat m\u011bs\u00edce a to je v po\u0159\u00e1dku. Ale \u010das mezi t\u00edm, kdy n\u011bkdo probl\u00e9m nahl\u00e1s\u00ed, a kdy n\u011bkdo s mand\u00e1tem \u0159ekne „ano, budeme to \u0159e\u0161it<\/em>“ nebo „ne, te\u010f ne, a tady je pro\u010d<\/em>„, by m\u011bl b\u00fdt m\u011b\u0159iteln\u00fd a kr\u00e1tk\u00fd. Tohle \u010d\u00edslo firmy skoro nikdy nesleduj\u00ed a p\u0159itom je to nejlep\u0161\u00ed indik\u00e1tor, jestli insighty nezapadaj\u00ed.<\/p>\n

    Pod\u00edl podn\u011bt\u016f od front-line, kter\u00e9 vedou ke konkr\u00e9tn\u00ed zm\u011bn\u011b<\/strong>. Nemus\u00ed to b\u00fdt velk\u00e9 procento. I 10 a\u017e 15 % je slu\u0161n\u00fd v\u00fdsledek, pokud tam skute\u010dn\u011b je. Pokud je to procento nula nebo bl\u00edzko nule dlouhodob\u011b, tv\u016fj closed-loop je jen closed-mouth. Zav\u00edr\u00e1\u0161 tikety, ne smy\u010dku.<\/p>\n

    Na z\u00e1v\u011br<\/h2>\n

    Closed-loop nen\u00ed projekt, kter\u00fd jednou nastav\u00ed\u0161 a pak b\u011b\u017e\u00ed s\u00e1m. Je to n\u00e1vyk, kter\u00fd se mus\u00ed \u017eivit. Vy\u017eaduje, aby lidi na front-line v\u011b\u0159ili, \u017ee m\u00e1 smysl hl\u00e1sit probl\u00e9m, aby CX t\u00fdm m\u011bl \u010das a mand\u00e1t ho analyzovat, a aby veden\u00ed bylo ochotn\u00e9 m\u011bnit procesy na z\u00e1klad\u011b dat od lid\u00ed, kte\u0159\u00ed stoj\u00ed nejbl\u00ed\u017e z\u00e1kazn\u00edkovi.<\/p>\n

    Ta st\u00ed\u017enost, kterou dnes vy\u0159e\u0161\u00ed\u0161 rychlou omluvou a slevov\u00fdm kup\u00f3nem, je jenom polovina pr\u00e1ce. Ta druh\u00e1 polovina, ta, kter\u00e1 rozhoduje o tom, jestli se za m\u011bs\u00edc neobjev\u00ed znovu, se odehr\u00e1v\u00e1 mimo o\u010di z\u00e1kazn\u00edka<\/strong>. A pr\u00e1v\u011b tam se pozn\u00e1, jestli firma CX skute\u010dn\u011b d\u011bl\u00e1, nebo jenom has\u00ed.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Minul\u00fd t\u00fdden mi kolegyn\u011b z jin\u00e9 firmy psala, \u017ee \u0159e\u0161\u00ed […]<\/p>\n","protected":false},"author":5,"featured_media":7419,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[55,72],"tags":[70],"class_list":["post-7418","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-strategie","category-vsechny-clanky","tag-featured"],"_links":{"self":[{"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/posts\/7418","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/comments?post=7418"}],"version-history":[{"count":4,"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/posts\/7418\/revisions"}],"predecessor-version":[{"id":7429,"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/posts\/7418\/revisions\/7429"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/media\/7419"}],"wp:attachment":[{"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/media?parent=7418"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/categories?post=7418"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.insightsofa.com\/cs\/wp-json\/wp\/v2\/tags?post=7418"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}