Loomio

Strategic app design workshop in February

Benjamin Knight PublicSeen by 39

For the week that Rob is in town, we are having a series of workshops to map out the work required to take us to the point of scale. Rich is dumping all the notes from these workshops in this thread (master doc here). They'll be digested and turned into something more accessible and useful over time.

Feel free to chime in with queries or input at any time.

Benjamin Knight

@robertguthrie will be in Wellington from Feb 11th, so there was talk of having the workshop then if it makes sense in the context of everything else.

Benjamin Knight

@robertguthrie , it would be great to hear your ideas here - what were the main things you'd want to get out of a workshop like this?

Benjamin Knight

This is mostly about the structural design of the app @chloewaretini

Richard D. Bartlett

Yeah it might be useful to throw down a list of all the things we could cover, and then choose priorities. Here's some stuff I've been thinking about:

Restructuring the app to communicate the 'mental model'

User has many groups; group has many discussions; discussion has many proposals. This model is currently not being communicated as well as it could - e.g. we see users starting new proposals when they mean to start new discussions.

My intuition on this question points to a) change the Discussion page to make it more obviously a subset of the group and b) change the Group page to be more distinct from the Dashboard and c) change the Dashboard to be more like an activity feed - which would have serious ramifications for the Notifications.

Start to think about huge groups

What happens if we allow subgroups of subgroups of subgroups? e.g. Aotearoa NZ > Wellington > Allen St > Enspiral Space. What if a subgroup could appoint a delegate to represent them in the parent group? (fun fact: if we had max 50 members per subgroup, at 5 layers deep that's enough to cover 300 million people).

We don't need to solve this problem yet but it might be useful to think about it as we embark on a new design.

Start to think about user-specific as opposed to group-specific growth

We've put a lot of energy into developing a good system for new groups to come on board, but we haven't really given much thought to new users joining existing groups.

Think about a discussion timeline and a group timeline

Big discussions might be easier to keep track of with a horizontal timeline at the top of the page marking significant points.

Robert Guthrie

@richarddbartlett I feel it might distract from this discussion if we discuss features/objectives in too much depth here.

Think of this workshop as a Product development/strategy meeting where we can bring up all the desired product features that people have for Loomio and give them a decent examination of their build complexity and value in the context of Loomio's business/growth goals.

For some features this might deserve half a day or a day. Really plan these suckers out and come up with words and pictures that explain the final result clearly.

If after 3 or 4 days we may have the major features people have in mind identified and described - then we can prioritise in the context of Loomio's objectives and leave the developers and other Loomio team members with a very clear understanding of what we're going to build, and what Loomio will be able to do in the next 3, 6, 9 months.

Examples on my mind are:
* Redesigning notifications to be discussion centric.
* Building a mobile experience from scratch
*'Doodle like' (groupless/adhoc group) loomio's
* Discussion threading models
* alternative decision/proposal types, mood gathering tools

Aaron Thornton

Looks like all great content to me. My feeling would be to lean toward scaling features, as this is a phase we need to be in very soon.

Jon Lemmon

So it sounds like we want to make sure we've figured out Loomio's "business/growth goals" before this workshop. In which case, it probably makes sense to schedule in a short workshop for business/growth goals before doing this product/design workshop?

Robert Guthrie

@jonlemmon Yep we definitely need to do that.
Things to think about are total number of users, size of groups, types of groups (govt? private? nonprofit? english speaking?), access method (mobile or desktop or tablet), data sensitivity/security, ability to setup private loomio instances.. and I'm sure much more.

These two main areas of focus will overlap a bit and I think they compliment each other well/are good to think about at the same time - however in general the loomio goals should drive the features and should be stated before we start on detailed feature breakdowns.

Jon Lemmon

@robertguthrie that sounds great. Sounds like we just need to make sure the rest of the group is on board with the plan and then schedule a time that works for us.

PS - You mentioned earlier that it'd be good to have a UX person involved in the process. Kelly mentioned that she's keen to help us out however she can, so we might be able to get her along for part of it.

Robert Guthrie

Ok I wanna agree on a date so I can book flights. When I talked with @jonlemmon, @benjaminknight, @richarddbartlett, @aaronthornton about this we were pretty sure that we'd do it the week following CALH.

Can I please ask one of you guys (sorry I'm stupid busy and not feeling inclusive enough right now) to talk to the other people and get a sense of if that is going to work for everyone who needs to be in attendance?

(btw.. timeslot decision widget needs to be considered at this workshop!)

I wanna lock this in please so that I can change my flights.

vivien maidaborn

I am available 11th - 13th Feb. My sense is that the first 2 days will be useful for me to attend. I would like to add collective wisdom features to the agenda
I like everything else being suggested. Should we start the first day with half day on business goals developing work started already?

Benjamin Knight

Sounds great! Time to move this to proposal so we can lock the date in?

Loomio app design jam: starting February 11th

proposal by Benjamin Knight Closed Fri 1 Feb 2013 8:27PM

It's time for a strategic workshop about the design of the Loomio app!

This is a proposal that we start the workshop on the 11th of February, with duration, content, and mixture of people involved to be determined in ongoing discussion from now til then.

Sound good?

Results

Robert Guthrie
Agree

Coolio says: 'We gonna have fun jamming on loomio, Word, Wassup'

Benjamin Knight
Agree

looking forward to looking forward

Jon Lemmon
Agree

Sounds great! Unfortunately Aaron won't be around, but I think it would be hard for us to find a day when everyone can attend. So this might have to do. Maybe we can think about a way of somehow including remote individuals in parts of the process.

Aaron Thornton
Agree

Let there be light!
p.s can someone fix this wonky button?

Benjamin Knight

My feeling is that we still have a big chunk of work to do around engagement and accessibility, which I'd love to workshop in detail (possibly bringing in some people super experienced in accessibility in online environments), particularly first time experience.

At the other end of the timeline, I'd love for us to workshop some of the very big ideas that have been popping up recently, about the mechanics of groups being able to interact with each other (and the broad implications of implementing things like spokesperson delegation [i.e. parpolity], and decision-making delegation [i.e. fluid democracy]). I cannot wait!

Would also love to talk about different approaches to scalability, particularly in relation to distributed local hosting etc

Aaron Thornton

I will hopefully find a way to skype in at some stage even if it means sitting on a cafe grande at Starbucks for a couple of hours.

Robert Guthrie

I did not get a proposal closing soon notification for this? When did my code break?

Benjamin Knight

Good point @robertguthrie ! Now I think about it I'm wondering whether the proposal closing soon notifications have been working for the last few weeks?

Alanna Irving

I'm keen! I will definitely be around on the 11th, and probably the 12th. I have another commitment Feb 13-15 (though not sure exactly what times per day). Whoever is organizing, please include me :)

Jon Lemmon

Yeah, it's been broken for a few weeks. Probably since Christmas time. Richard and I noticed this about a week ago... started fixing it. It should be fixed when we deploy 1.4 sometime next week.

Billy

I would be interested in contributing to this, too

Richard D. Bartlett

Someone needs to take the lead on designing and hosting this workshop. Who? What? When? Where? Why? @robertguthrie @jonlemmon @alannakrause come to mind.

Robert Guthrie

Who is decided isnt it? People who want to join in.
What is Loomio objectives and then features.
Where is important and I don't know .. Ben mentioned we could use his house... @benjaminknight ?

I've had a pretty strong Idea of what I wanna do with this time but I would very much appreciate support.

Sorry but I don't have any more time to contribute before monday... So see ya then.

Benjamin Knight

Looks like we've got some a few guests coming to stay for a week from Monday @robertguthrie , so our house might be a bit full up. Could still be a possibility for small focused groups who need to hear birds singing to work up here though.

Seems like something relatively low-key with us breaking into groups and working mostly at the Enspiral office could work well?

Just let us know what support you need Robbie! How about a meeting on Monday morning at Enspiral to plan the week? Would 10am suit people? Thoughts?

Jon Lemmon

Woah! Monday at 10am seems early if we're all up late the night before. But if ya'll are up for it then count me in!

Richard D. Bartlett

I'm in for 10am. sounds fun. We will be in a fine state of mind for reimagining the future.

Billy

Some more sense of timeframe and agenda would be nice in advance... both to organise ideas and schedule the rest of life. Like, is this a days-long proposition, as alluded below? Or is the agenda just gonna emerge Monday morning?

vivien maidaborn

We could meet here at my house if we are 6-8 or 9 of us, then small groups is also possible, happy to host. I have appointments on Tuesday and we'd so I will be abit in and out, and also of course need to do some work on Monday engaging WCC reference group and responding to MOJ

Alanna Irving

Can someone please clarify when and where we are meeting?? This is tomorrow and I'm fairly confused. @robertguthrie @richarddbartlett @benjaminknight @jonlemmon

Benjamin Knight

Apologies for confusion! A bunch of us have been away from internet access for the last 4 days (Rich and I are just back now, Jon and Rob don't get back until tomorrow), so nothing specific has been scheduled yet.

I think the idea is to have a low-key chat when Jon and Rob get back to town tomorrow and think about planning the week :)

Alanna Irving

OK so we're not having a workshop today? I am only here Monday/Tuesday so I'd planned to come in. Please let me know if/when the workshop is happening...

vivien maidaborn

good learning for me, unless someone is taking responsibility for a proposed gathering it probably wont happen.

Billy

Glad I checked this before walking downtown... let me know if/when stuff is happening

Alanna Irving

I think this is kind of lame :( There are several people who have been put out by this now. Hard to say who to direct the annoyance at because it appears to be a sort of group fail, but still think it's lame.

Nicolas Wormser

Hey people, it's been two days I'm catching up with the conversations I didn't take the time to read in the last 10 months. It is very interesting and exciting, and this work is giving me a broad (though probably far from comprehensive) view of where we are now (as compared to ten months ago), what people seem the most interested in, and what our most important challenges could be in the future.

Reading all the discussions through, I'm writing down the things that come back on the table again and again, such as features, ideas regarding strategy etc… I've begun to make a mind map of all the information I come across that might help having a wide picture of all this, and help prioritising some things over others.

It's just one man's view of all this, but a global one, that I think could be helpful in finding directions in the workshops that are going to happen this week. Also, I haven't taken part in all the informal (off loomio) discussions and it is definitely possible that my work will not reflect the reality of the situation because of this.

I should be done with this work Tuesday evening, will try to finish it off quickly, but I don't want to rush it. I've still quite a few discussions to read through and don't want to miss out on anything. Haha I'm just realizing how I might sound as a stalker right now…

Benjamin Knight

Just updated the context panel to explain the change in focus - hope this makes sense, but feel free to ask for clarification if not.

It's unfortunate but this has been a situation where no-one had the capacity to coordinate, and it wasn't well communicated, largely because so many have been away from the internet. Apologies for any inconvenience that resulted from the confusion, and thanks for understanding.

@alannakrause , I'm not sure if this was a shortcoming of text-based communication or if I'm misinterpreting, but I feel like your comment wasn't framed in the most productive way. I understand your frustration with the situation, but I hope you can see how it arose. Would be great to talk about this in person if you come in today.

Alanna Irving

@benjaminknight I see what you're saying, but several people put the call out via this Loomio that this workshop was happening, and then let it drop in a way that left others confused. I think it was kind of on the people who kicked this off to see it through a bit more. I came in last week and was told today would be a good chance to jump back into things with the Loomio team - met with @richarddbartlett and @vivienmaidaborn. Now I'm sitting at home confused and unsure about when/if I should even be coming in or if I came in what would be happening or who would be around. I am more just bummed because I was really looking forward to seeing you all again and working together and now I'm disappointed because it's not happening. If not this week, when would be a good time for me to get back on board with the team?

Benjamin Knight

I'll give you a call in a couple of minutes if that suits.

Alanna Irving

Yeah sweet... sorry if I sounded annoyed. I just miss all you guys I guess.

Richard D. Bartlett

Update
We had an informal catch up today to figure out what we’d like to achieve this week while Rob is in town. The key priorities:

  • Roadmap for Org and App
  • App structure overhaul - sketch designs + start to test paper prototypes
  • UX design
  • Clarify work processes
  • Identify skill gaps and strategise filling them
  • Org structure + onboarding

We’re thinking the most productive way to get through this work will be have a series of focussed workshops with the coop members, pulling the right people into the room for specific sessions.

I’ll be doing what I can to document progress to make it accessible to the input of the broader community.

Timeframes
Tuesday

  • 11am - 12pm: develop Org Roadmap; synthesize customer learnings; develop framework for strategic non-customer relationships; working with interns
  • 1:30pm - 2:30pm: develop App Roadmap
  • 3:30pm - 4:30pm: Roles, responsibilities, recruitment: starting from the ‘moderate growth strategy’, clarify and firm up needs; what do we need for the next three months? What do we need for a scale-ready team?
  • 6:30pm: Play shop curry work party idea festival - start sketching ideas for UI 2.0

Wednesday

  • 9am: App next steps
  • 10am: Jam on social loans documentation
  • 2pm - 3pm: Develop role description for interns and sketch integration process
  • 3pm: Jeff from Strategic Pay coming to talk to us about their methodology for job sizing, how to set salaries, understand how the market determines ‘market value’ etc.
  • 5:30pm: strategic pizza & beer with Wise Group IT people

We’ll timetable Thursday and Friday over the next few days.

Jon Lemmon

@nicolaswormser that sounds great. =)

Richard D. Bartlett

Update 2
We had three more meetings today, with dinner and a design jam ahead of us. Here’s the raw dump of the notes so far, apologies for shorthand. Expect this to be clarified further of the coming days.

Feel 100% free to chime in with queries or any input you have.

Org Roadmap Meeting

Predominant focus for this meeting was identifying all the big pieces of work necessary to get us to the Scale phase.

Strategic phases timeline (broad, high-level overview of strategic focus, timelined)

Discovery (Jan 2012 >>)
Validation (June 2012 >>)
Engagement (Oct 2012 >>)
Efficiency (Jan 2013 >>)
Scale (July 2013 >>)

Resourcing Efficiency phase

  • Direct sales revenue - growth target 10,000 users by March 31st, signup + payment automated, social marketing campaign, recruiting and training new account managers, active online community building/management, comms/documentation, support,
  • Social loans
  • Ongoing donations
  • Grants
  • Focused fundraising/Crowd funding

Legal Structure
Constitution, coop structure; well underway

Organisational Processes/Structure
Recruitment process, delegation, transparency, governance/decision-making/board, financial structure/fluid equity/asset capitalization, inclusion and diversity, strategic workshops/retreat, UX processes, development processes, work processes

Customer learning
Feeding customer feedback into feature development, developing online facilitation processes, admin feature side, crowd facilitation, UX processes, security/encryption, invitation process

Customer acquisition
Mainly covered in growth target (building 10,000 user base through online growth) - focus on strategic customers internationally - conference timeline - localization -

Comms/Documentation/Support/Community Management
Need to figure out how big this gap is, how much resource/time will be required. Elements: open-source community management, community support group, building features that support an open community group.

Social Marketing strategy

CFO
Financial transparency / financial strategy

App Roadmap Meeting

We started by listing all the major features to be completed before Scale, then we started to prioritise them. They’re presented here in a vaguely prioritised list, I’m hoping @jonlemmon will turn this into a Trello board.

Feature categories

  • Invitations workflow/group request (re-invite, bulk invite)
  • New user walkthrough
  • New group setup/walkthrough
  • Super-admin features
  • Notifications
  • Subscription system
  • Contribute page
  • Feedback system/online community
  • Crowd facilitation: flagging/moderation
  • Sandbox/live demo
  • Super-admins metrics
  • Group analytics dashboard e.g. engagement rates
  • Users, admins, group metrics
  • Email cleanup (deliverability)
  • Revamp dashboards
  • Export discussion to document
  • Freeze discussions: close discussion to new content + lockdown permissions
  • Discussion features (useful button, reply-to, editing comments, preview everything)
  • Group administration features
  • Search
  • Archive/delete discussion
  • Change proposal close date
  • Single sign on
  • Concurrent proposals / proposal types or modules
  • Connecting groups together
  • Anonymous comments
  • Delete proposal
  • Delete users
  • Delete group
  • User roles
  • Export data (users, groups)
  • Ad hoc/doodle-style/branch.com/flexible permissions/non-group decisions: discussion-centric

We’re going to work through them in more depth in a series of workshops:

Workshops

  • Starting tonight, follow 10-12 Thursday: UI rework, notifications, search, group dashboard;
  • Side conversation tonight: Online community
  • 9am-3pm Wednesday: Invitations - group request process, approval process, contribute page, subscription calculator, new group/user walkthrough/wizard
  • 9am-10am Thursday: Checkup and specfest for other features
  • Metrics: internal and external; time TBC

Other work
Besides the features, the other major pieces of work we identified for the app are:

  • Security strategy
  • Develop privacy policy
  • Platform support (devices, browsers)

Roles, responsibilities, recruitment##

On this meeting we started to sketch out where we are in terms of people and roles, what gaps we need to fill, and how we can move forward.

Now
Full-timers: Jon, Rich, Vivien, Ben, Aaron
As of this week: Jon, Rich, Ben & Aaron will be paid subsistence wages

Coop Members: Jon, Rich, Vivien, Ben, Alanna, Aaron
Contributors: Hannah, John, Rob, Matt, Simon, Liz, Uma, Paul, James, Chloe, Nicolas, Neva, etc. (non-exhaustive)
Advisors: Josh, Rochelle, Linc, Craig, etc. (non-exhaustive)

Commitment

  • Hannah: has made space to commit to the project, can do 2 days to start with; would like to graduate to paid role; code
  • Simon: would like to do 20hrs; to make rent, would need some token money asap; knowledge, information, analysis, communication
  • John: at least 2 days; working towards getting paid at some point; code
  • Rob: keen to be full time or 4 days; need to be paid; coding + product management
  • Alanna: keen to do 2 days for the next three months, then reassess; don’t need to be paid yet (work for equity); need help to figure out best role
  • Ben: full time, probably for this year and next; happy to maintain subsistence pay; strategic relationships (a little account management, comms, community management etc)
  • Rich: full time this year; happy to maintain subsistence pay; front end dev, internal comms, support, load balancer, etc
  • Jon: full time, probably all this year and next; current role can be all-consuming, want to create boundaries for responsibilities: coordinating & supporting developers, while keeping some time to actually do some coding
  • Viv: 4 days; like to be paid when it is affordable; business development, keen to develop international facilitation network, international strategic customers,
  • Aaron: full time; code + design, emotional equaliser

Resource Holes
UX designer, social media, branding/aesthetic design, community coordinator

Process Holes
orientation, training, resources, welcoming

Payment levels
Salaries to be determined after job sizing meeting.
People from July are budgeted to be paid maximum $40k cash, accruing the balance as fluid equity with a 1.25 multiplier. Equity to be paid after Loomio can afford it.

Suggested recruitment process
We write role descriptions based on what we’re doing and what we need. Everyone applies for a job. Everyone gets an interview with a few coop members + an external advisor.

Work allocation
Need to balance flexibility + freedom with responsibility + accountability. Likely everyone will have a formal role description (c.f. Morning Star’s CLOU = colleague letter of understanding)

Role descriptions
Spells out coop needs, technical skills, character competencies, responsibilities, with a focus on ongoing flexibility of work allocation

Equity
Everyone in a formal agreement with Loomio earns equity and/or pay
Temporary exception for interns who are paid with learning (transition from unpaid intern to paid contributor needs to be explicit)
Other volunteers won’t receive equity or pay until relationship is formalised (i.e. role description outlined and responsibilities agreed); backpay can be negotiated per person.

Aaron Thornton

Wow. What amazing results. You rock. Look foward to the next post. A

Richard D. Bartlett

Update 3
Dinner was such a good time we skipped the evening workshop. For this morning’s workshop we started by outlining the existing new group process, identified the main challenges with this system, and then started sketching out the specs for an improved process.

Invitation process workshop

Current Process

Admin = group initiator; LoomioAdmin = Loomio team member; User = group member

  • Admin Requests Group (from inside or outside app)
  • Admin taken to Confirmation page (massive anti-climax)
  • LoomioAdmin reviews Group Request
  • Admin receives docs email see here
  • LoomioAdmin approves Group Request
  • Admin receives activation link
  • If not signed in, Admin goes to sign up/sign in page
  • Admin arrives on Example Discussion
  • (Admin sets Group Description)
  • (Admin may set up sub-groups)
  • Admin emails Users to introduce Loomio
  • Admin creates initial Discussion and Decisions
  • Admin sends invites to Users
  • Admin sends follow up email to make sure Users successfully accessed
  • (Admin contacts LoomioAdmin to resend invitation link)
  • New Users login, are taken straight to the Example Discussion and can see the helper text

Main Challenges

  • Coherence between the content of the docs email, example discussion, and helper text
  • Automation of the steps that are overly manual, i.e. LoomioAdmin approval process; Admin’s group setup + invitation process
  • Communication/Training A) Telling the Admin how to set up an ideal first discussion/decision; B) Giving new Users an overview of the mental model: Home > Group > Discussion > Decision
  • Group/Home page distinction For users with one group, the group page is nearly indistinguishable from the home page; there is no obvious incentive for them to find that page.
  • Follow up Currently there is no system for LoomioAdmins to follow up on new groups, or for group Admins to follow up on new users.
  • Payment Need to make decisions and then design a payment model (e.g. maybe there’s a 1 month free trial before the question of payment comes up)

Improved Process

Process Overview

  • Admin fills in Group Request Form
  • Admin taken to Confirmation page
  • LoomioAdmin responds to Request
  • Admin receives Response Email
  • Admin goes through Group Setup Wizard
  • (Admin follows up members that haven’t set up their accounts)
  • User receives invite email from person they know, inviting them to participate in a specific decision with a deadline.
  • They click link, taken to ‘Join your group on Loomio landing page’

Group Request Form
Sections:

  • Basic group information (group name + Admin name + Admin email + expected size)
  • Explain payment model, i.e. groups with a budget pay for use, which subsidises groups without a budget; will include information about terms e.g. free trial
  • Choose your plan: Pay what you can/Subscription
  • Some survey information: e.g. where did you hear about Loomio? are you an existing user? what specific type of group? how geographically distributed is your group? what language is native to your group?

Confirmation Page

  • Thanks for your request. We’ll review your request and approve it asap.
  • You should receive an email. Tell us if not. (tests our email deliverability)
  • While you wait for approval, here’s an intro to Loomio, how to use the tool, possibly a template for an email to send to your group about using an online tool

Response Process
LoomioAdmin responds to Request (responder is recorded):

  • Sort the incoming requests into high or low-touch categories. This is important based on the principle that when the engagement rates of the low touch groups approaches that of the high touch groups, we are ready to open up the app
  • Select the timeframe (now, a given month, or an indefinite delay)
  • Based on this info, send response email

Response Email

  • Thanks, your group will be approved in X months, or
  • Thanks, your group has been approved. Here’s the activation link.

Group Setup Wizard
Admin clicks activation link, admin lands in group setup wizard:

  • Group name, description, privacy settings
  • First discussion + decision
  • Membership (list of emails)
  • Customise invitation: default should include call to action like ‘you have been invited to participate in this group to make this decision’, must include activation link
  • Send invites
  • Drop them in the app, with specific help information highlighted: go here to get the basics of the tool, how to be a good facilitator, or ignore this and get started playing around.

Join your group on Loomio landing page
User receives invitation email, activation link takes them to the ‘Join your group on Loomio’ landing page:

  • {Group Title} is trialling Loomio for discussion and decision making. You’ve been invited to participate by {Group Admin}.
  • Sign up/in to use Loomio
  • Accept/Reject this invitation

More work to do

  • Go deeper into the new user experience
  • Discussion about payment process (includes trial option)
  • Follow-up process, both for Admins and LoomioAdmins
  • Start wireframing each of the above steps, get feedback from the wider community + some more standardised UX testing before development.