On this page:

Brainstorming ways to help build the Emacs community

John Wiegley and I had lots of fun brainstorming ways to help move Emacs forward, particularly as I’m carving out more of my time to focus on Emacs. Here’s what we talked about:

A rough outline of things to flesh out into articles/chapters:

  • productivity, org-mode
  • development
    • emacs lisp
    • haskel, rails, java, and other languages…
  • writing
  • e-mail
  • IRC/Twitter/FB
  • web
  • games and diversions
  • documentation
  • learning and discovery

Learning Emacs development:

  • tools
  • cons cells
  • macros, quoting
  • control structures
  • Emacs structures: windows, buffers, text properties, etc.
  • lambdas
  • libraries

Ideas for visualizations:

  • #emacs word cloud or URL frequency/analysis
  • IUseThis for Emacs, maybe with annotations

Cookbook:

  • PLEAC for Emacs? Emacs Lisp cookbook?
  • Coding patterns

IDE challenges:

  • IntelliSense
  • Excellent project browsing
  • Refactoring
  • Integrated test harnesses
  • Asynchronous operation
  • Performance (especially of code analysis and navigation tools)

Target communities/audiences?

  • Emacs beginners: getting more into Emacs, learning more about packages, customizing Emacs; learning path through packages, maybe with time estimates?
  • Emacs intermediate: tweaking Emacs, getting into Emacs Lisp, contributing upstream; need to update Writing GNU Emacs Extensions
  • Keyboard enthusiasts: keyboard shortcuts, customizability
  • Non-developers (writers, scientists, mathematicians, etc.): Context-specific functionality, starter kits, easy installs, articles, screencasts – learn from Aquamacs, Ready Lisp. Pre-built Org starter kits? screencasts, interactive tutorials, games as introductions
  • Users of defunct editors: migrated features, migration guides
  • IDE users: integration with other parts of life
  • Vim users: configurability envy, migration/emulation

Emacs performance: elp, memory-use-counts, garbage collection, algorithms, cookbook, core work

Discovery:

  • packages: popularity, reverse dependency graph, URL log for #emacs, 24 packages for Christmas and other blog series, IUseThis, reminders to be lazier / stories for inspiration
  • EmacsWiki: guided tour, CSS design

Imagining awesomeness in 5 years: Responsive editor that’s easy to set up; SEO so that people can find useful resources; context/goal-specific documentation; regular virtual show&tell

Imagining nonawesomeness: Weak async; marginal/niche; people moving away to other editors because of growing gaps; performance issues; unmaintained code; developer burnout

EmacsConf: mailing list for next year, venue?

 

Here’s what I’m looking forward to devoting some of my time to:

Write and draw

  • EmacsWiki page updates
  • Guided tours
  • Emacs Lisp cookbook
  • Package reviews
  • Interviews with people so that they can share their tips (incl. screencast and transcript)

Analyze

  • Package use
  • Performance
  • Logs

Learn

  • Performance optimization (Emacs Lisp and core)
  • Package descriptions and use

Code

  • Issues
  • Feature requests
  • Integration
  • New code

Lots of possibilities!

Visual book notes: Best Practices Are Stupid: 40 ways to Out-Innovate the Competition–Stephen M. Shapiro

Here’s my visual summary of Stephen M. Shapiro’s 2011 book Best Practices Are Stupid: 40 Ways to Out-Innovate the Competition (affiliate link). It’s a good book for people handling innovation management in medium and large enterprises, although small business owners might still be able to apply a few tips like the one about getting out and observing your customers (Lessons from Indiana Jones, p.69) and when to buy/innovate/hire solutions (There’s no such thing as a “know-it-all”, p.42).

Click on the image to view a larger version, and feel free to share it under the Creative Commons Attribution Licence!

20121211 Book - Best Practices Are Stupid - Stephen M. Shapiro

Check out my other sketchnotes and visual book notes!

Brainstorming breakdowns, assumptions, and possibilities

image

Lightweight personas for ideation workshops

One of the techniques we use to help a group generate ideas in Innovation Discovery workshops is to create light-weight personas. Anchoring the brainstorming using a name, a face, and a story makes it easier for people to generate and later evaluate concrete ideas. The personas also give the group a common vocabulary for talking about different audience segments. For example, if the group defined John as a middle-aged professional concerned about healthcare issues, people can then ask, “What would John think about this?” during other sessions.

The persona ideation exercise is great for sparking energy and getting people to stand up. It can be used in different places, and it can become a running theme.

  • Beginning of workshop -Defining personas - talking about characteristics and challenges: Who are the target segments? What are the gaps? What’s the worst-case scenario?
  • During the workshop – Brainstorming: How can we apply the ideas discussed in the previous session and other ideas we generate to build an ideal scenario for each of these personas?
  • End of the workshop – Evaluating and summarizing: Which of the parts of the ideal scenario can be implemented easily, and which take more effort? Which potential initiatives serve which personas, and how well?

Structure of the session:

Goal: Concrete vision, ideas for initiatives

Input: Light-weight personas which we flesh out with the help of the clients during the workshop session.

Output: Scenarios for each of the personas, and possible summary of key initiatives to explore in the next session.

Preparing:

  1. Identify a few persona types that reflect the client’s target audiences, with the planning team’s help. Ex: entrepreneur, parent, student, and so on.
  2. Look for pictures through Flickr Advanced Search (check all the checkboxes related to Creative Commons so that you can search for commercial-use modifiable photos). Stock photography sites such as sxc.hu and stockxpert.com are also useful, although I prefer to use Flickr because the people and situations look more real than posed. Put the pictures into a presentation, one slide per picture, with proper photo credits. If possible, crop the picture so that only one person is in it, and scale it up so that it fills the slide.
  3. Review the pictures and select which ones will be used. Aim for a diverse mix that represents the target audience well in terms of ages, professions, races, etc.
  4. Give the personas nicknames for reference. Use names that are easy to remember and spell. Alliteration is fun to use and makes names more memorable (ex: Bob the baker). Label the final slides with the nicknames in a large font, so that the names can be read from a distance. Adjust the photo contrast if necessary.
  5. Print full-colour copies of the pictures with names. You can post these next to easel sheets taped to the walls for brainstorming. If you have access to a poster printer, you can print large sheets of paper with the picture and the name at the top of the page.
  6. Finalize your persona presentation. Your presentation can be as simple as flipping through all of those pictures one by one, or you can show them all together if there’s space on the slide.

During a break before the session:

  1. Tape up 1-2 easel sheets per persona. Spread these around the room, making sure that there’s enough space for people to stand and talk. Have at least one blank set of easel sheets just in case you need to create a new persona on the fly. If you have plenty of space, put up more easel sheets.
  2. Place markers, Post-it notes, and masking tape near the persona groups. Different-coloured markers and notes give people flexibility.
  3. If you want (and you don’t have too many personas), post the persona pictures next to the easel sheets.

During the session:

  1. Explain the structure and flow of the session (goal, input, output, and the next few steps).
  2. Very briefly review the personas with names, faces, and light detail.
  3. Review the different personas, pointing them out around the room. Ask people to define the characteristics. You can change the characters completely at this point, or introduce new ones. A co-facilitator (or coworker closest to the poster) should jot quick notes about characteristics.
  4. Find out if you need additional personas. Use the blank pages you’ve set aside or repurpose a persona that didn’t click.
  5. Review the personas with the characteristics again, pointing them out around the room. asking people to move to the one they want to focus on. See if you can get people to take responsibility for reporting back at the end. Consider the balance of people among the different groups.
  6. Explain the structure again: people are going to figure out what that persona’s “moment of truth” is with the organization (key customer experience?) and walk through what that scenario could be in 2-3 years (or whatever the workshop’s vision timeframe is). Point out the markers and the notes. Encourage people to move around to other personas they’re interested in contributing to as well.
  7. Give people a time limit. Split up into groups. Walk around and facilitate, asking questions.
  8. Remind people when the time limit is almost up.
  9. Get the groups’ attention. Ask them to briefly tell their persona’s story based on the brainstorm. Take public notes on the different initiatives that can enable that scenario. These notes can be used during the analysis portion.

Analysis (can be done in another session or by another facilitator):

  1. If there are a lot of common initiatives, do the next analysis as a large group. If there are separate initiatives, let people continue the analysis from there.
  2. Let each group (or the large group) discuss which initiatives can be done by either organization separately, and which initiatives need collaboration. Help prioritize the initiatives in terms of perceived effort and benefit. Capture the results in a table.
  3. Review the results with the team.

After the workshop:

Summarize the persona characteristics and stories (may be bullet-point form) in the workshop output document.

Lessons learned:

  • Don’t offer too many choices, because clients may just want to have all of them.
  • Don’t give personas too much detail, because clients will benefit the most from personalizing them during the workshop.
  • Don’t be afraid to revamp your personas entirely.
  • Don’t panic. =)