Create effective behaviors to achieve a project’s purpose

Most companies have mission statements or credos. Some successful companies also use aphorisms effectively. Should we use a similar strategy at the project level? I believe so. I manage technical projects. The technical design brief is an important document. It level sets the team on topics such as design features, performance features, target market, sales volumes, etc. The technical design brief tells the team what we need to execute but it doesn’t provide the higher purpose or drive behavior.

Each project team member shows up for basic reasons. Some only care about earning a salary. Others strive for the next promotion. Some simply have a passion for the product or service they create. Every individual is motivated differently but the challenge is to get a group of people to work together to achieve a project’s goals. One idea is to look beyond the technical design brief and establish the purpose. For example, a new medical device may provide patients more freedom to do tasks on their own versus depending on a family member or nurse. Before a project kickoff, try sharing personal stories of individuals that will benefit from your product. Doing so will connect your team to the project’s purpose and will help motivate the team to dig deep and work hard during the tough times.

I’ve eaten at Shake Shake and enjoy their burgers. I researched the company and learned it is part of a successful restaurant group that struggled early on. Danny Meyer is the founder of Union Square Hospitality Group. He is known for short phrases (aphorisms) that provide vivid guidance of the behaviors he believes are critical to success. These behaviors help individuals provide excellent service and solve problems without explicit direction from a supervisor. Some of them include:

1. Bring a Charitable Assumption and err on the side of generosity
2. Center the Salt Shaker with an unwavering commitment to the excellence and the values that matter most
3. Write a Great Next Chapter. The road to success is paved with mistakes well-handled.

If your company has official corporate behaviors, I recommend you piggy back on them and establish additional ones for your Project Management Office (PMO), Research and Development (R&D), or project team. My teams do not have documented behaviors at the project level. I’m thinking of creating some related to communication and team support since most of my team works remotely. Here are a few that come to mind.

1. Signal Often (share critical information and raise concerns ASAP)
2. Close Open Loops (dont let questions go unanswered or let tasks go incomplete)
3. Be A Shoulder To Lean On (we should be ready and motivated to help each other)

Please leave a comment to share any behaviors that have helped guide your team’s success. For additional reading, check out The Culture Code by Daniel Coyle and Setting the Table: The Transforming Power of Hospitality in Business by Danny Meyer.