abhijit_sen wrote:
Leadership is not only working for project. It is when you go out of your normal duty calls and do something exemplery. It is when you can inject fresh blood in your team mates when nothing is going right.
Expanding your project from size of 10 to 100+ is leadership trait. Working on one project, and bringing project from another client in same area another example.
Leadership cannot be counted or pointed to. A leader can turn even silly things into countable attributes and a waster can do just opposite of that.
I can do is must however equally at ease should be I can't do because X, Y, & Z .....
Don't wait for oppurtunity, just create them and you are leader.
I understand what you are saying and growing a project from size of 10 to 100 (while I do not clearly understand what growing a project means) is the kind of tangible examples I meant when I said "point to." Whether you count, point to, demonstrate leadership, it still has to be tangible enough to describe. You actually pointed to "injecting fresh blood" and growing a project as examples... and those are the kind of things I wanted to see.
Let me give you examples of the daily duties I would be involved in.
Product management creates requirements for the next product release. The software development team would process them and create design specs out of them. We move on to scheduling and planning for our tasks, implement them, and so on. In this context, what are some things I can mention in terms of leadership? I unofficially managed some junior engineers to provide guidance for their tasks... did some scheduling.. things of that sort. However, are they enough to demonstrate the level of leadership the adcoms would perceive as "great" leadership? Compared to some examples, they seem underwhelming. Perhaps not. That's what I'm trying to understand.
close
Updated on: 10 Mar 2008, 17:51
