Shipping 10x faster, part II

jasonleow  •  3 Mar 2024   •    
Screenshot

Continuing the thinking from the post yesterday about shipping 10x faster, I asked the question on Twitter to crowdsource more tips and hacks:

  • Some indication of product-market fit. Because why build it if you don’t know if there’s potential for success? This could be say, a validated product in a saturated market. Or there’s paying customers. Some form of kw/customer research is helpful. Been wanting to not mess around with building something unique and instead just build something in a saturated market and validated product… simpler.
  • Preferred/familiar tech stack. A starter app or boilerplate that gets you 90% of the way.
  • Preset workflows/processes for the whole process.
  • An undisturbed block of time. I see this as timeboxing the effort to a predetermined window of time, say 1-2 weeks, and organising life and chores beforehand to have that focus.
  • Ruthlessly scoping a MVP small enough. A strong conviction to prioritising the single feature that truly matters to customers.
  • Commitment to launch deadline, and a shipping pace/schedule, and the smart organisation of time, effort and other life commitments around it.
  • A marketing stack would be helpful too. Places where you know you can launch to, or a community where customers hang out, or an existing audience.
  • Basic marketing materials, swipe files and established workflows to make open graph images, logos, web graphics, etc. Now I use DALLE to generate logos and web graphics, svgrepo for SVG icons, and Sketch to design anything else. What I lack is a good copywriting swipe file to get good conversion copy up fast. This usually takes longer than I realise! I think copywriting frameworks like Pain-Agitate-Solution is a good tool too.
  • Outsource some of the help. A virtual assistant to do the admin and time-consuming onerous stuff, or a customer support assistant.

What else?

Comments

Repurpose what you’ve already done.

I’ve always felt you should lean into Lifelog. The main reason I write here is because of the small cohort of rather nice people. Which seems like a terrible idea for a viral app, but what if you leaned into small cohorts at scale? I’m thinking forum software with forced user limits and tools to encourage small user bases to write—like streak tracking and word minimums.

Winkletter  •  3 Mar 2024, 5:45 am

@Winkletter Agree. Repurpose my old code will be key. I’ve always copied functions from different projects to one another, like Lifelog to plugins, or vice versa.

Great idea re: small cohorts at scale. Sounds like #ship30for30 actually! They have a proven model. But building a large community and giving coaching and all… feels like something I’m not too keen on. I feel I got to find a different approach. I often look to Buster Benson’s 750words as a role model of how Lifelog can be like.

Not sure if you joined by then, but I once tried leaning into Lifelog. Stopped building features and tried to grow in for 2 years. Failed. Now I’m just building it out to be the tool I/we need and enjoy writing on.

jasonleow  •  5 Mar 2024, 2:36 am

Discover more

Sourced from other writers across Lifelog

Ooops we couldn't find any related post...