Skip to main content

Firing By PowerPoint (Beyond Bullets)

Forget about your antics at the last Christmas party - Cliff points to a real career killer.
beyond bullets: Board Fires CEO Over PowerPoint

Ok, sure there were some other things that may have gone wrong but it certainly re-emphasizes the importance of being about to publicly speak, especially when you're in a role that demands you communicate.

But what role doesn't? The age of "I don't have to communicate with others" is certainly behind us in almost EVERY industry. I get really frustrated when I hear developers or other people of a technical nature say "I don't present" or "I don't like to talk about what I'm doing". If you can't make what you do sound interesting, something needs to change.

Now communication is a two (or more) way street and I'm sure many have stopped reading or listening to certain people because they don't like what they hear or what the person has to say. That's fine.

But to be in any kind of position of responsibility and not be able to communicate effectively strikes me as nuts and while it may not get you fired as this CEO was, it certainly draws into question the qualities that you may have been hired for in the first place.

(this may sound like a rant and I'm sure many can point to examples where I have mis-communicated and had to restate something, but the point is not mis-communication, rather it's simply BAD communication. Then again, maybe I'm frustrated because I've dealt with too many people where I've simply flipped the bozo bit! - because of their inability to communicate. They may have talent but the head in the sand attitude doesn't always fly. Anyways, now I'm off on a tangent so I'll stop here but point to another bozo bit article (here.)

I can appreciate that technology can be tricky for execs but if it's the industry you're in, it really shouldn't be. (I sat in on a online presentation recently where none of the slides worked - and it was a presentation on webinars, ironically - and only the audio was there. The company blamed the provider but then yesterday, I went to a similar presentation with the same providerWebex (but different company) and they had more people attend and it worked. )

That post should certainly be a wake-up call, Cliff - Thanks!

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...