The Next Web

DECEMBER 2, 2013

Founder Kevin Systrom launched Instagram with 25,000 beta users on October 6, 2010; two years later, the app continues to see massive growth, recently reporting 150 million active users. Luck, timing and social engineering are bigger components than most entrepreneurs care to imagine,” adds Werdelin. million to develop.”.

Cost 168

Cost San Francisco New York City Ruby 168

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. In a project like that there are lots of big questions that need to be answered in order to build a working product. Thats pretty clear.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. With 21 employees today, kaChing is devoted to recruiting professional managers and finding product/market fit , first for money managers, then for consumers.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. January 6, 2010 12:49 AM Anonymoussaid. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 5, 2010

I used to give copies of Four Steps out to my employees, in the hopes that it would instantly indoctrinate them into the methodology of Customer Development. I used to give copies of Four Steps out to my employees, in the hopes that it would instantly indoctrinate them into the methodology of Customer Development.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. whos on the engineering team?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

OCTOBER 26, 2009

The key to successful integration of customer feedback is to make each kind of collection part of the regular company discipline of building and releasing products. Anyone who has worked in a real-world product development team can tell you how utopian that sounds.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. Nothing is more demoralizing to an engineering team. Use some customer development to find out. They dont really create value.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

techcocktail.com

OCTOBER 23, 2010

Dedication: At a typical organization, dedication of its employees is important. be the manager and product developer). Developer – Most likely your product requires some engineering. 1 comment… read it below or add one } John Guidos August 27, 2010 at 7:55 pm I want to be your legal counsel.

San Francisco 44

San Francisco Startup PHP San Diego 44

Startup Lessons Learned

MARCH 25, 2009

March 27, 2009 7:07 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

MARCH 17, 2009

aandarian yahoo c o m March 26, 2009 10:44 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

MARCH 4, 2009

Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Combining agile development with customer developm. April 23, 2010 in San Francisco. Facebook Fans Recent & Upcoming Events 2010 I am experimenting with using Plancast to track my 2010 event schedule. Join the Lean Startup discussion at Web 2.0

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Austin Startup

MARCH 22, 2010

million from the State of Texas through the Texas Emerging Technology Fund (TETF) for the development of its module?integrated SolarBridge expects to add a total of 60 employees in Austin over the next 3 years. SolarBridge Technologies announced that it has been awarded $1.5 integrated microinverter and management system.

Texas 54

Texas Architecture Austin Product Development 54

Startup Lessons Learned

JULY 2, 2009

For example, I often cite a real example of a problem that has as its root cause a new employee who was not properly trained. I pick that example on purpose, for two reasons: 1) most of the companies I work with deal with this problem and yet 2) almost none of them have any kind of training program in place for new employees.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

OCTOBER 30, 2008

Everyone from the receptionist to engineers is selling. Over-communicate with employees, investors, customers. Ive also used the voluntary salary reduction tool - its particularly useful as a way to get passionate employees who dont have a lot of personal expenses to buy into the mission of the company at a deep level.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Hearpreneur

JANUARY 7, 2022

This eventually creates animosity and is the worst type of employee to have. I never desired to be that employee, and hence chose to implement my own ideas and do things my own. Since I began in 2010, there have been ups and downs, but I wouldn't have it any other way. Then they decided to fire all of the high-paid employees.

Entrepreneur 118

Entrepreneur Technical Review Software Review Non-Compete 118

Startup Lessons Learned

MARCH 3, 2009

Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. The rule is simple: every employee is 100% responsible for how they spend their time. The suggestion is that you implement one single company-wide rule. I asked why.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. On the one hand, it gives you insight into what kind of employee the candidate might be. 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.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

MARCH 23, 2009

And warm wishes for a successful 2010, filled with lots of MVP's. I started writing and teaching about shipping imperfect products a few years ago but this is a far better, practical and more powerful presentation. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco.

San Francisco 167

San Francisco Lean Continuous Deployment Audio 167

Startup Lessons Learned

OCTOBER 19, 2009

Then, the company spends no more than a few hundred dollars marketing the product through search engines and to the contacts in its sales database and LinkedIn. It isnt until a customer actually clicks or calls to place an order that TPGTEXs developers will build the software. "We Read the rest. Read the rest.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

FEBRUARY 7, 2010

Lessons Learned by Eric Ries Sunday, February 7, 2010 Tell your Startup Visa story Ive been promising big Startup Visa -related news on Twitter for a few weeks. Whether youre a US citizen or an immigrant, entrepreneur or investor, founder or employee, theres something you can do. Soon, I promise. Soon, I promise.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

JUNE 23, 2009

Priority will be given to employees of companies participating in the fbFund REV program, but I am confident that there will be room for members of the general public who want to attend. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Bring your questions.

Lean 74

Lean San Francisco Continuous Deployment DC 74

Startup Lessons Learned

SEPTEMBER 19, 2009

In fact theyd cause there to be more jobs for Americans, because the companies they started would hire more employees as they grew. In fact theyd cause there to be more jobs for Americans, because the companies they started would hire more employees as they grew. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

JUNE 21, 2010

Lessons Learned by Eric Ries Monday, June 21, 2010 What is a startup? Yet, the real stories of successful startups are full of activities that can rightly be called institution-building: hiring creative employees, coordinating their activities, and creating a company culture that delivers results. How can that be part of a startup?

San Francisco 168

San Francisco Startup Lean Continuous Deployment 168

Startup Lessons Learned

MAY 7, 2009

We eventually discovered (via five whys ) that we also had to get each new employee acculturated to a fearless way of thinking. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. For people we hired from larger companies especially, this was challenging.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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. Here are two specific ways it can go horribly wrong.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

MARCH 31, 2009

April 2, 2009 5:41 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) April 23, 2010 in San Francisco.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 27, 2010

Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?) One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

www.quora.com

JANUARY 16, 2011

He , Srikanth Narayan , Ben Werdmuller von Elgg , Jo Vi Ko , Justin Lee , Giovanni Tardini , David de Weerdt , Vineet Thanedar , Ryan Brideau , Jonathan Meiri , Rob Weedn , Krzysztof Kowalczyk , Greg Pilling , Kevin Leland , Parham Michael Ossareh , Dan Loewenherz , Mary Specht , Engin Erdo?an Yishan Wong • Nov 8, 2010 lol.if

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Startup Lessons Learned

AUGUST 20, 2009

Because this radical notion of progress is located firmly in the heads of its employees, and not in any artifacts they produce, the lean startup is employee-centric and knowledge-obsessed. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. It is a truly fun place to work.

Lean 68

Lean San Francisco Startup Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Our bias as technologists is to over-focus on the product part of the problem, and five whys tends to counteract that tendency.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 9, 2009

Then I wouldnt have the chance to work with the incredible employees and mentors from whom I learned so much. Google was not the first search engine, but it's the one that succeeded. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, And yet, missing out on these trends wasnt the end of the world.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

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. And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Hire a CTO or VP Engineering.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MARCH 27, 2009

Customer Development : a disciplined approach to finding out if there is a market for your product before its too late. Customer Development Engineering : techniques for accelerating your product development. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Bring your questions.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

MAY 1, 2009

A: have them deploy code to production on their first day as an employee. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Facebook Fans Recent & Upcoming Events 2010 I am experimenting with using Plancast to track my 2010 event schedule. What else?"

Lean 60

Lean San Francisco Startup Continuous Deployment 60