Create Mission > Vision > Goals documents

[davidbhayes]

[davidbhayes]

_{Sent with GitHawk}

[DanLaRoche]

Here is my stab at these questions. It might be a good exercise to have multiple people fill this out to make sure we're all on the same page about the group.

Answers to Drucker's Questions, Google Doc

[DanLaRoche]

This blog has some interesting elaborations on the questions, if you were like me and had no idea what the difference is between primary and supporting customers:
http://govinnovators.com/2014/10/druckers-5-questions/

[abettermap]

Looks good, Dan. Nicely written.

[davidbhayes]

1. What is your mission?

The mission of CFFC (Code for Fort Collins) is two-fold. On the one hand, we want to have satisfied volunteers who continue to serve in the organization and get value from doing it. Hopefully, they're learning, padding their resumes, and feel that they're making a difference in the community (they are).

On the service side, I see the mission of CFFC as being that no worthy project in Fort Collins goes undone for lack of technical expertise. That is, we serve in an advising role for projects that we're not the best ones to build, and in a building role in the projects that make sense for us. Ideally, we make projects as impactful as they can be, by taking account for real-world use, making sure they they have the marketing, political, etc power to succeed, and making them make the biggest splash they can. (Members can create these projects/needs, but serving non-members is where the most impact is likely made.)

2. Who is your customer/client?

Again, two fold:

1. A developer, marketer, designer, etc who wants to have an impact in their community and is looking for us to help them do that. They're looking for a chance to learn, a salve to loneliness, etc.
2. A non-profit organization, activist with a dream, or citizen who thinks its time for something to exist that didn't before, or make better something that's otherwise working less-well than it should.

3. What does the customer/client consider value

1. Members consider value a relatively effortless path into a community, project, and role that offer them something that their job cannot: a confidence they are doing good things in the world and having fun doing it.
2. External-stakeholders consider value their problems being solved or projects being completed. That is, they'll general have approached us with a need (this website/service/etc needs to exist/be improved) and they're satisfied that they got the value that spurred them to get involved with us.

4. What have been our results?

Our results are two semi-complete projects, which on a per-year basis I'm not super pumped about, but I think it's not bad. We've also got two in-progress projects, and two in-planning ones.

We're also starting to have a coherent set of team members, though I'd love that they were more diverse and better reflected the demographics and skill-sets who would make us the most effective organization of all.

5. What is our plan?

My basic ideas:

1. Develop a mission statement and roles that allow people to feel better that they fit into the organization and can contribute to it.
2. Throw regular parties to celebrate what we've done, what we're doing, and thank our volunteers for being involved. (Hopefully thus get some new ones)
3. Continue to research and discuss best-practices and learn from Code for America and other brigades so that we can implement their best ideas.
4. Find and continue to develop new projects, and finishing our existing ones, so that we can show off our organization to the world.
5. Create a regular mailing list and blog post that highlights what's happening for the less-active brigade members.
6. Develop a leadership organization that can much of the listed above and more happen consistently, without relying on anyone too much or ham-stringing them too severely.