Using Enterprise Architecture to achieve competitive advantage through IT. Are you successful or aggravated?

« May 2008 | Main | July 2008 »

June 30, 2008

Role of an Architect: Lessons from the movies - Part 2

- Amit Jnagal, Senior Technical Architect, Infosys

In my previous post, I talked about Henry Fonda's role in 12 Angry Men and the lessons it held for an Enterprise Architect. Let us switch from Hollywood to Bollywood. Consider the movie Lagaan (Year of Release: 2001; Director: Ashutosh Gowarikar; Our Architect: Bhuwan, played by Aamir Khan; Architect's character: Peasant, captain of a novice cricket team).

Lagaan highlights some aspects of an Architect's job - selling ideas, negotiation, leading change etc.

The movie ‘Lagaan’ will always be remembered for having made it to the Oscars from India and being one of the most successful Indian movies of recent times. The word ‘Lagaan’ translates to Tax that the British Government used to collect, from Indian peasants & Kings alike, during their rule. The movie depicts the struggle of a man who is offered a tax release package if he can beat the English at the game of cricket. The only problem is that neither he nor anyone else that he knows understands or has ever played the game. He is given three months time to learn the game, convince others, form a team and beat the English team.

The lessons that an architect can learn from this movie are:
•    Selling ideas & on boarding people
•    Never lose sight of the goal even in turmoil
•    Negotiation
•    Leading change
•    Asking for help
•    Overcoming traditional barriers
•    Having & maintaining faith
•    Courage under fire

Scenes to watch for:
1. In the first half of the movie there is a scene where our architect is thrown the challenge of beating the English at the game. He does not react immediately and waits for the opponent to raise the stake from one year’s tax break for one village to three years tax break for the whole province.

Nothing has taught me to do my due diligence more than this scene from this movie. As an architect you need to know when is the stake good enough to take a risk or walk away. Walking away is extremely difficult for most of us but sometimes it just makes common sense!

2. There is another very interesting scene during the beginning of the match between the two teams.  Since our architect’s team has never played the game of this scale before, they fret when the match starts. Irrespective of the direction of any shot being hit, everyone on the field starts running towards the ball. Till the time the architect instructs everyone to hold their ground and purpose and only pursue shots that are fired in their direction.

I have personally experienced this problem in large scale projects. The team totally loses control from top to bottom when a small issues comes in a high risk, high stakes project. It is at times like these that the architect should preserve common sense and pacify his team. Make sure the issues are tackled in the same way that they are tackled in a medium scale project. He needs to keep panic at bay and maintain order in the functioning of the team.

3. There is another scene shot on the immediate next day after the challenge is accepted by our architect. He still does not have any other player in his team and is looking for recruitment. The approach that he uses is same as that used by Napoleon when he had to get his army across the Alps - by convincing the army that this was in fact not the Alps, but just another mountain. In the movie, our architect ridicules the game of cricket by comparing it with a simple game of stick & peg which everyone is comfortable with. He gets a child to take the bowl and tries to hit it hard with a home-made bat. The setting that he chooses is the village center to get maximum effect.

This scene can teach an architect attributes like idea selling, on-boarding people & leading change. It also gives good insight into how to handle new technology and get your team up to speed. People who have seen this movie will also agree with another lesson that comes from this episode – help can come from unexpected quarters. The first team mate that our architect gathers is a mad fortune teller whom most of the village has written off as a no good, cynic.

4. While the team is practicing for the big day and they are still short of players our architect stumbles upon a hidden talented spin bowler. The problem is that he is an untouchable belonging to a lower caste and none of the other players want to play with him. The way our architect tackles this problem in the movie is by first embracing the new bowler and then reminding everyone of the common goal and common enemy. He also makes it crystal clear that this is not just a game and there is no one in the team whose ego is bigger than the goal. Later in the movie, this decision turns out to be a match winner where this same bowler walks away with the hat-trick.

The corollary on our side is not too hard to imagine. Working with big teams, all of us come across people whose egos sometime wears bigger shoes than their own. It becomes the job of an architect to herd everyone as a team and lead them to a common goal. It also teaches us how to overcome traditions and barriers that they impose.

5. One last scene that I would like to mention is in the last 30 minutes of the movie. The team finds out that one of them has been cheating in the game with the intention of making them lose for his personal gains. As soon as this truth surfaces, the immediate reaction from everyone is to kill that person in utter rage. Everyone besides our architect, that is. He knows that in this last hour, he cannot afford to lose out one player and go to play with one player short. His best bet is to make sure that this person turns around and plays his heart out in the next day’s play. After saving him from the rage of the crowd, he explains him how this is his last chance and how he would need to prove himself in order to stay alive. This gamble pays off handsomely the next day when that person plays instrumental role in clinching a crucial wicket.

The lesson that we architects can take from this particular scene is to never lose sight of the big goal, even under pressure or turmoil. It also teaches us about second chances and the process of renegotiating trust.

June 23, 2008

Role of an Architect: Lessons from the movies

- Amit Jnagal, Senior Technical Architect, Infosys

None of us are new to the entertainment value of movies. They can make us laugh, cry, ponder, put us to sleep, wake us up and can entertain. The use of movies for the purpose of education is not new either. In fact, there is a special genre of movies with educational values, meant for different audiences.

Recently, I was in a discussion with my mentor. We started talking about challenges faced by the new age architects. Gradually, the conversation drifted from these challenges to the amazing world of movies. Soon after that conversation, I was conducting some training sessions for budding architects. The opening act for this training was titled – ‘The Role of an Enterprise Architect’.  While preparing for that workshop, I related it back to the conversation about movies and what lessons can we architects learn from them

Movies (from Hollywood & Bollywood) can offer good lessons to architects and in general provide a good overview about role of an architect.

Let us consider 12 Angry Men (Year of Release:1957; Director: Sidney Lumet; Our Architect: Juror#8 played by Henry Fonda; Architect's character: Juror in a 12 member Jury

It would be highly in-appropriate if I tried to relate the role of an Architect to characters in movies and started with any other movie. 12 Angry Men is a black and white movie which depicts a murder trial for which a jury of 12 members is to deliberate and come up with a decision.

At the start of the deliberation, 11 of the members are convinced that the defendant is guilty of murder in the first degree and one person, only one person is doubtful. For the next one hour, this single gentleman convinces everyone else of the loopholes in the case and gets a 12-0 verdict acquitting the accused of all charges.

Incidentally, this 12th person who single handedly turns the opinion around happens to be an Architect by profession (a civil one though).

The lessons that an architect can learn from this movie are:
•    Consensus Building
•    How to speak your mind and not go with the general opinion when you are not convinced
•    How to use facts to justify your argument when emotions run high
•    Innovation
•    Never, ever to let go of your common sense

Scenes to watch out for:

  • There is a scene in the middle of the movie about a fact presented in the case according to which it takes less than 10 seconds for an injured person to walk about 20 meters. Our architect proves, by enacting the situation, that it is not possible.

I can very easily relate to this situation in architecture work. A lot of time people come to the negotiation table with pre-conceived notions or facts that they believe to be true. If you doubt the authenticity of a fact, go ahead and challenge it. Do some research, collect facts and go back to the table with figures and numbers. It can help you turn the balance to your advantage. The other aspect of our work that this scene highlights is the need and importance of PoC’s to validate hypothesis and bring certainty in projects.

  • Towards the beginning of the movie, there is a scene where the jury talks about a witness who remembers the accused carrying the same knife with which the murder was committed. The architect produces an exactly similar looking knife that he purchased after hearing the argument. He proves that the knife is not extra ordinary and is very easy to get hold of. This shows the importance of doing your homework or research on a project.

This scene again emphasis the value of research and doing your homework. Before going for a discussion, you can find new insights if you spend some time with Google or an expert that you trust. It also teaches us architects to look beyond what the eye can see. Sometimes, the facts are not what they seem.

June 16, 2008

EA Coverage in Orlando (The Gartner EA Summit)

Wow, is the only way to start looking at the turnout in Orlando for the Gartner Enterprise Architecture (EA) Summit held last week (June  11 - 13). More so since all the participants braved the thunderstorms and weather to show up despite stranded flights. For myself, I decided to take matters into my own hands after an unscheduled landing in Tampa and drove down enjoying Florida’s wide lane freeways which seemed surprisingly dry given the stormy weather hours ago.

Back to the EA conference which mostly starred Gartner VPs and Analysts, the whole conference was about Business Architecture (BA), EBA, SOA and Information Architecture.

There was an over bearing importance on Business Architecture and managing the goals of the organization and hence the CEO.

One area which keeps beating us is the missing steps between the as-is to to-be systems. Especially rationalization of systems and the specific options to “simplify” the underlying assets without making systems overly complex as we add BA, BPM, SOA into the mix.

The turnout as mentioned in the Gartner opening by Anne Lapkin (Research VP, Gartner), had an extended industry presence from manufacturing, services industry and telcos besides the regular financial services, retail and insurance segment. While the turnout was huge, we still missed the CIOs in the audience.

Does this mean the CIOs and CTOs relate less to EA? Given the magnifying glass business sponsors have on IT budgets and its alignment to strategic corporate initiatives, EA, information architecture, security are topics getting into the hot seat.

June 11, 2008

The changing discipline of Enterprise Architecture

Recently, I made a presentation (below) on the changing discipline of Enterprise Architecture (EA) at a Butler group event.  It was interesting to note that a majority of the participants had already implemented foundation elements of EA, such as enterprise-wide technology standards and policies.  There was a definite push towards business process architecture.  This obviously got us into SOA territory (when was the last time someone tried to do services without processes?) 

One of the lead Butler Group analysts went on to explain how one can't necessarily do one without the other, especially if we are looking at a business transformation context.  Incidentally, he coined the term ‘Service Oriented Enterprise Architecture’ too, which naturally put a smile on my face as a colleague and I wrote a paper on the missing link between EA and SOA last year. We presented it at the Deutsche Post SOA Days Conference held in Bonn, Germany (this is the pre-eminent SOA conference held in the ASG region).

So, it's good to know that the industry is heading in the same direction.  We need to do a much better job with enterprise IT architecture before going the whole hog into the architecture of an enterprise.  Today, we are still unable to effectively define an execution platform to support a business operating model.  I have also been a fan of learning to walk before one runs!  So, let's get the operating model defined and ensure that we collectively define and model the 4 dimensions of EA for that operating model in a consistent, repeatable and manageable fashion.

The presentation

June 06, 2008

Vendor Architects as Client’s Trusted Advisors

- Mohan Babu K (cross posted from the Managing Offshore IT blog)

Many of my peers enjoy the privilege of being trusted advisors to clients we work with, though I guess this comes with a lot of responsibility too. I use the phrase with caution since in our industry misuse of terminologies are rampant. In a sense, the term ‘trusted advisor’ is akin to another concept of ‘thought leader:’ every technologist and consultant worth her/his salt wants to be in that position though many don’t have a clue of what it takes to be one, or even to continue down the path when closer to that utopian goal.

Case in point, I am on the road this week, traveling with a client team that is embarking on a large integration [SOA] initiative. As is to be expected, they have floated Request for Information (RFI) to software platform vendors and are in the process of continuing down a deeper technical evaluation.

Since an existing Infosys team is already engaged with the client in the application development space, they looked to us for advisory assistance during this exercise. The request came at extremely short notice and we managed to quickly put together a team to for required support to the client and I offered to join them in person. A few interesting aspects jumped out during the exercise:

  • We traveled to two large software vendors headquartered in the West Coast - that I shall not name for obvious reasons – where the vendors put together a series of secessions that included the usual Dog and Pony show along with sessions that were more customized deep-dives with their internal product experts
  •  The client was already aware that we had expertise in the platforms and the fact that we were also tier-1 alliance partners to the vendors being evaluated so the expectation was clear: be our trusted [read impartial] advisor in this engagement
  • My team did factor in the yin-yang from our internal alliance management groups, each of which had an interest in positioning the specific vendor (alliance partner) for obvious reasons: the vendors were leaning on our alliance teams. 
  • Another obvious dynamic that my team in this engagement has to watch out for: client’s projects are downstream work for service providers. But in our eagerness to get started on the work, we should not spur them towards a decision.

While the evaluation is proceeding as expected, my eye remains on the ball :: translating the results of this exercise and evaluation into a strategy that the client’s executives can propose to their stakeholders … which will then have to get projectized…. And will hopefully get executed using our Global Delivery model

The horses are just out of the gate, so it would be hard for me to even speculate on the direction of the evaluation; but stay tuned.

Ps: And in case you are wondering, client’s advisors don’t get the trinkets and t-shirts while accompanying them to the vendor’s company store. :-(