Posted by David | Posted in Leadership, Work | Posted on 06-04-2010
1
Linkedin is a marvelous tool for professionals. This is nothing new and given my limited readership, we probably are connected via Linkedin already.
Here are some personal rules I follow when using the tool:
Don’t collect connections
Only Connect with people you discussed or corresponded with and whom you feel are professionals
Connect with co-workers and former colleagues
Ignore invites from people you don’t know
Import your list of contacts to reconnect with former business partners
Recommend former colleagues but not current colleagues
Rarely ask for a recommendation and only if you already gave one some time before
Use a personal e-mail address for logging in, not a work e-mail address
Register any new e-mail address that you expect people to use now or in the future
Provide a summary and complete profile. Vendors, customers, former colleagues, future colleagues, and prospective recruits are likely to examine it before engaging in business with you.
I don’t see much value in groups or discussions. Unfortunately, signal to noise ratio is very low in those forums.
I religiously follow my connections’ updates and their new connections. This is great to find common colleagues or out of touch friends.
Please share with me your personal rules for Linkedin. I am always interested in learning new tricks.
As a manager you’ve been taught, either by your peers, or through hard knocks, to avoid micromanaging your teams. You quickly learn that micromanagement only alienate people.
Anyway, I have noticed that delegation appears to be a difficult concept for inexperienced managers that I had the opportunity to mentor. Delegation does not come naturally. Newly appointed supervisors often think “If you want something done, do it yourself.”
Delegation of authority is an investment and you need patience and time to see your investment come to fruition. It may take a few weeks, a few months, or a year but your patience will be rewarded in the end.
This is the theme of Jurgen Appelo’s humorous article.
If you are working with teams distributed across multiple timezones, you know how difficult it can be to operate efficiently at times. Over the years, you surely have experimented and tried out different patterns or processes that work in your context.
I have been working for ten years with teams that were in timezones seven to thirteen hours away from my own and we have experimented quite a bit. This is fun and frustrating at the same time.
J.D. Meiers exposes some patterns and practices that will work with distributed teams. I have found that those patterns are not appropriate in every circumstances but they are an excellent summary that will prevent you from reinventing the wheel
We are using Agile methodologies at work and I was looking for ways to explain the fundamental differences between those two development methodologies. It turns out that this video is pretty good at doing just this. Enjoy…