This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customerdevelopment? But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." Many of us are not accustomed to thinking about markets or customers in a disciplined way.
Take the example of a design team prepping mock-ups for their developmentteam. Give the devteam your very first sketches and let them get started. And over time, the developmentteam may be able to start anticipating your needs. That frees up even more development resources, and so on.
One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. As we''ve grown, we now have a great qualitative research team dedicated helping us stay close.
I met one recently that is working on a really innovative product, and the stories I heard from their developmentteam made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. one more thought, where were the code reviews? October 6, 2008 12:17 AM r& said.
To get to this Transition stage, the company needed passionate visionaries who can articulate a compelling vision, agile enough to learn and discover in real time, resilient enough to deal with countless failures, and responsive enough to capitalize on what they learned in order to secure early customers. What’s Next.
Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product developmentteam that can turn an early product into a Whole Product. The Entrepreneur’s Guide to CustomerDevelopment ► June (3) What is a startup?
Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product developmentteam of a startup (large or small) is a service organization. I am basically a one-man shop.
You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. So the product developmentteam was busy creating lots of split-tests for lots of hypotheses. Each day, the analytics team would share a report with them that had the details of how each test was doing.
The idea of leverage is simple: for every ounce of effort your product developmentteam puts into your product, find ways to magnify that effort by getting many other people to invest along with you. For example, I recently created a customer validation exercise around the Lean Startup Workshop. Its a key lean startup concept.
The technical interview is at the heart of these challenges when building a product developmentteam, and so I thought it deserved an entire post on its own. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation.
As I evolved my thinking, I started to frame the problem this way: How can we devise a product development process that allows the business leaders to take responsibility for the outcome by making conscious trade-offs? When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer.
Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content