Gathering project perspectives

/0 Comments/in /by

Effective project managers work to understand the diverse perspectives stakeholders have about a project, so they can manage conflicts and keep everyone engaged. Interviews and polling are two standard approaches. Here are other effective methods to gather different viewpoints of a project.

  • Interactive workshops. To identify project perspectives that are otherwise hard to uncover, consider brainstorming, mind-mapping, or other approaches involving rich interaction between stakeholders. The benefit of interactive workshops is that you can connect ideas to the outcomes stakeholders expect from the project. Free-flowing discussions can also generate new ideas, which might expand the value the project brings to the organization.

  • Focus groups. These meetings allow for in-depth discussions and can reveal nuanced opinions that might not come up in larger settings. Focus groups aim to gather insights, while the goal of an interactive workshop is to solve problems, generate ideas, or provide training actively. A consensus is often the target of interactive workshops, which is not the case for focus groups. For example, an interactive workshop would be appropriate to develop potential new processes for billing customers and then select the best option by consensus. A focus group would be held to collect features that various customers would want from a new version of a product. In the focus group, consensus isn’t the goal. It’s collecting a broad set of ideas for new product features.

  • Establish a sponsorship committee. A sponsorship committee can provide ongoing insights and guidance throughout the project’s lifecycle. The committee doesn’t reduce the sponsor’s decision-making power. It enables people to present other perspectives to assist the sponsor in setting project direction.

  • Job shadowing. Shadowing is a powerful approach to gathering project perspectives. Observing stakeholders at work provides unique insights into how people perform their work and the potential improvements the project can deliver. Stakeholders often don’t know the potential of new tools or have difficulty articulating business challenges.

  • Town hall meetings. Town hall meetings can reveal perspectives for projects with a broad impact on communities within and outside the organization. These events capture a wide range of viewpoints and concerns. Pro tip: Have an experienced facilitator run town hall meetings, because managing meetings with widely disparate stakeholders can be challenging.

  • Cross-functional team rotations. Implement short-term rotations where team members work in different project areas or departments. This cross-pollination of ideas can bring fresh perspectives to the project.

Think about your current project or a recent one. How did you uncover stakeholders’ perspectives about the project? Would any of these methods help identify perspectives?

For more about stakeholders, check out Natasha Kasimtseva’s Managing Project Stakeholders course or Dana Brownlee’s Managing Up for Project Managers: Working with Challenging Senior Stakeholders.

Coming Up

Office Hours Live Survival Tips for Managing a Difficult Boss, Wednesday Dec 4, 2024, 9:00 AM MT

We’ve all had at least one – a boss that makes our jobs challenging if not impossible. They come in several forms,each with their unique challenges, such as the clueless chameleon, the MIA boss, the meddlesome micromanager, the wishful thinker, and more. In this Office Hours, Dana Brownlee joins me to talk about the different types of difficult bosses, how to identify which one we’re dealing with and what we can do to work with them successfully. To sign up, click here.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 81,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________

Integration is a people first process

/0 Comments/in /by

Project integration can be tricky when you combine multiple technical components, processes, or both. Most people focus on the technical side of an integration. Yet, the problems in integrations are often technical errors caused by communication and human elements. Here are some actions that help prevent technical issues with integrations.  

  • Specifically assign ownership. Two or more teams serving as owners on an integration exercise is asking for trouble. Like with project tasks, assign one owner to coordinate integration efforts and guide the teams. That way, decisions are made on time and you avoid the “left hand thinking the right hand was working on this” type of issue.  
  • Create a communication plan specific to each integration. Communication between all teams is critical for success in integrations. Create a communication plan so all parties know how, when, and who will direct integration teams. It doesn’t have to be overly detailed. Make sure that team communication is managed and kept in a version-controlled central location. Assign primary and backup points of contact. Share issues related to people or technical issues between teams with critical project personnel even if they aren’t a member of an integration team (think project manager). 
  • Create cultural alignment. Teams from different companies or geographies will have different cultural norms. As a result, decision-making, problem-solving approaches, and engagement with different companies can vary dramatically. Creating cultural alignment around how the teams operate is important for integration success, but often overlooked. Work with the people assigned as integration owners to create cultural alignment between teams in an integration exercise. 
  • Don’t skimp on travel. Integration teams must work together smoothly, and technical integrations must work perfectly to achieve project success. Allow the teams to work in the same space and examine the same technical tools and components together. This makes a huge difference when it comes to working efficiently. You can avoid expensive technical misinterpretations by co-locating integration team members at various times during their work. The efficiencies gained and the technical errors avoided will more than make up for the travel expense.
  • Assemble the best possible change management review team. Integrations are complicated. Effective change management is crucial. A review team with knowledgeable team members and management is essential. Experienced integration project managers will often have a different review team for integration changes because of the depth of knowledge required to make appropriate decisions. This often means two change reviews, one with the integration review team and the second with the standard project review team. The extra time is worthwhile to ensure the best minds review integration-related changes.

For more about project integration, check out Oliver Yarbrough’s Project Management Foundations: Integration course.

Coming Up

Office Hours Live – Survival Tips for Managing a Difficult Boss Wed, Dec 4, 2024, 9:00 AM MT

We’ve all had at least one – a boss that makes our jobs challenging if not impossible. They come in several forms, each with their unique challenges, such as the clueless chameleon, the MIA boss, the meddlesome micromanager, the wishful thinker, and more. In this Office Hours, Dana Brownlee joins me to talk about the different types of difficult bosses and what we can do to work with them successfully. To sign up, click here.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 80,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________

When should the sponsor address the project team?

/0 Comments/in /by

The project manager is the primary communicator with the project team. Sometimes, the sponsor’s presence makes a significant impact on the project team. Here are times to leverage the sponsor’s influence.

  • The Kickoff meeting. This meeting sets the project’s direction and confirms the responsibilities of the project manager and the team. Also, the sponsor can talk about the project’s purpose. It’s powerful to hear this from the manager who will benefit the most from project outcomes. That way, team members can ask business-related questions to clarify project benefits and approaches to deliver those benefits.
  • Recognizing project milestones. The sponsor is the best person to acknowledge progress. The sponsor’s recognition validates the relevance of the project and management’s interest in project success. This pep talk also confirms that the team is on the right track and boosts their motivation. 
  • When significant changes occur. Business, staff, and project conditions often change, sometimes drastically. When that happens, the sponsor must reassert the project’s business value. As a critical member of the management team, the sponsor’s reassurance helps the project team stay focused during turmoil. 
  • When a major issue occurs. Significant issues can derail a project. When a major issue occurs, the sponsor can act as an engaged participant in crisis management. This shows their dedication to the project’s success despite the challenges. The sponsor can also validate and reinforce issue response actions. The project team’s morale and dedication is boosted when they see the sponsor participate in recovering the project, rather than assign blame.
  • Recognizing outstanding performance.  Attention from a senior leader  accentuates recognition. If the sponsor is part of a recognition event, it will be memorable and powerful for the project team.
  • Town Hall meetings. Things change in the business and discoveries during a project may raise questions in stakeholders minds . Town Hall meetings are an effective way to keep everyone up to speed. Have the sponsor present status at these meetings to remind everyone of the project’s importance.
  • Project closure. The sponsor being present at closure is the ultimate form of recognition. This acknowledges the project and the team member’s contribution to the business.

Think about whether there is an opportunity to leverage your project sponsor in your current project. If so, great! Next step, discuss with them how they can help the project by communicating with the team. It’s always good to give them some hints (or direct requests) for points to make.

For more about  project sponsors, check out Antonio Nieto-Rodriguez’course, How to Be an Effective Project Sponsor.

Coming Up

Office Hours Live Survival Tips for Managing a Difficult Boss,  Wed, Dec 4, 2024, 9:00 AM MT

We’ve all had at least one – a boss that makes our jobs challenging if not impossible. They come in several forms, each with their unique challenges, such as the clueless chameleon, the MIA boss, the meddlesome micromanager, the wishful thinker, and more. In this Office Hours, Dana Brownlee joins me to talk about the different types of difficult bosses and what we can do to work with them successfully.

_______________________________________

This article belongs to the Bonnie’s Project Pointers newsletter series, which has more than 80,000 subscribers. This newsletter is 100% written by a human (no aliens or AIs involved). If you like this article, you can subscribe to receive notifications when a new article posts.

Want to learn more about the topics I talk about in these newsletters? Watch my courses in the LinkedIn Learning Library and tune into my LinkedIn Office Hours live broadcasts.

_______________________________________