Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. That’s right.

San Francisco 154

San Francisco Lean Metrics Design 154

Steve Blank

SEPTEMBER 24, 2009

I’ve watched new CEO’s brought into large existing consumer products companies to turn around a failing strategy. Their new strategy included a complete revamp and simplification of the product line. Also, there are a variety of strategies for “easing out&# gracefully such as finding an outsourcing vendor or new partner.

Customer 201

Customer Silicon Valley RSS California 201

Startup Lessons Learned

OCTOBER 28, 2008

We pitch to potential partners, vendors, publishers, conferences, employees, and even lawyers. Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. 2comments: King of the Herd said.

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

SEPTEMBER 12, 2008

You might get a bunch of inbound emails from other press and partners, and all of these things can contribute to a feeling that you’re on your way to getting tons of traffic. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, It strokes your ego.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

AUGUST 26, 2009

As a result, the companies get a lot of exposure to VCs, investors, and partners in larger, more traditional startup hubs. 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.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. Were doomed! Or the press. Or to our team.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

steveblank.com

JULY 8, 2011

AgileZen – project management visually see and interact with your work Kanbanery – Simple online team or personal kanban board LeanKit Kanban – Great for visualizing work of product development Kanban Pad – “Nice and lean” and free online Kanban tool Banana Scrum – A tool simple as Scrum itself.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Startup Lessons Learned

MARCH 13, 2009

Establish credibility with potential partners. In some businesses, especially in certain industries like traditional enterprise software, you simply cannot bring a new product to market on your own. You need to combine your product with others, and this requires partners like OEMs or system integrators.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

JUNE 8, 2009

I got a powerful taste of datablindness recently, as I’ve started to work with various large companies as partners in setting up events, speeches, and other products to sell around the Lean Startup concept. So the product development team was busy creating lots of split-tests for lots of hypotheses.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

SoCal CTO

DECEMBER 1, 2010

aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. When It’s Darkest Men See the Stars - Steve Blank , November 24, 2010 When It’s Darkest Men See the Stars. but: Something is Still Missing.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

DECEMBER 7, 2008

This is one of the bedrock practices of any lean startup , and so its a common piece of advice I give out. At the end of the day, the product development team of a startup (large or small) is a service organization. Labels: five whys root cause analysis , product development 8comments: William Pietri said.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

DECEMBER 14, 2009

A great product enables customers, developers, partners, and even competitors to exchange their unique currencies in combinations that lead to financial success for the company that organizes them. One clue that you don’t have product/market fit – you’re trying to evaluate your business to see if you have it.

Customer 156

Customer San Francisco Viral Lean 156

Up and Running

MAY 23, 2016

Step 1: Start with a lean plan. It’s the fastest way to get your idea onto paper, and it’s the very first step in the lean planning process, which is much easier and more iterative than traditional business planning methods. List key partners and resources you will need, and then list your core team as well as their roles.

Software Review 74

Software Review Software Delaware Forecast 74

bizthoughts.mikelee.org

MARCH 8, 2012

link] # 4 hours ago Going #lean and testing with imagemaps, cuz concepts are cheap and code is expensive. # iPhone & iPad #distribution #ormaybemarketing # 19 hours ago @davemcclure Idea 2: Partner with someone with an established distribution channel, ie. 2 hours ago What wise & mature words.

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

mashable.com

JUNE 11, 2013

In fact, recent research shows that 75% of startups fail (based on a study of 2,000 startups that received VC funding from 2004 to 2010). At first, we tend to see the business and our partners at their best, full of promise, and cant conceive that they will ever be anything but their best. Some startups are destined for failure. "A

Cofounder 111

Cofounder Technical Review Startup Software Review 111

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Team Configuration 500 Startups Guerilla Marketing Organizations Entrepreneurship Startup Founders & Entrepreneurs Startups Startup Incubators and Seed Programs Seedcamp Y Combinator TechStars Lean Startups What is the perfect startup team? Lakshman Prasad • Nov 16, 2010.

Technical Review 51

Technical Review Startup CTO Hire Cofounder 51

Startup Lessons Learned

SEPTEMBER 11, 2009

Suffice to say that our partners, vendors, and most importantly regular mainstream customers all found the idea disturbing. Eric, I am not only a member of the IMVU community, but I am your business partner. I was especially moved by this: "I am not only a member of the IMVU community, but I am your business partner.

Community 158

Community Management Lean Software Review 158

techcocktail.com

OCTOBER 23, 2010

But while you are small and lean, take advantage of everyone skills; if someone on your team is a great writer, have them take charge of your press releases and marketing content. be the manager and product developer). Talent: Each team member needs to have talent – they all need to own their abilities and focus on their assets.

San Francisco 44

San Francisco Startup PHP San Diego 44

www.vccafe.com

MARCH 11, 2013

Lean Methodology Sources. Steve Blank on Lean Customer Development. Part 3- Lean Cust. Steve Blank’s Lean Startup Resources. Lean Startup Circle â?? Great for visualizing work of product development. Lean project management. agile product management. Codeacademy. SW Courses.

Software Review 53

Software Review Technical Review Startup 53

betashop.com

OCTOBER 8, 2012

On October 27, 2010 I wrote a blog post about the “ 57 Things I Learned Founding 3 Tech Companies.”. This past week while I was in Tokyo for meetings with potential partners for Fab, I was invited to participate in a panel discussion on startups. Fab.com Fab Feed Bradfords Blog. The discussion quickly turned to those 57 things.

Technical Review 108

Technical Review Technology Software Review Valuation 108

Startup Lessons Learned

OCTOBER 23, 2009

Mainstream customers don’t have enough motivation to buy an early product, and so building in response to their feedback is futile. The lean startup methodology is based on enlisting customers as allies, which requires honesty and integrity. The following was written an actual lean startup practitioner.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

JANUARY 1, 2009

I see that as a great way for my product to grow, but while Ive partnered with companies in my consulting business, its not something Im as familiar with now that Im on the product side. I question what numbers I would need to be considered respectable and/or worth a potential partners time. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

viniciusvacanti.com

SEPTEMBER 7, 2010

Home About Contact Me How To Make It as a First-Time Entrepreneur Vinicius Vacanti Guide to Finding a Technical Co-Founder September 7, 2010 | View Comments Steve Job's Technical Co-Founder “I’ve got this HUGE idea. I just need to find a technical co-founder.&# The timing just never worked out. Vinicius Vacanti WOW!

Cofounder 43

Cofounder Technical Cofounder Founder Ruby 43

techcrunch.com

OCTOBER 23, 2010

In Meebo’s case, for example, I was lucky enough to partner up with Elaine and Sandy. Second, like I said, forget everything else and just get your product out the door. No looking for partnerships (who’s going to partner with you anyway?). If no one ever uses your product, you have no value. Partner up?

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84