Tag Archives: grove

33 people, 22 venues, 4 hours, 3 platforms: 1 brilliant remote meeting

Last week, my colleague Malgosia Kostecka and I co-facilitated a challenging four-hour remote meeting of 33 attendees in 22 locations involving complex work: developing a mission statement and the initial five-year vision for a new organization. This meeting kicked off a five-month process to explore different models for how the organization might be structured. Over the summer, sub-groups will design possible models and prepare to present them to the whole group. The process will conclude in October with the group’s first face-to-face meeting, where the final mission, vision, and five-year strategy will be set. These will then be used in securing approval to launch the organization.

For this kickoff, we used Zoom, Boardthing, and Slack as our workspaces. I’m happy to report that it went well. Astonishingly well, actually, given that I always assume something will go horribly wrong! We barely needed Plans B and C and didn’t reach Plans D or E at all. Here’s how it worked.

Pre-Meeting Preparation
Facilitators:

  • We worked closely with the meeting sponsors to identify outcomes and understand who would be in the meeting.
  • We set up Slack for the whole team, since they will be doing ongoing work throughout the summer. The ongoing setup includes channels for smaller working groups, plus one for questions, general information, and workgroup chairs. Special temporary channels were also set up for the meeting (see Plan C, below).
  • We set up a Zoom room for the main meeting space.
  • We created a Boardthing board for collecting and sorting vision ideas. Advance setup included creating a list of instructions, uploading a template image for sorting the ideas, and preparing an agreement scale in case we needed it.
  • We prepared 14 digital templates covering each part of the meeting from the Do-Now to Closing Thoughts. Not all were used, but they were ready!
  • We created a spreadsheet to track who had signed in to Slack, who had done the tech check, who was to be at the one co-located venue, and who would be in each breakout discussion group during the meeting. We took into account the 11 people who would be connecting from a single location when planning breakout groups.
  • We prepared a visual roadmap of the entire process, from this kickoff meeting throughout the summer and fall to the final group meeting scheduled in October.
  • We prepared the agenda (a detailed facilitators’ version and a more general participants’ version).
  • We prepared a text document with participant names and email addresses, key web links that would need to be copied and pasted, and a few technical support statements that we would likely need to paste multiple times.

Participants:

  • Prior to our involvement, participants went through a selection process based on interest, expertise, and availability. There were also initial discussions about the process and its outcomes.
  • We asked participants to sign in to the Slack team space prior to the meeting and to have Slack open during the meeting itself.
  • They were also encouraged to attend a brief tech check to make sure they could access Zoom.

Meeting Tools/Technologies

As mentioned above, we used Zoom, Boardthing, and Slack; additionally, I used Autodesk Sketchbook, a spreadsheet, and a text editor. We used a countdown timer to time breaks.

Agenda & Activities

The planned timing is on the agenda image here. The actual timing is noted in parentheses next to each activity below.

Picture of the meeting's agenda.

Our agenda. Organization and other names have been removed.

 

  1. Do-Now & Orientation (15 minutes)
  • The do-now was designed to help folks start thinking about the meeting content and give them something to do while everyone else got connected. Everyone was to type into a special Slack channel, answering the question: Why is this organization important to you personally? [Wondering whats a do-now is? Here’s a PDF that explains.]
  • Once everyone was settled and had had a chance to work on the do-now, the sponsors opened the meeting by setting the context for the work this team will be doing, why do it now, and why the team was comprised of these particular people.
  • I introduced myself briefly when I took over, and ran through the outcomes, agenda, roles and rules as shown above. I left space for additional rules but the group didn’t add any.
  • I mentioned the backchannels (Slack and the chat feature of Zoom) and encouraged participants to speak up in those channels if they were having trouble. Malgosia was monitoring both channels throughout the meeting.
  • We asked people to turn off their video cameras while they were in the full-group session and said they were welcome to use them in the breakouts later.
  1. Introductions (30 minutes)
  • Since this group is not an intact team but a group of colleagues from different organizations, we invested some time in team introductions. Using a prepared template that showed six ‘tables’ — one for each of the working groups that will meet over the summer — we went around the virtual room.
  • Malgosia and I modeled what we were looking for with our own introductions first.
  • Each person’s name was already written in, along with his or her organization. When it came time to speak, each person said who they were and where they worked and also shared one hope or expectation for the process. I added each person’s hope/expectation to the template as they spoke, using Sketchbook and my Wacom Cintiq pen display tablet (it’s like the 27HD but mine is a 24HD).
  1. Project Roadmap (10 minutes)
  • We placed the project roadmap on the screen and walked through it to be sure the five-month process was clear.
  • Facilitators and meeting sponsors/workgroup chairs answered questions as they arose.

After that, we took a five-minute stretch break. I placed a countdown timer on the shared screen to time five minutes.

  1. New Org.’s Mission (55 minutes)
  • After the break, we shifted to developing a draft mission statement. We started by reviewing mission statements from four or five well-known organizations (selected in advance and written on a template).
  • Next, we explained the process we were about to use, as well as the backup plan should our initial plan fail (see Backup Plans, below). We answered questions (all this took a little less than 10 minutes) and then got started.
  • First, each person wrote down an answer to the question: What is this organization’s reason for being? This was done individually on whatever piece of paper was handy. (5 minutes)
  • Next, we grouped everyone into trios using the Zoom breakout rooms. In each group, the three people shared what each had written and generated one statement for the trio — either choosing one of the three, or writing a new one. (10 minutes)
  • Whenever they worked in breakouts, we checked in with each group periodically to make sure that everything was going well.
  • Next, we grouped up three trios together to make a group of nine, and they repeated the process: listen to each trio’s statement, and come up with one statement for your group of nine. (15 minutes)
  • This resulted in three statements. We came back to a whole-group discussion, and each group read their statement. We captured it on a template using Sketchbook and screen sharing, and then briefly discussed the three statements. We noted issues and key questions that would need to be resolved in the work over the summer. (10 minutes)

We ended that segment with three possible mission statements, agreeing to finalize the new organization’s mission in October.

At this point we were halfway through the four-hour time, and we took a 20-minute break to stretch, wolf down food, adjust any technical glitches, and so on. Once again I shared the countdown timer.

  1. Vision Images (10 minutes)
  • After the break, we briefly reviewed the agenda to check in with the process and our progress.
  • Then we shifted to working on the vision. We opened with a guided imagery activity, set five years in the future. We set the context by saying that five years had passed and the organization was very successful. Then, everyone listened and imagined, but did not answer or speak, as we asked the following questions: What activities are happening throughout the year? Who is involved? What are the media saying? What publications and resources exist that didn’t before? How is your work different now?
  • Everyone was then given five minutes to jot down some ideas that had come to them during the visioning.
  1. New Org.’s Vision (65 minutes)
  • Using a template prepared in advance (a Mandala with the imagery questions written in the segment circles), we asked the group to share thoughts that they had had. We worked through each of the questions and captured ideas as they were voiced. (25 minutes)
  • When that was complete, we saved it and uploaded it to Slack right away so that everyone could use it during the next activity.
  • Once again, before launching into the activity, we showed a template with the steps written out, reviewed them, and answered questions. We explained and gave examples of what we were looking for: specific vision themes, or what the organization will be, do, or have in five years’ time. (about 5 minutes)
  • Once everyone was ready, we pasted the Boardthing link into the Zoom chat and into Slack and asked everyone to open it.
  • While they were doing that, we placed them into breakout groups of about six people (the 11 co-located people formed two groups where they were).
  • Each group was responsible for generating 3-5 cards in Boardthing. Each card included one key theme for the vision, either pulled from the previous conversations or generated now. (25 minutes)
  • While they worked, we checked in on each breakout to make sure that everything was going well.

After that time, we gave everyone else a 5-minute stretch break (using the timer). Meanwhile, Malgosia and I took an initial pass on the cards, grouping them into rough clusters and proposing cluster names. When the group returned, we had six or seven theme categories and three or four cards that we weren’t able to place in groups.

  1. Refining the Vision (15 minutes)
  • After the break, we reviewed the clusters and asked for corrections or changes. We refined the cluster names and added the loose cards to clusters with the group’s guidance.
  • We copied the seven cluster heading cards and placed them into the vision template in Boardthing.
  • The group discussed and refined the vision elements further, adding nuances and making distinctions, until they were happy with the draft vision.
  • We did a brief and informal check for alignment, and declared victory!
  1. Next Steps & Closing (7 minutes)
  • We briefly brought back the process roadmap and reviewed it again, answering new questions.
  • The sponsors outlined next steps, thanked everyone for their involvement, and closed the meeting — on time. Well, almost. We were two minutes over.

After the meeting, we created a PDF file containing all the meeting charts, including screenshots from and a link to the Boardthing board, sent it to the sponsors, and uploaded it to the team’s Slack space. Now we are in the process of planning and scheduling the series of smaller remote meetings for each of the six working groups that will take place over the summer.

Backup Plans

When I create a backup plan, I pick the thing that is most likely to go wrong, imagine what will happen if it does, and come up with a workaround. I keep doing this until the only remaining workaround is for everyone to talk normally on the phone while I take notes on paper. The backup plans for this meeting centered on people not having access to Zoom, or the Zoom breakout groups not working, since those were the trickiest parts of the meeting.

  • Plan A: The meeting as designed and described above, and basically what we did.
  • Plan B: Assuming people couldn’t see the screen but could connect to Zoom via the phone, they would be paired up with a ‘screen buddy’ who could help them create Boardthing cards. I also read everything that was on the templates and described each new one briefly as I brought it up.
  • Plan C: Plan C covered us if the breakout groups in Zoom failed. In every meeting, there are always a few people who can’t get into the breakout rooms, and I have yet to figure out why. If it’s just a few, then I leave them in the main room and they become their own breakout group. If it’s a lot, then we are into Plan C. To prepare for Plan C, we created temporary channels in Slack for each breakout group and invited those people to each channel. The instructions to the group were that if the Zoom breakout wasn’t working, they were to have their discussions via text in the Slack channels instead. We only needed to do this with one group once.
  • Plan D: Plan D assumed failure of Boardthing, or failure of people to get into Boardthing. In this case, I would have brought it up and shared my screen and we would have talked through the process, perhaps collecting ideas in Slack and having Malgosia read them to me to type in. Luckily, we didn’t need to do this.
  • Plan E was the last-ditch backup, where we do the whole thing in full-group discussion while I share my screen and do graphic recording.

What I Would Do Differently

I learned a LOT about Zoom breakout rooms in this meeting. One thing I should have taken advantage of more is the ability to set breakout groups up in advance and then re-use them. If I had done that, it would have greatly simplified (and speeded up) the process of getting people into breakout rooms. Instead, I created different groupings on the fly based on lists in our spreadsheets, which got a little complicated and took some time to set up. Astute readers will notice that in steps 4 and 6 in particular, we lost a few minutes of work time getting people into the breakout rooms.

On the whole, though, I’m happy with how it went, and I’ve heard very positive feedback from the participants and sponsors as well.

Need a Good Remote Meeting?

Do you need to get work done with a remote group? I’d love to help. Contact services@grove.com to set up a time to talk about what you need.

Recorded archive: Digital Tools workshop

Friday’s Digital Tools for Graphic Recording workshop was recorded, and you can view the streaming archive here. It’s a WebEx recording, so you may need to download a client to view it.

I apologize in advance for the brief periods where my screen and I vanish (it happens twice). Don’t worry — I come back 🙂  I’m hoping to be able to edit those out eventually, but at the moment, I’m still trying to work out how to edit a WebEx recording — I can adjust the start and end times, or at least I could if I had a PC and not a Mac, but I can’t change anything in the middle! (And trust me, there’s quite a lot I could safely edit out…)

Post-workshop Debrief

Workshop Title

Last Friday, I led a workshop at The Grove called Digital Tools for Graphic Recording. Anne Merkelson moderated the session, and Tomi Nagai-Rothe and Ed Palmer provided backup and technical support. Over 130 people attended the free online workshop, which was scheduled to go for an hour but ended up running about 90 minutes. I learned a lot — especially about giving an online workshop to that many people — and I also mentioned a bunch of tools and offered to make my Sketchbook Pro brush sets available for download. Read on for all that info.

Lessons Learned

WebEx Lessons. We had some technical issues — at least, I did. I got kicked out of the conference twice when the WebEx client quit on me. (Thanks, everyone, for hanging in there til I got back!) We’re still not sure exactly what happened.

This was a much larger workshop than I’ve run before, and I now have some pre-workshop housekeeping steps that I’ll take care of next time. My thanks go to the attendees who helped me take care of these tasks on the fly this time! Next time, pre-flight will include:

  1. Setting the conference options in advance to mute the beeps when people enter and leave.
  2. Muting everyone at once! I knew there had to be a way to do that, but I sure couldn’t find it until someone showed me where it was.
  3. Logging in as myself and also as admin, then passing presenter control to myself so the admin account isn’t required the whole time. We have a theory that the client crashes were related to the fact that I was logged in as the admin.

There are a few other things I might do differently next time:

  1. We learned afterward that some people tried to access the session from their iPads and were not able to. I don’t have information about the nature of the problems, but next time I’ll recommend that participants use computers.
  2. It appeared that some people who joined the session after I had started sharing my screen couldn’t find the chat window. I did cotton on and help them locate it eventually, but next time I would add instructions for this to the introduction of the session.

We did some things right, which means attendees probably didn’t notice them. I’ll mention those, too:

  1. In addition to the presenter (me), we had one person who was focusing only on collecting and moderating questions, and two people who were focused on helping people who had connection troubles.
  2. The session “started” 15 minutes before the official start time so that people could come in, test their connection, make sure they could see and hear, and so on.
  3. I had the right headset! If you’re on a Mac, you want a USB headset, not the kind with a pink and a green connector.
  4. I remembered to hit “record!”

Presentation Lessons. I heard some feedback that the middle section of the presentation got kind of visually confusing. I had opened all my palettes in Sketchbook Pro (SBP), just as I do when I’m recording, but it would have made more sense to open them one at a time as I was talking about them (brushes only when I was talking about brushes, layers only for the layers piece, and so on).

Another comment was that I did a lot of things in SBP without explaining or narrating what I was doing. This may well have been confusing, especially to people who aren’t familar with the software. In the future I’ll try to be more explicit about saying what my mouse is doing!

Links & Notes

Here’s a list of links to some things I talked about. If I said something you wanted to look up and it’s not listed here, post a question in the comments and I’ll add it.

Workshop Agenda

Some of the key points I made were these:

  1. There are lots of options for digital graphic recording. When choosing which to use, match the tools to your own comfort and skill level and also to the meeting’s venue and outcomes.
  2. Set up your file in advance to facilitate the kind of distribution you will want. Use a low-res (72 dpi or thereabouts) for images that will be emailed and printed small-scale, on letter-sized paper. Use higher resolution (300 dpi) and a larger canvas size for images that will need to be printed larger. Remember that Sketchbook Pro has a limit on how large you can make your file — this is a flexible combination of print dimensions and resolution.
  3. Set up a custom brush set with the brushes you will need most. Create at least two sizes of each brush, one for thick lines like titles, and one for fine lines and details.
  4. Learn to use layers; I use at least three: one for outlines and details, one under that for colors, and one under that for shading and shadows.

Brush Sets

These sets are the ones I use most when I’m using Sketchbook Pro for graphic recording. They work on the computer, but not on the iPad (whole different brush thing there), and only with Sketchbook Pro. I use SBP 5.0, and they might not work with an earlier version. I know they’ll work on a Mac but I’m not sure if they’ll work on a PC too. (Let me know if you find out.)

They’re provided here with no warranty of any kind; if they run amok and wreak havoc on your computer, you will have my deepest sympathy, but that’s about it 🙂

Rachel’s favorite Sketchbook Pro brush set for graphic recording (72 dpi): use these brushes when you’re recording at screen resolution.

Rachel’s favorite Sketchbook Pro brush set for graphic recording (300 dpi): use these brushes when you’re recording at print resolution. They’re bigger so the lines will show up properly.

To install the brush sets:

  1. Download the file(s) and save them on your computer somewhere that you will be able to find them again. They should end in .zip.
  2. Launch Sketchbook Pro.
  3. If your brush palette isn’t open, go to Window > Brush Palette to make it appear.
  4. Click and hold in the little tiny circle of circles in the top right of the brush palette (see below).
  5. Swipe your mouse straight down through the icon with three brushes and an arrow pointing down (tooltip says: Import Brush Set).
  6. Navigate to where you saved the brush sets. Click one of the .zip files and click Open. Ta da!
  7. Repeat steps 4-6 to load the other brush set, if you wanted both.

If you get the little spinny ball and the brush set doesn’t load the first time, don’t panic. Repeat steps 4-6 and it should work the second time.

circle-menu

The menu you need is here.

Unanswered Questions

There were a few questions from the workshop that we didn’t have time to address:

Q: Can you hook up an iPad to a projector through a VGA connector? Does it work if you are on WebEx? 

A: This question has a two-part answer. Yes, you can hook the iPad to a projector; however, you can’t control WebEx from it to the same extent as you can on a computer. The iPad doesn’t work like a VGA tablet. The tablet is an input device, like your mouse or keyboard; it talks to your computer, which can be connected to WebEx. The iPad is another computer, not an input device, so you can’t use it to control your computer* to run WebEx. There is an iPad app for WebEx, but it doesn’t give you all the functions you need to record a webmeeting.

* The caveat here is that technically you can use certain apps to control your computer from your iPad. They’re not yet robust or fast enough to allow the iPad to replace a tablet for real-time graphic recording in a web meeting, though.

Q: It seems there are a couple ways to look at it. (1) Facilitate a virtual digital meeting and record as you go, or (2) use a moderator, facilitator and recorder. When is that better than (3) using a video conference with the camera on the paper you are using on the wall — then you document for archiving after the meeting? 

A: In my personal opinion, (2) is better than (1) most of the time. A small meeting can be recorded and facilitated by one person, especially if everyone in the meeting knows one another and the content is not too emotional or controversial. Some graphic recorders, too, are skilled enough to handle more challenging meetings this way (I’m not one of them). Larger meetings, or meetings where the facilitator will frequently be called upon to manage the group’s energy, will benefit from having a separate graphic recorder and facilitator. Another attendee also suggested a third person, a moderator who handles the web conference itself. An excellent idea.

When choosing between (1) or (2) and (3) — recording in a web meeting versus using a webcam and paper — the factors in play are the comfort level of the facilitator/recorder and attendees with one method or the other, the equipment you have available, and what you want to do with the recording after the meeting. Personal preference is another factor. Neither method is inherently better than the other.

Q: How do you print all the different layers? Will a complete picture show up on one page of paper? 

A: All the layers that are visible will be included in the print. You can also flatten the file into one layer when you’re done, if you’re sure that you don’t need the layers any longer. I always keep one layered version and use “Save As” to make a flattened one, if I need to.

Q: What’s the maximum number of layers you use?

A: I’m a layer hog! When I forget to keep track, I can end up with a lot. I know I’ve had stacks up in the twenties before. Typically, I try to keep it to three or four, and on the iPad you can’t have more than six in SBP.

Thanks to all those who attended, and especially to those who helped me out with WebEx and made suggestions for future improvements.

Updated May 24, 2013, to fix missing images after the blog moved.

Online Workshop on Digital Tools for Graphic Recording (from The Grove)

Media_httpnewsgroveco_cafeq

I’m at it again! Tune in for a free, one-hour workshop on digital tools for graphic recording, offered by The Grove Consultants on December 9, 2011, from 12:00-1:00 pm Pacific Time. See original news post on The Grove’s site for more details or to register.

Registration Open: Free Creative Lettering Webinar on August 23

Media_httpnewsgroveco_jisus

Registration is open for the one-hour online seminar on creative lettering I’ll be leading for The Grove on August 23. Check the article for the registration link and instructions. See you there!