Building Leadership Skills on Project Teams

I recently had the pleasure of sharing this as a presentation at PMI HNL Professional Development Day 2015 and enjoyed the feedback that I've incorporated into this posting to continue to share and build on thoughts that makes us successful when working with people!

If you want a different outcome, ask yourself what are you doing differently to achieve this outcome.

Requirements

Understand that project teams are made up with people of diverse experience & expertise; while valuable to the team, realize that they each take a different view of the challenge at hand

Physically displaying items – whether in pictures of end result or large words posted on the wall – help clarify and ensure everyone is literally on the same page.

Consider “Draw the Pig” icebreaker – instructions available at:  http://www.whiteman.af.mil/shared/media/document/AFD-130408-056.pdf  

Risk

Draw out the potential outcomes (comic strips are great for actions) – how likely are they to occur?  Are they worth prioritizing? 

Getting Feedback

Post ideas on a large easel sheet of paper (one idea per page) and post in a common area.  Leave markers and encourage people to comment over a few days.  Great for identifying what’s in and out of scope!

Listening

Listening is about asking the right QUESTIONS (not the right answers – if you knew the answer, why are you asking the question?)

Listen to all the information the person shares versus focusing on just what you want to hear – you may miss out on valuable information!

Get a scribe – someone NOT a stakeholder to take notes so that you may engage with your stakeholders.  Then review afterwards with the scribe and highlight key insights from your listening.

Process Definition

How a process works is sometimes better to see in person.  If you can’t physically see the action then act it out (think charades!). 

Brainstorming

Use the “Red Cup” or other object – one idea per person, must say an idea before passing, can only say one idea and continue for a short amount of time with a hard time limit (push people to go faster!) – focus is on QUANTITY not quality.  It removes the “analysis paralysis” by focusing on the object while getting equal participation by all, regardless of position or expertise.  There are no right or wrong answers, just ideas to grow on.

     Question from presentation: Brainstorming in this way could still allow influence on others - YES!  Participants, even though the focus is on equal pariticipation by all, could still be influencing others; however, the goal of brainstorming is quantity.  If you're more focused on not influencing, then anonymous techniques (via email and a facilitator) or non-verbal techniques (using post-its on a wall) may be preferred.  Adjust to your situation!

Prototyping

Build something a user can interact with – SHOW what the envisioned end result is, do not tell them.  Give them something to interact with.

Prioritizing

Write out each item on a post-it, one per post-it.  Then provide stakeholders with poker chips (or other voting item) and have them vote.  They can place as many as they want on each, but no “buying” more.                                                     

Just TRY it!  And build on Lessons Learned!

Excellence in Process

I read a great article in a white paper by IAG Consulting that looked at requirements quality.  I love the idea that the process you use to gather the requirements is more important the the requirements you write.  They premise this on the idea that if you have a solid process to elicit the information, then you will end up with excellent information.  A great point back to the proverbial saying "garbage in, garbage out."

This is such a simple but important thought out to the world - considering your effort (quantity) and your level of attention (quality).  You can certainly apply this to requirements, but you could also apply to almost any activity in any profession!! (Creating scope documents and test plans for my fellow PMs and BAs certainly comes to mind!).

In our fast paced world we so quickly jump into requirements gathering with the excitement to hurry up and write down requirements as fast as we can.  We then spend plenty time going back and revising, editing, re-organizing, adding, editing, deleting and so on until we almost want to start on a clean slate!

What if BEFORE you jump into anything, you write out a quick plan on what you plan to do.  It does not have to be long, just a few minutes, but consider your stakeholders, where the information is today, what do you already know and what do you need to find out.

Consider going grocery shopping.  You have the approach to walk every aisle.  This often ends up with way more in your cart than you planned and often probably a lot longer (and more expensive) than you planned the trip.  You can try run in and just look in certain areas for a few items, finding yourself backtracking and forgetting a few items.  Or, as I often do, I create a grocery list throughout the week.  I then plan to go by the grocery store I'm familiar with at a time later in the week when I know it is not as crowded.  I then go in, get my items (and only my items) and am back out on my way home ready to cook dinner.

This same thought process, while small in comparison, can lead to much stronger quality requirements and project plans.  But too often we simply dive into the activity versus taking a moment and asking ourselves "How are we going to do this?"  Try explaining your process to a younger child - I love hearing their feedback as they will quickly point out any errors in logic!

Spheres of Control, Influence and Control

Working on a team that includes Business Analysts, Project Managers and Software Developers, the sphere of responsibility can quickly grow out of control.  Like any team or organization, prioritization always represents a challenge and a great manager made an interesting thought when some discussion was being made:

"Consider your sphere of control, your sphere of influence and sphere of concern."

I loved this visual concept when thinking about priorities.   I found it a great way to reset myself. 

Think about the things you CAN do (whether you should or not is another thing to think about later) - these are things in your control.  If you can't change how the other team will react, what their priorities are, etc., then stop trying to control it.  Control what you can and prioritize that accordingly.  Then those things you're worrying about - consider what you can influence.  And then only focus on those items.  If you think you have no effect on the outcome, then save your time.  And then concern - what do you need to know so that you can best plan your actions for the future.  These thoughts are great when considering which meetings to attend.  Setup a meeting when you need action - control what you can and influence others to attend and contribute so that you can move on with your deliverables.  When responding to a meeting invite as what your level is for that meeting - control, influence, concern. 

And this can go both ways, especially when considering organizational structures.  A manager that chooses to attend a meeting may positively or negatively influence those attending. 

Everyone is given 24 hours in a day - it is up to you how you spend it, so prioritization gets to be a key component in your daily actions.  So remember what you can control, influence and are concerned about and see if this approach helps you streamline your day for more attention to higher priorities (like surfing! :) ).

What are your thoughts?

More Thoughts on BA's and Change

 
  As in prior posts of Words of Wisdom for BA's, I had summarized some further thoughts on leadership and managing change in the Business Analysis profession.  I figured this was a good "Monday morning food for thought" type of post such to charge you up ready for another week in the challenging world of business.

Comments and thoughts are welcomed and continue to lead change from wherever you find yourself!

Encourage Problem Sharing...but Always Bring Ideas with You

I love this article’s thoughts around ‘problem’ – “can bring any problem, as long as bring at least three ideas for a solution.” Encouraging sharing of challenges AND the ideas that surround them. And the ideas don’t have to be the best solution, just something to plant the seed. Many times these issues arise from those most involved with the work performed, yet they are so removed from the end source that it is hard for them to see a true solution. However, when you encourage them to share their ideas, you are getting end user feedback and insights that a ‘back office’ would never be appreciative of.

You ask someone why they perform a task the way they do and you get the answer “because I was told to” (often by a managing or senior person). This is NOT a bad answer, but perhaps the wrong question. Consider then if you asked the person next “if they could change anything about the process, what would it be an why.” If you’ve established some trust with this person, I’m sure they’ve envisioned many ideas on how to improve the process, create better quality while freeing up more of their time to innovate further.

How are you encouraging others to not just uncover areas of improvement but to encourage the generation of impactful ideas?
Read Adam Bryant's Interview with Jennifer Dulski, COO of Change.org, here.