WebSeitz/wikilog
z2006-08-23- Mann Pushing Through Finish Line
is a Product Manager/CTO with a track-record of bringing a business perspective to building agile product-development teams for start-ups, and is seeking a senior role in an entrepreneurial organization building disruptive Internet-driven products.

(backlinks off) (map off)
(search off)
last edited by BillSeitz on Oct 20, 2008 5:45 am

on the failure of most groups to get the benefit of their work. We are thinking about the finish line in the wrong place and confuse getting things done with what needs to happen to make sure we enjoy the results we need them to deliver. From my own experiences, and what I witness with clients, the problem arises from very little about what comes right after done. What would happen if you mapped out, from the start of every initiative or , 5 more steps that needed to be done beyond the obvious finish line? there. At first I was thinking that this contradicted an mentality, but then I realized that the true point is that many managers generate half-baked initiatives, and don't want to put the resources or to actual messy execution. So they treat a first step as a finish line, and then jump onto the next thing. Depending on the size/structure of the organization, I'm not sure you need to plan the details of those later steps in advance, as long as you acknowledge that those steps need to happen, and happen right away, after that non-finish line. Maybe this is a problem with the whole mentality, because it has the risk of making you concentrate on completing the task plan, regardless of [OutCome]. (Perhaps similar to the challenge.)


 




Bill Seitz, fluxent at gmail dot com, Weblog