When a large technical program begins to slip, the galvanizing statement is usually, “We’re behind schedule.” Milestones move. Forecasts change. Leadership demands more frequent reporting. In complex enterprise environments, the schedule is usually the most visible indicator of trouble, but it is rarely the original source of the problem. By the time delivery dates begin … Continue reading Most Program Failures Aren’t Schedule Failures — They’re Dependency Failures
Author: Jim McMullen
I’m Writing Again
For the past couple of years, I haven’t written much publicly. That wasn’t accidental. My focus was on leading complex technical programs — platform migrations and integrations, post-acquisition system alignment, and large cross-functional initiatives where the margin for error is small and the stakes are high. Those kinds of programs demand attention. They also leave … Continue reading I’m Writing Again
15 quick tips on written communication for project leaders
As project managers and team leaders, effective communication is vitally important to provide instructions to team members, persuade stakeholders to take action, document decisions and requests, and provide informational updates. Here are some quick tips for those of you in a leadership role on project teams, program management, or any business leadership role, really. Chat … Continue reading 15 quick tips on written communication for project leaders
Is Bulleted Text the downfall of communication?
A colleague said last week that bullet lists are the "bane of business communication" and attributed billions of dollars of damage to them. He's a good writer and a thoughtful guy. His prose is better than most and includes a lot of information that he feels the reader needs to know. I see his point. … Continue reading Is Bulleted Text the downfall of communication?
What we can all learn from Stack Overflow’s security incident
Stack Overflow had a security breach, and they have generously shared the details of how a hacker worked through multiple layers of security over 11 days. They gained access to source code, security keys, build processes, and some PII. Reading their account (at https://stackoverflow.blog/2021/01/25/a-deeper-dive-into-our-may-2019-security-incident) really brought home an important lesson... small issues in overlapping layers … Continue reading What we can all learn from Stack Overflow’s security incident
Try Fail Learn Grow 