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

ctotodevelopers.blogspot.com

JULY 11, 2012

Social, Agile, and Transformation. I cover several topics including agile software development, software startups, web 2.0, Strategic Agile Thinking: Balancing Value, Innovation and Research. 2) The agile "happy place". Agile teams sprint when value is known, implementation is low risk. and business transformation.

Agile 40

Agile Architecture Offshore Software Developers 40

YoungUpstarts

APRIL 21, 2013

Creators of new products in environments of extreme uncertainty, startups face enormous risks. Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. There are principally three engines of growth in any startup.

Lean 193

Lean Technical Review North America Startup 193

Both Sides of the Table

NOVEMBER 27, 2011

functional workgroups vs. product workgroups). 8:17 How did you decide to go with either shrinkwrap or web only product? 42:20 Did agile development influence you? 46:50 Engines of Growth. 48:30 Vanity metrics. 52:00 Actionable metrics. when is the right time to go big with PR? Eric is so damn good.

Silicon Valley 301

Silicon Valley Lean Social Media PR 301

ReadWriteStart

APRIL 8, 2023

In contrast, it left several e-trends: augmented reality, zero coding, the marketplace boom, and product subscriptions are just a few of them. With the help of voice assistants, such as Siri and Alexa, you can purchase the product just by saying it while running errands. We will deliver product x every three months with free shipping.”

eCommerce 185

eCommerce Technical Review Software Review Analytics 185

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. I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

MARCH 6, 2013

Vinod Khosla Founder Dave McClure Founding Partner Eric Ries Author Steve Blank Serial Entrepreneur & Professor Todd Park CTO Travis Kalanick CEO & Co-Founder Joe Zadeh Director of Product Sam Shank Co-Founder & CEO NEW! Seth Sternberg Co-Founder & CEO Scott Chacon CIO Kevin Hale Senior Product Manager NEW!

Lean 165

Lean Cofounder Startup Software Engineering 165

Startup Lessons Learned

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. This workshop brings together leading thinkers from Lean Production and Lean software. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

ConversionXL

FEBRUARY 28, 2017

Think you’re sitting on the next big idea for a product or a product feature? So, how can you validate the ideas sitting in your startup notebook or your product feature backlog without wasting resources? So, if you put the time and money into creating the product, will it actually sell or will it fall flat?

Product 48

Product Audience Stock Conversion 48

YoungUpstarts

DECEMBER 14, 2017

by Amanda Setili, author of “ Fearless Growth: The New Rules to Stay Competitive, Foster Innovation, and Dominate Your Markets “ Polarization is a common problem for companies trying to make smart and agile strategic decisions. They know how to reach the consumers who are in the market for their products. and Malaysia.

Agile 113

Agile Malaysia Technical Review Metrics 113

Steve Blank

MARCH 3, 2015

During the Cold War with the Soviet Union, science and engineering at both Stanford and U.C. Starting in the 1950’s, Stanford’s engineering department became “outward facing” and developed a culture of spinouts and active faculty support and participation in the first wave of Silicon Valley startups. The Business Plan is Dead.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

OnlyOnce

AUGUST 31, 2017

Over the years, I’ve written a lot about the Agile methodology on this blog. For those of you who are regular readers, you may remember a post I wrote about our Agile Everywhere initiative — where all Return Path teams were tasked with implementing agile practices. weren’t at all familiar with agile practices.

Agile 54

Agile Metrics Restful Engineer 54

Both Sides of the Table

MAY 27, 2013

In this period (less than 2 years) he has brought on incredibly talented senior execs is sales, marketing, product management, client services, finance, vp engineering and more. You may know how much to pay in cash or equity for your new VP Engineering. The Agile Board. In his spare time he raised nearly $30 million.

Advisory Board 365

Advisory Board CTO Hire Fractional CTO Los Angeles 365

TechEmpower

OCTOBER 9, 2023

Artificial Intelligence (AI), and particularly Large Language Models (LLMs), have significantly transformed the search engine as we’ve known it. Enhancing Front-End Product Search We also developed a front-end search tool that revolutionized the way users search for products. Strive for a balanced outcome.

Artificial Inteligence 346

Artificial Inteligence Generative AI Search Database 346

Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Up and Running

NOVEMBER 29, 2017

He says the “create” approach means working on your project until you’re certain it’s completely polished and looks like the top products in the market, and your strategies and sales tools are all top-notch before you ever think of launching. Two of my startups failed because I was so busy “creating” or perfecting the products.

Acquisition 93

Acquisition Startup Engineer Metrics 93

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

JUNE 26, 2015

In the last five years “ Lean Startup ” methodologies have enabled entrepreneurs to efficiently build a startup by searching for product/market fit rather than blindly trying to execute. Here the company executes a known business model (known customers, product features, competitors, pricing, distribution channel, supply chain, etc.)

Lean 120

Lean Management Business Model Incubator 120

Steve Blank

JULY 13, 2021

Founders of startups (and new ventures inside existing companies) are searching for product/market fit and a repeatable and scalable business model. Consequently the methodologies for launching products in startups were different than for existing companies. Neither cases nor business plans replicate the actual startup experience.

Lean 433

Lean Agile Business Model Business Plan 433

Startup Lessons Learned

JUNE 2, 2010

Five Whys has its origins in the Toyota Production System. And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Expo SF (May.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

View from Seed

FEBRUARY 27, 2019

As the former Head of Product at Blue Apron where I also built and led our Analytics & Data Science team (I know enough SQL to be dangerous), I have an intuitive sense for the “when” and “what” of this role. Analytics is about designing, reporting, and leveraging operating metrics to aid strategic and functional decision-making.

Analytics 149

Analytics Hiring SQL Forecast 149

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. The biggest source of waste in new product development is building something that nobody wants.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 7, 2008

Thats the conclusion Ive come to after watching tons of online products fail for a complete lack of customers. Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Nothing made any difference.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. They might do anything !

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. Every startup has a chance to change the world, by bringing not just a new product, but an entirely new institution into existence. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JUNE 17, 2010

I was an engineer on the engineering team. The art team would often be involved in the specification phase of a new feature, since they were responsible for the look-and-feel of the product. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

ConversionXL

MAY 22, 2017

How their product leaders and CMOs embrace the change adjusting product/marketing strategies based on new technologies. In AI implications on Marketing and Analytics , I placed my considerations explaining how and why Artificial Intelligence (AI) will shape the next generation of Analytics and Marketing SaaS products.

Customer 92

Customer Marketing Artificial Inteligence Clickthrough 92

Women Entrepreneurs Can

MARCH 2, 2023

Through this refine and test approach, entrepreneurs minimize wasting resources – like time and money – and continue to improve their products and services while increasing efficiencies and decreasing cycle times. We demonstrate courage when we align our efforts and activities with those metrics despite our personal feelings and desires.

Lean 98

Lean South Korea Metrics Framework 98

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. He wrote it in 2000, and as far as I know has never updated it. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Everyone was in the flow; the team was hyper-productive. In many cases, they did the impossible, building a new product faster, cheaper, and better than anyone could have predicted.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

andrewchenblog.com

MARCH 10, 2010

The interesting part is when you get a couple months into your product cycle. Most engineers know that in this kind of a case, the best practice is NOT to rewrite your code, but rather refactor it continually and take down the so-called “Technical debt&# so that it’s always under control.

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

APRIL 14, 2009

This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. Every board meeting, the metrics of success change. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. And what of the product development team?

Customer 167

Customer San Francisco Lean Hockey Stick 167