Startup Lessons Learned

OCTOBER 7, 2016

I’ve always been intrigued by the concepts of design thinking and customer empathy and how those concepts might intersect with local government. The first was one of our teams that was evaluating the need for an online business license application program. The team used Lean Startup principles to evaluate the issue. Absolutely.

Government 165

Government Lean Startup San Francisco 165

Steve Blank

NOVEMBER 16, 2009

I was in New York last week with my class at Columbia University and several events made me realize that the Customer Development model needs to better describe its fit with web-based businesses. What metrics do we use to see if we learned enough in Customer Discovery ?

Customer Development 224

Customer Development Web Developer Customer 224

The Next Web

SEPTEMBER 15, 2013

Apigee , Mashery , 3Scale , Layer7 , etc) get acquired and/or receive large rounds of funding, we are also seeing an uptick in new players, new tools and services, new publications, and even a series of API-focused conferences. The key to a successful API program is to know your audience. The reality: “API as a tactic”.

API 135

API Audience Dividend Programming 135

Startup Lessons Learned

APRIL 25, 2011

The number of Lean Startup meetup groups has crossed 100, spreading out from traditional startup hubs like San Francisco and New York to a wide variety of places. No BS, no vanity metrics, no launches, no PR. Design + Lean Startup = Lean UX. This year, the word pivot has become over-hyped ( even on TechCrunch ).

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

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. Unfortunately, its easy to lose track of positioning effects when optimizing for a single metric.

Metrics 88

Metrics San Francisco Lean Viral 88

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. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much? for Harvard Business Revie.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Steve Blank

JULY 13, 2021

When Harvard started the MBA program there were no graduate-level business textbooks. While MBA programs proliferated during the first half of the 20th century, they focused on teaching management of existing companies. By 1991 there were 57 undergraduate and 22 MBA programs. There were no classes on how to start a business.

Lean 435

Lean Agile Business Model Business Plan 435

Startup Lessons Learned

APRIL 4, 2010

To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much? Our mystery keynote is now revealed and I couldnt be more excited.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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

YoungUpstarts

JANUARY 21, 2016

There are three crucial keys: 1) Be ready to demonstrate the relevance of the items being measured to the well-being of the business, 2) Ensure that those who are being measured can create positive changes in the metrics, and 3) Make sure rewards and consequences associated with desired performance levels are fair. There will be fear.

Employee 100

Employee Customer Leadership Metrics 100

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

Hearpreneur

DECEMBER 29, 2021

Thanks to Wes Marlan, Lighthouse Web Design, Inc ! #2- We are successfully dominating the core markets within the Dubai Real Estate arena and our recent growth into New York, Los Angeles, and Miami is proving to be extremely successful. One of the key metrics of success in Real Estate is having a large market share.

Entrepreneur 138

Entrepreneur Social Media Employee Los Angeles 138

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. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

SoCal CTO

JUNE 9, 2010

Berkeley Boalt Law School and runs their entrepreneurship program. Bending over: How to sell to large companies - A Smart Bear: Startups and Marketing for Geeks , May 24, 2010 This is a guest post by Steve Hanov , who blogs about programming and startups. The New York Times has a story about it in today's business section.

Fractional CTO 248

Fractional CTO Startup Venture Capital Cofounder 248

Startup Lessons Learned

JUNE 2, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

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

AUGUST 26, 2009

And, as one entrepreneur put it to me, "we understood that a big part of our responsibility in the program was to make sure the mentors have a good experience, by taking their advice to heart and giving them a feeling of being part of our evolution as a company." TechStars encourages them to go wherever opportunities take them.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. Some designers also hate optimizing (which is why the “41 shades of blue&# test is so famous – a famous designer claims to have quit over it ). And they’re not the only ones.

San Francisco 154

San Francisco Lean Metrics Design 154

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

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. 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. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

OCTOBER 4, 2008

He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). Im one of those people whos been programming since they can remember. I got my start programming on an old IBM XT; it was thanks to MUDs that I first discovered the internet. November 25, 2009 9:54 AM Danny Wong said.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

AUGUST 2, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

FEBRUARY 28, 2009

I used to think that investments in metrics were a form of waste. Customers dont care if you have good metrics, only if you have a good product. The only reason we learned the art of metrics-based decision making at IMVU was out of necessity. that justify decisions already made. I think it was $350 the next, and so on.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

MARCH 29, 2010

Lessons Learned by Eric Ries Monday, March 29, 2010 New conference website, speakers, agenda The Startup Lessons Learned Conference on April 23 is fast approaching. We have a brand new website up at [link]. Weve got a new scholarship program up and running. Is design important to lean startups?

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

SEPTEMBER 15, 2008

I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much? for Harvard Business Revie. Startup Lessons Learned - the Conference (April 23. Amazon PostRank

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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. I assumed he was there to refute my critique of extreme programming, but nothing could be further from the truth. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

NOVEMBER 12, 2009

Lessons Learned by Eric Ries Thursday, November 12, 2009 New York: three straight days of Lean Startup (two of which are free) Greetings from Europe, where Im just wrapping up an incredible (and exhausting) speaking tour. Expo in New York, theres good news. For those who want to come see me at Web 2.0

New York 94

New York Lean San Francisco Continuous Deployment 94

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much? Anyway, thanks Stevey for your thoughtful post. Learning is better than optimization (the local ma.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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. Departments were built and were even metrics-driven. But there was no feedback loop to help the company find the right metrics to focus on.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 12, 2010

Some of the most active: SF , New York , DC , Chicago - but there are many more listed here. Some of the most active: SF , New York , DC , Chicago - but there are many more listed here. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much? for Harvard Business Revie.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JUNE 8, 2009

That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Yet even among those who have access to good actionable metrics, I’ve noticed a phenomenon that prevents taking maximum advantage of data. Use pilot programs. What’s happening?

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

SEPTEMBER 2, 2008

Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JANUARY 12, 2009

Lessons Learned by Eric Ries Monday, January 12, 2009 Why PHP won When I first learned to program on the web, Perl + CGI was the dominant platform. Youll notice a pattern: most of the key features that enabled PHPs success are considered among its defects by experts in language design. In most cases, simple changes are simple to make.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

FEBRUARY 8, 2010

Lessons Learned by Eric Ries Monday, February 8, 2010 Beware of Vanity Metrics (for Harvard Business Review) The next article in my series on entrepreneurship for Harvard Business Review is live today. Once again, we revisit the topic of Actionable metrics and their nemesis: Vanity metrics. Remember "metrics are people, too."

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121