Application Development How I Wrote Shape Up

Application Development How I Wrote Shape Up

Application Development Here’s a little behind-the-scenes look at the development of our newest book, Shape Up: Stop Running in Circles and Ship W

Application Development A Beginner’s Guide to Starting and Marketing an App
Application Development Stack Abuse: Serverless Python Application Development with AWS Chalice
Application Development iPaaS – perfect-fitted solution for large enterprise systems?

Application Development

Here’s a little behind-the-scenes look at the development of our newest book, Shape Up: Stop Running in Circles and Ship Work that Matters.

In August 2018, Jason Fried (Basecamp’s founder and CEO) asked me to write a book about how we work. “Sure thing!” I said — having no clue how to go about it or what it would entail.

I didn’t know how to write a book. But I did know how to give a workshop. So I put a call out on Twitter.

⭐️ Announcement: Join me for a one day workshop in Chicago, Dec 20th. “Shape and Ship 1.0” is a workshop on Basecamp’s product management techniques. Learn how we design, develop and deliver new products and features. Apply by Dec 3. https://t.co/NAUxNiuVoG— Ryan Singer (@rjs) November 28, 2018
The workshop was a prototyping device. It was going to do three things:

Force me to come up with a full day’s worth of content that could eventually become a book.Get instant feedback from an audience to learn what’s interesting, what resonates and what doesn’t.Put something out into the world that people could buy, so I could interview them afterward using the jobs-to-be-done approach.I priced the workshop at $1,000 a seat and made people fill out a lengthy application before letting them buy a ticket. The application asked them to tell stories about problems they experienced with product development. Using their answers, I could screen out anyone who was merely curious or a fan but wasn’t really struggling. This created the best possible audience for getting feedback: hungry and motivated with skin in the game.

After the workshop, I emailed every attendee and asked if I could interview them by phone. The interview wasn’t about the workshop—it was about what was going on in their company when they decided to apply. I had a lot to say about product development, but I didn’t know which specific things actually mattered to people. I didn’t know what they were struggling with. The interviews gave me a way to learn what was going wrong in their teams, how they made the decision to attend the workshop, and what they hoped to get out of it.

I did a quick jobs-to-be-done analysis on the interviews and pulled out four jobs they were hiring the workshop to do. Since I considered the workshop a proxy for the book, I could use these jobs to define the key requirements.

Job 1Job 2Job 3Job 4Armed with a better understanding of the demand, I could flip to the supply side. How do I explain what we do? How should I structure the way we work into some kind of outline?

To do that, I used a technique I learned from Bob Moesta that he learned from Genichi Taguchi. The principle goes like this: to learn how an engine works, follow a drop of gasoline over time— from pouring it into the fuel tank and onward. For us, that meant trace the path of a project. Before it was a project, it was… what? An idea? A debate? A conversation?

With this point of view, we used a system mapping technique to spell out how a “drop” of work moved from one phase to another when we developed product at Basecamp.

Following a “drop” of work through a series of systemsThat gave me the three-part structure for the book and the outline for all the chapters in the first draft. Part Three turned out to be tricky because there is a lot of looping. To arrive at the final structure for part three, I interviewed a couple people at Basecamp about situations when they reached for the techniques. That revealed struggling moments (“I hate asking for status…”, “I don’t have any progress to show…”) that I could use for the macro structure of Part Three.

The last major trick was the cartoons. Jobs have functional, social, and emotional components. The system map was intensely functional—all about how to get from this step to that step. The cartoons were a way to set the emotional and social context for each step. They also helped me focus by framing each chapter not just as a “step” but as a situation: who’s there, how do they feel, and why are they motivated to do this?

Setting the social and emotional tone for a chapterI wrote the first draft and drew the first sketches in dark mode on my iPad Pro. It helped me get out of the intimidating feeling of staring at a blank white page. I used Bear for the first drafts and drew the sketches in Notability. When I was purely writing, I’d use the Smart Keyboard. For times when I was alternating between sketching and writing, I folded back the keyboard and used a Logitech Keys-To-Go beside the iPad.

Writing and sketching at the same time in split window mode on the iPadOne thing took a lot of pressure off: Jason’s idea to launch Shape Up as a web book. Releasing it online meant a wide audience, a better chance for the ideas to spread, and — most importantly for me—the ability to make changes after the fact. The book had only the lightest editing when we launched it. Thanks to many tweets and emails from readers, the book was typo free within a couple days of launch.

Shape Up is available to read free online (we don’t even ask for your email address). Just today we released a downloadable PDF version.

The feedback so far has been amazing. Thanks everyone for reading and sharing the book.

Read More

COMMENTS

WORDPRESS: 0
DISQUS: 0