Cameron Armstrong on Warpcast

Content pfp

0 reply

0 recast

0 reaction

Cameron Armstrong pfp

Cameron Armstrong

Since it’s the topic du jour on the purple app… What’s the right balance between “ship and iterate” and “build something great first”?

17 replies

5 recasts

24 reactions

Cameron Armstrong pfp

Cameron Armstrong

“Ship then iterate” is necessary, but not sufficient. It’s a tactical device to maximize the rate of change of learning. The entire point is to get good enough, fast enough, and in small enough chunks that by the time you actually do something important for users you’re capable of doing a good job…

2 replies

1 recast

7 reactions

Jojo pfp

i thought you would ask “goku or vegeta” 😡😡

1 reply

0 recast

2 reactions

Sid pfp

https://warpcast.com/woj.eth/0x31b576ae

1 reply

0 recast

1 reaction

links 🏴 pfp

The balance is different for every context. The key is that you can’t build something great without feedback (unless you’re a genius or lucky, and even then it can’t last)

1 reply

0 recast

1 reaction

Ese 🌳 pfp

A gym approach is the way to go imo, ship as much as you can without getting burned, the worse thing you can do when training is injuring yourself, because then even if you have the will to train you’re not going to be able to do so, so first getting the max amount of info about technical stuff, so you can train well

1 reply

0 recast

1 reaction

Special Agent Royo pfp

Special Agent Royo

Isn't entirely dependent on competition? different verticals can handle different levels of quality... In entertainment you can't ship embarrassing stuff... Even good won't cut it...

1 reply

0 recast

0 reaction

Jason Goldberg Ⓜ️ 💜 pfp

Jason Goldberg Ⓜ️ 💜

0 reply

0 recast

1 reaction

Lauren McDonagh-Pereira pfp

Lauren McDonagh-Pereira

@lampphotography

For this crowd? Ship and iterate. For normies that aren't as obsessed with this tech? Build something great first. 10 $DEGEN

1 reply

0 recast

1 reaction

richie is foraging pfp

richie is foraging

it's a false dichotomy. we should build something great within the scope of our conviction about what actually solves the problem. but it's easy to delude ourselves into thinking something is needed vs just cool. build something small, but great. ship it, then iterate to get to the next threshold of conviction.

0 reply

0 recast

1 reaction

Shashank pfp

for all startups it's almost always better to ship fast, be scrappy and iterate. some later stage or large tech companies however do tend to have a certain quality bar/ brand value at stake for shipping new products and it's a calculated tradeoff. same for certain deep tech/ hardware startups

0 reply

0 recast

1 reaction

Gabriel Ayuso pfp

@gabrielayuso.eth

The ability to ship and iterate is one of the main things that separates startups from big tech. It's best to get feedback from real users than research and focus groups. Hold of any big launch announcement until your product is good enough (not perfect). Then keep iterating with a larger cohort, etc.

1 reply

0 recast

1 reaction

Les Greys pfp

Balance hard. I just curious. Imbalance emerges, I remind self be nice to self, balance emerges, I go curious, imbalance emerges, I remind self be nice to self, balance emerges, I go.

0 reply

0 recast

1 reaction

meguce pfp

build-->feedback-->update-->feedback-->ship-->feedback-->update

0 reply

0 recast

1 reaction

Fran pfp

Ship QUALITY always. Ship features only as needed. You want feedback on your product not feedback on obvious bugs.

0 reply

0 recast

1 reaction

Majid pfp

We do not lead the team, that means there is no way for it, only the team members can speed up the team's movement with their efforts and responsibility.

0 reply

0 recast

1 reaction

ash pfp

You can show founders examples of what Airbnb or Twitter v1 looked like (terrible!) and they’d still want to build the perfect product before shipping. Building is fun. Shipping, getting feedback and iterating, not so much fun.

0 reply

0 recast

1 reaction

Cashcore pfp

I guess the principle in software engineering in general also applies here. Try to find and implement an MVP (minimum viable product) first. That is, a prototype that can show the value proposition of the product. Then iterate based on the feedback on that MVP. Thanks for the intriguing question! Here is 1 $DEGEN

0 reply

0 recast

0 reaction