Many challenges within a project arise when team members notice the tip of an iceberg, representing a problem, but hesitate to call it out. Often, people feel it’s not their place to speak up, worry about potential reactions from others, or question their qualifications and experience in calling it an issue. Sometimes, apathy can also contribute to this silence.
However, the consequence of not calling out the proverbial iceberg is that when it eventually hits, the impact is detrimental to everyone involved with the project, including the hesitant observer.
Granted that sometimes even calling it out might not do much good if you are surrounded by people who only think that their experiences matter or resist acknowledging problems they must confront. Nevertheless, call out you must. Because if there is any chance of avoiding a problem in the project, you must take it. Even if no immediate action is taken, documenting the concern in writing becomes essential for future reference and lessons learned.
Your career is not going to be about one project, but the habits you develop during projects will shape your lifelong learning. Reflecting on such past experiences can prove valuable in subsequent projects, years down the line. Furthermore, consistently looking for early warning signs and addressing potential risks before they escalate becomes a valuable skill.
And call it out in a manner that you are heard and acknowledged. Just whispering about a problem or sending a subdued email amongst the pile of the day does no one any good. If the need be call it out repeatedly until someone actually listens to it.
Every Project and Team can benefit from the tagline of the New York Police Department “If You See Something Say Something“