My friend Nikunj brought some books for me yesterday,as always he cares about me for all aspects.Truly amazing friend.
Today I just got time to look in to books,And found one good small books about motivation.
Books is really small one so any one can finish in one session.I would like to mention few points which I like most .
1) Keep Giving Feedback.
The Failure to give appropriate and timely feedback is the most extreme cruelty that we can inflict on any human being.
Human being crave feedback so, if you are trying to be a good leader learn to give timely feedback.
2) Manage Agreements,Not people.
If you manage to make an agreement and get work accordingly , you will never require to manage people.Just make a strong bond through which your subordinate inspire to full fill all agreements.
Those that are most slow in making a promise are the most faithful in the performance of it.
3) Play both good cops and bad cops
If your actions inspire others to dream more, learn more,do more and become more , you are a leader- John Quincy Adams
4) Motivate by Doing
People can be divided into two classes, those who go ahead and do something , and those who sit still and inquire, why wasn't it done other way? -oliver Wendell Holmes.
Figure out what you want to achieve and start achieving , your staff will follow for the same.
5) Use Positive Reinforcement
The first Duty of a leader is optimism.
How does your subordinate feels after meeting with you?Does they feel uplifted?
6) Use 10 Minutes well
Man must not allow the clock and the calender to blind him to the fact that each moment of his life is a miracle and a mystery.
Use following in your routine
I am proud of you
What is your opinion?
If you please....
Thanks you..
7) To Motivate your people ,first just Relax
A Frightened captain makes a frightened crew-lister sinclair
8) Use the power of deadlines..
The best way to predict the future is to create it-Peter Drucker
Just Do it.
9) Let your mind rule your heart.
If you don't think about the future , you won't have one.
10) Make it happen today
There is no tomorrow.
11) Stop pushing
Pull the string and it will follow wherever you wish ,push it an dit will go nowhere at all-Dwight D. Eisnehower
12) Create a Vision
The reason most goals are not achieved is that we spend our time doing second things first.
-Robert J.Mckain
Hope you will have some good ideas about how to motivate your staff? from this post.
Tuesday, January 20, 2009
Friday, September 19, 2008
Easy No , Hard No
When you ask manager to list what are the most difficult things to do?
You will find one answer in top of the list mostly "Saying no"
Here,I would like to explain you Easy no and hard no and how to deal with them.
If your employee come and ask you some thing to finish as per your earlier discussion with him/her.
You will check feasibility and if its not feasible you will say "no, we will do it later on".
This is an easy no.
(a) you have strong logic behind your decision,
(b) Person who is asking is with lower power and authority
Suppose you dont have above two and you require to take decision at that time ,it will be Hard no.
You will find difficulty to get the way of saying hard no.Manager often face this situation.
I read article in Tech republic and found few helpful things.
Know the facts. More you know about the issue , more you will be able to identify problem, solution and more you will be able to defend you decision.
Believe in yourself. If you will doubt yourself then you will find difficulty to win over others.
Don’t take it personally. Always Remain emotionally detached while dealing with this kind of issue.
Understand your position relative to others. Realize that saying no is a statement of position and the weight of your no is dependent on your relative position of authority/power and your persuasiveness.
You will find one answer in top of the list mostly "Saying no"
Here,I would like to explain you Easy no and hard no and how to deal with them.
If your employee come and ask you some thing to finish as per your earlier discussion with him/her.
You will check feasibility and if its not feasible you will say "no, we will do it later on".
This is an easy no.
(a) you have strong logic behind your decision,
(b) Person who is asking is with lower power and authority
Suppose you dont have above two and you require to take decision at that time ,it will be Hard no.
You will find difficulty to get the way of saying hard no.Manager often face this situation.
I read article in Tech republic and found few helpful things.
Know the facts. More you know about the issue , more you will be able to identify problem, solution and more you will be able to defend you decision.
Believe in yourself. If you will doubt yourself then you will find difficulty to win over others.
Don’t take it personally. Always Remain emotionally detached while dealing with this kind of issue.
Understand your position relative to others. Realize that saying no is a statement of position and the weight of your no is dependent on your relative position of authority/power and your persuasiveness.
Tuesday, August 12, 2008
what is procrastination?
Does your to do list increase day by day?Are you adding same task again & again because of UN finished or not yet started status?
That means deferment of actions or tasks to a later time which increase your anxiety,This is by all means Procrastination. It is now common in IT industry as of being over loaded by tons of work to do.
That means deferment of actions or tasks to a later time which increase your anxiety,This is by all means Procrastination. It is now common in IT industry as of being over loaded by tons of work to do.
They do not have any priority table or do not understand work break up structure perfectly. Usually they are not able to interpret meaning of Urgent Task and Important tasks.
Procrastination is had major drawback on psychological manner too…it used to indulge feeling of guild, self-disgust & depression.So, it requires to be cured promptly as it is identified.
Thursday, July 10, 2008
Time estimation of project
Hi use following technique for time estimation of project.
P.E.R.T
Programm evaluation and review technique.
It averages Pessmistic estimation,Most Likely and Optimistic.
A.E.T.=Aprox.Estimated time
P.E.=Pessimistic Estimation
M.L.E.=Most likely Estimation
O.E.=Optimistic Estimatoin
A.E.T.=(P.E+4(MLE)+O.E)/6.
P.E.R.T
Programm evaluation and review technique.
It averages Pessmistic estimation,Most Likely and Optimistic.
A.E.T.=Aprox.Estimated time
P.E.=Pessimistic Estimation
M.L.E.=Most likely Estimation
O.E.=Optimistic Estimatoin
A.E.T.=(P.E+4(MLE)+O.E)/6.
Thursday, July 3, 2008
Assess Yourself for better progress
I understand the mission/vision of my organization. Yes or NoPlease explain answer.........
2. I know what I am accountable for. Yes or No
Please explain answer........
3. I know how to measure my progress. Yes or NoPlease explain answer.......
4. I have the tools, knowledge and support I need to do my job well. Yes or No
Please explain answer.......
5. At work I have the opportunity to succeed daily. Yes or No
Please explain answer.......
6. I receive regular constructive communication from my supervisor. Yes or No
Please explain answer.......
7. I feel my supervisor cares about me as a person, not just as an employee. Yes or No
Please explain answer.......
8. I am encouraged to continually develop my skills. Yes or No
Please explain answer......
9. My opinions are valued by my supervisor. Yes or No.
Please explain answer.......
10. I would encourage anyone who is qualified to work for my organizationand for my supervisor. Yes or No
Please explain answer......
Try to give answers of these questions and assess Your self.....
I got this tutorial from leadershiptools.com
Tuesday, June 17, 2008
Few Quotes to build up spirit.
"Mistakes are the portals of discovery."
- James Joyce
"Results? Why man, I have gotten a lot of results. I know 50,000 things that won't work."
- Thomas A. Edison
"There is no security on this earth: There is only opportunity."
- General Douglas MacArthur
"The trouble with most of us is that we would rather be ruined by praise than saved by criticism."- -Norman Vincent Peale
"Assume nothing, pursue everything."
- Kevin Riper
"The best preparation for tomorrow is to do today's work superbly well."
-Sir William Osler
"To find fault is easy: To do better may be difficult."
- Plutarch
”Coming together is a beginning.
Keeping together is progress.
Working together is success.”
- Henry Ford
”The ratio of We’s to I’s is the best indicator of the development of a team.”
- Lewis B. Ergen
”I am easily satisfied with the very best.”
- Winston Churchill
”The future belongs to those who see possibilities before they become obvious.”
- John Scully
”A championship team is a team of champions.”
- Unknown
- James Joyce
"Results? Why man, I have gotten a lot of results. I know 50,000 things that won't work."
- Thomas A. Edison
"There is no security on this earth: There is only opportunity."
- General Douglas MacArthur
"The trouble with most of us is that we would rather be ruined by praise than saved by criticism."- -Norman Vincent Peale
"Assume nothing, pursue everything."
- Kevin Riper
"The best preparation for tomorrow is to do today's work superbly well."
-Sir William Osler
"To find fault is easy: To do better may be difficult."
- Plutarch
”Coming together is a beginning.
Keeping together is progress.
Working together is success.”
- Henry Ford
”The ratio of We’s to I’s is the best indicator of the development of a team.”
- Lewis B. Ergen
”I am easily satisfied with the very best.”
- Winston Churchill
”The future belongs to those who see possibilities before they become obvious.”
- John Scully
”A championship team is a team of champions.”
- Unknown
Wednesday, June 11, 2008
Things a developer should never ignore
1: Clarifying user requirements
As you spend more time developing an application, you can sometimes predict some of the requests of your customers. Don’t take this for granted and assume you know more than your users do. When you receive the requirements, spend some time with them and review their specification to confirm you are on the same page. Not doing so can end up costing you time as you rework the application later on.
2: Collaborating
Call it brainstorming, call it peer code review, call it whatever you want — but just make sure you collaborate with those around you. Bouncing ideas off others will help you identify any holes in your potential solution and might even help you develop a solution better than your original design.
3: Version control
Anybody who has ever had his or her code stepped on or deleted knows the value of a good version control system. It doesn’t matter if its CVS, ClearCase, or even Visual Source Safe. Get it, learn it, and use it. You don’t want all your hard work to be blown away with a few mistaken keystrokes.
4: Basic system testing
Most developers don’t like to test. Or maybe I should say most developers hate testing. But it’s crucial for you to do your own testing before you release it to anybody else. Nothing will get your testing group upset and knocking on your door quicker than receiving code that doesn’t perform the basics. Make sure entry screens allow input, check that you can’t enter a letter where only numbers are allowed, verify that reports actually print information and that columns add up — the basic stuff.
5: Usability
Early in my career, I designed a screen for a group of data entry users. I thought my design was so slick. The system had all the bells and whistles they needed and then some. I was just about ready to install it when it was pointed out to me that the users almost never used a mouse. My design had added some buttons to the screen and had them lifting their hands from the keyboard over and over. Not efficient for them and very humbling for me. Spend some time to learn about the types of usability issues your customers may have and everybody will be happier.
6: System performance
In this era of instant gratification, it’s hard to satisfy end users. When they click on a button, they expect that the system will immediately respond. Or they may have the misconception that overnight processes really should take only an hour or two. When developing your application, ensure that you understand what type of response the users expect and require.
7: Comments in your code
Comments are the bane of many developers’ existence. We want to spend our time writing code not writing about code. But most of us have been tasked at some point with going in and maintaining somebody else’s work. If you’re like me, you may have sometimes found it so confusing that your first reaction was to rip it all out and start over. My experiences have taught me that even by adding some very basic commenting around sections of code and trying to use descriptive variable names and the like, you can have a significant positive impact on the next person who has to maintain your legacy.
8: Logging
When you’re developing applications (especially those without any type of user interface), make sure you build some helpful logging solutions into the code. There are few worse things for a developer to do than to try to debug an application with little visibility into what is going on when it is running.
It doesn’t have to be overly complex. Maybe just writing out some of the values of your variables or counters at certain places in the code or when it hits certain subroutines. You can set it up so it logs only when a particular environmental condition exists (maybe a specific text file exists in a directory). Trapping anything that is going to help you track down and resolve issues quickly is what you’re going for here.
9: Keeping your skills up to date
Still coding in something a few years old? Many people work for companies run by legacy applications that are past their prime. But that doesn’t mean you should ignore what’s going on in the world around you. A lot of the new technologies out there can be integrated and could provide a boost to you and your company. Take some time to try to understand them a bit, and who knows when you can use it to your advantage.
10: Taking pride in your work
One thing I always thought about and tried to pass along to my teams was the concept of having pride and ownership in the applications we were responsible for. I never wanted to hear that my applications weren’t working at their peak capabilities or that users were happy. And if we did hear about a problem, we would go out of our way to do everything we could to rectify the situation immediately.
It doesn’t matter if you are a head-down developer in a large organization, a systems designer, or a single jack-of-all-trades for your own company. Taking some of these ideas into consideration will not only help you produce a better end product but it will also allow you continue to evolve yourself and your career to the next level.
Source :Techrepublic Blogs and articles
As you spend more time developing an application, you can sometimes predict some of the requests of your customers. Don’t take this for granted and assume you know more than your users do. When you receive the requirements, spend some time with them and review their specification to confirm you are on the same page. Not doing so can end up costing you time as you rework the application later on.
2: Collaborating
Call it brainstorming, call it peer code review, call it whatever you want — but just make sure you collaborate with those around you. Bouncing ideas off others will help you identify any holes in your potential solution and might even help you develop a solution better than your original design.
3: Version control
Anybody who has ever had his or her code stepped on or deleted knows the value of a good version control system. It doesn’t matter if its CVS, ClearCase, or even Visual Source Safe. Get it, learn it, and use it. You don’t want all your hard work to be blown away with a few mistaken keystrokes.
4: Basic system testing
Most developers don’t like to test. Or maybe I should say most developers hate testing. But it’s crucial for you to do your own testing before you release it to anybody else. Nothing will get your testing group upset and knocking on your door quicker than receiving code that doesn’t perform the basics. Make sure entry screens allow input, check that you can’t enter a letter where only numbers are allowed, verify that reports actually print information and that columns add up — the basic stuff.
5: Usability
Early in my career, I designed a screen for a group of data entry users. I thought my design was so slick. The system had all the bells and whistles they needed and then some. I was just about ready to install it when it was pointed out to me that the users almost never used a mouse. My design had added some buttons to the screen and had them lifting their hands from the keyboard over and over. Not efficient for them and very humbling for me. Spend some time to learn about the types of usability issues your customers may have and everybody will be happier.
6: System performance
In this era of instant gratification, it’s hard to satisfy end users. When they click on a button, they expect that the system will immediately respond. Or they may have the misconception that overnight processes really should take only an hour or two. When developing your application, ensure that you understand what type of response the users expect and require.
7: Comments in your code
Comments are the bane of many developers’ existence. We want to spend our time writing code not writing about code. But most of us have been tasked at some point with going in and maintaining somebody else’s work. If you’re like me, you may have sometimes found it so confusing that your first reaction was to rip it all out and start over. My experiences have taught me that even by adding some very basic commenting around sections of code and trying to use descriptive variable names and the like, you can have a significant positive impact on the next person who has to maintain your legacy.
8: Logging
When you’re developing applications (especially those without any type of user interface), make sure you build some helpful logging solutions into the code. There are few worse things for a developer to do than to try to debug an application with little visibility into what is going on when it is running.
It doesn’t have to be overly complex. Maybe just writing out some of the values of your variables or counters at certain places in the code or when it hits certain subroutines. You can set it up so it logs only when a particular environmental condition exists (maybe a specific text file exists in a directory). Trapping anything that is going to help you track down and resolve issues quickly is what you’re going for here.
9: Keeping your skills up to date
Still coding in something a few years old? Many people work for companies run by legacy applications that are past their prime. But that doesn’t mean you should ignore what’s going on in the world around you. A lot of the new technologies out there can be integrated and could provide a boost to you and your company. Take some time to try to understand them a bit, and who knows when you can use it to your advantage.
10: Taking pride in your work
One thing I always thought about and tried to pass along to my teams was the concept of having pride and ownership in the applications we were responsible for. I never wanted to hear that my applications weren’t working at their peak capabilities or that users were happy. And if we did hear about a problem, we would go out of our way to do everything we could to rectify the situation immediately.
It doesn’t matter if you are a head-down developer in a large organization, a systems designer, or a single jack-of-all-trades for your own company. Taking some of these ideas into consideration will not only help you produce a better end product but it will also allow you continue to evolve yourself and your career to the next level.
Source :Techrepublic Blogs and articles
Subscribe to:
Posts (Atom)
