From: Richard on
On 19/04/2010 15:55, Tronscend wrote:
> "Richard"<yuk(a)ntlworld.com> skrev i melding
> news:831bt1Fuf2U1(a)mid.individual.net...
>> On 18/04/2010 21:48, Ken Pledger wrote:
>>> In article<830hoeFu2mU1(a)mid.individual.net>,
>>> Richard<yuk(a)ntlworld.com> wrote:
>>>
> ......
>
>> Thanks. But, I think I might have solved things sufficiently.
>>
> ......
>
> Looks like it, but as an interested layman ....
>
> a) "means" and "ends" are not ontological kinds, so to speak;
> they are a two-step chain of events arbitrarily lifted out of an otherwise
> seamless timeline.
> IOW, you can move the two-step window back and forth, seeing event 1 as the
> cause/precondition for E2,
> and then move one step, seeing E2 as C/P for E3 and so forth, and of course
> the other way (E-1 to E1...).
> So there is per se nothing wrong with seeing "Increase visitors" both as an
> end in relation to "Better advertizing (etc.)", and as a means in relation
> to "Shops opening". It is a matter of convenience or purpose, either in
> analysis or in presentation.

Exactly. In constructing (what is a fictious problem tree /objectives
tree.I'm dreaming it up, but the problems could easily be as I imagine)
- I am discovering just what you say.

There is a kind of "right" way or "better" way to constructing the
initial problem tree. The better ways are less confusing, more
convenient, better suited for a purpose, or analysis etc.

There is probably something on the WWW about how best to construct a
problem tree.

What I seemed to have understood, is that something like "increase in
visitors", should be, sort of, a header, and not be stated as an output.
Having said that, of course, it could be seen to be an output in some
objective tree - but it looks like, *in the circumstances*, "increase in
visitors" out to be the collective result of group of ouputs, not
refered to as an output itself.

In project cycle management, using a logical framework matrix, I'm
supposed to end up with a series of objectives. As per:

Overall Goal
Project Purpose
Outcomes/Outputs
Activities

Anyway,(for my assignment)I reckon the (fictious) focal problem could be
shops closing in the town, which converts to a (fictitious) project
purpose of "openning shops". Openning of shops, saves the town
economically. :c)

"Openning shops" happens when certain outcomes/ouputs are achieved.

And of course activities have to be developed to bring obout the outputs.

Openning of shops (project purpose)
| |
Increase visitors Low shop rents
| |
town Environment (output) (some output)
town advertising (output)
town transportation (output)

I belive that both "Increase in visitors" and "Low rents" appear in the
problem tree, *but NOT in the Logical Framework Matrix*.

But, I'm unduly rabbiting-on a bit about not that much. :c) I just
reckon that I must not put "increase in visitors" as a output.

>
> b) In the problem, you introduced both a timeline as well as a reciprocal
> effect (fewer visitors, shops closing, even fewer visitors, more shops
> closing .... etc.). A cycle.
> To the degree that this is an important part of the presentation of the
> problem, perhaps you might consider including it in the model also when
> presenting the solution (More visitors, fewer shops closing, even more
> visitors, shops opening....).
> Opening the loop to plot it on a timeline, you might get some quantifiable
> points like "More than 10x visitors (needing product x (coffee, gas,
> lodging...) may constitute a market for 10x businesses (by 10th of
> February); 10x businesses may constitute an attraction for 20x visitors (by
> 25th of May); More than 20x visitors (needing product x (coffee, gas,
> lodging...) may constitute a market for 20x businesses ....." ; IOW the
> upward spiral, or a part of a business cycle or whatever you may want to
> call it.
> Anyway, the point is to distinguish "timeless" "logical" loops from actual
> temporal events.
>
> T

Gotcha. I will mention this cycle when I present my stuff.

Some of what I need is here:

http://www.locallivelihoods.com/Documents/Toolkit%202.1.pdf

Cheers. Rich