How would you approa
[2024-02-05 12:05:34 PM] : How would you approach 30x500 differently if you were trying to complete it in a week?
1 Reply
[2024-02-05 12:06:33 PM] : Caveats: I've been in the course for months and have shipped a few ebombs on my tech blog. I'm almost done with the course itself. So I'm not really starting from zero.
[2024-02-05 12:06:50 PM] : At the end of this week I'd like to ship something tiny, nothing fancy.
[2024-02-05 12:17:22 PM] : december
Launch:FTW / Year of Hustle has a step by step plan for launching a Tiny product in 100 hours ( 8 hours / wk * 13 weeks).
Maybe use that as a template and see what/how much you can fit in the time available to you.
[2024-02-05 03:36:27 PM] : LaunchFTW came to mind for me too.
another point of reference is the 24 hour challenge that amy used to launch her book, Just F'ing Ship. She journaled the process in quite a bit of detail here: https://stackingthebricks.com/24-hour-product-challenge/
[2024-02-05 03:37:49 PM] : one of the nice side effects of a "public" launch challenge like that is that, depending on who you're creating it for, talking about the creation process itself can be a part of how you promote it.
[2024-02-05 03:47:02 PM] : if I were to apply the 30x500 approach in just a week, I'd be looking at it from the zoomed out view of the 30x500 Canvas and building my week around making sure that all of the parts were built into my plan:
• A clear answer to who I'm building for, and where I can find them
• A very specific pain that they're aware of and want solved. Ideally, a pain that I understand (so I don't have to do a lot of new research), and is somehow linked to their time or money
• a place to talk about that problem, and how I'm solving it, at least a couple of times a day. I'd focus on sharing updates/progress reports, etc, more documenting what I'm doing rather than wasting time on "what to talk about". this imperfectly replaces the ebomb process, but for the sake of the challenge, achieves the same goal of earning attention and trust through a different means.
• a super tight backwards plan for producing the first version of the thing I've decided to make, including a list of the absolute essentials...and the parts that I'm willing to cut as I fall behind because I inevitably will.
• at least one place that people are already looking (aka a watering hole of some kind) where I can post those updates too, for people who don't already follow me.
• an email signup so people can opt into getting those updates as I post them, and a notification/discount when it's done
this all borrows heavily from that 24 hour challenge that Amy did for JFS, and I've definitely seen work for others.
the real key is front loading decisions and actions that save you time later, simplify steps, or even remove steps entirely.