<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jun 26, 2016 at 1:19 PM, Dave Crossland <span dir="ltr"><<a href="mailto:dave@lab6.com" target="_blank">dave@lab6.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">Hi</div><div class="gmail_extra"><br></div><div class="gmail_extra">Sameer, thanks for this! Please can I repost this on the youtube channel, <a href="https://www.youtube.com/channel/UCfsR9AEb7HuPRAc14jfiI6g" target="_blank">https://www.youtube.com/channel/UCfsR9AEb7HuPRAc14jfiI6g</a>, with a CC-BY license ? :)</div><div class="gmail_extra"><br></div></div></blockquote><div><br></div><div>I don't think it's very useful on the Youtube channel, as that's outward facing. I did this primarily for our community, and to explain all that in emails is hard, hence the screencast. I'd say leave it as webm on the wiki for now, with annotations, as necessary. <br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"></div><div class="gmail_extra">Here's an auto transcription: <a href="https://wiki.sugarlabs.org/go/Vision_proposal_2016/Call_2" target="_blank">https://wiki.sugarlabs.org/go/Vision_proposal_2016/Call_2</a><br></div><div class="gmail_extra"><br></div></div></blockquote><div><br></div><div>Thanks. I think your notes (below) are a lot more useful.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On 24 June 2016 at 18:20, Sameer Verma <span dir="ltr"><<a href="mailto:sverma@sfsu.edu" target="_blank">sverma@sfsu.edu</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> </blockquote></span><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div>3) There are several confounding variables at play. For example, Sugar is a FOSS project. Sugarlabs is an agency established to foster/facilitate/support Sugar, the project. However, the two are not the same. So, in our effort to establish a strategic plan, the unit of analysis should be clear. For me, as a SLOB member, the unit of analysis is Sugarlabs, the agency. Everything I look at, is through that lens, including Sugar, OLPC, Sugarizer, etc. <br><br></div><div>I've put together a screencast describing how all these things are related. I hope this will bring some clarity. <br><a href="https://wiki.sugarlabs.org/images/1/18/Sugarlabs-strategy-overview.webm" target="_blank">https://wiki.sugarlabs.org/images/1/18/Sugarlabs-strategy-overview.webm</a></div></div></blockquote></span></div><br>In the period 0m-7m, you say that that there should be 2 units of analysis, for Sugar Labs and for Sugar, and therefore 2 separate sets of Vision/Mission/Goals/etc, but these should be aligned. Is this correct?</div><div class="gmail_extra"><br></div></div></blockquote><div><br></div><div>Yes, that's what we should aim to do, but more so on the Vision and Mission level. The Goals etc. can be different, as long as these support their respective Vision and Mission.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"></div><div class="gmail_extra"><br></div><div class="gmail_extra">Then 8m-18m, you describe a 7 phase model of a firm:</div><div class="gmail_extra"><br></div></div></blockquote><div><br></div><div><br>5 phase chain, which includes supply and demand sides.<br><br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"></div><div class="gmail_extra">1. Inbound logistics (capital goods, labour) </div><div class="gmail_extra"><br></div><div class="gmail_extra">2. Operations (production, combination of capital goods and labour to produce commodities; Sugar Labs ) </div><div class="gmail_extra"><br></div><div class="gmail_extra">3. Outbound Logistics (distribution, shipping, go to market; eg each sugar release being minted, and then a distro packaging it, or OLPC taking a sugar release and combining it with some distro) <br clear="all"><div><br></div><div>4. Marketing and Sales (managing perceptions, which for a software freedom project is often not sales as in exchange of commodities for money, but instead the success of propaganda at converting neutral people to advocates who agree with the ideology) </div><div><br></div><div>5. Service (Consulting, eg the process of working with schools to realise the value created in earlier stages which may be obvious to us but not to them.)</div><div><br></div><div>You then group phases 1-3 as 'supply side' and 4-5 as 'demand side,' and note that traditionally OLPC has taken care of the demand side while Sugar Labs has taken care of the supply side; and note that such partitioning of supply/demand often creates conflict in free software projects which have more appreciation for the left side than for the right side; and note that the demand side needs attention as it increases the value of the software created.</div><div><br></div></div></div></blockquote><div><br></div><div>Correct. <br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div></div><div>This all seems sage to me :) Did I miss any essential point?</div><div><br></div><div><br></div></div></div></blockquote><div><br></div><div>Note: In attempting to increase the value of Sugar by focusing on Marketing, Sales and Service, we have to at least maintain status quo on the left side. Unless we have production of a stable code base, the demand side cannot leverage it. <br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div></div><div>Then 18m-31m you describe a 5 phase model of strategy:<br></div><div><br></div><div>1. Vision (long term) 'dream statement' of where we dream to be in a few years - the world we hope to arrive into, the big picture we are moving towards.</div><div><br></div><div>2. Mission (long term) what are we, what do we do, why do we do it - this should hold good for the same amount of time as the Vision; what exists today, that powers us to move towards the Vision</div><div><br></div><div>3. Goals (mid term) expected outcomes that are not measurable, eg "Increase adoption of Sugar by non-English-native-speaking children". These typically arise from a SWOT analysis. </div><div><br></div><div>4. Objectives (mid term) specific targets that are measurable, eg "Increase 8 translation locales from 80% coverage to 100% coverage before 2017/1/1"</div><div><br></div><div>5. Tasks (short term) actual activities that are assigned to people to get done, eg "Chris Leonard to organize volunteers to meet the translation objective."</div><div><br></div><div>You noted that typically the common focus of activity of free software projects is at the 4-5 level, with bon mots like "release early, release often," while 1-2-3 change slowly and typically get much less attention from free software project contributors, and the Sugar project isn't alone in this. </div><div><br></div><div>Again, I concur. Something I found missing from your presentation was a guide to how long (ie, in word count) these statements should be. What do you think?</div><div><div><br></div></div></div></div></blockquote><div><br></div><div>We'll come to that soon. No specific guidelines, but it should be brief enough for a stranger to read and understand the vision we propose.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div></div><div>You also noted that while there is no general recommendation for what duration to consider long, mid or short term - as this is relative to each given project - and the core idea is that the earlier phases change less often than the latter ones - you give some recommended durations for the lifespan of these statements for the Sugar Project. </div><div><br></div><div>I therefore propose the following concrete dates for these durations, that are within your recommended durations:</div><div><br></div><div><div>1. Vision (now - 2020/1/1)</div><div><br></div><div>2. Mission (now - 2020/1/1)</div><div><br></div></div></div></div></div></blockquote><div><br></div><div>We can shoot for five years, with an understanding that we revisit in three. <br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div><div></div><div>3. Goals (now - 2018/1/1)</div><div><br></div><div>4. Objectives (now - 2018/1/1)</div><div><br></div></div></div></div></div></blockquote><div><br></div><div>12 to 18 months is ok. Perhaps 18, with reassessment every 6 months. <br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div><div><div></div><div>5. Tasks (now - 2017/1/1)</div></div></div><div><br></div></div></div></blockquote><div><br></div><div>Correct. <br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div></div><div>You also note that this phase strategy is a framework for situating the SWOT analysis that Sean called for, that is, it is a method for defining Objectives. You point to the 2x2 matrix graphic on <a href="https://en.wikipedia.org/wiki/SWOT_analysis" target="_blank">https://en.wikipedia.org/wiki/SWOT_analysis</a> and note that Strengths/Weaknesses are internal to the project - aspects that we control - while Opportunities/Threats are external, beyond our control; and these can be combined to generate 4 categories of objectives:</div><div><br></div><div>1. S + O = things to pursue</div><div><br></div><div>2. W + O = things to convert</div><div><br></div><div>3. S + T = things to reduce</div><div><br></div><div>4. W + T = things to defend</div><div><br></div></div></div></blockquote><div><br></div><div>I'd replace + with & <br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div></div><div>However, since this is phase 4 of 5, and we haven't finished defining the earlier stages, I propose to postpone a SWOT analysis until those stages are wrapped up. </div><div><br></div></div></div></blockquote><div><br></div><div>SWOT can be done in parallel with Vision & Mission. The outcome of (Vision & Mission) *combined* with the outcome of (SWOT/Pursue/Convert/Reduce/Defend) should lead to the formation of Goals. <br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div></div><div><br></div><div><br></div><div>Finally 31m-33m you conclude that the approach to drafting a vision statement with wide consensus is not productive when done via email or an IRC board meeting, and you want SLOB and the community to understand there is a specific process you have in mind for developing these productively, and to be patient as this process can take time to wrap up; and you offer to do some other screencasts to present further details of that specific process. </div><div><br></div></div></div></blockquote><div><br></div><div>I'll send out information on this briefly. It will be a form (Google Forms) to collect answers to questions designed to elicit responses to components of Vision. Once we have that input, we can start putting common concepts together and prioritize. I'd appreciate some help in putting that together. We'll of course have access to the backend Google Spreadsheet, so rest assured that all input will be available for us to look at. The form simply allows for not influencing ideas (me too! or I disagree!) in the initial stages.<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div></div><div>This is awesome! I'm looking forward to the next screencast so we can learn how to participate in defining the vision productively :) </div><span class="HOEnZb"><font color="#888888"><div><br></div></font></span></div></div></blockquote><div><br></div><div>Coming soon :-) <br><br></div><div>Sameer<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><div></div>-- <br><div data-smartmail="gmail_signature">Cheers<br>Dave</div> </font></span></div></div> </blockquote></div><br><br clear="all"><br><br></div></div>