Recently Rick Davies eloquently wrote in his blog ('Rick on the Road': http://mandenews.blogspot.com/) about different ways that people articulate program logic in logframes. This is an issue that I've also battled, and have written about elsewhere (http://www.aid-it.com/Portals/0/Documents/070105_Aristotle%20and%20Plato%20at%20it%20again.pdf).  Many users of logframes seem to lose sight of the fact that the 'vertical logic' is supposed to describe the temporal sequence of change.  That is, how a particular project is anticipated to contribute to social change through time.  Instead, some folk use the vertical logic to systematically disaggregate the problem...in what Rick succinctly decribes as a "hirerearchy of inclusion".  An analogy of this approach to program logic is: * the Goal = a wall * the Purpose = the bricks that make up the wall * the Outputs = the sand and cement that make up the bricks * the Acivities = the molecules that makes up the grains of sand and cement etc... ...