|
Story time for the young kids in the room: Once upon a time, in my role as a technical consultant for hire at a large multinational corporation, I found myself tasked with a management board presentation. I was filling in for several project managers who were otherwise engaged due to urgent commitments. My responsibility was to elucidate the difficulties stemming from the company's current internal systems integration architecture. I was to outline immediate measures for mitigating existing issues and offer a comprehensive plan for long-term resolution. With only a few days' notice, I prepared the required technical material, knowing well that the management board I was to address had a decidedly technical inclination. As I delved into the presentation, I began to perceive an escalating sense of discomfort in the room. I quickly sought to discern whether the material was perhaps too tedious or excessively technical. Although the management board was known for its technical expertise, I couldn't immediately pinpoint the cause of the unrest. However, clarity struck in a sudden flash when a senior member of management hesitantly inquired, "Why are you using Mark's materials?" Mark, a pseudonym in this story, was the absent CTO who should have been present at the meeting. After an instant of cognitive dissonance, the truth become clear...The CTO, who had engaged my services as a technical consultant, had been presenting my work to the management board for months, all the while assuming full authorship of the technical reports and presentations... |
After about 6 months, he's presenting this identical idea to our team!
Guess what, it was approved by upper management!!
Except, the lack of details he had in his super high level stuff lacked any insights, so I called him out in the next meeting and basically said have you seen this document I've been socialising for the last 6 months!?
He said it was 'different'..