Filepicker.io helps mobile and web application developers directly integrate with the user’s files in multiple cloud storage platforms. We save developers time because they don’t have to write custom code for file upload and file management.
Since we are developers, we understand that developers are a VERY rational audience. Their decision making is driven by these key questions:
“Will this save me time?”
“Will this save me from doing schlep work?”
“Will this introduce unmanageable risk?”
“Do I lose inordinate amounts of control in my technology architecture?”
Driven by these beliefs, as developer advocate, I find myself focusing on questions like:
“Why did you decide to try us in your app?”
“How much time will this save you?”
“What are your concerns on risks and control and how can we help you resolve those?”
“What were the roadblocks you faced when integrating?”
All perfectly valid customer development questions. Steve Blank would agree.
But, a couple of days ago a twitter exchange surfaced on our feed that caused me to see things in new light. At the end of the exchange, I realized I had developed a blind spot in understanding the broader customer context. Customers were using us in ways that we had least anticipated.
Disclaimer: The screen shot below is of a public twitter exchange but i have intentionally obscured details for added privacy reasons.
A quick note on how our product works:
- Developer integrates Filepicker.io
- When user uploads files from their hard drive or their cloud storage platform we create unique urls
- Urls are used by developers for call-backs and other processing operations.
Well, at least this is how we expect it to be used.
But as the twitter exchange shows, here is a situation where a user directly used the Filepicker.io url to send a screenshot to his colleagues/friends. We hadn’t expected this to happen. We tried to figure out how he had done it. You can generate sample urls in the docs page on our website that you can share with others.
But that’s not what happened. It turns out that the user was a developer and had used the CLI tool in the community which allows you to get a public link for any file! This interaction helped me realize that this was an interesting situation of the developer’s professional persona intersecting with his personal/user persona. Who would have thought that the value of Filepicker.io for him was that he could share files without leaving tmux?
What did we learn?
When doing customer development it’s valuable to focus on the non-work related persona of the customer. Often we focus almost exclusively on the professional persona of the customer while ignoring what the customer likes, does, loves outside the product-market context of your interaction.
So how do you resolve this blind spot?
Well for starters there are a few questions you may want to include in your persona interviews:
a. Walk me through a day in your life?
b. What are your interests outside work?
c. What do you do in your free time?
d. Do you work alone or with others?
e. How do your personal interests influence your professional interests and vice-versa?
At Filepicker.io, as a company focused on helping developers we invested time in learning the professional persona of our customers. But as this twitter interaction taught us we should learn about the non-professional persona of the customer as well.
Follow the discussion on Hacker News
Filestack is a dynamic team dedicated to revolutionizing file uploads and management for web and mobile applications. Our user-friendly API seamlessly integrates with major cloud services, offering developers a reliable and efficient file handling experience.
Read More →