Do you ever want to bounce ideas off someone else? Or learn the way they approach a particular problem? I’m not talking about anyone’s specific capabilities. Instead, we can enhance our abilities by working with someone else. That brings its problem: How do you choose that learning partner? I’ve worked with several partners as a […]
How to Describe All the Value When You Want to Influence Do you ever wonder how to describe the value of the changes you’ve led or want to lead? Fred, a project leader, needs a new job. His company—despite his project’s success—laid him off. He needs to influence hiring managers to look at his resume
Ginny, a project manager, had a frustrating meeting with her boss, Henry, the VP of Engineering. His exact words to her were, “I don’t care how you get it done, but we need all of these two feature sets done. Now!” She explained she needed more teams to finish the work. Otherwise, people would be
Three Planning Ideas to Support Your Future Decisions Many organizations use deliverable-based planning, specifying the various features or products the teams expect to deliver and when. I’m a fan of short-term deliverable-based planning because it focuses everyone on the (few) deliverables. But the pandemic taught us a critical idea: while long-term deliverable-based planning can illuminate
Work Solo or Collaborate? How to Choose Based on What Benefits You Do you prefer collaborative or solo work? Some of us prefer to work alone because we know how to be effective, even if our work is not independent of everyone else’s work. Or, if we work as part of a workgroup, such as
Too many leaders work solo—and that’s because their managers expect them to do so. However, these managers and leaders often need other leaders across the organization to deliver the necessary work. In that case, one-on-ones can help. These peer one-on-ones can help build trust, clear impediments across the organization, and create allies for change. How
The news is full of this “quiet quitting” idea. Supposedly, employees are doing just what the work demands and no more. That sounds reasonable to me. (See the blog post, It’s Time to Clarify Work Boundaries and “Quiet Quitting.”) I don’t see why people should do “more” than a day’s worth of work in a day.
We’re pretty good at knowing when someone is a good fit for a technical role. But how do we know when someone is ready for technical leadership or management? That’s a lot more difficult, and that’s because leadership or management—at any level—is a different job than working in the technology. Here are some ideas based
Fred, a client, asked how I could help him get more work out of his resources. I asked if he meant people. He said yes. So I asked if he focused more on what each person did or if he focused on the team’s work. “Each person.” I smiled and said, “I have a deal
Acme’s project portfolio team was stuck. Three months ago, they’d funded five experimental projects at $150k each. The portfolio team hoped those projects might offer the organization new customers and revenue streams. Now, the project teams reported several concerns: The technology was more complex than anyone had expected. Instead of the teams’ typical 2-4 days