𝖨𝗍 𝗐𝖺𝗌 𝖺𝗇𝗈𝗍𝗁𝖾𝗋 𝖽𝖺𝗒 𝗂𝗇 𝗍𝗁𝖾 𝗆𝗂𝖽𝖽𝗅𝖾 𝗈𝖿 𝖺 𝗆𝖺𝗃𝗈𝗋 𝗂𝗇𝖼𝗂𝖽𝖾𝗇𝗍 𝖻𝗋𝗂𝖽𝗀𝖾 𝗋𝖾𝗅𝖺𝗍𝖾𝖽 𝗍𝗈 𝗍𝗁𝖾 𝗌𝖺𝗅𝖾𝗌 𝖺𝗇𝖺𝗅𝗒𝗍𝗂𝖼𝗌 𝖽𝖺𝗌𝗁𝖻𝗈𝖺𝗋𝖽. 𝖲𝗈𝗆𝖾 𝖺𝗎𝗍𝗈𝗆𝖺𝗍𝗂𝗈𝗇 𝗌𝖼𝗋𝗂𝗉𝗍𝗌 𝗐𝖾𝗋𝖾 𝖿𝖺𝗂𝗅𝗂𝗇𝗀, 𝖺𝗇𝖽 𝖽𝖺𝗍𝖺 𝗆𝗈𝗏𝖾𝗆𝖾𝗇𝗍 𝖻𝖾𝗍𝗐𝖾𝖾𝗇 𝗇𝗈𝖽𝖾𝗌 𝗐𝖺𝗌𝗇’𝗍 𝗁𝖺𝗉𝗉𝖾𝗇𝗂𝗇𝗀. 𝖨 𝖽𝗈𝗏𝖾 𝗂𝗇𝗍𝗈 𝗍𝗁𝖾 𝗂𝗇𝖼𝗂𝖽𝖾𝗇𝗍 𝖻𝗋𝗂𝖽𝗀𝖾.

𝖫𝟤 𝖬𝖾𝗆𝖻𝖾𝗋 𝗈𝗇 𝖡𝗋𝗂𝖽𝗀𝖾: “𝖱𝖺𝗏𝗂 𝖼𝗋𝖾𝖺𝗍𝖾𝖽 𝗍𝗁𝗂𝗌 𝗌𝖼𝗋𝗂𝗉𝗍 𝗅𝖺𝗌𝗍 𝗐𝖾𝖾𝗄. 𝖧𝖾 𝗄𝗇𝗈𝗐𝗌 𝗍𝗁𝖾 𝗅𝗈𝗀𝗂𝖼 𝖻𝖾𝗁𝗂𝗇𝖽 𝗂𝗍. 𝖯𝗅𝖾𝖺𝗌𝖾 𝖺𝗌𝗄 𝗁𝗂𝗆 𝗍𝗈 𝗃𝗈𝗂𝗇 𝗍𝗁𝖾 𝖻𝗋𝗂𝖽𝗀𝖾 𝗍𝗈 𝗁𝖾𝗅𝗉 𝗎𝗌 𝖿𝗂𝗑 𝗍𝗁𝗂𝗌.”

𝖬𝖺𝗃𝗈𝗋 𝖨𝗇𝖼𝗂𝖽𝖾𝗇𝗍 𝖬𝖺𝗇𝖺𝗀𝖾𝗋: “𝖱𝖺𝗏𝗂 𝗂𝗌 𝗇𝗈𝗍 𝗉𝗂𝖼𝗄𝗂𝗇𝗀 𝗎𝗉 𝗍𝗁𝖾 𝖼𝖺𝗅𝗅. 𝖫𝖾𝗍 𝗆𝖾 𝖺𝖽𝖽 𝗁𝗂𝗌 𝗆𝖺𝗇𝖺𝗀𝖾𝗋 𝗍𝗈 𝗍𝗁𝖾 𝖻𝗋𝗂𝖽𝗀𝖾.”

𝖱𝖺𝗏𝗂’𝗌 𝖬𝖺𝗇𝖺𝗀𝖾𝗋: “𝖱𝖺𝗏𝗂 𝗂𝗌 𝗈𝖿𝖿 𝗍𝗈 𝖺 𝗍𝖾𝖼𝗁 𝖼𝗈𝗇𝖿𝖾𝗋𝖾𝗇𝖼𝖾 𝗍𝗈𝖽𝖺𝗒. 𝖧𝖾’𝗌 𝗈𝗇 𝗁𝗂𝗌 𝖽𝖺𝗒 𝗈𝖿𝖿. 𝖮𝗇𝗅𝗒 𝗁𝖾 𝗄𝗇𝗈𝗐𝗌 𝗐𝗁𝖺𝗍 𝗍𝗈 𝖽𝗈 𝗁𝖾𝗋𝖾.”

𝖠𝗇𝖽 𝗃𝗎𝗌𝗍 𝗅𝗂𝗄𝖾 𝗍𝗁𝖺𝗍, 𝗐𝖾 𝖿𝗈𝗎𝗇𝖽 𝗈𝗎𝗋𝗌𝖾𝗅𝗏𝖾𝗌 𝗂𝗇 𝖺 𝗌𝗂𝗍𝗎𝖺𝗍𝗂𝗈𝗇 𝖽𝖾𝖿𝗂𝗇𝖾𝖽 𝖻𝗒 ‘𝗍𝗋𝗂𝖻𝖺𝗅 𝗄𝗇𝗈𝗐𝗅𝖾𝖽𝗀𝖾’ 𝗅𝗂𝗆𝗂𝗍𝖾𝖽 𝗍𝗈 𝖱𝖺𝗏𝗂, 𝗅𝖾𝖺𝗏𝗂𝗇𝗀 𝗍𝗁𝖾 𝗋𝖾𝗌𝗍 𝗈𝖿 𝗎𝗌 𝖼𝗅𝗎𝖾𝗅𝖾𝗌𝗌 𝖺𝖻𝗈𝗎𝗍 𝗐𝗁𝖺𝗍 𝗍𝗈 𝖽𝗈!

𝖳𝗁𝗂𝗌 𝖾𝗑𝗉𝖾𝗋𝗂𝖾𝗇𝖼𝖾 𝗍𝖺𝗎𝗀𝗁𝗍 𝖺 𝗁𝖺𝗋𝖽 𝗐𝖺𝗒 𝗍𝗁𝖺𝗍 𝗋𝖾𝗅𝗒𝗂𝗇𝗀 𝗈𝗇 𝗈𝗇𝖾 𝗉𝖾𝗋𝗌𝗈𝗇’𝗌 𝗆𝖾𝗆𝗈𝗋𝗒 𝗂𝗇 𝖨𝖳 𝗂𝗌 𝗅𝗂𝗄𝖾 𝗐𝖺𝗇𝖽𝖾𝗋𝗂𝗇𝗀 𝗂𝗇 𝗍𝗁𝖾 𝖽𝖺𝗋𝗄 𝗐𝗂𝗍𝗁𝗈𝗎𝗍 𝖺 𝖿𝗅𝖺𝗌𝗁𝗅𝗂𝗀𝗁𝗍. 𝖥𝗋𝗈𝗆 𝗍𝗁𝖺𝗍 𝗆𝗈𝗆𝖾𝗇𝗍 𝗈𝗇, 𝖽𝗈𝖼𝗎𝗆𝖾𝗇𝗍𝖺𝗍𝗂𝗈𝗇 𝗐𝖺𝗌 𝗆𝖺𝖽𝖾 𝖺 𝗆𝖺𝗇𝖽𝖺𝗍𝗈𝗋𝗒 𝗉𝖺𝗋𝗍 𝗈𝖿 𝖾𝗏𝖾𝗇 the 𝗍𝗂𝗇𝗂𝖾𝗌𝗍 𝖾𝗇𝗁𝖺𝗇𝖼𝖾𝗆𝖾𝗇𝗍 𝖺𝗇𝖽 𝗐𝖺𝗌 𝗂𝗇𝖼𝗅𝗎𝖽𝖾𝖽 𝗂𝗇 𝗍𝗁𝖾 𝗌𝗂𝗀𝗇-𝗈𝖿𝖿 𝖼𝗁𝖾𝖼𝗄𝗅𝗂𝗌𝗍 𝖺𝗇𝖽 𝗂𝗇 𝗍𝗁𝖾 𝖼𝗁𝖺𝗇𝗀𝖾 𝗆𝖺𝗇𝖺𝗀𝖾𝗆𝖾𝗇𝗍 𝗉𝗋𝗈𝖼𝖾𝗌𝗌.

𝖱𝖾𝗅𝗒𝗂𝗇𝗀 𝗈𝗇 𝖺 𝗌𝗂𝗇𝗀𝗅𝖾 𝗉𝖾𝗋𝗌𝗈𝗇’𝗌 𝗄𝗇𝗈𝗐𝗅𝖾𝖽𝗀𝖾 𝗂𝗌 𝖺 𝗌𝗎𝗋𝖾𝖿𝗂𝗋𝖾 𝗐𝖺𝗒 𝗍𝗈 𝗂𝗇𝗏𝗂𝗍𝖾 𝖼𝗁𝖺𝗈𝗌. 𝖨𝖿 𝗒𝗈𝗎𝗋 technology 𝖽𝖾𝗉𝖾𝗇𝖽𝗌 𝗈𝗇 ‘𝖱𝖺𝗏𝗂 𝗍𝗁𝖾 𝖨𝗇𝖿𝗈𝗋𝗆𝖺𝗍𝗂𝗈𝗇 𝖬𝖺𝗀𝗂𝖼𝗂𝖺𝗇,’ 𝗂𝗍 𝗂𝗌 𝗍𝗂𝗆𝖾 𝗍𝗈 𝗋𝖾𝗍𝗁𝗂𝗇𝗄 𝗒𝗈𝗎𝗋 𝖽𝗈𝖼𝗎𝗆𝖾𝗇𝗍𝖺𝗍𝗂𝗈𝗇 𝗌𝗍𝗋𝖺𝗍𝖾𝗀𝗒. 𝖣𝗈 𝗇𝗈𝗍 𝗅𝖾𝗍 𝗒𝗈𝗎𝗋 𝗄𝗇𝗈𝗐𝗅𝖾𝖽𝗀𝖾 𝖻𝖺𝗌𝖾 𝗏𝖺𝗇𝗂𝗌𝗁 𝗅𝗂𝗄𝖾 𝖺 𝗆𝖺𝗀𝗂𝖼𝗂𝖺𝗇’𝗌 𝗋𝖺𝖻𝖻𝗂𝗍!”

𝖯𝖲: 𝘞𝘦 𝘥𝘰 𝘯𝘰𝘵 𝘳𝘶𝘯 𝘐𝘛 𝘭𝘪𝘬𝘦 𝘢 𝘤𝘪𝘳𝘤𝘶𝘴. 𝘐𝘧 𝘙𝘢𝘷𝘪 𝘪𝘴 𝘯𝘰𝘵 𝘩𝘦𝘳𝘦, 𝘸𝘦 𝘮𝘪𝘨𝘩𝘵 𝘢𝘴 𝘸𝘦𝘭𝘭 𝘣𝘦 𝘫𝘶𝘨𝘨𝘭𝘪𝘯𝘨 𝘧𝘭𝘢𝘮𝘪𝘯𝘨 𝘵𝘰𝘳𝘤𝘩𝘦𝘴 𝘸𝘩𝘪𝘭𝘦 𝘳𝘪𝘥𝘪𝘯𝘨 𝘶𝘯𝘪𝘤𝘺𝘤𝘭𝘦𝘴! 😉

𝗗𝗶𝘀𝗰𝗹𝗮𝗶𝗺𝗲𝗿 – 𝗥𝗮𝘃𝗶 𝗶𝘀 𝗮𝗻 𝗶𝗺𝗮𝗴𝗶𝗻𝗮𝗿𝘆 𝗻𝗮𝗺𝗲 𝗵𝗲𝗿𝗲 𝗯𝘂𝘁 𝗻𝗼𝘁 𝘁𝗵𝗲 𝗶𝗻𝗰𝗶𝗱𝗲𝗻𝘁 𝗺𝗲𝗻𝘁𝗶𝗼𝗻𝗲𝗱 𝗮𝗯𝗼𝘃𝗲. 😊

#ITManagement #TechHumour #ITLeadership #ITGovernance #ChangeManagement #ITBestPractices #JSTalks