Why Non-Readers Want My Book Software
I had a great conversation this week and gained some unexpected insights. I was catching up with someone I worked with years ago and haven’t talked to in a few years. He’s a talented software engineer, and I love getting his perspective because it’s so different from mine. Part of our conversation was about my latest project and his projects. He asked some good questions about my project, and I asked him a few about his perspective on my project. One of my questions was about his reading and learning habits.
He shared that he isn’t a big reader of books, but he sees the value in the wisdom recorded in books and he’s interested in the software I'm building. I asked more questions about how he’d use it. Here’s what I learned:
- He has no desire to start reading whole books; it’s too time-consuming.
- The ability to access a repository of solutions would reduce his need to create solutions from scratch. He could leverage what others before him figured out to create better solutions in less time.
- Using a tool like this could accelerate how he learns about specific things without needing to spend hours reading books. He would learn more without materially increasing the time he applies to learning.
This is an interesting use case because I didn’t anticipate nonreaders seeing value in what I’m building. But this conversation showed me that there are likely countless use cases I haven’t anticipated. When you present people with a way to save time, they quickly see the value in it. This software shouldn’t make people change their behavior but should complement what people are already doing (or not doing).