Our LSM Sketchboard

I had a great time at Lean Startup Machine last weekend and learned a lot. I’d like to give a big shout-out to my collaborators, Gordon Agress, Joshua Haas, Miraya Yao, Ray Schmitz and Sebastian Park who were all enthusiastic, brilliant and cool under pressure. I sincerely appreciate the time and effort that the organizers and mentors contributed to making the event so great. It was amazing to spend the weekend with so many thought leaders in the Lean Startup space.

Rather than one long blog post about the whole event, I’ll start by writing about something our group found really helpful and several people asked me about, our sketchboard (that big brown piece of paper with all the stuff stuck on it).

Picture of team at table, with sketchboard on wall
Our team workspace

The challenge

Lean Startup Machine weekend is intense and not for the faint of heart. In just 48 hours, you form a team, decide on an idea to pursue, and create a product using Lean Startup principles and activities. We needed to engage in customer discovery activities in an asynchronous, and yet coordinated way. How would we keep track of what we were doing and understand patterns as they emerged, without a lot of time for synthesis or reflection? Based on some good experiences I’ve had using sketchboards as part of the LUXr program, I decided to build a sketchboard to help us track our evolving understanding of the problem, the users and their needs.

What was on our sketchboard?

Our sketchboard evolved over the weekend.  We added new information and put revised information on top of older versions, but the structure I established at the beginning held up pretty well. I tried to set it up so it supported telling a story about the problem we were solving. The project name and objectives at the top, problem, ecology and competitive information on the left, user research, segmentation and personas on the right.

Note: you can click on the image to see a larger version of the sketchboard

 

Sketchboard with annotations

 

A – Our project name “DomainMatcher”

B – Our hypothesis, Customer-Problem-Solution statement

C – Competitors in the space

D – Sketch of the ecosystem, with subject matter experts (SMEs) outside buyers and sellers

E/F – This section started out as just two groups domain “sellers” (E)  and domain “buyers” (F) but quickly evolved to visually represent our segmentation theory. Sellers were arranged by low # domains to high # domains held and buyers were arranged into buckets (founders, advertisers, blogger/vanity and flippers). The blue tape indicates we engaged with that person. The provisional personas (Sam the seller and Brenda the buyer) were added once we determined our early adopter targets and drew on elements we heard in our conversations with buyers and sellers.

G – Paper prototype of our buyer Minimum Viable Product v.1

H – A reminder of our goals for the weekend, “Question assumptions” “Iterate” and “Get out of the building.”

How it helped us

I expected that this would help our team keep track of the work to be done and help us create a shared understanding of emerging patterns. I was pleasantly surprised at how quickly people jumped in, contributed their own elements to the board and used it as a focal point for conversation. I believe a healthy sketchboard is owned by the entire team, and isn’t the work of a single person.

Mariya uses the sketchboard to engage with Hiten
Mariya and Ray work with Hiten

An unexpected side-benefit was how it made it easier for us to engage with other people. Several mentors and LSM participants came by, looked at the board and said “OK, I get it, here’s something I can do to help.” It was great to have a visual artifact we could use to quickly orient other people to our project and where we stood, pretty much in real time.

 

More about sketchboards

If you want to see another example of a sketchboard used in a slightly different way (with a nifty video), check out this post from the Adaptive Path blog “Sketchboards: Discover Better + Faster UX Solutions.”

More about Lean Startup Machine

Lean Startup Machine is a weekend long boot-camp where entrepreneurs learn Lean Startup principles through real-world problem solving and coaching from mentors that get it. In 48 hrs, you’ll pitch an idea, form a team and attempt to build something customers actually want. The prize? Cash, mentorship and glory. This is a single weekend that will change how you think about building startups forever.

 

Getting ready for LSM

I’m attending Lean Startup Machine this weekend. Participants were selected via application. At the event we’ll pitch ideas and form small teams of people with business, tech and design skills. (Hooray for cross-functional and collaborative teams!) We’ll learn Lean Startup methods by doing customer discovery and making things together. The program runs Friday night through Sunday eve and there are prizes at the end for the best projects.

I want to get the most out of the experience so I am preparing for it. One aspect is establishing what I personally want to get out of the event. Here’s my objective.

I’m agnostic about the platform and idea I work on this weekend. What matters to me is:
– The team has a good mix of skills
– The team plays well together
– The idea we’re working with is relevant to people who are easily accessable this weekend

LSM participants have many different skill sets and personal objectives. I can’t assume they know me, or anything about what I do. Because of my own objectives, It matters to me that I attract compatible working partners. I created this brief bio and shared it with the group list before the event. It was hard to write because a) in this context, I’m a learner not an expert and b) I do have something to offer and don’t want to under-sell myself. This is what I shared with the group.

Here’s why you would be interested in working with me:
– I am a UXer with big experience and a small ego
– I am great at finding people to talk to and listening to them
– I make quick, lightweight concept sketches (pen/paper)
– I help teams quickly generate ideas and decide on a course of action

My other form of prep is research. I’m reading books and blogs and watching videos. I am trying to figure out “what is lean startup?” “how does it work? “who are the thought leaders?” “where are the examples of people’s experiences with it?”

Observations

  • The Lean Startup movement is young, decentralized and experiential/evolving.
  • Eric Ries identifies it as a movement, not a method or process, and acknowledges participation from prior art and other contributors. (Kent Beck/XP/agile, Steve Blank/Customer Development)
  • It draws on a large existing body of information that requires the learner to know “prior art” or be able to dig back to understand it (e.g. some knowledge of agile terms and practices is assumed).
  • There’s a LOT of amazing great stuff out there if you can find it.

Pain

  • As a person newly interested in the movement, I’ve needed to figure out who are the people who are relevant, then do a lot of research into their blogs/videos (and a little into tech press) to figure out what matters.
  • A lot of the conversation is happening on lists, and at conference proceedings (which aren’t always very well documented)
  • There’s a lot of cross-checking involved (e.g. watching a video, the speaker will reference something I need to go follow up)

What’s useful

  • I find Eric Ries’ “talking head” videos about “what is Lean Startup” “What is a MVP” etc, very helpful. Some of them are informal, some of them are a little more produced, but they’re great for linking/sending to people to say “see, this is what I mean…”
  • I’ve found SocratED helpful, because it pulls together some of these distributed resources in a curated way.
  • I’m finding delicious somewhat helpful, mostly to track my own progress, but somewhat to find other links tagged “lsm” and “lean startup.”
  • Quora hasn’t been very helpful to me yet. Still trying to figure out how to use it effectively.

I’ll post some more impressions after the event, watch this space!