Suggestions from https://wiki.ubuntu.com/UDS-R/LeadershipSummit

Actively training successors (involving team members in leadership jobs, opening up governance/leadership )
When projects are new things are more open and free-form, as the team grows there become more processes and tasks that may become tedious to maintain
Team may begin with generalists who can do everything
You sometimes find people who have a special skill, who are good at presenting or organising.
How do you determine what talents/skills a person has? Personal relationship, positive encouragement
Stay aware of what volunteers are able to and interested in doing
Important to harness volunteer energy while it's there, and scale back when it's lacking (it's ok to scale back!)
New class of contributors: users who need more of a framework, more instructions. Less self-starting.
Some people have misconceptions about involvement in Ubuntu, that there are requirements or need to be "allowed to" work on something rather than just jumping in, we should encourage these people to get involved
As leaders in the community we should strive to empower others to do things like give the presentations at their events rather than inviting us to do them
Provide lists of opportunities, a TODO list.

Reaching the outer rims of the Ubuntu universe (Reaching out to new contributors who are not in the loop yet )
Leadership Clinic (workshop where you bring up your struggling project/team and the people  present brainstorm with you on how to resolve them - this might work well in small groups who present their work after 10 minutes)
Making your project do-ocractic (make new contributors feel empowered and creative, but make sure the team/project is progressing)
Milestones and mid-cycle check points for community projects
more team reports
work items work great for everyone, not everybody knows how to use them
Changing "user" perception (Develop strategies to encourage people new to Ubuntu to drop the "user"  mindset as a way to increase participation in the project)
Encouraging "localness" (A discussion about how we might foster the creation of highly localized  teams and capitalize on the ease of collaboration on a local scale)
You don't need to wait for things to be 'official', you can go and do it, even if you have no country/state LoCo.
Encourage to work together, with the main LoCo. There's a lot of good arguments: horse-power, being official as one team. It makes things easier.
Ubuntu Member "incubator" (A program to expeditiously create and on-board Ubuntu Members)
sometimes we have people who become member and then drop all activities - collect badges
sometimes people don't know what's special about being member
to some it doesn't seem interesting enough, the benefits seem irrelevant to them

Governance discussion (Are current governance processes accelerating or capping growth? Are  they scaleable to match the growing population of people discovering  Ubuntu?)
How to respond to "How can I get involved?"
One-on-one mentoring to find out where they can get involved
Don't confront them with wall of text for how to contribute
Suggested making simple flow chart or website that explores interests
Define "requirements" for involvement (they are often much less than new contributors think!)
General good LoCo ideas:
categorise ideas, try to group people into teams
encourage small, fun events
encourage a feeling of one team, no matter which part of the state/country they are from

Balance on taking responsibility and sharing/leaving it to others
Sometimes there simply isn't volunteers (any solutions?)
Ways to notice danger of burnout before it happens (degelate early, delegate often?)

Work items:
[dholbach] Write a blog post (summary).
[popey] Draft proof of concept for choosing how to participate
[dholbach] help getting the draft out to teams, blog, etc.
[joseeantonior] Edit the Question2Answer template and ask to get localized version of a Q&A system
[dholbach] add flavour teams to CC checkup schedule
[dholbach] mail CC list about the idea to reach out to regularly teams to check in how they're doing
[itnet7] Check into automating the team reports by way of the LoCo Team Portal, and try and get it implemented.
[dholbach] bring up the idea of creating a mailing list for the broader community (we can use it for announcements)
[czajkowksi] mail all councils/boards who can approve members to notify the CC about new members
[jpickett] review https://wiki.ubuntu.com/Membership and send suggestion to CC
[knome] work on a proof-of-concept for a simple website for sending and gathering team reports easily