A New Version Of Google Chrome Now Due Every Six Weeks. The reason: Google is creating many few features at ever greater speeds and want to get them to users – however, it also ends up easing the pressure on developers. When releases are slow (e.g. every 6 months or so) designers get pressured to finish up features earlier or risk having them not show up for another half-year. When releases are more frequent, there is less pressure to hit it “this time” because “next time” is only a few weeks away.
Rapid iteration and continuous improvement in the context of it is a key element of swarming. Ministries can use a similar approach when releasing tools and information. Think of your newsletter: if it comes out once a quarter, you’re only sharing your vision 4 times a year. If it comes out once a month, you’ve gone up to 12 times a year. If it comes out once a week, 52 times a year. How many times does it take to acquire a new member of the swarm? Based on that, how many new members will you get per year? Further, how often are the tools you release being updated based on user feedback?
Vision-sharing is key to acquiring new members who help fulfill the promise. Tools are key to enabling them to fulfill the promise. Frequent release is key to spreading it further and improving it more. If with each release a tool is improved by, say, even 1%, but the releases are frequent, then it will easily out-compete other tools and, as it noticeably improves, generate word-of-mouth.
Comments on this entry are closed.