On this page:

LotusScript: Checking another database for categories that do not contain a document of a particular type

We want to scale up Innovation Discovery and share the insights/workshop methods with more people, so one of my tasks is to remove sensitive information from our workshop output documents, post the scrubbed output documents in our community, and update the relevant sector page in our wiki.

This would be easier if people notified me after engagements, but at least we’ve gotten people into the habit of adding files to the Teamroom. I decided that instead of asking people to remember one more step in our post-engagement process, I would just regularly get into the habit of checking the Teamroom for updated documents. The Teamroom date view is useful, but there are other documents mixed into this, and I don’t think I can get my team members to adopt a consistent naming scheme or document type. However, if I wrote an agent to tell me which client categories didn’t have a final output document entry yet, I could use that to find new entries and follow up on old ones. So I did.

I didn’t have access to create new agents in the Teamroom database. I worked around this by creating this agent in my own database and then connecting to the other database from there.

Sub Initialize
	'This script looks for all the client categories that do not have a final documents entry
	'Display the current document's Categories field
	
	Dim dbID As New NotesDatabase("","dbom1\global18.nsf")
	Dim doc As NotesDocument
	Dim catView As NotesView
	Set catView = dbID.getView("CategoryLookup")
	'Determine list of clients
	Set doc = catView.Getfirstdocument()
	Dim clients List As String
	Dim finished List As String
	Do Until(doc Is Nothing)
		Dim category As String
		category = doc.Getitemvalue("Categories")(0)
		If (InStr(category, "Clients") <> 0) Then
			'This belongs in the client category. Has it been found? Add it to the list
			category = Mid(category, 9)
			clients(category) = category 
			If (doc.GetItemValue("DocType")(0) = "Final output") Then
				finished(category) = category 	
			End If 
		End if
		Set doc = catView.Getnextdocument(doc)
	Loop
	'Remove completed items
	Dim s As String
	s = ""
	ForAll client In clients
		If (Not IsElement(finished(client))) then
			s = s + client + " "
		End if
	End ForAll
	MessageBox(s)
End Sub

I change entries to the “Final output” document type after I’ve processed them. So far, so good!

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. =)

Process: Using Activities to organize workshop-related information

We regularly organize Innovation Discovery workshops that bring together experts across IBM and client decisionmakers to explore emerging topics. In the past, this involved a flurry of e-mail, particularly if we had last-minute substitutions. The flurry could get confusing, as we usually plan several workshops simultaneously. I refuse to keep all this information in my inbox. I’ve been setting up Activities for each of the workshops I keep an eye on, and we’re getting better at using the Activities to organize information.

Here’s what the workshop Activity needs to do:

  • Store planning information: agenda, logistics, etc.
  • Store workshop and output files: bios, presentations, and so on.
  • Store links to relevant resources, such as the associated Idea Lab
  • Share background information (both general and client-specific) with experts
  • Keep a record of correspondence related to the workshop, so that people who join the workshop late can see the context

In addition to storing information, the Activity can also help:

  • Organize bookmarked profiles and e-mail correspondence during the search for experts, so that organizers can see which potential speakers have already been contacted and what the status is
  • Remind people of the steps to take in organizing sub-activities such as the Idea Lab
  • Organize related resources for those sub-activities
  • Collect all final documents and share them with the group without filling people’s mail files

It’s easier to set up and add people to an Activity than it is to set up and add people to a TeamRoom, and with Lotus Notes 8.5, you can sync Activities for offline use.

NOTE: Although it works best when lots of people use it, the Activity works well even with just one person updating it (me). I keep others in the loop by using the e-mail notification features. This is good to know if the lack of adoption among your team members has been holding you back from using Activities or other nifty tools. They don’t need to use it if they don’t want to. It works even better when other people use it, of course, and someday it may even reach the point of mainstream acceptance. We’ll see. =)

Here are the ingredients we’ve been working with, and some improvements I’d like to try the next time we organize one:

  • README: How to use this activity – This entry is essential. This should be the first item on the list. It should describe the structure of the Activity, what’s in the different sections, and what to do when.
  • Planning: This section should contain the latest agenda. When logistics are sorted out (including which hotels people are staying at), include them here as well.
  • Output: Final presentations and output documents go in this section. We put this near the top for easy reference.
  • Client information: All the account-related information goes here.
  • Background information: Industry-related notes, and so on.
  • Finding experts: Any bookmarked profiles for experts under consideration. Also, e-mail correspondence for referrals, confirmation, etc. This helps us do the search for speakers even if a team member is suddenly unavailable.
  • Idea Lab: Checklist and related resources for the idea lab, if we’re running one for this workshop.
  • Discovery Lab: Draft presentations, more planning documents, related resources (such as the link for visitor wireless accounts), and correspondence. This is a work area that people can use to coordinate with each other.
  • Post-lab checklist: Post-engagement checklist that reminds us to do our lessons learned, case study, etc.
  • Minutes and archive: Meeting minutes, meeting invitations, other correspondence, and other files.

I love refining these tools!