For release early, release often, you need to know where you are going. It works especially well if you have a model to copy: Microsoft Windows 1.0, 2.0, 3.0 w

For release early, release often, you need to know where you are going. It works especially well if you have a model to copy: Microsoft Windows 1.0, 2.0, 3.0 was based on the Macintosh. Linux was based on Unix. Or you can have clear vision that you are working towards - in this case, the model you are copying is imaginary. I guess that's the "Grand Scheme" the article is talking about. You do have to have a way to keep that in mind, and build towards it. You can do this by giving selective attention to the feedback (bug reports, feature requests, complaints) that leads towards your Grand Scheme. This also builds a user base that is aligned with what you want to do (by encouraging those people, and turning off the others). Then your user base supports your vision, instead of undermining it. You are the captain.