<?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:blogger='http://schemas.google.com/blogger/2008' 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-690197384329559541</id><updated>2024-09-05T06:27:01.968-05:00</updated><category term="Project Manager"/><category term="Project Management"/><category term="jobs"/><category term="unemployment"/><category term="Quotable"/><category term="Technology"/><category term="Random Thoughts"/><category term="humor"/><category term="Business Organization"/><category term="Change"/><category term="Innovation"/><category term="Social Media"/><category term="leadership"/><category term="Agile"/><category term="Process"/><category term="Web 2.0"/><category term="Daylight Saving Time"/><category term="Ends"/><category term="Event"/><category term="Internet"/><category term="Means"/><category term="PMI"/><category term="PMP"/><category term="Regulation"/><category term="Security"/><category term="Twitter"/><category term="Value Proposition"/><category term="learning"/><category term="obstacles"/><category term="recruiter"/><category term="risk"/><title type='text'>enweave</title><subtitle type='html'>Enweave -- in the fabric of collective, collaborative, connected thought.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default?start-index=26&amp;max-results=25&amp;redirect=false'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>102</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-8224960094072085204</id><published>2012-06-07T07:37:00.000-05:00</published><updated>2012-06-07T07:37:19.668-05:00</updated><title type='text'>Assumption = Question: Question Assumptions</title><summary type="text">In the domain of Program and Project management, challenging assumptions consumes much of our time and attention for a very basic and very sound reason. The death blow to most failed efforts is, in one way or another, traceable to an invalid or faulty assumption.&amp;nbsp;
An assumption is essentially an unanswered question. Answer them early and often during the course of any effort and the risk of </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/8224960094072085204/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/8224960094072085204?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8224960094072085204'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8224960094072085204'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/06/assumption-question-question.html' title='Assumption = Question: Question Assumptions'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-8558738205687373014</id><published>2012-04-13T09:55:00.000-05:00</published><updated>2012-04-13T09:55:38.709-05:00</updated><title type='text'>Breaking New Ground: Ditch Requirements</title><summary type="text">

In an environment of &quot;knowns,&quot; where standards exist, we can talk about requirements. Where we are facing the unknown--new territory--where no standards exist, there are no requirements so we think and act in terms of assumptions or hypotheses.

Hypotheses are proposed answers formulated as questions.... Assumptions held as provisionally true until proven (tested). Put another way,&amp;nbsp;</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/8558738205687373014/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/8558738205687373014?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8558738205687373014'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8558738205687373014'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/04/breaking-new-ground-ditch-requirements.html' title='Breaking New Ground: Ditch Requirements'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-8166448868296106551</id><published>2012-04-12T07:06:00.001-05:00</published><updated>2013-09-30T10:05:53.536-05:00</updated><title type='text'>The Struggle for Success</title><summary type="text">
In the world of projects, we constantly struggle for success and one of the longest, most difficult, and time consuming battles we face in that struggle is defining what we mean by &quot;success.&quot;

Over many decades managing a wildly diverse collection of projects and project types for clients large and small, one way of defining what success means has proven most useful. It can be described in the </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/8166448868296106551/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/8166448868296106551?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8166448868296106551'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8166448868296106551'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/04/struggle-for-success.html' title='The Struggle for Success'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-5397588648931653021</id><published>2012-04-11T08:46:00.002-05:00</published><updated>2012-04-11T08:46:44.936-05:00</updated><title type='text'>W.A.I.T. and Listen</title><summary type="text">

For those claiming a leadership role at any level as well as those carrying the tag &quot;consultant&quot; after their name there is an acronym worth burning into your brain: W.A.I.T. &quot;Why Am I Talking.&quot;

We have a word--several, actually, and none are &quot;family friendly&quot; sobriquets--for people who consistently fail to understand that nothing they will ever say is as important as that which they will hear.</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/5397588648931653021/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/5397588648931653021?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/5397588648931653021'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/5397588648931653021'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/04/wait-and-listen.html' title='W.A.I.T. and Listen'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-2651087519569724565</id><published>2012-04-09T11:15:00.000-05:00</published><updated>2012-04-09T11:15:20.431-05:00</updated><title type='text'>Uncertainty Principles: Forget the Assumptions, Get the Facts</title><summary type="text">

Uncertainty is something we all deal with in both our personal and professional lives and is frequently mis-characterized as risk. However,&amp;nbsp;lack of knowledge is not technically a risk. Since we identified a key piece of information that is currently lacking from our critical knowledge base, it is a certainty, not a risk.&amp;nbsp;Uncertainty&amp;nbsp;should be&amp;nbsp;treated as such instead of as a </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/2651087519569724565/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/2651087519569724565?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/2651087519569724565'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/2651087519569724565'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/04/uncertainty-principles-forget.html' title='Uncertainty Principles: Forget the Assumptions, Get the Facts'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-5201743631355621684</id><published>2012-04-04T08:57:00.000-05:00</published><updated>2012-04-04T10:56:45.657-05:00</updated><title type='text'>Data Sea; Data Do</title><summary type="text">We live and work in a sea of data trying to envision, understand, and plan for the future. That data, however, by its very nature is primarily about the past.

In order to make use of data in ways applicable to the future, we apply theories. These theories are often referred to as predictive models, which are frequently integrated into decision models along with other&amp;nbsp;theoretical&amp;nbsp;</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/5201743631355621684/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/5201743631355621684?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/5201743631355621684'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/5201743631355621684'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/04/data-sea-data-do.html' title='Data Sea; Data Do'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-3921234056742045814</id><published>2012-04-03T08:25:00.000-05:00</published><updated>2012-04-03T08:25:32.523-05:00</updated><title type='text'>Defining Deliverable Outputs</title><summary type="text">
A &quot;deliverable,&quot; in project management, is an object (tangible or intangible) created by a project for delivery to an internal or external client. A deliverable might be a report, video, document, system upgrade, process change, any other product or service or piece thereof. Activities (work) are connected with deliverables.

Creating a deliverable is a process. What is needed to produce the </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/3921234056742045814/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/3921234056742045814?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/3921234056742045814'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/3921234056742045814'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/04/defining-deliverable-outputs.html' title='Defining Deliverable Outputs'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-3259939690642954516</id><published>2012-04-02T08:43:00.000-05:00</published><updated>2012-04-02T08:43:22.300-05:00</updated><title type='text'>A deadline is a deadline, right?</title><summary type="text">

No, not entirely; there are at least two different types of deadlines: Hard and soft. In project management terms, a &quot;hard&quot; deadline is on the critical path and missing it has serious, perhaps fatal, consequences to the project. A &quot;soft&quot; deadline is still a deadline but not on critical path and without those dire consequences if missed. There are other distinctions as well but prioritizing </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/3259939690642954516/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/3259939690642954516?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/3259939690642954516'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/3259939690642954516'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/04/deadline-is-deadline-right.html' title='A deadline is a deadline, right?'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-9013203208968969913</id><published>2012-03-05T05:00:00.000-06:00</published><updated>2012-04-02T08:56:15.228-05:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Business Organization"/><category scheme="http://www.blogger.com/atom/ns#" term="leadership"/><category scheme="http://www.blogger.com/atom/ns#" term="Process"/><category scheme="http://www.blogger.com/atom/ns#" term="Project Management"/><title type='text'>Leaders and Managers</title><summary type="text">At one time--quite a few years ago now--as a contractor in the construction business with several teams of hard-working people, lessons about improving the way people come together to accomplish goals was a daily part of life. It still is today but one such incident from that earlier time stands out with great clarity, a memory and line of thinking that has only grown more important with the </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/9013203208968969913/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/9013203208968969913?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/9013203208968969913'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/9013203208968969913'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/03/leaders-and-managers.html' title='Leaders and Managers'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-1330629215135349346</id><published>2012-03-01T16:46:00.002-06:00</published><updated>2012-03-01T16:47:06.052-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Change"/><category scheme="http://www.blogger.com/atom/ns#" term="Process"/><category scheme="http://www.blogger.com/atom/ns#" term="Project Management"/><category scheme="http://www.blogger.com/atom/ns#" term="Project Manager"/><category scheme="http://www.blogger.com/atom/ns#" term="Quotable"/><title type='text'>Planning Value</title><summary type="text">The value in creating plans is not found in blindly following them but in using them as tools to intelligently and proactively manage inevitable change.


Posted by: William W. (Woody) Williams


   Subscribe</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/1330629215135349346/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/1330629215135349346?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/1330629215135349346'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/1330629215135349346'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/03/value-in-creating-plans-is-not-found-in.html' title='Planning Value'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-4590813437475495076</id><published>2012-02-29T07:16:00.000-06:00</published><updated>2012-02-29T07:16:11.133-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Business Organization"/><category scheme="http://www.blogger.com/atom/ns#" term="Change"/><category scheme="http://www.blogger.com/atom/ns#" term="Project Management"/><title type='text'>Inevitable</title><summary type="text">
Change is both rapid and constant. Proactively embrace that fact in ways that drive improvement.

Creating plans, process, and methods that address the inevitable changes of circumstance may seem daunting. &amp;nbsp;However, to do otherwise is to expect that circumstances change to fit plans, processes, and methods which makes disaster inevitable.


Posted by: William W. (Woody) Williams


   </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/4590813437475495076/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/4590813437475495076?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/4590813437475495076'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/4590813437475495076'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/02/inevitable.html' title='Inevitable'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-4178050589163589411</id><published>2012-02-25T07:48:00.000-06:00</published><updated>2012-02-25T07:48:11.509-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Project Management"/><category scheme="http://www.blogger.com/atom/ns#" term="Quotable"/><category scheme="http://www.blogger.com/atom/ns#" term="Random Thoughts"/><title type='text'>Why small is sometimes big</title><summary type="text">‎&quot;Starting small&quot; doesn&#39;t necessarily mean doing small things. Starting step one of massive, complex, daunting goal broken down and prioritized in manageable chunks is &quot;starting small.&quot; Starting is the key.

Posted by: William W. (Woody) Williams


   Subscribe</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/4178050589163589411/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/4178050589163589411?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/4178050589163589411'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/4178050589163589411'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/02/why-small-is-sometimes-big.html' title='Why small is sometimes big'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-8115121790567275401</id><published>2012-02-24T07:36:00.001-06:00</published><updated>2012-02-24T07:36:32.867-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Innovation"/><category scheme="http://www.blogger.com/atom/ns#" term="Quotable"/><category scheme="http://www.blogger.com/atom/ns#" term="Random Thoughts"/><title type='text'>Intelligence, talent, and genius</title><summary type="text">Almost anyone with intelligence and some talent is able to complicate matters; arrive at a solution that is bigger, more complex than the problem. There is, however, a world of difference between intelligence, talent and genius. Some portion of genius is required to solve problems in ways that simplify, rather than complicate, the outcome.

Posted by: William W. (Woody) Williams


   Subscribe</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/8115121790567275401/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/8115121790567275401?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8115121790567275401'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8115121790567275401'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/02/intelligence-talent-and-genius.html' title='Intelligence, talent, and genius'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-1155831292073824482</id><published>2012-02-20T08:08:00.001-06:00</published><updated>2012-02-20T08:08:49.778-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="obstacles"/><category scheme="http://www.blogger.com/atom/ns#" term="Quotable"/><category scheme="http://www.blogger.com/atom/ns#" term="Random Thoughts"/><category scheme="http://www.blogger.com/atom/ns#" term="risk"/><title type='text'>Risks and Obstacles</title><summary type="text">A risk is not an obstacle; it hasn&#39;t materialized. Equating risks with impediments or barriers is placing a mental obstacle of our own construction directly in our forward path.


Posted by: William W. (Woody) Williams


   Subscribe</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/1155831292073824482/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/1155831292073824482?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/1155831292073824482'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/1155831292073824482'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2012/02/risks-and-obstacles.html' title='Risks and Obstacles'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-3220267272769415553</id><published>2011-10-04T12:00:00.000-05:00</published><updated>2011-10-05T17:13:00.902-05:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Project Management"/><category scheme="http://www.blogger.com/atom/ns#" term="Project Manager"/><category scheme="http://www.blogger.com/atom/ns#" term="Quotable"/><title type='text'>Hyperbole</title><summary type="text">Hyperbole is the downfall of requirements, proposals, and status reports.

Posted by: William W. (Woody) Williams



   Subscribe
</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/3220267272769415553/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/3220267272769415553?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/3220267272769415553'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/3220267272769415553'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2011/10/hyperbole-is-downfall-of-requirements.html' title='Hyperbole'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-731721550069759915</id><published>2011-10-04T07:00:00.000-05:00</published><updated>2011-10-05T17:14:04.436-05:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Business Organization"/><category scheme="http://www.blogger.com/atom/ns#" term="Change"/><category scheme="http://www.blogger.com/atom/ns#" term="Innovation"/><category scheme="http://www.blogger.com/atom/ns#" term="Random Thoughts"/><title type='text'></title><summary type="text">For most business endeavors, too much success is just as disastrous as complete failure. 


Posted by: William W. (Woody) Williams


   Subscribe
</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/731721550069759915/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/731721550069759915?isPopup=true' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/731721550069759915'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/731721550069759915'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2011/10/for-most-business-endeavors-too-much.html' title=''/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-6123341447314146912</id><published>2011-10-03T16:28:00.000-05:00</published><updated>2012-02-25T07:51:31.478-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Ends"/><category scheme="http://www.blogger.com/atom/ns#" term="Means"/><category scheme="http://www.blogger.com/atom/ns#" term="Process"/><category scheme="http://www.blogger.com/atom/ns#" term="Project Management"/><category scheme="http://www.blogger.com/atom/ns#" term="Project Manager"/><title type='text'>I am a project manager</title><summary type="text">
I am a project manager: At its most basic, that means knowing &quot;how&quot; to get things done. That &quot;how&quot; stands, primarily, for &quot;process.&quot; Many, but not all, my thoughts here share that focus on process.

I am deeply involved in both program and portfolio management. That means not just&quot;how&quot; but &quot;what&quot; and &quot;why&quot; and &quot;when.&quot; &quot;What&quot; is to be accomplished could be referred to as &quot;the ends.&quot; &quot;How&quot; the </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/6123341447314146912/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/6123341447314146912?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/6123341447314146912'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/6123341447314146912'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2011/10/i-am-project-manager.html' title='I am a project manager'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-5962431054154969232</id><published>2011-08-25T16:03:00.000-05:00</published><updated>2011-10-05T11:10:54.247-05:00</updated><title type='text'>Quotable: Disaster</title><summary type="text">Disaster Quotes Page 2 - BrainyQuote

&quot;If a sufficient number of management layers are  superimposed on top of each other, it can be assured that disaster is  not left to chance.&quot; ~Norman Ralph Augustine


Posted by: William W. (Woody) Williams

   Subscribe
</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/5962431054154969232/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/5962431054154969232?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/5962431054154969232'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/5962431054154969232'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2011/08/disaster-quotes-page-2-brainyquote.html' title='Quotable: Disaster'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-7775993227090171685</id><published>2010-04-23T05:54:00.000-05:00</published><updated>2011-10-05T11:12:22.038-05:00</updated><title type='text'>Why do projects succeed?</title><summary type="text">We&#39;ve all seen &quot;top ten&quot; lists and read &quot;why projects fail&quot; rants. Here, we&#39;ve discussed project failure as well as on Twitter #pmot, and LinkedIn. It may be (creating another &quot;top ten&quot;) the number one item of discussion among project professionals. If not, it&#39;s certainly near the top.

Projects fail for every reason... all reasons. At some level there may be value in knowing what all those </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/7775993227090171685/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/7775993227090171685?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/7775993227090171685'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/7775993227090171685'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2010/04/why-do-projects-succeed.html' title='Why do projects succeed?'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-4368644508387834469</id><published>2010-04-22T05:54:00.000-05:00</published><updated>2012-02-25T08:02:07.540-06:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="Business Organization"/><title type='text'>Similarity and Success</title><summary type="text">In my consulting work withing large, complex organizations, I began to realize remarkable similarities among organizations. In fact, there were more remarkable similarities among successful, large organizations than remarkable differences.

In smaller organizations I found this not to be the case at all; quite the opposite. The differences among younger, smaller organizations and particularly </summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/4368644508387834469/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/4368644508387834469?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/4368644508387834469'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/4368644508387834469'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2010/04/similarity-and-success.html' title='Similarity and Success'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-8522232480651369048</id><published>2010-04-20T06:43:00.002-05:00</published><updated>2012-03-02T08:06:10.966-06:00</updated><title type='text'>People or Process</title><summary type="text">Committed, engaged, talented people may succeed despite deeply flawed processes but it is incredibly difficult and they burn out rapidly. Even the best--world class--processes may deliver flawed outcomes without committed, engaged, talented people. It is not &quot;one or the other,&quot; it is &quot;both.&quot;</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/8522232480651369048/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/8522232480651369048?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8522232480651369048'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8522232480651369048'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2010/04/people-or-process.html' title='People or Process'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-3174456141561171268</id><published>2010-04-19T08:17:00.001-05:00</published><updated>2010-04-19T08:17:29.031-05:00</updated><title type='text'>Process Improvement Opportunity</title><summary type="text">Common business plan: Hare-brained Idea &gt; Foregone Conclusion = Instant Wealth</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/3174456141561171268/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/3174456141561171268?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/3174456141561171268'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/3174456141561171268'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2010/04/process-improvement-opportunity.html' title='Process Improvement Opportunity'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-634817505144248290</id><published>2010-04-16T06:15:00.001-05:00</published><updated>2010-04-16T06:15:50.453-05:00</updated><title type='text'>Contact with the enemy...</title><summary type="text">Planning is often followed by blind adherence to a plan. The first leads to success; the second to failure. Plan accordingly.</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/634817505144248290/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/634817505144248290?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/634817505144248290'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/634817505144248290'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2010/04/contact-with-enemy.html' title='Contact with the enemy...'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-8626621175760257918</id><published>2010-04-09T19:31:00.001-05:00</published><updated>2010-04-09T19:31:46.974-05:00</updated><title type='text'>Friday Epiphany</title><summary type="text">Friday Epiphany: The biggest obstacle you will face is the one you never expected.</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/8626621175760257918/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/8626621175760257918?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8626621175760257918'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8626621175760257918'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2010/04/friday-epiphany.html' title='Friday Epiphany'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-690197384329559541.post-8829398538175145100</id><published>2010-04-09T06:40:00.001-05:00</published><updated>2010-04-09T06:40:32.678-05:00</updated><title type='text'>Engage</title><summary type="text">Talk isn&#39;t cheap when it leads to understanding. Engage.</summary><link rel='replies' type='application/atom+xml' href='http://enweave.blogspot.com/feeds/8829398538175145100/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment/fullpage/post/690197384329559541/8829398538175145100?isPopup=true' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8829398538175145100'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/690197384329559541/posts/default/8829398538175145100'/><link rel='alternate' type='text/html' href='http://enweave.blogspot.com/2010/04/engage.html' title='Engage'/><author><name>Smiling Coyote</name><uri>http://www.blogger.com/profile/03680888005773413594</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='https://img1.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>