Tag: challenge


Ce billet est aussi publié en français sur mon blogue.

In a previous post (in French), I was telling you that my LinkedIn profile has generated some interesting opportunities, one of my HEC Montréal teachers asking me to go in one of her master class to speak about challenges the analyst meet in an integrated systems projet.  The premises behind this idea are very interesting, and those of you who studied in IT at HEC Montréal will agree with me.

Indeed, no matter the interest coming from ERP-style software like SAP, and despite their growing popularity, ERP are rarely the unique solution to business problems in an organization.  Actually, solutions to these problems are usually made of many systems (some of them being already in place) that need to interact closely, and among which we may find an ERP system.

Considering this, we might argue why IT programs at HEC Montréal (and probably in other universities) are so focused on teaching through SAP or other ERP systems (although I learned a lot through these classes).  Based on that and on my last 5 years on two major non-ERP projects, I identified the 7 biggest challenges faced by a business analyst in a integrated systems (plural form) project.

    1. Expanded horizons: understand the organization and its systems
    2. Define a vision: create solutions without destroying the current one
    3. Communicate better: many systems means many friction points
    4. Teams work: many systems means many teams
    5. Meet commitments: commit to provide a stable solution
    6. Rush for success: go ahead in an iterative way to reach your objectives
    7. The IIBA to get it done: structure and methodology to succeed

These behaviors are not specific to this type of project, but are especially critical when you are in one of these.  Check out my blog in the upcoming weeks; all these challenges will be covered by a detailed post.  This list will get updated with links to these posts.

Have you ever found yourself in this situation?  How did you get through it?  Leave your comments!

Le leadership est mort, vive le constructivisme

Étant chef d’équipe depuis peu, j’ai commencé à lire quelques trucs sur les caractéristiques d’un bon leader, afin d’en devenir un éventuellement.  Je suis en train de lire Influencer: the power to change anything (revue à venir), un livre très intéressant sur la façon d’influencer les gens dans une direction particulière.

Récemment, je suis tombé sur un article très intéressant du Harvard Business Review qui remettait en question toute la notion du leadership, que l’auteur décrit comme étant une notion du 20e siècle appelée à disparaître!

Le problème tourne essentiellement autour de ceci selon l’auteur:

Today’s biggest human challenge isn’t leading broken organizations slightly better. It’s building better organizations in the first place. It isn’t about leadership: it’s about « buildership », or what I often refer to as Constructivism.

Le constructivisme (par opposition au leadership) serait donc axé sur la mise en en place de nouvelles façons de penser, plutôt que d’améliorer celles en place; sur la création d’une prospérité plus authentique.  Les exemples donnés par l’auteur (Ghandi vs Obama, entre autres) appuient très bien la réflexion, et le manifeste du constructivisme est aussi une bonne illustration du concept:

The Builders’ Manifesto

  1. The boss drives group members; the leader coaches them. The Builder learns from them.
  2. The boss depends upon authority; the leader on good will. The Builder depends on good.
  3. The boss inspires fear; the leader inspires enthusiasm. The Builder is inspired — by changing the world.
  4. The boss says « I »; the leader says « we ». The Builder says « all » — people, communities, and society.
  5. The boss assigns the task, the leader sets the pace. The Builder sees the outcome.
  6. The boss says, « Get there on time; » the leader gets there ahead of time. The Builder makes sure « getting there » matters.
  7. The boss fixes the blame for the breakdown; the leader fixes the breakdown. The Builder prevents the breakdown.
  8. The boss knows how; the leader shows how. The Builder shows why.
  9. The boss makes work a drudgery; the leader makes work a game. The Builder organizes love, not work.
  10. The boss says, « Go; » the leader says, « Let’s go. » The Builder says: « come. »

Je compte bien m’inspirer de ces deux articles pour guider mes initiatives en 2010.  Si jamais vous avez d’autres livres ou articles à me suggérer sur le leadership, laissez vos commentaires!

EricProvost.net est hébergé par Servage sur Wordpress | Thème: Motion by 85ideas.