Program Design
Are there better ways to start or improve nonprofit programs? This blog is about building better nonprofits, so you probably hope I'll have more answers than questions. I do.
I've written about many brainstorming techniques that you might be able to employ generically for dealing with any nonprofit challenge. This post summarizes some of those ideas and explains how to apply them to program design.
A simple desire to challenge ideas, assumptions, and requirements would be a good place to start. What are the assumptions and usual requirements for a certain type of program? Write them down and examine each one to see if it is valid. Verify that each requirement is really a requirement now, and not a bad assumption or an outmoded idea. Spend about 10 minutes on this exercise..
Break down program design into component parts and look at each of the components. using either stratals or the filament technique. The filament technique calls for writing down the usual requirements for a type or program then writing down ways to fulfill each of the requirements. A stratal is a set of five statements about the subject of your challenge. Spend ten minutes on either the filament technique or the stratal technique.
Try to escape from the usual assumptions, constraints, and taken-for-granted ideas about program design. Use what Edward De Bono called an "escape provocation" to set aside your assumptions. Take an assumption and act like it does not exist. You should have already listed the assumptions behind your program.
Are there better ways to start or improve nonprofit programs? This blog is about building better nonprofits, so you probably hope I'll have more answers than questions. I do.
I've written about many brainstorming techniques that you might be able to employ generically for dealing with any nonprofit challenge. This post summarizes some of those ideas and explains how to apply them to program design.
A simple desire to challenge ideas, assumptions, and requirements would be a good place to start. What are the assumptions and usual requirements for a certain type of program? Write them down and examine each one to see if it is valid. Verify that each requirement is really a requirement now, and not a bad assumption or an outmoded idea. Spend about 10 minutes on this exercise..
Break down program design into component parts and look at each of the components. using either stratals or the filament technique. The filament technique calls for writing down the usual requirements for a type or program then writing down ways to fulfill each of the requirements. A stratal is a set of five statements about the subject of your challenge. Spend ten minutes on either the filament technique or the stratal technique.
Try to escape from the usual assumptions, constraints, and taken-for-granted ideas about program design. Use what Edward De Bono called an "escape provocation" to set aside your assumptions. Take an assumption and act like it does not exist. You should have already listed the assumptions behind your program.
Comments
Post a Comment