Working with/for PEPP has proven to be an interesting experience. From the outset of this project and my first meeting with Duke, it was pretty clear that those of us who would be collaborating with the organization would be given free rein to post whatever content we saw fit to post. Duke placed a great deal of trust in all of us, but at the same time indicated that there were certain topics and areas it would be in everyone's best interest to avoid discussing (certain undeveloped organizational projects, etc.). In a very real sense, there was no obvious "authority" over what went into my blog.
In all honesty, I might have benefitted from a bit of authoritative feedback;Duke was almost too hands off. It has been difficult to gauge what his opinion of the blog and its value to PEPP, if any, truly is. Some of this is the result of me not asking for more direction.
In terms of authority (or my perception of it anyway), DUKE WAS PEPP! I was aware of the existence of a board of directors, but they were for all intents and purposes nonentities regarding this project. Although I never really reported to Duke per se, he has been my only real contact within the organization; it was never really suggested that I deal with the board. About halfway through the project, Amy actually gave me the name of another individual on the board who dealt more directly with the "Waking the Sleeping Giant" initiative-consultation with this person at an earlier stage might have led me to choose another direction for my blogs. Again, a lot of this was my failure to adequately inquire about the resources available through the organization itself; no questions asked=no direction given.
The previously mentioned factors significantly affected the direction that I chose for my blog. Left relatively to my own devices, I set a course which I felt was solid and worthwhile. The topic I chose predetermined my audience; the outcome is fairly obvious to those who have looked at my posts.
One observation: a project like this can almost be looked at like an equation. On one side of the equation you have the organization, which is composed of extremely busy people who are 1)often very uncertain as to how the project could/should impact the organization 2)too preoccupied with running the organization to devote a significant amount of energy to examine that issue. On the other side you have the student, also very busy (albeit not as busy as the org reps) who is 1)probably equally uncertain as to how the project could/should impact the organization and 2)probably assuming a greater level of direction from the org than he/she is likely to get (of course, a lot of this depends on the initiative of the student). It would seem that a major challenge in a project like this would be to keep either side of the equation from cancelling out the other. I may take some flak for saying this-but the student may be bearing too much of the burden in determining the direction and content of the blog. If the ultimate goal is to do what is useful and beneficial to the organization, it is completely necessary for the organization to have a clearly defined objective for the student. I think that this issue will probably resolve itself if the course conitinues and the same organizations are willing to participate; at that point they will have had more experience with the medium and perhaps develop more efficient protocols for its future application.