Tuesday, June 11, 2013

Key Takeaways



I came into this class wondering what I would learn from an IT class in my MBA program, since I am already an IT professional.  What I experienced was a leadership class that used IT strategy as the primary focus.  First, it gave me some specific models to use to describe situations along with insight into right way to use them.  It gave me insight into the risks I may unknowingly bring upon myself and prompted me to surround myself with different viewpoints as a way to mitigate risk and improve strategy.  Finally, I was reminded that we get the behavior we reward;  if I need my team or my customer to behave a certain way, I must think of a strategy to draw out the behavior I want to see and reward it when I see it.  

1.  Technology Adoption Model (TAM):  Perceived ease of use and perceived usefulness lead to changes in behavioral intention.  Behavioral intention leads to actual use.

This model succinctly describes the intended outcome of the analysis and planning activities in a project.  Success criteria and project vision should map to the goals above for a project to start on the right track and stay there.  I will use this model throughout projects to challenge people at each stage of the process to confirm that we are building a system that will be perceived to be useful and easy to use.  I will also consistently involve business customer feedback in the process, so if a project team starts to drift away from the target, the customer can bring us back into alignment.

2.  Remember IT in the mergers and acquisitions process

Unexpected costs in mergers often occur when IT has not been included in the M&A process.  Solving systems problems at the last minute can lead to fire-fighting solutions, frustrations, and bad outcomes for the bottom line.  I will continue to encourage my business partners to bring IT into the discussion very early into the acquisition process.  I will also make sure that IT is prepared to participate in the discussion.

3.  Hidden Traps in Decision Making:  Anchoring - be aware of the risk of giving something to react to.  

This is a very meaningful takeaway for me.  In IT we often will provide wireframes, prototypes, and mock-ups to try to get input from our customers.  While I have always believed in this strategy, the hidden trap is that I am setting up my customers to accept my solution whether it actually suits their needs or not.  To address this, I will try not to take this shortcut too early in the development process.  I will continue to focus on outcomes and business needs longer into the timeline before suggesting a solution.  I will encourage my team to do the same.  I believe this approach will lead to more business-relevant outcomes and better technology adoption.  It will be a challenge to find the right balance of avoiding the anchoring trap will quickly delivering technology.

4.  Hidden Traps in Decision Making:  Confirming-Evidence - surround myself with differing opinions.

As a project manager, I always seek to harmonize the team as quickly as possible.  Having like minds and people who get along can be helpful in this process.  I understand now that this could actually present risk for my projects.  To address this issue, I will seek out constructive dissenters.  I will try to bring in people who are willing to discuss alternatives in a civil and professional format and who are willing to stand up for what they think is right.  In support of these efforts I also must improve my own level of patience.  These conversations will take longer but yield better results.  I will also need to create a culture within my team where we can safely disagree with one another.

5.  We get the behavior we reward

This means that we should expect most employees to model the example set by managers and the people they promote.  I think of it as a carrot-only approach that sets the stage for positive reinforcement.  I cannot increase the salaries of people that don’t report to me, but I can provide good feedback to leadership and provide positive exposure for team members who do a good job.  I can also provide more autonomy for team members who are willing to collaborate and willing to engage in creative problem solving.



No comments:

Post a Comment