<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-8552627</id><updated>2011-04-21T21:05:28.579-07:00</updated><category term='quality'/><category term='software product lines'/><category term='tools'/><category term='metrics'/><category term='change managemment'/><category term='management'/><category term='software development'/><category term='efficiency'/><title type='text'>Leader for Success</title><subtitle type='html'>Thoughts on software and high tech leadership
&lt;br&gt;&lt;br&gt;
by Jeffrey Paul Anderson</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>65</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-8552627.post-1329435043718449629</id><published>2008-11-27T15:37:00.000-08:00</published><updated>2008-11-27T16:31:53.472-08:00</updated><title type='text'>Maven, Woodstock and Netbeans 6.5</title><summary type='text'>I spent quite a bit of time trying to "mavenize" our woodstock based project.   I am sure someone will point out how to do this easier, but I was unable to find a reference.   This magic works for me and I haven't been able to find something simpler.  At the high level, what I did was create a standard webapp project with the option to create a dedicated library.  I used the .jars in that </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/1329435043718449629/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=1329435043718449629' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/1329435043718449629'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/1329435043718449629'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2008/11/maven-woodstock-and-netbeans-65.html' title='Maven, Woodstock and Netbeans 6.5'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-8441561403701588100</id><published>2008-07-05T11:15:00.000-07:00</published><updated>2008-07-05T11:45:16.873-07:00</updated><title type='text'>Saving Energy with Wake-on-LAN</title><summary type='text'>Another tech posting, nothing about leadership today.I confess: have a lot of computers.   Two of them are on full time - one hosts a web site and one hosts a development repository using SVN over an SSH tunnel.   After two years of the SVN machine being on 24x7, I wondered if I could put it to sleep and just wake it up when needed.  This led me to the Wake-On-LAN feature which was a little </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/8441561403701588100/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=8441561403701588100' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8441561403701588100'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8441561403701588100'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2008/07/saving-energy-with-wake-on-lan.html' title='Saving Energy with Wake-on-LAN'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-6879181221607248387</id><published>2008-05-10T10:25:00.000-07:00</published><updated>2008-11-12T17:41:07.125-08:00</updated><title type='text'>Repairing an 85W Magsafe Power Adapter</title><summary type='text'>A little different post today - not about leadership, process, or some great new technology.   It's about fixing something yourself; fixing things sometimes pleases me almost as much as creating things.   After you read this, go get a copy of Sam Martin's How to Mow The Lawn.I love my Macbook Pro.  I like the idea of the Magsafe adapter, but I'm not happy with the fact that it's single sourced.  </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/6879181221607248387/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=6879181221607248387' title='12 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6879181221607248387'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6879181221607248387'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2008/05/repairing-85w-magsafe-power-adapter.html' title='Repairing an 85W Magsafe Power Adapter'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_udJRBirzYHg/SCXdWJFm4lI/AAAAAAAAAA0/53h3y0_l0RM/s72-c/Library+-+4448.jpg' height='72' width='72'/><thr:total>12</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-6283583848227053607</id><published>2008-03-30T20:27:00.000-07:00</published><updated>2008-03-30T21:08:44.616-07:00</updated><title type='text'>ACM queucast</title><summary type='text'>The Association for Computing Machinery (ACM) has a podcast series called "queuecast".   It's a fairly quiet feed since many of them are "premium".  But I very much enjoyed the recent queuecast featuring Jason Hoffman, CTO of Joyent.  In the first segment, he talks about how he "isn't interested in evolution", in response to his developers saying they want to iterate and evolve the product.  His </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/6283583848227053607/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=6283583848227053607' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6283583848227053607'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6283583848227053607'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2008/03/acm-queucast.html' title='ACM queucast'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-2463172536262132698</id><published>2008-01-21T08:12:00.000-08:00</published><updated>2008-01-21T08:37:33.058-08:00</updated><title type='text'>Vicious Measurement</title><summary type='text'>ACM's Queue magazine features a regular Q&amp;A column by someone with the pseudonym Kode Vicious.  This month he talks about measurement, in a humorous and short story entitled "Take a Freakin' Measurement".  He makes the case that you should measure as much as it takes to reach your desired level of confidence, but that anything less isn't science.   His style is different than mine, but I think </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/2463172536262132698/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=2463172536262132698' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/2463172536262132698'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/2463172536262132698'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2008/01/vicious-measurement.html' title='Vicious Measurement'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-2443665509694971769</id><published>2008-01-09T19:56:00.000-08:00</published><updated>2008-01-09T20:22:14.164-08:00</updated><title type='text'>Active Design Reviews: So sensible</title><summary type='text'>I'm often embarrassed when I discover a method that has been around for decades, makes perfectly good sense, but I haven't seen it practiced and didn't know about it.  Active Design Reviews (ADR) are such a method.  First described in 1985 by Parnas and Weiss, they devised a system which mitigates non-participation in design reviews. ADR changes yes/no questions asked in a design review (e.g. "do</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/2443665509694971769/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=2443665509694971769' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/2443665509694971769'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/2443665509694971769'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2008/01/active-design-reviews-so-sensible.html' title='Active Design Reviews: So sensible'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-3582149292600676137</id><published>2007-12-16T12:56:00.001-08:00</published><updated>2007-12-16T13:00:26.705-08:00</updated><title type='text'>Government concept of emergency</title><summary type='text'>This really shows the difference between business and government.  In this story in the San Diego Union-Tribune, Schwarzenegger is getting ready to declare an emergency.  But we don't want to rush this emergency or anything:Schwarzenegger will not declare an emergency until early next month, when the Legislature is scheduled to return from its annual fall recess that began in September.</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/3582149292600676137/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=3582149292600676137' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3582149292600676137'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3582149292600676137'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/12/government-concept-of-emergency.html' title='Government concept of emergency'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5074556690429557788</id><published>2007-12-09T16:01:00.000-08:00</published><updated>2007-12-09T16:19:13.282-08:00</updated><title type='text'>Software Engineering Institute and Software Product Lines</title><summary type='text'>SEI has a certificate program in SPL, and I decided I'd take the leap all the way across the country to check it out.  If SPL works, it addresses a problem we've wanted to solve for decades: reuse of working code.   The first course is basically a high speed tour through the book, Software Product Lines, by Paul Clements and Linda Norththrup.  The book is excellent, covering all 29 practice areas</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5074556690429557788/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5074556690429557788' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5074556690429557788'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5074556690429557788'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/12/software-engineering-institute-and.html' title='Software Engineering Institute and Software Product Lines'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-8832950048798629153</id><published>2007-11-18T08:00:00.001-08:00</published><updated>2007-11-18T08:10:45.646-08:00</updated><title type='text'>Innovation Management modeled like the Internet</title><summary type='text'>The Nov 15 issue of CIO magazine interviews Gary Hamel about innovation management.  He says that our management skills are mostly tuned for efficiency, and that isn't what we need to focus on any more.   Efficiency is about conformity, whereas innovation is about diversity.  He also says that what management needs to do now is model the Internet: amplify and aggregate human capabilities.  </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/8832950048798629153/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=8832950048798629153' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8832950048798629153'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8832950048798629153'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/11/innovation-management-modeled-like.html' title='Innovation Management modeled like the Internet'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5678313836042901276</id><published>2007-11-16T07:36:00.000-08:00</published><updated>2007-11-16T08:56:37.096-08:00</updated><title type='text'>Requirements and Capabilities</title><summary type='text'>I attended  a presentation yesterday which was intended to help people understand how to do Design for Manufacturing when  offshore manufacturing is the objective.   Unfortunately the presentation fell way short of its target, and the crowd even got a little annoyed.   The presenter was talking about models that have worked before:Document wellFollow the process exactlyManufacturing team has </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5678313836042901276/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5678313836042901276' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5678313836042901276'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5678313836042901276'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/11/requirements-and-capabilities.html' title='Requirements and Capabilities'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-6311499955512149476</id><published>2007-11-04T13:28:00.000-08:00</published><updated>2007-11-04T13:48:08.422-08:00</updated><title type='text'>Information hiding</title><summary type='text'>The August 2007 Communications of the ACM has an article called Offshore Outsourcing: The Risk of Keeping Mum.  In it they discuss factors that contribute to information hiding.  They reference a model developed by G. Hofstede, which breaks down cultural differences into 5 factors, and then combine it with work done by Keil and Robey [ACM 44 Apr 2001] which identified fear of being punished as </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/6311499955512149476/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=6311499955512149476' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6311499955512149476'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6311499955512149476'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/11/information-hiding.html' title='Information hiding'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4038872644725998158</id><published>2007-10-28T12:36:00.000-07:00</published><updated>2007-10-28T13:06:34.005-07:00</updated><title type='text'>Exit Strategies</title><summary type='text'>Many people have asked  "What's your exit strategy?" when discussing my startup.   Initially, I found this offensive, because in my mind if you build a viable business, you will have exit possibilities, should you desire one.   Moreover once you are successful, you'll have a better idea of exactly how it should be done.   Isn't building a business that has long term value what starting a business</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4038872644725998158/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4038872644725998158' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4038872644725998158'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4038872644725998158'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/10/exit-strategies.html' title='Exit Strategies'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-1002613409821172685</id><published>2007-10-21T11:36:00.001-07:00</published><updated>2007-10-21T12:22:21.510-07:00</updated><title type='text'>Open source practices even if you aren't using open source</title><summary type='text'>At High Regard Software, we're trying to make it easier to "onboard" new developers for our startup, RideGrid.   We are using some open source, notably pieces of Apache Commons.   Even if you are not using any open source, there is a lot that can be learned from Open Source to make it easier to do development.   The argument for this is straightforward: if the tool set works for collaborators </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/1002613409821172685/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=1002613409821172685' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/1002613409821172685'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/1002613409821172685'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/10/open-source-practices-even-if-you-arent.html' title='Open source practices even if you aren&apos;t using open source'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-6454850190124235835</id><published>2007-10-14T14:55:00.001-07:00</published><updated>2007-10-15T11:13:57.929-07:00</updated><title type='text'>Software Development and the Environment</title><summary type='text'>What can software leaders do to help improve the environment?  Reduce the footprint we leave in the process of doing our work.  Each of you may have unique ways you can do this, but there are some that could be nearly universal and I'll cover those here.   The areas I've actually been involved with are listed below, followed by more details about each in terms of what to expect and the challenges</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/6454850190124235835/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=6454850190124235835' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6454850190124235835'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6454850190124235835'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/10/software-development-and-environment.html' title='Software Development and the Environment'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4043588995860651021</id><published>2007-10-10T10:02:00.000-07:00</published><updated>2007-10-10T10:24:54.614-07:00</updated><title type='text'>You can't "make it up later"</title><summary type='text'>When you see a schedule challenge, followed by words like "but we'll make it up", you should be seriously suspicious.   When the plan isn't working, the idea that things will magically get better in the future simply strains credibility.   My inspiration for this post is Boeing's announcement today of a six month slip of their new airliner, the 787.  The kicker here is that they've known about </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4043588995860651021/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4043588995860651021' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4043588995860651021'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4043588995860651021'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/10/you-cant-make-it-up-later.html' title='You can&apos;t &quot;make it up later&quot;'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4025417019468244892</id><published>2007-10-08T06:50:00.000-07:00</published><updated>2007-10-08T07:02:18.176-07:00</updated><title type='text'>Focus</title><summary type='text'>I saw this story this morning, about Columbus Day protests in Colorado.  At the risk of being insensitive, this seems like a complete waste of energy.   You can argue the relevance of the federal holiday I suppose.  It was 500 years ago, and Columbus didn't really discover America, he simply introduced Europe to it.   But what's the point of the protest?  Draw attention to behavior we no longer </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4025417019468244892/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4025417019468244892' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4025417019468244892'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4025417019468244892'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/10/focus.html' title='Focus'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4963962471769929609</id><published>2007-09-30T10:23:00.001-07:00</published><updated>2007-09-30T10:35:44.285-07:00</updated><title type='text'>Teaching engineers</title><summary type='text'>What do we want our Universities to teach computer science and computer engineering students?   I've  lamented that teachings are sort of bipolar: flip-flopping between minutiae associated with implementation   (and attendant lack of attention to design),  and interesting but in the long run nearly useless theory.   This week's New York Times Magazine describes a  new university, Olin, which </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4963962471769929609/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4963962471769929609' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4963962471769929609'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4963962471769929609'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/09/teaching-engineers.html' title='Teaching engineers'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4136210754127614761</id><published>2007-09-27T08:05:00.000-07:00</published><updated>2007-09-27T08:26:47.465-07:00</updated><title type='text'>Moral Hazard</title><summary type='text'>It's fascinating to me to read about whether lower fed discount rates cause inflation, and even whether it's good for the stock market.   I wish I'd blogged on it last week, because there was  great article that basically said we have no idea how the economy really works.   We understand some things, for example, a smaller discount rate immediately increases the value of stocks.  When the </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4136210754127614761/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4136210754127614761' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4136210754127614761'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4136210754127614761'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/09/moral-hazard.html' title='Moral Hazard'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5028464098989375110</id><published>2007-09-26T16:57:00.000-07:00</published><updated>2007-09-26T17:10:51.548-07:00</updated><title type='text'>Another negotiating tool: WIFM</title><summary type='text'>You may have heard WIFM in the context of managing others.  WIFM stands for "Whats In it For Me?".   Sometimes you'll hear it as "WIFM radio".  (Ironically, there is at least one real WIFM radio station).   WIFM doesn't mean look out for yourself - rather it's a reminder that others will be looking out for themselves.   So put yourself in the other's perspective, and then answer the question of </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5028464098989375110/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5028464098989375110' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5028464098989375110'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5028464098989375110'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/09/another-negotiating-tool-wifm.html' title='Another negotiating tool: WIFM'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4404925193397881632</id><published>2007-09-24T14:50:00.000-07:00</published><updated>2007-09-24T15:17:03.676-07:00</updated><title type='text'>Negotiating</title><summary type='text'>I'm currently doing a little negotiating, so it was timely that this month's HBR has an article in it about negotiation.  Entitled Investigative Negotiation, it resonates with me because it is loaded with examples and techniques about understanding the motives of the people you are negotiating with, rather than trying to "win".   It somewhat reminds me of advice on selling by Jeffrey Gitomer, and</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4404925193397881632/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4404925193397881632' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4404925193397881632'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4404925193397881632'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/09/negotiating.html' title='Negotiating'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4586255464439388484</id><published>2007-09-17T15:41:00.000-07:00</published><updated>2007-09-17T15:53:25.015-07:00</updated><title type='text'>Measurement Constructs</title><summary type='text'>I've been learning about the methods used by the PSM group, which is detailed in their reference book here.    One of the concepts is what they term a Measurement Construct.  It's a graphical structure that shows how you go from an Attribute to an Information Product.   At first the whole thing seemed very intuitive, but the structure helps you consider all the aspects of metrics.  What are we </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4586255464439388484/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4586255464439388484' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4586255464439388484'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4586255464439388484'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/09/measurement-constructs.html' title='Measurement Constructs'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-3366460560855173829</id><published>2007-09-12T12:38:00.000-07:00</published><updated>2007-09-12T12:54:44.149-07:00</updated><title type='text'>Geeking out</title><summary type='text'>My excuse for not blogging recently is that I have been totally geeking out on the technical details of my startup.   We're using windows, mac and ubuntu, NetBeans 5.5.1 with the visual webpack and the mobility pack,  Sun's Java Application Server, asterisk (via asterisk-java), a third party routing library and SAS, mySQL,  some Apache Commons stuff, svn and a bunch of free tools.  We share our </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/3366460560855173829/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=3366460560855173829' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3366460560855173829'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3366460560855173829'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/09/geeking-out.html' title='Geeking out'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-2823344478253232185</id><published>2007-08-27T17:20:00.000-07:00</published><updated>2008-11-12T17:41:07.789-08:00</updated><title type='text'>Confused about Open Source?</title><summary type='text'>I found this excellent reference from O'Reilly, which compares various licensing mechanisms including GPL, LGPL, Apache, etc.   The entire book is online in PDF format, and it walks you through the important legal language  of each type and then explains it to you in english.   You don't have to read the entire book to get to a good understanding of how they differ.  I recommend this for any </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/2823344478253232185/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=2823344478253232185' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/2823344478253232185'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/2823344478253232185'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/08/confused-about-open-source.html' title='Confused about Open Source?'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_udJRBirzYHg/RtNtkAza00I/AAAAAAAAAAM/bikviL06whg/s72-c/IMG_2526.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5159977653771168047</id><published>2007-08-27T17:04:00.000-07:00</published><updated>2007-08-27T17:18:28.048-07:00</updated><title type='text'>Blog Action Day: the environment</title><summary type='text'>On October 15, blog action day, thousands of bloggers will blog normally, but include something regarding the environment.    If you blog, check them out and register!   If you read blogs, October 15 should be interesting.   The promo video is here:</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5159977653771168047/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5159977653771168047' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5159977653771168047'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5159977653771168047'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/08/blog-action-day-environment.html' title='Blog Action Day: the environment'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-1662692211838629273</id><published>2007-08-19T14:39:00.000-07:00</published><updated>2007-08-19T14:55:18.949-07:00</updated><title type='text'>"Buying Back" risk</title><summary type='text'>In the September 2005 issue of the Communications of the ACM, Philip Armour touches on a method to keep two plans: the work-to plan, and the commit-to plan.  He says that if an organization chooses not to intentionally manage the risk due to uncertainty, that either the customer (through lack of quality) or the development team (through overtime) ultimately pays for the risk as it materializes </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/1662692211838629273/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=1662692211838629273' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/1662692211838629273'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/1662692211838629273'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/08/buying-back-risk.html' title='&quot;Buying Back&quot; risk'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-2045110871931599198</id><published>2007-08-08T15:47:00.000-07:00</published><updated>2007-08-08T16:18:48.113-07:00</updated><title type='text'>Harmony and Apathy</title><summary type='text'>In a 1997 article entitled, How Management Teams Can Have a Good Fight, Eisenhardt, Kahwajy and Bourgeois make the case that the absence of conflict is not harmony, it's apathy.  They talk about healthy conflict versus interpersonal conflict.   Healthy conflict explores options and leads to better understanding.   Interpersonal conflict involves emotions which block efficient and effective </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/2045110871931599198/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=2045110871931599198' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/2045110871931599198'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/2045110871931599198'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/08/harmony-and-apathy.html' title='Harmony and Apathy'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-3747007940245822726</id><published>2007-07-30T11:12:00.000-07:00</published><updated>2007-07-30T11:37:20.584-07:00</updated><title type='text'>Metrics: avoiding pitfalls</title><summary type='text'>Karl E. Wiegers,  who wrote a great book I've used called "Peer Reviews In Software", published these ten traps to avoid when implementing a metrics program.  Anyone who has implemented  a metrics program likely has experienced every one of these.  It's a handy reference to put on your wall.  Most are self explanatory and intuitive, once you see them. The one I'm not quite sure I'm on board with </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/3747007940245822726/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=3747007940245822726' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3747007940245822726'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3747007940245822726'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/07/metrics-avoiding-pitfalls.html' title='Metrics: avoiding pitfalls'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-611255246956558268</id><published>2007-07-23T09:55:00.000-07:00</published><updated>2007-07-23T10:04:00.769-07:00</updated><title type='text'>There is no magic.</title><summary type='text'>That's the conclusion of Terry Coatta's writeup on the demise of CORBA:http://www.acmqueue.com/modules.php?name=Content&amp;pa=showpage&amp;pid=491We think of SOA as being a paradigm shift; it's actually an improvement which provides greater flexibility than CORBA and others, but the old rules still apply.  Distributed computing is still hard, in general.</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/611255246956558268/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=611255246956558268' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/611255246956558268'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/611255246956558268'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/07/there-is-no-magic.html' title='There is no magic.'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-3028048419195942798</id><published>2007-07-15T17:35:00.000-07:00</published><updated>2007-07-15T17:55:00.035-07:00</updated><title type='text'>Deliberate Practice`</title><summary type='text'>If you Google those two words, you'll find the term ascribed to Dr. K Anders Ericson. His research indicates that expert competence in an area is learned, not gifted, and that it requires special attention to what a person doesn't yet do well.  He quotes Sam Snead:It is only human nature to practice what you can already do well, since it's a hell of a lots less work and a hell of a lot more </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/3028048419195942798/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=3028048419195942798' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3028048419195942798'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3028048419195942798'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/07/deliberate-practice.html' title='Deliberate Practice`'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5551795836814089392</id><published>2007-07-09T13:00:00.000-07:00</published><updated>2007-07-09T13:14:42.957-07:00</updated><title type='text'>Disruptive Change</title><summary type='text'>Clayton M. Christensen, author of The Innovator's Dilemma, along with Michael Overdorf, wrote a paper in 2000 about why companies succeed or fail at disruptive innovation.   They argue that established companies by definition can't do disruption - the processes and values of the organization keep them on a track of evolutionary changes, which Christensen calls sustaining innovation.  The idea is </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5551795836814089392/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5551795836814089392' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5551795836814089392'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5551795836814089392'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/07/disruptive-change.html' title='Disruptive Change'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-6843205721653093043</id><published>2007-07-01T15:13:00.000-07:00</published><updated>2007-07-01T15:24:45.120-07:00</updated><title type='text'>Another dimension in innovation measurement</title><summary type='text'>Morten T Hansen and Julian Birkinshaw describe yet another method of analyzing and improving a company's ability to innovate.  They describe an "Innovation Value Chain" which gets evaluated in its ability to Create, Convert and Diffuse innovation.  In other words we often just think about the ideas, but many great ideas go un-monetized because they get lost in the shuffle, are not properly funded</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/6843205721653093043/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=6843205721653093043' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6843205721653093043'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6843205721653093043'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/07/another-dimension-in-innoivation.html' title='Another dimension in innovation measurement'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4312651252411922824</id><published>2007-06-17T18:51:00.001-07:00</published><updated>2007-06-17T18:58:22.534-07:00</updated><title type='text'>Great Reading: Patterns</title><summary type='text'>I'm reading  a book that software executives can use to understand Design Patterns. After going through this book you'll be able to ask better questions about the architecture of your OO software.  So far I've only gone through the Strategy, Observer, and Decorator patterns... but suddenly I  understand them and can talk at a much higher level of design than ever before.   The book is well </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4312651252411922824/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4312651252411922824' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4312651252411922824'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4312651252411922824'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/06/great-reading-patterns.html' title='Great Reading: Patterns'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-3203531659002021439</id><published>2007-06-17T17:48:00.000-07:00</published><updated>2007-06-17T18:26:07.827-07:00</updated><title type='text'>Arrogance</title><summary type='text'>I was discussing Arrogance last week with a colleague;  we noted some really smart people who have changed professions, who think they know so much more than those who have studied the profession for decades.Peter Drucker wrote, in an article entitled "Managing Oneself":Far too many people—especially people with great expertise in one area—are contemptuous of knowledge in other areas or believe </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/3203531659002021439/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=3203531659002021439' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3203531659002021439'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3203531659002021439'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/06/arrogance.html' title='Arrogance'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-3654641209045518114</id><published>2007-06-05T08:27:00.000-07:00</published><updated>2007-06-05T08:50:33.238-07:00</updated><title type='text'>Problems and Solutions</title><summary type='text'>Dr. Arthur D. Levinson, CEO of Genentech,  is quoted in the Wall Street Journal today:I have a philosophy -- I invite criticism. But don't ever come to me with a complaint without saying, here is what we might do to make it better. I am happy to hear Part A if I hear Part B.I have tremendous respect for the man; he's built a successful business in an industry he describes as the "biggest money </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/3654641209045518114/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=3654641209045518114' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3654641209045518114'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3654641209045518114'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/06/problems-and-solutions.html' title='Problems and Solutions'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-8928765885794386143</id><published>2007-05-28T10:12:00.000-07:00</published><updated>2007-05-28T10:42:36.580-07:00</updated><title type='text'>Measurement of Innovation</title><summary type='text'>I found a reference for developing innovation metrics that I find useful.  It breaks down factors that one needs to be innovative and gives suggestions for measuring those factors.  Specifically, how to measure the resources, capability and leadership factors that might collectively be predictors of innovation. Is innovation easier to measure than quality?  Typically we measure what quality is </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/8928765885794386143/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=8928765885794386143' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8928765885794386143'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8928765885794386143'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/05/measurement-of-innovation.html' title='Measurement of Innovation'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-7330699040862751362</id><published>2007-05-20T13:52:00.000-07:00</published><updated>2007-05-20T14:10:55.147-07:00</updated><title type='text'>Emotions</title><summary type='text'>I had a new experience this week.   One I hope not to repeat.  The simple version of the story is that I needed $200 in cash, and ended up at one of those non-bank ATM machines.  I asked for $200, it only dispensed $100, and I managed to pull another $20 out that was stuck in the output slot.  This isn't what we've come to expect from these machines... at least not after we've used them hundreds </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/7330699040862751362/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=7330699040862751362' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/7330699040862751362'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/7330699040862751362'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/05/emotions.html' title='Emotions'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-8147917000949899544</id><published>2007-05-13T12:19:00.000-07:00</published><updated>2007-05-13T13:10:45.932-07:00</updated><title type='text'>Speaking Up</title><summary type='text'>Maybe I'm a consultant because I say things when I shouldn't.   Frankly, that's what you want in a consultant - you pay them to tell you the truth. There are surely engagements where you get paid to tell someone something they want to hear  - probably mostly as a subject matter expert in a legal proceeding (I'm sure I have offended  a lot of experts now).  But really, wouldn't the world be a </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/8147917000949899544/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=8147917000949899544' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8147917000949899544'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8147917000949899544'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/05/speaking-up.html' title='Speaking Up'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5230132134247265690</id><published>2007-05-06T20:38:00.000-07:00</published><updated>2007-05-07T17:08:36.402-07:00</updated><title type='text'>Leading the seriously talented</title><summary type='text'>In high tech, we can hope that through corporate reputation, good fortune, persistence, and good choices, we get to have people on our team that are really smart.  Ideally, smarter than we are.  Consider the alternative: a team of people who are not as smart as their leader? The challenge with really smart people is they do not really want to be led.  I have seen this.   According to an article </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5230132134247265690/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5230132134247265690' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5230132134247265690'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5230132134247265690'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/05/leading-seriously-talented.html' title='Leading the seriously talented'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4519053573376301572</id><published>2007-04-29T18:04:00.000-07:00</published><updated>2007-04-29T18:59:42.877-07:00</updated><title type='text'>Measurement is hard</title><summary type='text'>I was going to title this post "ISO 15939", but then many of you would not be reading this.   However, this last week I was introduced to a measurement world I am still trying to figure out.   It looks compelling, and it is related to this standard.  One of our challenges is convincing people that they should expend the effort to measure something.  One of the books on this subject I like is </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4519053573376301572/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4519053573376301572' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4519053573376301572'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4519053573376301572'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/04/measurement-is-hard.html' title='Measurement is hard'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-6069230128503493602</id><published>2007-04-21T12:54:00.000-07:00</published><updated>2007-04-21T14:28:24.112-07:00</updated><title type='text'>Praise is getting harder</title><summary type='text'>The Wall Street Journal yesterday did an article on younger workers' need for praise.  (You'll need an online subscription to read the article). The article claims that popular self-esteem-building parenting and coaching techniques have created a generation for whom a lack of continuous feedback feels like rebuke. The abundance of praise may have led to the formation of a cadre of narcissists.  </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/6069230128503493602/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=6069230128503493602' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6069230128503493602'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6069230128503493602'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/04/praise-is-getting-harder.html' title='Praise is getting harder'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-1512085356694481400</id><published>2007-04-15T20:35:00.000-07:00</published><updated>2007-04-15T21:12:40.527-07:00</updated><title type='text'>Develop, Support or Punt?</title><summary type='text'>As a leader, having identified an individual's lack of skill in a particular area, how do you decide whether to try to develop the skill, simply provide support from someone else in the weak area, or move the person out of the role or team?   After all, it's the leader's job to remove roadblocks and provide support, right?   When does support stop being a good thing and start being a problem?I </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/1512085356694481400/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=1512085356694481400' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/1512085356694481400'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/1512085356694481400'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/04/develop-support-or-punt.html' title='Develop, Support or Punt?'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4770607543875948282</id><published>2007-04-09T07:18:00.000-07:00</published><updated>2007-04-09T07:27:00.292-07:00</updated><title type='text'>Eco-Capitalism</title><summary type='text'>This twelve minute video talks about how some large companies have made environmental progress and money at the same time.  Not only is this a fabulous trend for business and the planet, but it shows that if you look for win-win strategies, you might find them.   Conversely, if your model of the world believes that something can't be done, your bias may inhibit or prevent it.</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4770607543875948282/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4770607543875948282' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4770607543875948282'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4770607543875948282'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/04/eco-capitalism.html' title='Eco-Capitalism'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-4053456473975928950</id><published>2007-04-01T16:56:00.000-07:00</published><updated>2007-04-01T17:43:18.137-07:00</updated><title type='text'>Intuition</title><summary type='text'>I love this quote attributed to Jack Welch (and I've probably got it wrong, sorry Jack):If we are going to make this decision based on opinion, I prefer mine.I like it because it is straight up - facts and analysis are credible scientific truth-seeking mechanisms.  Opinions are based on all kinds of human biases.  I attended a meeting recently regarding  a paper to be published soon, about </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/4053456473975928950/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=4053456473975928950' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4053456473975928950'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/4053456473975928950'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/04/intuition.html' title='Intuition'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5062494691783372550</id><published>2007-03-26T14:20:00.000-07:00</published><updated>2007-03-26T14:55:03.711-07:00</updated><title type='text'>Focus and Innovation</title><summary type='text'>In my experience, a major impediment to innovation is lack of focus.  If your organization isn't clear on what it is trying to accomplish and why, you are  likely to consume your resources on a myriad of time consuming projects that contribute little to the effectiveness of the current product, and leave no room for innovation. So if you want to innovate, get control of your portfolio.  It will </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5062494691783372550/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5062494691783372550' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5062494691783372550'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5062494691783372550'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/03/focus-and-innovation.html' title='Focus and Innovation'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-6506515198493860003</id><published>2007-03-11T18:23:00.000-07:00</published><updated>2007-03-11T18:39:23.124-07:00</updated><title type='text'>Acid test for secure development</title><summary type='text'>The March 1, 2007 issue of CIO magazine lays out questions for customers to ask you about your software development environment, and how to evaluate the answers.   The first 5 questions are in print:Do you review security at each phase of the software development life cycle?What methodologies do you use for security testing your products?Do third parties conduct security assessments on your </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/6506515198493860003/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=6506515198493860003' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6506515198493860003'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6506515198493860003'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/03/acid-test-for-secure-development.html' title='Acid test for secure development'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-3307103982431419382</id><published>2007-03-06T09:32:00.000-08:00</published><updated>2007-03-06T09:45:20.454-08:00</updated><title type='text'>Innovation Test</title><summary type='text'>I'm not sure if this is ridiculous or interesting, but I stumbled over a tool, put together by IBM Global Services, which portends to assess your organization's innovation strategy and benchmark it against 750 other companies.   I rated a former employer and ... surprise... we didn't score really well.  The assessment tool raises more questions than it answers, in my mind; and no doubt this is a </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/3307103982431419382/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=3307103982431419382' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3307103982431419382'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/3307103982431419382'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/03/innovation-test.html' title='Innovation Test'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-7925304576082888614</id><published>2007-02-24T12:00:00.000-08:00</published><updated>2007-02-24T12:03:24.792-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='tools'/><category scheme='http://www.blogger.com/atom/ns#' term='metrics'/><category scheme='http://www.blogger.com/atom/ns#' term='change managemment'/><title type='text'>Cool Change Management predictive metric</title><summary type='text'>The October 2005 issue of HBR has an article called "the hard side of change management".   They introduce  a new metric called DICE, which stands for "Duration", "Integrity of Performance, "Commitment", and "Effort".  In their study they found that by applying simple subjective scores to each of these areas, and then a simple formula to roll up a total score, they have a number which can be used</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/7925304576082888614/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=7925304576082888614' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/7925304576082888614'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/7925304576082888614'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/02/cool-change-management-predictive.html' title='Cool Change Management predictive metric'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-8361041758181372923</id><published>2007-02-23T07:40:00.000-08:00</published><updated>2007-02-23T11:19:10.968-08:00</updated><title type='text'>Root Cause (or, punishing the innocent)</title><summary type='text'>An article in the Wall Street Journal yesterday reminded me of how easy it is to fire people up to solve the wrong problem.   For those of you with an online WSJ account, you can view the story here.  There is also this article in Information Week which anyone can read.  The articles talk about a bill that republican Michael A Costello  is sponsoring,  Massachusetts House Bill 213, which would </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/8361041758181372923/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=8361041758181372923' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8361041758181372923'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8361041758181372923'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/02/root-cause-or-punishing-innocent.html' title='Root Cause (or, punishing the innocent)'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-8602444187869748043</id><published>2007-02-18T17:02:00.000-08:00</published><updated>2007-02-18T17:16:05.012-08:00</updated><title type='text'>A change tool: ADKAR</title><summary type='text'>I was considering a potential assignment and rummaging through my toolbox, when I recalled an acronym: ADKAR.  I don't recall where I originally learned it.   It is a diagnostic tool to help you figure out how far along a change an organization is, and what remains to be done. (A)wareness is present if  people are aware that a change needs to be made. (D)esire is present if  people want to change</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/8602444187869748043/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=8602444187869748043' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8602444187869748043'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8602444187869748043'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/02/change-tool-adkar.html' title='A change tool: ADKAR'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-6515668554919303665</id><published>2007-02-11T08:39:00.000-08:00</published><updated>2007-02-08T22:46:32.643-08:00</updated><title type='text'>The requirements factory</title><summary type='text'>I was speaking to some offshore development managers last week, where we were discussing what a challenge it is to get good requirements.  This is not a new phenomenon, it has just gotten so much harder with increasing levels of technical complexity and the cultural and distance diversity of our current development landscape.The May 1995 issue of Communications of the ACM included several </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/6515668554919303665/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=6515668554919303665' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6515668554919303665'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/6515668554919303665'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/02/requirements-factory.html' title='The requirements factory'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5419191950775485380</id><published>2007-02-06T18:18:00.000-08:00</published><updated>2007-02-07T06:08:10.093-08:00</updated><title type='text'>A well written product quality article</title><summary type='text'>I was part of an effort where we had a tremendous impact on quality in just a couple  of years.  We principally did it by turning the organization around from its earlier behaviors, and simply making it clear that quality is the developer's job, not the QA department's.  QA's job is to measure and prove that the developers did what they were supposed to (or that they didn't).  Development's job </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5419191950775485380/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5419191950775485380' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5419191950775485380'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5419191950775485380'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/02/well-written-product-quality-article.html' title='A well written product quality article'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-8860003535402435088</id><published>2007-02-05T10:29:00.000-08:00</published><updated>2007-02-05T10:50:36.777-08:00</updated><title type='text'>Effective Communication</title><summary type='text'>I found this on Ronny DeWinter's Software Quality blog:Communication levels:Not everything that is said is heard.Not everything that is heard is understood.Not everything that is understood is agreed.Not everything that is agreed is applied.Not everything that is applied is retained.That is a fantastic short synopsis of why communication is so difficult.  It shows that just getting someone to </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/8860003535402435088/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=8860003535402435088' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8860003535402435088'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/8860003535402435088'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/02/effective-communication.html' title='Effective Communication'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-7773775590344525297</id><published>2007-01-30T17:19:00.000-08:00</published><updated>2007-01-31T20:13:47.558-08:00</updated><title type='text'>Who's schedule is it anyway?</title><summary type='text'>Delivering new products on schedule is always difficult.  At a recent Agile Software seminar, someone asked the crowd if they had ever had any home remodeling done.   A lot of people raised their hands.   Then she asked if it went according to plan; very few people raised their hands.   The point she was making was:  if something as well understood as remodeling can't go according to plan, what </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/7773775590344525297/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=7773775590344525297' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/7773775590344525297'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/7773775590344525297'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/01/whos-schedule-is-it-anyway.html' title='Who&apos;s schedule is it anyway?'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-5403238952687511577</id><published>2007-01-21T13:45:00.000-08:00</published><updated>2007-01-21T14:15:13.450-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='quality'/><category scheme='http://www.blogger.com/atom/ns#' term='software product lines'/><category scheme='http://www.blogger.com/atom/ns#' term='software development'/><category scheme='http://www.blogger.com/atom/ns#' term='management'/><category scheme='http://www.blogger.com/atom/ns#' term='efficiency'/><title type='text'>Software Product Lines</title><summary type='text'>I decided to cover this subject since the December issue of Communications of the ACM is dedicated to the subject matter.  I first got introduced to the terminology last year when I was talking to a San Diego employer, who was looking for management talent with this skill set.  I didn't find much information on it then, but bought a (largely boring) book on it. If you haven't heard of it, it's </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/5403238952687511577/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=5403238952687511577' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5403238952687511577'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/5403238952687511577'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/01/software-product-lines.html' title='Software Product Lines'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-7720310398881682831</id><published>2007-01-14T11:17:00.000-08:00</published><updated>2007-01-14T12:24:05.734-08:00</updated><title type='text'>Sustainable Advantage</title><summary type='text'>Because I am such a fan of innovation, one of my former bosses once chided me, saying: "The only sustainable competitive advantage is execution".  The context of the discussion was about Apple Computer's innovations, and whether they were innovating or simply producing ... well .. art.  This quote from fastcompany.com inspired the conversation: If your cool new thing doesn't generate enough money</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/7720310398881682831/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=7720310398881682831' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/7720310398881682831'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/7720310398881682831'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/01/sustainable-advantage.html' title='Sustainable Advantage'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-116826738537833065</id><published>2007-01-08T06:06:00.000-08:00</published><updated>2007-01-08T06:43:05.390-08:00</updated><title type='text'>Innovation and middle management power</title><summary type='text'>Rosabeth Moss Kanter wrote an article for Harvard Business Review in 1982 that was reprinted in 2004, entitled "The Middle Manager as Innovator".  She points out that middle management drives changes that increase organization capacity.  Among the many things she says that I agree with, she talks about how lack of power in these ranks can interfere with the innovative process, because it inhibits</summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/116826738537833065/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=116826738537833065' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/116826738537833065'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/116826738537833065'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2007/01/innovation-and-middle-management-power.html' title='Innovation and middle management power'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-116724679470246918</id><published>2006-12-27T11:00:00.000-08:00</published><updated>2006-12-27T11:37:49.303-08:00</updated><title type='text'>Entrepreneurship and Insubordination</title><summary type='text'>Robert Nardelli is quoted as saying "there's only a fine line between entrepreneurship and insubordination".  I found this gem in the Oct 2006 issue of Harvard Business Review, in an article by David Garvin and Lynne Levesque.  I'll leave the details to your reading pleasure, but there were a few key points that resonate with me, regarding how to innovate within a corporation. First, quite a bit </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/116724679470246918/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=116724679470246918' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/116724679470246918'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/116724679470246918'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2006/12/entrepreneurship-and-insubordination.html' title='Entrepreneurship and Insubordination'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-115852948637903953</id><published>2006-09-17T14:18:00.000-07:00</published><updated>2006-09-17T15:23:46.466-07:00</updated><title type='text'>Sirens' call: Agile</title><summary type='text'>I consider myself an early adopter; I am usually the first to try new things.  When it comes to Agile software development, however, I have pretty much waited until it entered the mainstream.  We are there now.  Large, respectable companies are moving to some form of Agile.  They had to.  It is clear that what we have been doing hasn't led, in general, to higher quality, predictability, </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/115852948637903953/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=115852948637903953' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/115852948637903953'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/115852948637903953'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2006/09/sirens-call-agile.html' title='Sirens&apos; call: Agile'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-110546635116483068</id><published>2005-01-11T09:45:00.000-08:00</published><updated>2005-01-11T10:15:45.306-08:00</updated><title type='text'>Efficiency Metric</title><summary type='text'>I'm inspired by a very simple metric I've seen in a presentation from the lean software institute, which they refer to as "Staff Productivity". It is a deceptively simple equation:     Value Added Effort     ----------------     Total HoursThis number cannot exceed 1.0. Value Added is defined in the sense found in "Re-Engineering the Corporation"; it is that value that is tangible to the </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/110546635116483068/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=110546635116483068' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/110546635116483068'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/110546635116483068'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2005/01/efficiency-metric.html' title='Efficiency Metric'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-110116404444835781</id><published>2004-11-22T14:25:00.000-08:00</published><updated>2004-11-22T14:54:04.450-08:00</updated><title type='text'>Metrics and Radiators</title><summary type='text'>We all know that what gets measured gets done.  So why is it that so many software organizations don't have data on their performance?  My theory is that people are afraid to be measured.  I have personally seen aversion to ascribing defect rates to individuals.  The argument against it was that managers are not capable of interpreting the subtlety in the data, afraid that if one takes on harder </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/110116404444835781/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=110116404444835781' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/110116404444835781'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/110116404444835781'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2004/11/metrics-and-radiators.html' title='Metrics and Radiators'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-109959545893874665</id><published>2004-11-04T10:52:00.000-08:00</published><updated>2004-11-04T17:24:21.646-08:00</updated><title type='text'>Strategy and Mission</title><summary type='text'>Much has been written on strategy. It can be a fuzzy and cosmic subject.  I advocate a very simple approach to setting and communicating a strategy, and it can be done at all levels of the organization where choices are made.A simple strategy is one that is written specifically for the purpose of review by other parts of the organization.  It should cover what could be done, what will and won't </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/109959545893874665/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=109959545893874665' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109959545893874665'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109959545893874665'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2004/11/strategy-and-mission.html' title='Strategy and Mission'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-109862784060681187</id><published>2004-10-24T07:04:00.000-07:00</published><updated>2004-10-28T12:28:05.306-07:00</updated><title type='text'>Corporate Life Cycle</title><summary type='text'>I am a fan of Adizes'   model for the corporate life cycle.   In his book  Corporate Lifecycles, he describes four categories of roles that each executive should have reporting to him or her, in order to bring good conflict to the table that can be used for good decision making.  The four roles are PAEI:Performing.  In software product development, this is most of what we think about the </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/109862784060681187/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=109862784060681187' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109862784060681187'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109862784060681187'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2004/10/corporate-life-cycle.html' title='Corporate Life Cycle'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-109831645321988590</id><published>2004-10-20T16:33:00.000-07:00</published><updated>2004-10-20T16:54:13.220-07:00</updated><title type='text'>Approachability</title><summary type='text'>One of the best ways you can get input on all aspects of your organization is to make sure people want to talk to you.  This seems self evident, yet many leaders don't invite input except from superiors.  You can't just say "give me your input" and expect it to happen, you have to demonstrate that you care.What I do is make others feel respected and important.  Everyone.  The janitor.  The </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/109831645321988590/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=109831645321988590' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109831645321988590'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109831645321988590'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2004/10/approachability.html' title='Approachability'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-109702042064588941</id><published>2004-10-05T16:43:00.000-07:00</published><updated>2004-10-05T21:10:41.020-07:00</updated><title type='text'>The one true way</title><summary type='text'>You've all seen it: religious wars over technical solutions. emacs versus vi. C++ versus Java. VxWorks versus Embedded Linux. These are decisions you often can't make right because there is no right solution. And whichever you choose, you will alienate a percentage of your technical people. I've tried various ways to solve this dilemma with disappointing results.What should you do when faced </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/109702042064588941/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=109702042064588941' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109702042064588941'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109702042064588941'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2004/10/one-true-way.html' title='The one true way'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-8552627.post-109701596456329572</id><published>2004-10-05T15:30:00.001-07:00</published><updated>2004-10-05T16:43:01.476-07:00</updated><title type='text'>The most important thing about leadership</title><summary type='text'>What I have noticed when technical people complain about bad leadership (as opposed to lack of leadership), is that there is really a lack of trust. This typically occurs because the leader has either exhibited repeated selfish behavior or is failing to communicate openly and honestly. I have seen some leaders holding back information in the interest of appearing dignified or more intelligent </summary><link rel='replies' type='application/atom+xml' href='http://leader4success.blogspot.com/feeds/109701596456329572/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=8552627&amp;postID=109701596456329572' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109701596456329572'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/8552627/posts/default/109701596456329572'/><link rel='alternate' type='text/html' href='http://leader4success.blogspot.com/2004/10/most-important-thing-about-leadership.html' title='The most important thing about leadership'/><author><name>Jeffrey Paul Anderson</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='21' src='http://users.adelphia.net/~jeffpaulca/Jeff.jpg'/></author><thr:total>0</thr:total></entry></feed>
