Hey, so after having

[2023-10-27 10:37:55 AM] : Hey, so after having quite a disappointing launch I got to think about the great advice by alex and decided to go back a few steps and try to focus on a, hopefully, more concrete slice of my audience: php devs who are trying (failing?) to implement Docker. Looking back it makes sense that people who are simply struggling to not go crazy each time they try to deploy an app may not even know what Docker is so they probably won't be looking for a guide... yet :slightly_smiling_face:. So today I did a little safari with this new focus and I think I got some interesting information to draw on. Thanks for the support!
1 Reply
jasonswett
jasonswettOP2w ago
[2023-10-27 10:57:00 AM] : hey, i'm a fellow php dev who uses Docker. my interest is piqued! [2023-10-27 10:57:42 AM] : Let's talk :slightly_smiling_face: [2023-10-27 10:59:05 AM] : Happy to help! is 30 minutes enough? here's a link to my calendar https://calendly.com/nocomp/30min?month=2023-10 [2023-10-27 07:17:41 PM] : Hi Mauro Chojrin. I'm interested in what alex thinks from an audience standpoint. I also had the same exact struggle with audiences (narrowing them down). Wouldn't adding "...trying (failing) to implement Docker" be boxing your audience only to that specific pain? [2023-10-27 07:18:53 PM] : Mauro's pain is Spanish speaking PHP devs. [2023-10-27 07:19:07 PM] : That simple! [2023-10-27 07:20:23 PM] : The problem here isn't an audience narrowing problem. The product focuses on a specific pain, which is good. The pitch and launch just didn't match the pain the product was designed for. [2023-10-27 07:30:29 PM] : Ryan this is VERY different from trying to narrow before you do safari and start publishing ebombs! [2023-10-27 07:34:02 PM] : Think of it this way: • your audience are people with a shared identity • they have LOTS of pains, which you create ebombs to help with, earning you trust and credibility while also learning for yourself what people respond to and want more of • Based on that, you start narrowing pains (not audience!) to pick options that they will pay to solve. • Then you use the Fixstorming process to come up with lots of ways to help them solve that problem, and narrow that based on their and your constraints. • And then you ship with a pitch and email sequence that connects all the dots from along the way. [2023-10-27 07:35:19 PM] : If you try narrowing your audience too much before you start to earn their trust with ebombs, you're getting ahead of yourself :smile: [2023-11-05 07:20:11 PM] : Those bullet points gave me lots of epiphanies Alex!! :slightly_smiling_face: Thank you thank you [2023-11-05 07:20:44 PM] : "shared identity" is one of those epiphanies [2023-11-24 12:11:01 PM] : Hey. I've been going back to safari in preparation for the second attempt to this. I'll do a whole new version of the product since I got a (I believe) much better understanding of the pains I will address. The original version was probably too generic and even full with not so useful information. Anyway, I'm thinking in the direction of making the message behind my pitch something along the lines of "Go from I'll never figure out Docker! to I wouldn't go Docker-less ever again". Basically the idea is to target people who already know what Docker is and what the benefits of using it are (at least have a general idea) but never got around to actually implementing it. As a matter of fact, I was part of that group not too long ago :stuck_out_tongue:

Did you find this page helpful?