Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. It has to be found and managed.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

OCTOBER 5, 2008

Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. The product manager was clearly struggling to get results from the rest of the team. Frustration is mounting.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. This engineering manager is a smart guy, and very experienced.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." a roadmap for how to get to Product/Market Fit."

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 20, 2009

Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team. Give the dev team your very first sketches and let them get started. That frees up even more development resources, and so on.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 13, 2009

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.

Product Development 153

Product Development Developer San Francisco Product 153

OnlyOnce

MARCH 14, 2011

In Part Two, I’ll talk about some of the practices we’re using in our product management and development teams. We all knew if the feature or function that the client was asking for was within the realm of the possible. • We were very, very focused on creating customers and revenue —We were a startup.

Software Review 67

Software Review Development Team Review Later Stage Technical Review 67

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part one Ive written before about some of the advantages startups have when they are very small, like the benefits of having a pathetically small number of customers. Talking to potential customers and competitors customers.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JUNE 8, 2009

You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. Because of the extreme unknowns inherent in startup situations, we are all blind – to the realities of what customers what, market dynamics, and competitive threats. Imagine you are crossing the street.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

ConversionXL

JUNE 13, 2017

Traditionally associated with development and product management, agile is a lightweight and, well, agile framework for software development and bringing features and products to market. According to the Scrum Guide , the Product Owner is the sole person responsible for managing the Product Backlog.

SCRUM 112

SCRUM Agile Marketing Development Team Review 112

Startup Lessons Learned

OCTOBER 16, 2013

Palantir is a deep technical play and we had a lot of code to write just to fill out the product vision that we had already validated with potential customers; it took us two straight years of development to go from early prototypes to software that could be used in production. It wasn’t always this way.

Lean 167

Lean Startup Software Engineering Agile 167

Both Sides of the Table

APRIL 27, 2010

My original post was directed at hiring managers. My view still stands – for many hiring managers a large factor in looking through resumes of somebody who is 30+ and has never worked somewhere for more than 18 months will be the job hopping element. I learned how to better run a product management process.

Venture Capital 285

Venture Capital Hiring Software Review Stock Options 285

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

No wait, I forgot, actually the question is: What happens when employee #2 makes off with your code and roadmap and marketing data and customer list, moves to Bolivia, and starts selling your stuff world-wide at one-tenth the price? The good news: There are good answers to these questions! Now Adriana has an epiphany?:

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Steve Blank

JANUARY 21, 2010

Management in the Transition. 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.

Agile 120

Agile Development Team Review Leadership Merger 120

Startup Lessons Learned

NOVEMBER 29, 2008

Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. Communication.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. The last thing you need is a manager telling you how to do your job. But there *are* bad managers, and sometimes they cant be fixed.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94