Assumptions and Programming
28 08 2006Creating Passionate Users: Assumptions have a Sell By date
Here is an article from CPU about timing and assumptions. The point here is that assumptions, apart from just being guesses, are very time oriented. If we assume that something works or doesn’t, it usually is true only at certain times.
This got me thinking about programming events. How many assumptions do I have about programming and how new or old are they? Do I have a system of sniffing the milk to see if it’s still fresh or spoiled? Have I ever tried to list my assumptions?
The answers to these questions prompted even more questions.
Assumption #1: Teens want to be entertained
This is one that most people wouldn’t argue. It’s absolutely true. Yet, is that why teens come to church? Is that why they are drawn to an event? My answer is… maybe. Sometimes they absolutely are and sometimes they absolutely aren’t. How do we know when they aren’t? Good question. How many times are teens more interested in the hang out time before or after a meeting, than they are in the meeting itself? Could we just give them what they want and still expect them to grow in faith?
Assumption #2: Flow is king
I have always worked under a performers perspective. Make the experience flawless and minimize distractions to the flow of the night. Yet, I remember going to see some of the kids in my group play at a local hall and how disorganized it was and how thrown together it was. I was horrified for the kids, but they loved it. To them, flawless execution sometimes seems insincere and fake. They would much rather have a flow nightmare that expressed them as they are, than a flawless performance.
More on assumptions later.
Categories : Paul Martin, Youth Ministry, Tips, likeafire
















Recent Comments