Friday, 24 February 2017 07:06

Clear Project Goals = Better Team Relationships

Written by
Rate this item
(1 Vote)

We hear those words regularly: "We need to be more competitive!" Competition is good and competition is bad. When it’s your company’s product against another companies’ product, it is good.

When competition is within your team, it is not so good. Things go wrong, and things become less than productive. Team Members are so busy trying to sabotage and undermine each other they forget the reason they were all brought together in the first place – to make things happen. The best teams work together with common goals and objectives to be productive.

It’s sort of a 3 musketeer approach: “One for All and All for One”.

A common goal that is well understood is the best way to start a project. It brings clarity to the project team members at the beginning of the project. In reality we start projects were ideas are not fully developed, there are competing goals and there is outright confusion as to why the project team is even in the room in the first place.

What if a project started with a clear goal in mind? Maybe even the business value was well understood too. How about this example:

We are undertaking the consolidation of the Filbert, Dogbert and Wally CRM systems into a single CRM system because the contact center is having difficulty getting a true picture of where a customer is within the sales cycle. We need to establish a scoring system for potential customers in order to focus our contact center agents on customers who are more likely to purchase our products. This will reduce marketing costs by 50%, reduce call length times by 20% and improve our contact center agent’s ability to service our potential customers in an expedited manner. Additionally, our contact center agents will be able to see all potential and current customers in one system and avoid having to switch between multiple systems to locate a customer.

Does the paragraph above sound like a good goal? It’s pretty good because it does contain the problem statement and the business value in one paragraph. It tells a story about why the team is together. It’s also short enough to ramble off in a hallway conversation with an executive. Focus on getting a common goal that is clear to the entire team. Don’t get caught up on explaining the scope in words – try thinking outside the box and use a context diagram or other type of diagram.

Remember a picture is worth a thousand words.

If the goal were stated as, “We are going to consolidate CRM systems.” It would cause more confusion that anything else. It does not answer the question “Why?” because the goal is not clearly understood the team will be confused immediately at the start of the project.

Hold on there cowboy! That goal sounds like a solution. Being specific about a goal can sound like a solution so care needs to be taken to avoid having a goal point to a specific solution. We need to be careful about how these goal statements are crafted to not sound like a solution.

A task list is not a goal. A common goal is more than a list of tasks to complete or items on a checklist. It is about the journey and the destination. How you get there and take your journey as a team is as important as arriving at the destination with the desired results. Productive teams get this and start their journey together by defining the journey. “Guys, HOW are we going to get there? Agile? Waterfall? Scrumban? Combinations of one or more?”.

Think about it a bit. You get assigned to a project and have that first meeting with the project team. Does the team have a conversation about the path the project will take? Does the question “How will we get there?” ever get answered? The conversation typically winds up being, “We will talk about that later when we have more details” or “We just follow the PMO process.” I have shown up to quite a few meetings where the project schedule and tasks were already determined – all without input from the team.

Milestones are not the path to success. They are just points along the journey. Keep in mind that when you reach a milestone successfully that your customers don't say much about your success. “Wow this new 3 dimensional printer is so fast” or “Look at the stuff I can do with it”. No customer has ever said “Thankfully ABC company completed design on March 30th and moved into development using the waterfall methodology to build that new 3D printer.” Seriously I would break out a cold dead trout and slap them with it if that was said. The success here isn’t the fact there were deadlines – obviously there were deadlines and milestones – but rather the product experience by the customer.

Build the shared goal to start your projects off right. The concepts outlined in this article are a small part of Enterprise Analysis and building solid business cases for projects.

Read 4166 times
Paul Crosby

Paul has over 20 years of experience with global projects in the finance, insurance, state government, manufacturing and non-profit sectors as a business analyst and project manager.  Paul served as President and Technology officer for the IIBA Minneapolis St Paul Chapter.  Mr. Crosby has spoken at several conferences including IIBA Minneapolis-St Paul Chapter Meetings, Minnesota Government IT Symposium and Mind Surf Conference on the topics of Process Improvement, Kaizen for the BA, Strategic Enterprise Analysis, Project Management for the BA and Portfolio Management.  Mr. Crosby is currently the CFO for Bob the BA.

Comments  

0 # Bhargav Pathak 2017-03-20 23:42
Nice Article. What really matters is the final product. Its robustness and ease of use and most importantly, when it solves the problem :)
Reply | Reply with quote | Quote

Add comment

Security code
Refresh

search Articles

© BA Times.com 2016

DBC canada 250