An illustration of “snowflake” model of leadershi p 7 

Context in source publication

Context 1

... as a relatively new model for practicing leadership is developing and known as the “snowflake model”. Leaders develop other leaders who, in turn, develop other leaders, all the way “down” ( Fig. 1). As prior software was limited to only one level of leaders, a new approach was necessary. As a result, new software was developed, with the possibility of creating an indefinitely large snowflake, and many more new features. It is called ORSA ( Or ganizing S oftware A pplication). V. M AIN FEATURES OF ORSA As ORSA is derived from an idea of hierarchical snowflake organizing structure, developed and improved by Harvard University Professor Marshall Ganz, who is credited with devising the successful organizing model and training for Barack Obama’s winning 2008 presidential campaign, and many more successful grassroots campaigns. Consequently, main features of ORSA are developed having in mind those principles. ORSA is developed using known web-based technologies as PHP programming language, mySQL databases, JavaScript, HTML. It was developed in Zend PHP framework. As an idea behind community organizing actions is a dispersion of responsibilities all way down to the bottom level of activists (volunteers), the software should support a virtually unlimited number of levels inside the organization. Any volunteer can easily become a team leader, by simply adding more persons in his team bellow. Also, members of his team can make their own teams etc. Database is structured following a nested sets model, able 8 to represent infinitely large hierarchy levels . As simply adding members to the team is not sufficient to create an effective team, additional info about teams created can be added, and reviewed by members. Every team defines its purpose, norm and roles. An administrator (top level team leader) can create a measurable goal for an organization. The term “measurable” implies that the goal set can be defin ed by quantity. While creating a goal (e.g. collecting signatures), the administrator defines quantity of goal that should be achieved (e.g. one thousand), and also a deadline for completion of goal. The administrator then disperses a goal over his immediate successors (children). Those children are the parent nodes now, and they can disperse given amount of goal that should be accomplished to their child nodes, etc. like shown on Fig. 2 (a), and Fig. 2 ...