Talking to your customers: a disruptive Agile framework
lucasfcosta.com
Talking to your customers: a disruptive Agile framework
1–10 of 59 posts
Re: Talking to your customers: a disruptive Agile framework
#2Pro tip: If you're planning to build a product, you might need to find your customers first. Then follow the TTYC process.
Re: Talking to your customers: a disruptive Agile framework
#3Extending this further. Before building a product, talk to prospects and understand the problem better.
Re: Talking to your customers: a disruptive Agile framework
#4Yes but talking is enifficient and a waste of my velocity. I'd rather ship it (tm) and analyze the conversion funnels by cohort with A/B.
Cause that's what growth hacking gurus tell me on YouTube .
/s (hopefully that was obvious to all)
Re: Talking to your customers: a disruptive Agile framework
#5Pro tip: If you're planning to build a product, you might need to find your customers first. Then follow the TTYC process.
It's actually the other way around I found but yeah important to know where the customers are first and how to reach them.
If you want to find a customer, you need to have a product in my experience. Very few outside of US are willing to risk take.
Re: Talking to your customers: a disruptive Agile framework
#6Yes but talking is enifficient and a waste of my velocity. I'd rather ship it (tm) and analyze the conversion funnels by cohort with A/B. Cause that's what growth hacking gurus tell me on YouTube . /s (hopefully that was obvious to all)
The narrative minus the irony sure sounds a lot like what one of the adtech giants was doing. Might have been the cause of them having lost circa 50% of market cap when the chicken came to roost.
Re: Talking to your customers: a disruptive Agile framework
#7Pro tip: If you're planning to build a product, you might need to find your customers first. Then follow the TTYC process.
It's actually the other way around I found but yeah important to know where the customers are first and how to reach them. If you want to find a customer, you need to have a product in my experience. Very few outside of US are willing to risk take.
They likely don't mean 'customer' in the sense of a paying one, but a person with a need you can fulfil and resources to compensate you with.
It's sort of potential, not yet actualized aspect of a 'customer' as a piece of a 'person', that would become 'real' in a presence of your product.
Re: Talking to your customers: a disruptive Agile framework
#8I believe this approach will lead you to very incremental solutions.
It lowers the cost of failure (downside), but also the potential impact of success (upside). This approach determines your mindset as a product designer and destroys your potential product/business upside upfront. Most users get pitched "understandable ideas" because builders think they have to prove market fit before building product depth.
The most successful companies don't discover markets, they create them. Most visionaries forge the macro (10x) jump and then ask customers for the micro improvements. The meaningful, big-leap innovations are often not obvious from the start: If you're creating something that will be a great company 10 years from now, most people will probably not get it at first.
Re: Talking to your customers: a disruptive Agile framework
#9Somehow the customer will be replaced with a customer proxy who pretends to know what the customer wants.
Re: Talking to your customers: a disruptive Agile framework
#10Somehow the customer will be replaced with a customer proxy who pretends to know what the customer wants.
I take the requirements from the customers and I bring them to the engineers! What the hell is wrong with you people?!