<?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/'><id>tag:blogger.com,1999:blog-15466608.post5840794596807311840..comments</id><updated>2008-07-15T20:37:33.507+10:00</updated><category term='ethics'/><category term='Charles Handy'/><category term='case study'/><category term='Complexity'/><category term='tools'/><category term='multitasking'/><category term='Risk Management'/><category term='Relationships'/><category term='salaries'/><category term='enterprise architecture'/><category term='A Day In My Life'/><category term='RATER'/><category term='community'/><category term='done'/><category term='sldc'/><category term='Beer'/><category term='Apple'/><category term='time management'/><category term='Chaos'/><category term='Testing'/><category term='Duration'/><category term='PRINCE2'/><category term='Deliverables'/><category term='improvisation'/><category term='Fred Brooks'/><category term='wealth'/><category term='business analysis'/><category term='rewards'/><category term='Prioritization'/><category term='presentations; Business analyst'/><category term='video'/><category term='Humor'/><category term='priority'/><category term='Query'/><category term='product owner'/><category term='Managing Change'/><category term='Business Case'/><category term='Business Rules'/><category term='Service'/><category term='google wave'/><category term='P2M'/><category term='theory of knowledge'/><category term='Business Process Management'/><category term='Resume'/><category term='Implementation'/><category term='schedule'/><category term='career development'/><category term='iterative development'/><category term='UX'/><category term='Six Sigma'/><category term='Tips'/><category term='Strategy'/><category term='Customer'/><category term='requirements reuse'/><category term='PMI'/><category term='time tunnel'/><category term='Progress Reporting'/><category term='balanced scorecard'/><category term='Knowledge Management'/><category term='earned value'/><category term='constraints'/><category term='product management'/><category term='Agile'/><category term='Carnival of Business Analysts'/><category term='innovation'/><category term='design'/><category term='governance'/><category term='People Management'/><category term='Methodology'/><category term='velocity'/><category term='blogging'/><category term='Information'/><category term='Project Pitches'/><category term='Brainstorming'/><category term='conferences'/><category term='Estimating'/><category term='Software Project Management'/><category term='Social networking'/><category term='project jargon'/><category term='information architecture'/><category term='meet-up'/><category term='Memes'/><category term='Experimentation'/><category term='Consulting'/><category term='international projects'/><category term='PM University'/><category term='Stakeholders'/><category term='Finance'/><category term='project sociology'/><category term='five forces'/><category term='Sales'/><category term='decision making'/><category term='Leadership'/><category term='Cash'/><category term='survey'/><category term='voice'/><category term='Porter'/><category term='Compensation'/><category term='Information Overload'/><category term='Initiation'/><category term='uml'/><category term='Change Control'/><category term='off topic'/><category term='Applications'/><category term='It&apos;s Friday'/><category term='Law'/><category term='The Upside of Irrationality'/><category term='focus'/><category term='Quality Assurance'/><category term='Information Filtering'/><category term='business model'/><category term='Use Case'/><category term='mentoring'/><category term='Visualization'/><category term='Performance Management'/><category term='burn chart'/><category term='Event Management'/><category term='PowerPoint'/><category term='Contracts'/><category term='Risk Management 101'/><category term='Humour'/><category term='Ed Yourdon'/><category term='Google'/><category term='ADKAR'/><category term='Catalyze'/><category term='Systems Analyst'/><category term='revision numbering'/><category term='scrum'/><category term='Process Improvement'/><category term='Database'/><category term='document templates'/><category term='product backlog'/><category term='RAD'/><category term='Project Portfolio Management'/><category term='management'/><category term='CMMI'/><category term='Lessons'/><category term='completion'/><category term='Clutter'/><category term='Lean'/><category term='gannt-chart'/><category term='Melbourne'/><category term='RTM'/><category term='business architecture'/><category term='documentation'/><category term='Economics'/><category term='Objectives'/><category term='managing teams'/><category term='Business Process Analysis'/><category term='validation'/><category term='data modelling'/><category term='IIBA'/><category term='user stories'/><category term='Quality'/><category term='Openness'/><category term='PMO'/><category term='Scope'/><category term='values'/><category term='obsession'/><category term='Programme Management'/><category term='spiral'/><category term='reader survey'/><category term='You Make the Call'/><category term='roles'/><category term='Marketing'/><category term='professional development'/><category term='Communication'/><category term='Ideas'/><category term='Living Dead'/><category term='SWEBOK'/><category term='Servqual'/><category term='Alignment'/><category term='xp'/><category term='BA Handbook'/><category term='Policy'/><category term='Deming'/><category term='Requirements Management'/><category term='Project Management'/><category term='verification'/><category term='#AgileBA'/><category term='retrospective'/><category term='Juran'/><category term='PDM'/><category term='Agile Thursday'/><category term='Requirements'/><category term='pair programming'/><category term='Development'/><category term='Sponsors'/><category term='integration'/><category term='Remix'/><category term='Success'/><category term='WBS'/><category term='Value Management'/><category term='Release Management'/><category term='Change Management'/><category term='Guru'/><category term='Covey'/><category term='cost management'/><category term='Cleland'/><category term='simplicity'/><category term='Legal'/><category term='Waterfall'/><category term='Technology'/><category term='Soft skills'/><category term='bureacracy'/><category term='Sign-off'/><category term='Recruiting'/><category term='understanding business'/><category term='Resourcefulness'/><category term='I.T.'/><category term='Configuration Management'/><category term='kano'/><category term='Dispatches'/><category term='OGC'/><category term='itil'/><category term='Best Practice'/><category term='problem solving'/><category term='strategy map'/><category term='feedback'/><category term='Bloggers'/><category term='Planning'/><category term='kanban'/><category term='About the author'/><category term='Writing'/><category term='Warning labels'/><category term='CSM'/><category term='Strategic Needs Analysis'/><category term='integration management'/><category term='PMBOK'/><category term='Solution Design'/><category term='presentations'/><category term='Requirements Quality'/><category term='Information cost'/><category term='Capability'/><category term='research'/><category term='Enterprise Applications'/><category term='benefits management'/><category term='Music'/><category term='culture'/><category term='Wideman'/><category term='PIR'/><category term='Business analyst'/><category term='goals'/><category term='Search'/><category term='Web 2.0'/><category term='scum'/><category term='Requirements Fail'/><category term='Demos'/><category term='BABOK'/><category term='conflict'/><category term='slip'/><category term='Project Future'/><category term='Enterprise Analysis'/><category term='dates'/><category term='Project Outlook'/><category term='structure'/><category term='Continuous Improvement'/><category term='quotes'/><category term='Patterns'/><category term='Disaster Recovery'/><category term='Wiki'/><category term='failure'/><category term='book report'/><category term='Training'/><category term='V-model'/><category term='Task Management'/><title type='text'>Comments on Better Projects: Managing people, managing projects</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.betterprojects.net/feeds/5840794596807311840/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html'/><author><name>Craig Brown</name><uri>https://profiles.google.com/112202012347971122168</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//lh5.googleusercontent.com/-5L72U41FpZU/AAAAAAAAAAI/AAAAAAAAWQA/mXSiKGJCrtg/s512-c/photo.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-15466608.post-4678526090122455143</id><published>2008-07-15T20:37:00.000+10:00</published><updated>2008-07-15T20:37:00.000+10:00</updated><title type='text'>Thanks Ben.&lt;br&gt;&lt;br&gt;Good points.  Making the change...</title><content type='html'>Thanks Ben.&lt;BR/&gt;&lt;BR/&gt;Good points.  Making the change is probably the hardest part.&lt;BR/&gt;&lt;BR/&gt;When I manage people my approach is that of a coach and fcilitator, and although when things get turbulent it's always hard to not switch to an authoritarian mode, I can usually avoid it.&lt;BR/&gt;&lt;BR/&gt;It maeks life easier, frankly, and also my teams tend to 90% come on the journey with me.  (An usually choose to wear the 10% laggards as a natural cost of the change.)</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default/4678526090122455143'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default/4678526090122455143'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html?showComment=1216118220000#c4678526090122455143' title=''/><author><name>Craig Brown</name><uri>http://www.blogger.com/profile/01210437173582289473</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='03178891453306926128'/><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://bp1.blogger.com/_2vgIgz_H4g8/R_N7KvX60kI/AAAAAAAAAAM/bQ9aFL5J1K4/S220/IMG_4619-1.JPG'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html' ref='tag:blogger.com,1999:blog-15466608.post-5840794596807311840' source='http://www.blogger.com/feeds/15466608/posts/default/5840794596807311840' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1414953227'/></entry><entry><id>tag:blogger.com,1999:blog-15466608.post-9049653194202232912</id><published>2008-07-15T03:35:00.000+10:00</published><updated>2008-07-15T03:35:00.000+10:00</updated><title type='text'>Craig,&lt;br&gt;&lt;br&gt;You asked - "How do you keep everyon...</title><content type='html'>Craig,&lt;BR/&gt;&lt;BR/&gt;You asked - "How do you keep everyone working toward the organisation;s goals without some degree of top down control?"&lt;BR/&gt;&lt;BR/&gt;You don't.  Authority is not the problem.  The problem is using a top-down command and control approach to managing people.  &lt;BR/&gt;&lt;BR/&gt;Some one must be in authority and must be accountable for performance.  Someone must say "that is OK" and "that is not OK" in order to protect high standards of all values. Someone must say "that is a good goal", but not dictate the goal without the full prior participation by the workforce.  Better that the workforce decide on the goal and the boss only accede to it.  &lt;BR/&gt;&lt;BR/&gt;So we need a hierarchical structure but that does not mean that we manage people with a top-down approach.&lt;BR/&gt;&lt;BR/&gt;You also asked "And what do you do with employees who don't want to play ball?"&lt;BR/&gt;&lt;BR/&gt;As I pointed out in my post, management is responsible for supporting the workforce and one of those elements is discipline otherwise known as the enforcement of high standards. People who don't meet acceptable standards must experience fair and sure consequences otherwise those who are meeting standards will not feel appreciated since they must make up for non-performers.  &lt;BR/&gt;&lt;BR/&gt;Non-performers must be changed or removed from the team.  As I pointed out in the original post, this includes anyone who requires extensive orders.&lt;BR/&gt;&lt;BR/&gt;Hope that answers your questions.  If not, ask more.&lt;BR/&gt;&lt;BR/&gt;Best regards, Ben&lt;BR/&gt;Author "Leading People to be Highly Motivated and Committed"</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default/9049653194202232912'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default/9049653194202232912'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html?showComment=1216056900000#c9049653194202232912' title=''/><author><name>Ben Simonton</name><uri>http://www.bensimonton.com</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img1.blogblog.com/img/blank.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html' ref='tag:blogger.com,1999:blog-15466608.post-5840794596807311840' source='http://www.blogger.com/feeds/15466608/posts/default/5840794596807311840' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-452448396'/></entry><entry><id>tag:blogger.com,1999:blog-15466608.post-8295560546506723930</id><published>2008-07-12T21:55:00.000+10:00</published><updated>2008-07-12T21:55:00.000+10:00</updated><title type='text'>Excellent points Ben.&lt;br&gt;&lt;br&gt;(People - here's that...</title><content type='html'>Excellent points Ben.&lt;BR/&gt;&lt;BR/&gt;(People - here's that interview in a &lt;A HREF="http://www.extensor.co.uk/articles/int_simonton/interview_ben_simonton.html" REL="nofollow"&gt;hyperlink&lt;/A&gt;.)&lt;BR/&gt;&lt;BR/&gt;Here are two questions for you though;&lt;BR/&gt;&lt;BR/&gt;How do you keep everyone working toward the organisation;s goals without some degree of top down control?&lt;BR/&gt;&lt;BR/&gt;And what do you do with employees who don't want to play ball?</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default/8295560546506723930'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default/8295560546506723930'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html?showComment=1215863700000#c8295560546506723930' title=''/><author><name>Craig Brown</name><uri>http://www.blogger.com/profile/01210437173582289473</uri><email>noreply@blogger.com</email><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='OpenSocialUserId' value='03178891453306926128'/><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='26' height='32' src='http://bp1.blogger.com/_2vgIgz_H4g8/R_N7KvX60kI/AAAAAAAAAAM/bQ9aFL5J1K4/S220/IMG_4619-1.JPG'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html' ref='tag:blogger.com,1999:blog-15466608.post-5840794596807311840' source='http://www.blogger.com/feeds/15466608/posts/default/5840794596807311840' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1414953227'/></entry><entry><id>tag:blogger.com,1999:blog-15466608.post-8320191974216768047</id><published>2008-07-12T21:47:00.000+10:00</published><updated>2008-07-12T21:47:00.000+10:00</updated><title type='text'>Where does leadership fit into the picture?&lt;br&gt;&lt;br...</title><content type='html'>Where does leadership fit into the picture?&lt;BR/&gt;&lt;BR/&gt;Leadership applies to people and denotes the sending of value standard messages to people which most of them then follow/use. Thus we say that they have been "led" in the direction of those standards. Leadership is one side of the coin called values, the other side being followership.&lt;BR/&gt;&lt;BR/&gt;Leadership in the workplace consists of the value standards reflected in everything that an employee experiences because these standards are what employees follow by using them to perform their work. Most of what the employee experiences is the support or lack thereof provided by management - such as training, tools, parts, discipline, direction, material, procedures, rules, technical advice, documentation, information, planning, etc.&lt;BR/&gt;&lt;BR/&gt;Leadership is not a process any manager can change.  It happens inexorably every minute of every day because of the way people are. The only choice available to a manager is the standard (good, bad, mediocre or in between) which people will follow.&lt;BR/&gt;&lt;BR/&gt;In most workplaces, the top-down command and control technique is the method used to manage employees. Top-down concentrates on producing goals, targets, visions, orders and other directives in order to control the workforce and thereby achieve organizational success.   Concentrating on giving direction prevents these managers from doing much of anything else.  &lt;BR/&gt;&lt;BR/&gt;Thus top-down treats employees like robots in the "shut up and listen, I know better than you" mode, and rarely if ever listens to them. By so doing this approach ignores every employee's basic need to be heard and to be respected. This approach also makes top management ignorant of what is really going on in the workplace thus making their directives misguided at best and irrelevant at worst.&lt;BR/&gt;&lt;BR/&gt;In top-down, nobody listens to employee ideas, nobody values their opinions, and nobody gives them any recognition. The only way that the workforce can deal with managers who treat them in this way is to disengage and ignore their behavior. In the workplace this is seen as being sullen, uncommunicative, having a poor attitude, low morale and/or apathy. &lt;BR/&gt;&lt;BR/&gt;(During my first 12 years of managing people, I used top-down and was never aware of how bad my leadership was. It was not until I started really listening to employees that I began to understand.)&lt;BR/&gt;&lt;BR/&gt;In this way and others, top-down demeans and disrespects employees sending them very negative value standard messages. The standards reflected in this treatment "lead" employees to treat their work, their customers, each other and their bosses with the same level of disrespect they received. &lt;BR/&gt;&lt;BR/&gt;This is the road to very poor corporate performance as compared to the results that would be achieved using a better approach.  Top-down managers are their own worst enemies because they “lead” employees to the very worst performance.  (In “The Human Side of Enterprise”, author Douglas McGregor named this “Theory X” and named the other extreme “Theory Y”, but he did not provide how to achieve it.)&lt;BR/&gt;&lt;BR/&gt;If you want your employees to produce very high performance, swing to the other end of the spectrum thus leading toward the highest possible performance.  To do this, first get rid of all traces of a top-down approach. Everyone wants to do a good job, but don't want to be ordered around like a robot. &lt;BR/&gt;&lt;BR/&gt;Next, start treating employees with great respect and not like robots by listening to whatever they want to say when they want to say it and responding in a very respectful manner. Responding respectfully means resolving their complaints and suggestions and answering their questions to their satisfaction as well as yours, but most importantly theirs. It also means providing them more than enough opportunity to voice their complaints, suggestions and questions. Spend your time making your support reflect the very highest standards of all values by resolving their complaints and suggestions.  &lt;BR/&gt;&lt;BR/&gt;And realize that the highest quality and most respectful "direction" is the very least since no one likes to take orders or really needs them except in emergency situations.  Anyone routinely needing extensive orders should not be on your team.&lt;BR/&gt;&lt;BR/&gt;This treatment leads employees to treat their work, their customers, each other and their bosses with great respect.  Listening and responding respectfully also inspires them to unleash their full potential of creativity, innovation and productivity on their work giving them great pride in it and causes them to love to come to work.&lt;BR/&gt;&lt;BR/&gt;You will be stunned as I was by the huge amount of creativity, innovation and productivity you have unleashed. To learn how I escaped top-down after using it for 12 years, read an interview of me at&lt;BR/&gt;http://www.extensor.co.uk/articles/int_simonton/interview_ben_simonton.html&lt;BR/&gt;&lt;BR/&gt;Hope this helps, Ben&lt;BR/&gt;Author "Leading People to be Highly Motivated and Committed"</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default/8320191974216768047'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/15466608/5840794596807311840/comments/default/8320191974216768047'/><link rel='alternate' type='text/html' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html?showComment=1215863220000#c8320191974216768047' title=''/><author><name>Ben Simonton</name><uri>http://www.bensimonton.com</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img1.blogblog.com/img/blank.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.betterprojects.net/2008/07/managing-people-managing-projects.html' ref='tag:blogger.com,1999:blog-15466608.post-5840794596807311840' source='http://www.blogger.com/feeds/15466608/posts/default/5840794596807311840' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1409937258'/></entry></feed>
