Throughout our life we are driven towards success. In our childhood, our schools, sports, work, play, success is key. Sometimes it is classified as money, sometimes cars / homes / or other worldly things. Sometimes it is job title.
BUT there are other ways to define that achievement. Maybe it isn't the finish line, but rather the methods and accomplishments along the way to get there. Are they more important?
I often use the following as my personal email signature. Seeing it as I send emails allows me to keep a healthy perspective.
"Try not to become a man of success, but rather try to become a man of value." -- Albert Einstein
Tuesday, February 26, 2008
Business Analysis
How much time do you spend on your projects in the business analysis phase? Have you taken the time to research and record your business requirements? OR, do you hastily jump right into the design and solutions?
A just published survey from IAG notes " Almost 70% of companies surveyed set themselves up for both failure and significantly higher cost in their use of poor requirements practices."
A just published survey from IAG notes " Almost 70% of companies surveyed set themselves up for both failure and significantly higher cost in their use of poor requirements practices."
Thursday, February 21, 2008
Leadership -- plain and simple
I heard a good speaker today at a luncheon meeting. Her topic was leadership in Project Mangement.
While there are many, many good books out on leadership, and I have read quite a few including several articles lately, here are some key points to keep in mind.
A good leader is .....
* Not the same as a manager
* Asks inquisitive questions, sometime challenging questions
* Not the answer guy. S/he challenges others to do thinking and have or develop answers
* A motivator
* Exciting, excited and excitable. Encourages others to be the same
* Promoter of people, of thinking, of outside the box thinking when needed
* Yet, keeps focused to the point when necessary. i.e., keeps the main thing --- the main thing
* Has style
* Has respect for others
* Actively solicits input
* Not controlling, that is, willing to flex rules where appropriate.
Where are your weaknesses as a leader? Do you know them? Are you constantly attempting to improve yourself? Do you solicit feedback about both your known and unknown weaknesses? Are you open to honest feedback?
One must always have a mission to grow !! To grow, is to live !!
While there are many, many good books out on leadership, and I have read quite a few including several articles lately, here are some key points to keep in mind.
A good leader is .....
* Not the same as a manager
* Asks inquisitive questions, sometime challenging questions
* Not the answer guy. S/he challenges others to do thinking and have or develop answers
* A motivator
* Exciting, excited and excitable. Encourages others to be the same
* Promoter of people, of thinking, of outside the box thinking when needed
* Yet, keeps focused to the point when necessary. i.e., keeps the main thing --- the main thing
* Has style
* Has respect for others
* Actively solicits input
* Not controlling, that is, willing to flex rules where appropriate.
Where are your weaknesses as a leader? Do you know them? Are you constantly attempting to improve yourself? Do you solicit feedback about both your known and unknown weaknesses? Are you open to honest feedback?
One must always have a mission to grow !! To grow, is to live !!
Monday, February 11, 2008
How much techie is needed to do your job, OR....
If you have been in the business and tech world, how many times have you been present in a meeting where the "techies" start the techie talk jargon, and soon everyone must be at that same level or lose out?
Ever been present in a conversation or situation where someone, not necessarily a traditional techie by profession, thinks he/she must talk techie? Maybe has a family member who has taken a training class, lets say in Microsoft Access? And now they both think they are database experts? Or worse --- they have worked with a leading database vendor, written several dozen SQLs and now think they should be designers?
Why? Why? Is it that being "techie" or knowing how to speak "techie" gives one more value and / or credibility?
I used to be a techie many, many moons ago. (back before it became "I/T", and even before it was commonly known as M.I.S.) I gave up tryinging to keep up with the industry because the I/T industry is changing too fast. Current techie knowledge will be obsolete before the day is over.
And guess what? I still have a challenging career without that knowledge. I found out that it is best to let that level of detail to those others who want to stay with that level of activity. I can direct, manage, and lead those folks, and simply depend upon them to make the best decision. I don't need to know......
That last thought is a hard one for many people. There is an apparent belief that you must know the details in order to understand. Is that important? If others have that responsibility of knowledge, do you have to also? Redundancy and duplication of effort? Does my detailed knowledge significantly contribute to the solution at hand, especially if they have the stronger skill set? For illustration purposes, think of that car you drive every day. Do you personally know the details of how that enginre purrs, the electronic window opener that opens the right rear window as you drive, the heat that pours into the back seat as you turn the switch on the dash, the sound that changes from front to back by the push of a button?
Back to the original issue: How much techie is needed to do your job? If you are an I/T professional, with a speciality, stay with it, ensure growth, but always remember there are other technical specialities that supercede yours. (it never ends....)
And if you are a business professional, by all means, strive to learn and understand more about the technical world. Abuse that knowledge growth by searching out those with more expertise. AND.... guide them with your business knowledge towards a solution. The biggest factor of that last message is this ----- business, business problems, business solutions, are what it is all about!!!!!! Business gives us our paychecks, business is about customers and clients, business is about growth and prosperity. Technology is just a tool to support business. Perspective!!
Ever been present in a conversation or situation where someone, not necessarily a traditional techie by profession, thinks he/she must talk techie? Maybe has a family member who has taken a training class, lets say in Microsoft Access? And now they both think they are database experts? Or worse --- they have worked with a leading database vendor, written several dozen SQLs and now think they should be designers?
Why? Why? Is it that being "techie" or knowing how to speak "techie" gives one more value and / or credibility?
I used to be a techie many, many moons ago. (back before it became "I/T", and even before it was commonly known as M.I.S.) I gave up tryinging to keep up with the industry because the I/T industry is changing too fast. Current techie knowledge will be obsolete before the day is over.
And guess what? I still have a challenging career without that knowledge. I found out that it is best to let that level of detail to those others who want to stay with that level of activity. I can direct, manage, and lead those folks, and simply depend upon them to make the best decision. I don't need to know......
That last thought is a hard one for many people. There is an apparent belief that you must know the details in order to understand. Is that important? If others have that responsibility of knowledge, do you have to also? Redundancy and duplication of effort? Does my detailed knowledge significantly contribute to the solution at hand, especially if they have the stronger skill set? For illustration purposes, think of that car you drive every day. Do you personally know the details of how that enginre purrs, the electronic window opener that opens the right rear window as you drive, the heat that pours into the back seat as you turn the switch on the dash, the sound that changes from front to back by the push of a button?
Back to the original issue: How much techie is needed to do your job? If you are an I/T professional, with a speciality, stay with it, ensure growth, but always remember there are other technical specialities that supercede yours. (it never ends....)
And if you are a business professional, by all means, strive to learn and understand more about the technical world. Abuse that knowledge growth by searching out those with more expertise. AND.... guide them with your business knowledge towards a solution. The biggest factor of that last message is this ----- business, business problems, business solutions, are what it is all about!!!!!! Business gives us our paychecks, business is about customers and clients, business is about growth and prosperity. Technology is just a tool to support business. Perspective!!
Thursday, February 07, 2008
Think before Do
The message of the last post may have have lost its impact. This may have been because of my attempt to make a point about a specific instance.
It is often human nature to resolve problems that face us. Unfortunately sometimes we jump right to creating a solution.
THINK about it. And then even think about thinking. Guess what results -- deeper review may find options, alternatives, and event the ROOT cause, not just symptions.
THEN --- DO and ACT. This will likely result in better results.
It is often human nature to resolve problems that face us. Unfortunately sometimes we jump right to creating a solution.
THINK about it. And then even think about thinking. Guess what results -- deeper review may find options, alternatives, and event the ROOT cause, not just symptions.
THEN --- DO and ACT. This will likely result in better results.
Saturday, February 02, 2008
What vs. How
In the business world, there is always some challenges in front of us. Maybe, its a new product, maybe it is a problem needing to be solved. Sometimes maybe its not a problem to be solved but a symptom being encountered.
Clarifying the true problem or challenge needs to be clarified (that sounds like another story for another blog entry) We are always in haste to solve it.
Therein is a major concern. The business factors, that is, the business requirements *needs* should be clarified. That is, the WHATS.
Once that is clarified, then you can pursue the HOW to solve it, i.e., the design and the actual solution.
If you try to address HOW, before WHAT, are you sure you are in agreement of what you are trying to solve? are you sure you are pursuing the right problem? Are your peers, superiors, and subordinates necessarily in alignment? OR are you just assuming? (don't forget the old expression about when you assume, there is an a.. between u and me....). Hasty decisions generate mistakes, costs, and rework .......
Clarifying the true problem or challenge needs to be clarified (that sounds like another story for another blog entry) We are always in haste to solve it.
Therein is a major concern. The business factors, that is, the business requirements *needs* should be clarified. That is, the WHATS.
Once that is clarified, then you can pursue the HOW to solve it, i.e., the design and the actual solution.
If you try to address HOW, before WHAT, are you sure you are in agreement of what you are trying to solve? are you sure you are pursuing the right problem? Are your peers, superiors, and subordinates necessarily in alignment? OR are you just assuming? (don't forget the old expression about when you assume, there is an a.. between u and me....). Hasty decisions generate mistakes, costs, and rework .......
critter pictures
This is a posting to validate I can incorporate pictures into a blog
Almost all of these are in my own back yard.
Almost all of these are in my own back yard.
Subscribe to:
Posts (Atom)