Those golden chickens at the grocery store don’t roast themselves, but they might as well. The steps to get them from farm to table have several different stakeholders involved. From farmer to buyer to marketer to food technologist to in-store cook—if each of these parties does their job, a roast chicken is produced. It’s an example of stakeholders aligning toward objectives without the overcomplication of overcommunicating. Each stakeholder trusts the others and consistently delivers.
Communication in project delivery is vital, but sometimes, the less talk, the better. Even with the best-agreed objective, projects risk failure if stakeholder communications aren’t managed. Alignment is the key to success.
DO YOUR JOB
When assigned a new project role, where do you start? To paraphrase NFL coaching legend Bill Belichick, you need to do your job, take care of your responsibility, and do it right.
When setting out to make roast chickens, the farmer’s feedback on the oven temperature doesn’t matter. The marketer isn’t an expert on farming, so they shouldn’t be offering solutions on feed. And the buyer doesn’t need to be suggesting stuffing recipes. The group needs to prioritize trust in each stakeholder’s role over constant communication.
Earning the trust of your stakeholders is consistently doing your job and contributing positively to the overall objective. If your fellow stakeholders know you’ll deliver, they’ll leave you to do so.
ALIGNMENT ON THE WHAT AND HOW
This doesn’t just apply to roasting chickens. My company is designing a new job data system—stores log maintenance jobs, and the system manages the end-to-end process of tasks. It’s a huge amount of data and a lot of moving parts.
The project group is made up of different stakeholders, including users, parts buyers, fixers, dispatchers, and developers. Each stakeholder defines their design and output needs and effectively communicates them to the development team.
Applying the above, the project group needs to jointly determine two things: First, what do we want the system to do? And second, how will we work together to achieve this?
Even if the stakeholders worked effectively to define what success looks like, where projects can hiccup is on the second question: How will the group communicate throughout the process? This difficulty is in the planning of roles, responsibilities, and interactions between the moving parts.
As the popular adage attributed to Benjamin Franklin goes, “Failure to plan is planning to fail.” It’s crucial to align objectives and consider how the stakeholders must interact to identify potential areas of friction. One common area of friction is unsolicited feedback. While most feedback is provided with positive intentions, it can be a distraction and ultimately cause more problems. Stakeholders need to ultimately trust and respect each other’s expertise.
THE PITFALLS OF FAILING TO ALIGN
We all have intentions of aligning, but emotions, personalities, and working styles can impact progress. My approach is defining what my role is and how it contributes to the desired outcome. There is little to gain from progressing down the wrong path if the stakeholders aren’t aligned on what needs to be done.
A common issue with any IT-related project may be differing views between the development and finance teams. Instead of collaborating to align better, stakeholders point fingers. The development team says finance gave them different instructions, while the finance team says the development team ignored their input. Chaos ensues, and it’s a classic case of project goal misalignment.
When personalities clash and misalignments happen, you need a strategy to get back on the same page and prevent those issues in the first place.
THE PROJECT CHAMPION
The alignment of stakeholders is critical, but how do you get a group of passionate subject matter experts with strong opinions back on track? The answer is a project champion.
A project champion is not a project manager, but rather a coordinator who creates a channel for communications. In a recent project, we needed a mild-mannered, clear-thinking, mature person to be the finance team’s point man.
We enlisted “Greg,” whose epic poker face meant we often didn’t know if it was his birthday or his cat had just died. He was perfect for the role because he didn’t get offended or excited—he just took care of business. After three months in the role, alignment, communications, and project outcomes have improved astronomically because he eliminated hot-blooded fighting.
Greg was our project champion. We needed someone who could mediate conflict, take personalities out of the equation, and clearly articulate requirements. The key was that he knew when to move from talking to doing.
Every project is different, but you can pick out a few steps that are good starting points. First, focus on the end goal and build a list of milestones. A good technique is planning in 30-, 60-, and 90-day increments. This allows you to think one milestone at a time. Project teams can get stuck on day 90 problems when there is still plenty that will catch fire on day 30.
You also should be honest about your progress. This often becomes a dance between the project team and the project board. Leaders often don’t understand the technical issues, and what may seem like a straightforward problem, like selling a roast chicken, has lots of moving parts and different parties. The key is walking the line between keeping the board happy and your project manager even happier.
KNOWING WHEN TO STOP TALKING
The difference between a good painter and a master is that the master knows when to stop painting. Similarly, project teams can place a premium on communication, not realizing that less is often more. Just like the roast chicken that makes its way to your table, stakeholders don’t need to speak with each other as long as they are aligned on the outcome. Sometimes, teams just need to stop talking and do their jobs.
Sean is CFO- North America at City Facilities Management