Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. Agile software development. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JANUARY 18, 2011

(One of the common questions I hear is how to reconcile design and user experience (UX) methods with the Lean Startup. To answer, I asked one of my favorite designers to write a case study illustrating the way they work, taking us step-by-step through a real life redesign. This is something of an IMVU reunion. This is simply not true.

Design 167

Design Lean Metrics Silicon Valley 167

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. Combining agile development with customer developm. And when did there get to be 3000 of you?

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Steve Blank

JULY 13, 2021

With Lean LaunchPad, we were going to toss teaching the business plan aside and try to teach students a completely new, hands-on approach to starting companies – one which combines customer development, agile development, business models and pivots. Lean-driven (hypothesis testing/business model/customer development/agile engineering).

Lean 433

Lean Agile Business Model Business Plan 433

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. You can learn more about the event here. Its hosted by Kontagent and sponsored by Intel.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

APRIL 25, 2011

It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. Second, we’re presenting something unusual for an entrepreneurship conference: the CEO of a Fortune 1000 company. No BS, no vanity metrics, no launches, no PR.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

ReadWriteStart

APRIL 5, 2021

Similarly, many new businesses emerging in the modern world begin with a remote work model; it makes financial sense for young, cash-strapped businesses to save money and remain agile. Instead, its better to design your workflows and operational model from the ground up with remote work in mind. . Heading Back to the Office.

Startup 120

Startup Security Operations Agile 120

crowdSPRING Blog

MAY 1, 2015

We just love sharing articles about fonts, logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, economics and other interesting stuff! Why Revenue Isn’t the Most Important Financial Metric for Startups – buff.ly/1DhyQo4. Designing Settings — Medium bit.ly/1zppAUn.

Small Business 48

Small Business Design Social Media Startup 48

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

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. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Hearpreneur

DECEMBER 29, 2021

Thanks to Wes Marlan, Lighthouse Web Design, Inc ! #2- The year 2021 has presented a lot of business opportunities for us and we have successfully established our workflow and protocols. It's important to keep business agile. One of the key metrics of success in Real Estate is having a large market share. 2- Scaling up.

Entrepreneur 138

Entrepreneur Social Media Employee Los Angeles 138

TechEmpower

OCTOBER 9, 2023

This presents businesses with an opportunity to enhance their search functionalities for both internal and external users. Here's a suggested approach: Ground Truth Creation: Design a test dataset with established answers or recognized documents to serve as a reference point.

Artificial Inteligence 346

Artificial Inteligence Generative AI Search Database 346

Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Without further ado, the video: Slides are below: Minimum Viable Product View more presentations from Eric Ries. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

MARCH 3, 2015

See the presentation here.). The disadvantage is that its methodology was based on the old waterfall model of product development and not the agile and lean methods that startups use today. It taught lean theory ( business model design , customer development and agile engineering) and practice. Today the U.C.

Business Plan 120

Business Plan Silicon Valley Saudi Arabia Lean 120

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# The same process works in Interaction Design. This basic pattern is useful in all aspects of product development. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

OCTOBER 16, 2013

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. We''ve had to design and implement training programs to help on-board people to our culture and technology.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Steve Blank was very impressed by this presentation and mentioned it when he spoke at TiE on Wed-Sep-19.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Hearpreneur

SEPTEMBER 15, 2021

The fashion industry is always ripe for disruption since every consumer has their taste and style, and designers work round the clock to develop unique trends. Different designers produce garments based on body shape, size, skin color, season, and many other factors. Thanks to Harriet Chan, CocoFinder ! #6- 12- Manufacturing.

Artificial Inteligence 105

Artificial Inteligence Entrepreneur Technical Review Security 105

The Next Web

SEPTEMBER 8, 2013

I also want to explain that it is possible to have a truly agile work environment based on small, autonomous teams. Further feature development does not slow down the development process but as extra information is derived from live metrics, a/b testing becomes possible and the whole game needs to be operated. Being agile.

Software Review 146

Software Review Agile Analytics SCRUM 146

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. Chris and I had the opportunity to present on our approach this past spring at the MySQL Conference. Labels: agile , continuous deployment 1 comments: timothyfitz said.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. Product development deals in designs, which are fundamentally intangible.

Product Development 153

Product Development Developer San Francisco Product 153

Occam's Razor

APRIL 23, 2012

While there is a great deal of appreciation for the power of metrics/data, I've come to realize that Sr. Leaders don't quite appreciate the deep, and often corrosive, consequences of choosing metric x over metric y as a key performance indicator (KPI). It is a standard metric. Don't believe me?

Metrics 152

Metrics Analytics Search Channel 152

Startup Lessons Learned

JANUARY 30, 2009

Insist on high levels of usability, UI design, and polish. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. Departments were built and were even metrics-driven. Focus on quality.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Start-ups supposedly dont have time for detailed processes and procedures. Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

OCTOBER 7, 2016

series that also includes the Future of Work , the Future of Corporate Agility, Skill-Sharing, and more in the weeks leading up to Lean Startup Week. I’ve always been intrigued by the concepts of design thinking and customer empathy and how those concepts might intersect with local government. This interview is part of a “Future of….”

Government 165

Government Lean Startup San Francisco 165

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. A/B testing is set-based design. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Steve Blank

NOVEMBER 5, 2009

This post describes how companies using the Customer Development model can increase their credibility, valuation and probability of getting a first round of funding by presenting their results in a “Lesson Learned&# venture pitch. Tons of advice is available on how to pitch , present and market your company. How many are there?

Customer Development 262

Customer Development Developer Customer Silicon Valley 262

andrewchenblog.com

MARCH 10, 2010

However, there’s the other side of the coin, which is the product design. After you’ve added a ton of new features and stuck them all on the homepage, you create Product Design debt. Arguably, MySpace is a company that never paid down their product design debt, and their traffic has been impacted as a result.

Technical Review 47

Technical Review Design Las Vegas Product 47

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. I used to think that investments in metrics were a form of waste. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

SEPTEMBER 15, 2008

The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. No vanity metrics should be looked at. And it’s really hard.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

AUGUST 26, 2009

If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries. Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113