𝖣𝗎𝗋𝗂𝗇𝗀 𝗆𝗒 𝗌𝖾𝗋𝗏𝗂𝖼𝖾 𝖽𝖾𝗅𝗂𝗏𝖾𝗋𝗒 𝗅𝖾𝖺𝖽 𝗋𝗈𝗅𝖾 𝖾𝖺𝗋𝗅𝗂𝖾𝗋, 𝗐𝖾 𝗁𝖺𝖽 𝖺 𝗆𝗂𝗇𝗈𝗋 𝖲𝖠𝖯 𝖾𝗇𝗁𝖺𝗇𝖼𝖾𝗆𝖾𝗇𝗍 𝗍𝗈 𝖺𝖽𝖽 𝖺 𝖼𝗎𝗌𝗍𝗈𝗆 𝖿𝗂𝖾𝗅𝖽 𝗂𝗇 𝗍𝗁𝖾 ‘𝗂𝗇𝗇𝗈𝖼𝖾𝗇𝗍’ 𝗏𝖺𝟢𝟧 𝗋𝖾𝗉𝗈𝗋𝗍. 𝖨𝗍 𝗐𝖺𝗌 𝗈𝗇𝖾 𝗈𝖿 𝗍𝗁𝗈𝗌𝖾 𝖼𝗁𝖺𝗇𝗀𝖾𝗌 𝗒𝗈𝗎 𝖽𝗈𝗇’𝗍 𝖾𝗏𝖾𝗇 𝗍𝗁𝗂𝗇𝗄 𝗍𝗐𝗂𝖼𝖾 𝖺𝖻𝗈𝗎𝗍. 𝖩𝗎𝗌𝗍 𝖺 𝖿𝖾𝗐 𝗍𝗐𝖾𝖺𝗄𝗌 𝗍𝗈 𝖺 𝗋𝖾𝗉𝗈𝗋𝗍. 𝖨 𝗋𝖾𝗆𝖾𝗆𝖻𝖾𝗋 𝖼𝗁𝖺𝗂𝗋𝗂𝗇𝗀 𝗂𝗇 𝗍𝗁𝖾 𝖠𝖬𝖤𝖠 𝗋𝖾𝗀𝗂𝗈𝗇 𝖢𝗁𝖺𝗇𝗀𝖾 𝖠𝖽𝗏𝗂𝗌𝗈𝗋𝗒 𝖡𝗈𝖺𝗋𝖽 (𝖢𝖠𝖡) 𝗆𝖾𝖾𝗍𝗂𝗇𝗀:

𝖬𝖾: “𝖲𝗈, 𝗐𝖾 𝖺𝗋𝖾 𝖺𝗅𝗅 𝖼𝗅𝖾𝖺𝗋? 𝖳𝗁𝗂𝗌 𝖲𝖠𝖯 𝖼𝗁𝖺𝗇𝗀𝖾 𝗂𝗌 𝗆𝗂𝗇𝗈𝗋, 𝖰𝖠 𝖺𝗇𝖽 𝖴𝖠𝖳 𝗐𝖾𝗋𝖾 𝗌𝗆𝗈𝗈𝗍𝗁 𝖺𝗌 𝖻𝗎𝗍𝗍𝖾𝗋, 𝗋𝗂𝗀𝗁𝗍?”

𝖳𝖾𝖺𝗆: “𝖸𝖾𝗉, 𝗇𝗈 𝗂𝗌𝗌𝗎𝖾𝗌. 𝖯𝖺𝗌𝗌𝖾𝖽 𝗍𝖾𝗌𝗍𝗂𝗇𝗀 𝗂𝗇 𝖰𝖠 𝖾𝗇𝗏𝗂𝗋𝗈𝗇𝗆𝖾𝗇𝗍. 𝖴𝖠𝖳 𝖺𝖼𝖼𝖾𝗉𝗍𝖺𝗇𝖼𝖾 𝗋𝖾𝖼𝖾𝗂𝗏𝖾𝖽 𝖿𝗋𝗈𝗆 𝖻𝗎𝗌𝗂𝗇𝖾𝗌𝗌. 𝖨𝗍 𝗂𝗌 𝖻𝖺𝗋𝖾𝗅𝗒 𝖺 𝖻𝗅𝗂𝗉.”

𝖬𝖾: “𝖯𝖾𝗋𝖿𝖾𝖼𝗍. 𝖢𝗁𝖺𝗇𝗀𝖾 𝗋𝖾𝗅𝖾𝖺𝗌𝖾 𝖺𝗉𝗉𝗋𝗈𝗏𝖾𝖽 𝗂𝗇 𝗍𝗁𝖾 𝗉𝗅𝖺𝗇𝗇𝖾𝖽 𝖥𝗋𝗂𝖽𝖺𝗒 𝗋𝖾𝗅𝖾𝖺𝗌𝖾 𝗐𝗂𝗇𝖽𝗈𝗐.” (𝘍𝘢𝘮𝘰𝘶𝘴 𝘭𝘢𝘴𝘵 𝘸𝘰𝘳𝘥𝘴.)

𝖬𝗈𝗇𝖽𝖺𝗒 𝗆𝗈𝗋𝗇𝗂𝗇𝗀 𝖼𝗈𝗆𝖾𝗌 𝖺𝗋𝗈𝗎𝗇𝖽, 𝖺𝗇𝖽 𝖼𝗁𝖺𝗈𝗌 𝖾𝗋𝗎𝗉𝗍𝗌. 𝖳𝗁𝖾 𝖵𝖠𝟢𝟧 𝗋𝖾𝗉𝗈𝗋𝗍 𝗐𝖺𝗌 𝗇𝗈𝗐 𝗍𝗂𝗆𝗂𝗇𝗀 𝗈𝗎𝗍 𝗐𝗁𝗂𝖼𝗁 𝗐𝖺𝗌 𝗌𝗎𝗉𝗉𝗈𝗌𝖾𝖽 𝗍𝗈 𝖻𝖾 𝖿𝖺𝗌𝗍𝖾𝗋 𝗐𝗂𝗍𝗁 𝗍𝗁𝖾 𝗇𝖾𝗐 𝖿𝗂𝖾𝗅𝖽. 𝖲𝖺𝗅𝖾𝗌 𝗈𝗋𝖽𝖾𝗋𝗌 𝖼𝗈𝗎𝗅𝖽𝗇’𝗍 𝖻𝖾 𝗍𝗋𝖺𝖼𝗄𝖾𝖽, 𝖺𝗇𝖽 𝗍𝗁𝖾 𝖻𝖺𝖼𝗄𝗅𝗈𝗀 𝗐𝖺𝗌 𝗀𝗋𝗈𝗐𝗂𝗇𝗀 𝖻𝗒 𝗍𝗁𝖾 𝗆𝗂𝗇𝗎𝗍𝖾. 𝖳𝗁𝖾 𝗆𝗂𝗇𝗈𝗋 𝖼𝗁𝖺𝗇𝗀𝖾 𝗍𝗋𝗂𝗀𝗀𝖾𝗋ed 𝖺 “MIM – 𝗆𝖺𝗃𝗈𝗋 𝗂𝗇𝖼𝗂𝖽𝖾𝗇𝗍 𝗆𝖺𝗇𝖺𝗀𝖾𝗆𝖾𝗇𝗍” 𝗉𝗋𝗈𝖼𝖾𝗌𝗌 𝗂𝗆𝗆𝖾𝖽𝗂𝖺𝗍𝖾𝗅𝗒!

𝖠𝗇𝖽 𝗁𝖾𝗋𝖾 𝗂𝗌 𝗐𝗁𝖾𝗋𝖾 𝗍𝗁𝖾 𝗂𝗋𝗈𝗇𝗒 𝗁𝗂𝗍: 𝗤𝗔 𝗮𝗻𝗱 𝗨𝗔𝗧? 𝖯𝖺𝗌𝗌𝖾𝖽 𝗐𝗂𝗍𝗁 𝖿𝗅𝗒𝗂𝗇𝗀 𝖼𝗈𝗅𝗈𝗋𝗌. 𝗖𝗔𝗕 𝗱𝗶𝘀𝗰𝘂𝘀𝘀𝗶𝗼𝗻? 𝖭𝗈 𝗆𝖺𝗃𝗈𝗋 𝗋𝖾𝖽 𝖿𝗅𝖺𝗀𝗌. 𝗕𝘂𝘁 𝗽𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻? 𝖢𝗈𝗆𝗉𝗅𝖾𝗍𝖾𝗅𝗒 𝖽𝗈𝗐𝗇.

𝖳𝗁𝖾 𝗅𝖾𝗌𝗌𝗈𝗇? 𝖤𝗏𝖾𝗇 𝗐𝗁𝖾𝗇 𝖾𝗏𝖾𝗋𝗒𝗍𝗁𝗂𝗇𝗀 𝗅𝗈𝗈𝗄𝗌 𝗉𝖾𝗋𝖿𝖾𝖼𝗍 𝗂𝗇 𝗍𝖾𝗌𝗍𝗂𝗇𝗀, 𝗍𝗁𝖾𝗋𝖾 𝖺𝗋𝖾 𝖺𝗅𝗐𝖺𝗒𝗌 𝗎𝗇𝗄𝗇𝗈𝗐𝗇𝗌 𝗍𝗁𝖺𝗍 𝗅𝗎𝗋𝗄 𝗂𝗇 𝗉𝗋𝗈𝖽𝗎𝖼𝗍𝗂𝗈𝗇. 𝖭𝖾𝗏𝖾𝗋 𝗌𝗄𝗂𝗉 𝗋𝗂𝗀𝗈𝗋𝗈𝗎𝗌 𝗂𝗆𝗉𝖺𝖼𝗍 𝖺𝗇𝖺𝗅𝗒𝗌𝗂𝗌, 𝖿𝗎𝗇𝖼𝗍𝗂𝗈𝗇𝖺𝗅 𝗍𝖾𝗌𝗍𝗂𝗇𝗀, 𝗂𝗇𝗍𝖾𝗀𝗋𝖺𝗍𝗂𝗈𝗇 𝗍𝖾𝗌𝗍𝗂𝗇𝗀 𝖺𝗇𝖽 𝗋𝖾𝗀𝗋𝖾𝗌𝗌𝗂𝗈𝗇 𝗍𝖾𝗌𝗍𝗂𝗇𝗀 𝖺𝗇𝗒𝗆𝗈𝗋𝖾, 𝗇𝗈 𝗆𝖺𝗍𝗍𝖾𝗋 𝗁𝗈𝗐 “𝗌𝗆𝖺𝗅𝗅” 𝗈𝗋 “𝗌𝖺𝖿𝖾” 𝖺 𝖼𝗁𝖺𝗇𝗀𝖾 𝗌𝖾𝖾𝗆𝗌. 𝖠𝗇𝖽 𝗇𝖾𝗏𝖾𝗋 𝖿𝗈𝗋𝗀𝖾𝗍 𝗍𝗈 𝖽𝗈𝖼𝗎𝗆𝖾𝗇𝗍 𝖺 𝖽𝖾𝗍𝖺𝗂𝗅𝖾𝖽 𝖻𝖺𝖼𝗄𝗈𝗎𝗍 𝗉𝗅𝖺𝗇 𝗂𝗇 𝗒𝗈𝗎𝗋 𝖼𝗁𝖺𝗇𝗀𝖾 𝗋𝖾𝗊𝗎𝖾𝗌𝗍.

𝖯𝖲: “𝘐𝘵 𝘪𝘴 𝘫𝘶𝘴𝘵 𝘢 𝘵𝘪𝘯𝘺 𝘤𝘶𝘴𝘵𝘰𝘮 𝘧𝘪𝘦𝘭𝘥 𝘪𝘯 𝘝𝘈𝟢𝟧,” 𝘵𝘩𝘦𝘺 𝘴𝘢𝘪𝘥. “𝘞𝘩𝘢𝘵 𝘤𝘰𝘶𝘭𝘥 𝘱𝘰𝘴𝘴𝘪𝘣𝘭𝘺 𝘨𝘰 𝘸𝘳𝘰𝘯𝘨?” 𝘞𝘦𝘭𝘭, 𝘦𝘷𝘦𝘳𝘺𝘵𝘩𝘪𝘯𝘨. 𝘈𝘣𝘴𝘰𝘭𝘶𝘵𝘦𝘭𝘺 𝘦𝘷𝘦𝘳𝘺𝘵𝘩𝘪𝘯𝘨. 𝘈𝘯𝘥 𝘺𝘦𝘴, 𝘦𝘷𝘦𝘯 𝘢𝘧𝘵𝘦𝘳 𝘢𝘭𝘭 𝘵𝘩𝘦 𝘵𝘦𝘴𝘵𝘴 𝘱𝘢𝘴𝘴𝘦𝘥. 😉

#ChangeManagement #SAP #ITLeadership #TechHumor #TechLeadership #JSTalks