Failure of confidence

Diebold (now Premier Election Systems), admits voting machines have had critical software bug for the last 10 years that can result in votes being lost.

Nonsensical comments from election officials:

DuPage County election officials were upset to learn their election equipment vendor has acknowledged a programming error that could cause votes not to be tallied, but they said last week that they are confident local elections were not affected.

DuPage has used Premier equipment since 2001. Still, Saar [executive director of the DuPage County Election Commission] said he is confident there were no problems in previous elections.

Saar said DuPage has a rigorous pre-election testing regimen, and its election results are audited by a bipartisan committee.

Where does this confidence stem from? Obviously the pre-election testing and bipartisan committee failed to catch this critical flaw. Not to mention that the lab that certified voting machines was shut down for not actually doing their job.

The first NY Times article says that they have systems in place to audit and catch inconsistencies. But shouldn’t that have set off alarm bells that something in the system was broken?

How to write a grant the way I want to be taught grant writing

Grant Apple

I get really frustrated when going to grant-writing workshops. The workshops are usually laid out structurally rather than purposefully; emphasis is placed upon each individual section of the grant in isolation (the mission and history section, the budget section) instead of concentrating on how to effectively interpret your goals and objectives for a funder. The latter obviously has a structural component, but structure is how you organize your explanation, not how you turn your thoughts into a logical argument for funding. Grant writing is persuasive writing, not just expository.

For any burgeoning grant-writer, I think there are a few, mostly simple pieces for crafting an effective grant: some structural, some logical, and some reality-checking. I call it the APPPPPLE model—the L is actually the most important (and often overlooked) part, but putting it first makes a lousy mnemonic.


Ask: Every grant requires an explicit request for money. “Door is requesting $20,000 from the Window Foundation to expand our lock program into two new communities serving 20,000 homes.” There is an explicit dollar amount and purpose. In my personal style, I believe that the Ask should be the only part of the grant that is written in the passive voice (everything else should be active voice, e.g. no passive verbs: am is are was were be being been).

Proofing: Editing your work means more than running it through the spell-checker. You want to check for clarity, consistency, brevity, clear topic sentences, correct citations (if you are referencing study or census data, and you should) and yes, spelling and grammar. Some methods I use for this: reading it out loud to yourself, giving it to someone else to read (both familiar and unfamiliar with your plans), or plain not looking at it for 24 hours (or more). Priority check: if you have clear topic sentences, I as a reviewer won’t have to spend too much time making sense of paragraph interiors, which means your minor spelling or grammar errors will not glare out at me.

Partnerships: You need to demonstrate some level of involvement with your community. Seriously. Grant reviewers love collaborative projects; we’re cynically aware that oftentimes they run shallow, but legitimacy exchange is key to making your case.

Page Numbers: Every page of your grant application should include page numbers and the name of your organization or uniquely named program. This goes hand in hand with…

Paperclips: Unless you are explicitly asked for multiple copies of an application, you should send one copy (with original signatures—I like .07mm blue rollerball) that is held together with a tight paperclip (preferably one with a grippy texture), or a binder clip (of size commensurate with the thickness of the grant; no 2” binderclip for a 6 page proposal). Most reviewers make multiple copies of a grant and it’s a lot easier to add a staple than it is to remove one. If they’re asking for multiple copies, staple the copies (but keep the original paperclipped)—and if they provide explicit instructions otherwise, follow them with deadly accuracy.

Priority Mail: There are legitimate purposes to overnight a grant, but I would rather see that $18 be put into a $4 Priority Mail (with delivery confirmation) and the remainder spent on celebrating the completeness of your submission.

Logic Model: The “L” should really stand for what I say to people after reading their lousy propsal. “Look”, I say, “You need to have Programs tell you what they really are going to do.” Of course, when you’re an organization of one, you can’t punt like that. So to make it clear: you need to have a well flushed out logic model. Goals, objectives, outcomes, activities, indicators, and targets: google “nonprofit logic model”. A grant is just a logic model, explained in words, with a specific ask (and some general boilerplate, like your history and Directors).

Examples: The best way to be a good grant writer is to learn by example. Get a copy of other grant writer’s proposals (ask them, many are happy to help or even mentor you—though keep an open mind that they may not actually be good themselves). Try to get copies of reviewer evaluation sheets or rubrics (google for generic rubrics); they’ll help you understand the mind of a reviewer. Lastly, become a grant reviewer: find opportunities (check your local association of philanthropic organizations) where you can review other people’s grants and find out for yourself what is effective and what isn’t (it will shock you).

And that’s it. I also really like this book: The Only Grant-Writing Book You’ll Ever Need: Top Grant Writers and Grant Givers Share Their Secrets!

Nonprofit Board Management, Governance and Advice

Last weekend I was in NYC for the Craigslist Foundation’s Nonprofit Bootcamp. As a one-day conference, I’ve really enjoyed it as having a wide variety of informative sessions. This is my second time going and for 2 out of 3 of the sessions, I attended the Board Governance track. The following are my combined notes from 2 sessions: Board Governance 101 by Michael Davidson (Governance Matters), and Managing a Board by John Brothers (Cuidui Consulting) and David LaGreca (Volunteer Consulting Group).

7 Board Roles (from Michael Davidson)

  1. Setting Strategic Direction

  2. Providing Financial oversight and management

  3. Protecting assets and ensuring legal and ethical integrity

  4. Ensuring adequate resources

  5. Serve as advocates and ambassadors for the organization

  6. Developing and maintaining a cohesive and committed Board of Directors

  7. Select, support, partner with and evaluate the executive Director

4 Board Roles (from John Brothers and Dvid LaGreca)

  1. Know why the organization exists… and annually review why it should

  2. Interpret the organization’s work to the public in words of 2 syllables

  3. Combine a sense of obligation with a sense of humor

  4. Give money, or get it, or both

Board Structure: structure should be determined by what you are doing, not bylaws or god.

Board Giving: every board member should give a personally meaningful value. This can be arrived at through dialogue began by other board members who have already given.

Board Fundraising: The actual ask by a boardmember is easy (though no one ever wants to do it). The harder and more involved issue is how do board members represent the organizing and cultivate potential donors.

Executive Leadership: When your Director retires and you being a new search, often the discussion turns to: “Our last ED successfully led the organization for 20 years. We want someone exactly like her.” Instead, the board should continually evaluate the question: does our Executive Director have the skills and vision for the organization and world right now?”

Excellence: The New York Time’s Award of Excellence focuses heavily on board involvement and controls contributing to organizational effectiveness and success.

The Engaged Board: Through dialogue with your board, you should define the vision and characteristics that will have board members:

  • Expend significant time and effort

  • Make a meaningful financial contribution

  • Solicit contributions

Common Board Issues: vague expectations; not knowing what having “success” as a board member means; no feedback loops (was I good or bad as a board member); hot romance/cold match syndrome (hot and heavy dating/recruitment but a cold marriage/service)

The Board Chair: It is the Board Chair’s (the President usually) responsibility to create a functioning board. The board chair doesn’t support the organization, they support the board.

Terms and Limits: Michael strongly recommended terms as opportunities to review performance and lead some structure and legitimacy to ditching unengaged board members (deadwood). He was cooler on mandatory term limits, recommending instead board assessments to be more active. While the purpose of limits is to get fresh blood and ditch deadwood, they also mean that you lose your best members—even with by-years, they’ll find another cause to commit to. Also, Worrying about the problems takes our eyes off of motivating the good people

Creating Director Expectations: Have a board member Report Card that is completed every year for each board member.

Explaining benefits: the board as a whole has a responsibility to its members. This includes:

  • Sending information in a timely manner

  • Giving members training on how to explain, promote and raise money for the organization. Make it fun, interesting and absorbing

Engaging Board meetings: Board meetings can suck, no doubt about it. This is because they are used for reports that everybody can read, and not dialogue that requires people together to have. Michael recommended Consent Agendas: Send out all of the information (ED Report, Budget report, committee check-ins, etc.) in advance. Questions can be raised via email. If face-to-face discussion is still needed, it can be discussed during the meeting. This reserved the agenda for real, necessary, generative discussions. Bring in an outsider to start conversation or have real dialogue around the strategy or future of the organization.

Everyone at board meetings should have (eg be explicitly given) opportunities to “chirp”. Everyone loves to feel needed. Don’t typecast board members: for example, the treasurer shouldn’t be excluded from programmatic goal discussions.

Tell people at what points they are working: within the agenda, note “discussion only” or “discussion needed”, and make sure to include this at least once every meeting

ED Review: Yearly, have your Executive Director put together a review of their view of their own accomplishments. This leads to a dialogue with board of priorities for next year and allows the board to fill in where needed.

HR Policies: Make sure there is a mechanism in the HR manual for staff members to discuss the ED with the board.

The New 990: “The IRS can do things by regulation that could not be done by legislation” (referring to the failed Senator Grassley bill to bring Sarbannes-Oxley-type requirements to the nonprofit sector. While the new 990 form dramatically increases the level of disclosure of internal processes and controls, it’s also an opportunity to present your organization in a positive and effective light (since any organization’s 990 is available publicly through services like Guidestar or the Foundation Center ).

** Board Toolkit**: Documents that your board can create to guide and improve its ability to fulfill its leadership and governance responsibilities. From Governance Matters

Metaphors: John says that managing a board is nearly identical to caring for standing herds of horses; just replace “horse” with “board member” in the literature”.

Lessons for Nonprofitteers from Majora Carter

This is more notes from last weekend’s Craigslist Foundation’s Nonprofit Bootcamp.

Majora Carter, founder of Sustainable South Bronx, gave the afternoon keynote (I think the afternoon speech of a conference should be called a plenary). She spoke from experience in designing socially and ecologically sustainable projects. I think she covered some good points in her speech, but overall I felt like she was pitching to investors more than having an intimate discussion with peers—the latter being a tone I think Nancy Lublin nailed at last year’s Bootcamp ( audio; my notes). Also, I felt that her points were somewhat antagonistic (though perhaps reasonably so) but left out a sense of reality-check: yeah, you’re pissing off The Man, but does that mean that you’re changing society, or just being a nuisance?

  1. Take neither a vow of poverty nor stupidity

  2. Fight for something, not against something.

  3. Help can come in man forms

  4. Groundbreaking solutions abhor orthodoxy

  5. If nobody knows what you are doing, how are people going to care?

  6. Build on sucess and momentum. Why reinvent the wheel?

  7. If you feel like you have a target on your head, you are probably doing something right

  8. Be part of alliances that make sense for your organization

  9. When the time is right, don’t be afraid to move on

  10. You will know who your real friends are when you are doing well (I may have written this down wrong)

Caring on the Internet

I really liked this series of comments on a BoingBoing post

#3 posted by pAULbOWEN , August 17, 2008 12:48 PM

I should care because?

#4 posted by zarl , August 17, 2008 12:53 PM

Nobody cares that you don’t care.

Cleaving Running Reds from Jaybiking

Great article on why drivers call the kettle black when they complain about bicyclists break road-laws. I found interesting the distinction between running a red light and jaywalking/riding:

Let’s talk about red-light running. There are two types of red-light running. “Catching an orange” - or running the start of a red light - which every class of users does. And jaywalking or jaybiking - waiting for the intersection to clear and then crossing against the light - which only pedestrians and cyclists do.

Also, covers interesting analysis of why there isn’t such a thing as jaydriving. Though, as I commented, in my hometown it was pretty common to drive through a red light, late at night.

Are you Ahw or Arr?

Via some fun copy on BoingBoing Gadgets (“These “Toastabags” (phonemologically Bostonian, apparently…”) and someone’s analytical comment

, I came across a way to cleave English speakers: those that pronounce R’s (rhotic), and those that don’t(non-rhotic). From the wikipedia page on Rhotic and non-rhotic accents:

English pronunciation is divided into two main accent groups, the rhotic (pronounced /ˈroʊtɪk/) and non-rhotic, depending on when the sound typically represented in spelling with the letter R is pronounced. Rhotic speakers pronounce written /r/ in all positions, while non-rhotic speakers pronounce /r/ only if it is followed by a vowel sound (see “linking and intrusive R”), and not always even then.

What to ask before building a website

I’m always curious to see what people spec out for consulting (since I have my own template as well). Found this great listing (pasted below) from SitePoint

via one of our VISTAs’s personal website UI and Me.

Background * Goals. What are your specific goals? Consider: o company/brand awareness, o product/services awareness, o product/services sales, o community building, o entertainment, o knowledge sharing, and o internal communications. * Promotional Fit. How should your Website fit with current promotional and marketing strategies and materials? * Deadlines. What are the schedule or deadline requirements? * Funding. What are the budgetary constraints? * Measurement. How will you measure the success of the site? Next Steps: 1. Develop a ranked (from most- to least-important) Goals Master List. 2. Create a mission statement for the site. 3. Identify how the mission and goals of the site might change from short-term to long-term, given the direction of your organization and industry. Audience * External. Who is your EXTERNAL audience? Consider: o current customers, o potential customers, o suppliers, o professional/trade organizations, o investors, o competitors, o children, o schools/educators, and o the sight-impaired. * Internal. Who is your INTERNAL audience? Consider: o all employees, o management, o marketing/sales, o operations, and o IT. * Sub-groups. Determine all subgroups within the audiences identified above. * Define. Identify the interests, technical skills and special issues for each audience group and subgroup. Next Steps: 1. Create a ranked Audience Master List. 2. Develop an Aligned Master List by matching the Audience Master List to the Goals Master List. 3. Create usage scenarios based on Aligned Master List. Resources * Project Roles. Who are the resources that will be responsible for content management and technical support (include their names, titles, roles, and contact info)? * Team Skills. What are the technical and content management skills of each resource? Next Steps: For each resource, identify any training, software, hardware, scheduling and budgetary issues. Competition * Identify Competitors. Identify the sites of competitors and others that may provide direction for your site. * Important Elements. Identify the important elements of each competitor site: o functional features, o technologies used, o breadth of content and o look-and-feel. Content * Functionality. Which functional features should your site offer? Consider: o ecommerce/shopping cart, o site search, o customer service/support, o tech support, o discussion forums, o newsletter, o catalog/information o order forms, o feedback form, o member logon, o password protected areas, and o SSL-encrypted areas. * Information. Which informational elements should your site contain? Consider: o About Us page, o Contact Us page, o copyright notice, and o privacy statement. * Structure. What is your site’s hierarchy? For each of the 4-7 (though you can have more or less) main areas of the site, identify: o each main menu item, o all submenu items, and o additional content. Think of a tree-style hierarchy with the home page at the top. Next Steps: 1. Describe in detail each functional feature. What exactly will it do? 2. Identify the resources required, and any technical and budgetary issues associated with each functional feature. 3. Provide detail for each informational element. 4. Assign content responsibilities to the resources identified above.

Drupal: theme override for Upload.module's attachments list

Update: this functionality can now be achieved with the iTweak_upload module . Thanks to Damon for the tip!

I made a custom override for Drupal 6.x’s Upload.module’s attachments table that is displayed at the bottom of a node when you create file attachments. That table is, in my opinion, one of the ugliest common and default presentations in Drupal core. Below is an example of the before and after:

Example of override

To use it, unzip and drop the included folder into your active theme’s directory (e.g. /sites/default/all/garland), it should take effect without any other modifications—though you may have to reset the theme cache (goto admin/build/themes and click save without making any other changes).

Click Here to Download (

Also, I don’t know what the name is for these types of theme overrides: it’s not a module, and it’s not a whole theme. I posted this to a Drupal Group that, I think, calls them “ Themer Packs”.

The icon code is based on the CCK filefield module—but the current 6.0 version is kind’ve clunky and I wanted to port it to the core Upload module. The namespace is “shiny_upload”.

Also, as an aside, the reason doesn’t currently have this enabled is because it’s still running on Drupal 5.x branch

Digital Media Forensics

2nd rate band’s new single appears on bittorrent sites, band releases press release decrying leak, sleuthing ensues…turns out the band’s manager leaked the track himself. Damning on its own, but the interesting part is the forensic sleuthing that led to outing the guilty party:

With some help of a user in the community, we tracked down some of the initial seeders of the torrent. A BitTorrent site insider was kind enough to help us out, because BitTorrent is not supposed to be “abused” like this, and confirmed that the IP of one of the early seeders did indeed belong to the person who uploaded the torrent file.

It turns out that the uploader, a New York resident, had only uploaded one torrent, the BuckCherry track. When we entered the IP-address into the Wiki-scanner, we found out that the person in question had edited the BuckCherry wikipedia entry, and added the name of the band manager to another page.

This confirmed our suspicions, but it was not quite enough, since it could be an overly obsessed fan (if they have fans). So, we decided to send the band manager, Josh Klemme - who happens to live in New York - an email to ask for his opinion on our findings. Klemme, replied to our email within a few hours, and surprisingly enough his IP-address was the same as the uploader.