Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. kaChing launched a virtual portfolio management game on Facebook in January 2008 and a similar version shortly thereafter on kaChing.com.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. When we build products, we use a methodology.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

MARCH 17, 2009

Lessons Learned by Eric Ries Tuesday, March 17, 2009 Join the Lean Startup discussion at Web 2.0 Expo for free Im honored to announce that my Lean Startup session at the Web 2.0 Everyone else can register to come to both sessions for free, including the Lean Startup talk in the main conference. What does this mean for you?

Lean 76

Lean San Francisco Web Continuous Deployment 76

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.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JULY 5, 2010

I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. 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

NOVEMBER 13, 2008

Lessons Learned by Eric Ries Thursday, November 13, 2008 Five Whys Taiichi Ohno was one of the inventors of the Toyota Production System. 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. Good stuff.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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. October 20, 2008 9:34 PM Nivi said. October 20, 2008 10:36 PM Nathan said.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. On the one hand, it gives you insight into what kind of employee the candidate might be. December 2, 2008 8:53 AM Lisa said. Fantastic post.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

JANUARY 30, 2009

Insist on the incredibly high-IQ employees and hold them to incredibly high standards. It never generated positive returns for its investors, and most of its employees walked away dejected. This company had disciplined schedules, milestones, employee evaluations, and a culture of execution. Build a truly mainstream product.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 27, 2010

I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. I won’t apologize for this aspect of the Lean Startup methodology. Data can undermine this field.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

OCTOBER 28, 2008

Lessons Learned by Eric Ries Tuesday, October 28, 2008 A hierarchy of pitches Every company will need to pitch itself from time to time. We pitch to potential partners, vendors, publishers, conferences, employees, and even lawyers. How does a lean start-up find the all-star team worthy of pitching? is this team the one to back?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Austin Startup

DECEMBER 29, 2018

Bill Wood, founder of Silverton Partners and an early General Partner at Austin Ventures before, said something that got me thinking (quoting from the SiliconHills article ): Because it’s easy to startup a company and doesn’t take a lot of money, Silverton Partners sees more startups forming, Wood said. yes, in the 4th quarter of 2008.

Cofounder 48

Cofounder Austin Technical Review Advisory Board 48

Startup Lessons Learned

MARCH 16, 2009

In the case of C3, that was to run payroll for 87,000 employees, who were presumably receiving payroll before the project began. Notice that the unit of progress changes as we move from waterfall to agile to the lean startup. Thats why I prefer to think of them as two co-equals: the problem team and the solution team.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

DECEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, December 7, 2008 The hackers lament One of the thrilling parts of working and writing in Silicon Valley is the incredible variety of people Ive had the chance to meet. This is one of the bedrock practices of any lean startup , and so its a common piece of advice I give out. Another great article.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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. October 6, 2008 9:41 PM Eric said. Any thoughts?

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

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. Because this was such a big cultural change for most new employees, we didnt leave them to sink or swim on their own. Most importantly, we immediately thrust our new employees into a mindset of reduced fear.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 A new version of the Joel Test (draft) (This article is a draft - your comments are especially welcome as I think through these issues. I would add, though, a further question: Do new employees write code on their first day? Please leave feedback!) Its incredibly hard to do.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. Not to be outdone, the technologists on the team had also brought their big guns, and the meeting was packed with employees of every level – from VP’s all the way down to me. The Lean Startup Intensive is tomorrow at Web 2.0.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 1, 2009

One of the most common questions I get about the lean startup methodology is, "but what about Steve Jobs ?" So how do you reconcile his success with the lean startup, which seems to suggest the opposite?" Plus, the premise of the question misunderstands the lean startup, too. And he doesnt shy away from big-bang launch events.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JUNE 19, 2019

Andy Rachleff co-founded the venture capital firm Benchmark Capital in 1995. Then in 2008, he had a revelation from his experience on the Penn endowment board about how to democratize investing advice and “accidentally” founded a new company to do it. That's really, really hard for inexperienced employees to get. Most hedge.

Silicon Valley 159

Silicon Valley Lean Venture Capital Pre-Money Valuation 159

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process. More on that in a moment. They are close to breakeven.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MARCH 27, 2009

In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. Unfortunately for the current crop of founders, there is intense pressure to engage in selective memory when companies tell the story of their founding. And, of course, theres the Lean Startup session at the upcoming Web 2.0

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

OCTOBER 26, 2009

They had their own private forum, and a company founder (aka me) personally ran the group in its early days. Every two months, the company would have a big end-of-milestone meeting, with our Board of Directors, Business Advisory Board, and all employees present. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

DECEMBER 6, 2008

Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. Thats OK; like all lean transformations , you need to undertake this one in small steps. Expo SF (May.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Both Sides of the Table

AUGUST 30, 2010

We’re still caught in the “post recession bounce” : What’s happening is that the angel & VC community is still feeling good from having bounced back from the nadir of the famous “ RIP Good Times ” funk that we felt in 2008. You simply can’t do with with 50+ active investments for one person.

Entrepreneur 298

Entrepreneur Technical Review Balance Sheet Government 298

Startup Lessons Learned

MARCH 13, 2009

Founders push for it. In some ways, founders are even worse. They spend so much of their time trying to convince everyone around them that their idea is great and the company is doing well: employees, investors, partners, friends, family, significant others - its a long list. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

NOVEMBER 17, 2008

Lessons Learned by Eric Ries Monday, November 17, 2008 The four kinds of work, and how to get them done: part two In part one , I talked about four different kinds of work that every company has to do: innovation/R&D, strategy, growth, and maintenance/scalability. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

FEBRUARY 11, 2009

Thats all helpful for recruiting, retaining, and ramping-up a new employee. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. . The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

OCTOBER 30, 2008

Lessons Learned by Eric Ries Thursday, October 30, 2008 John Doerrs 10 lean startup tips I just saw video of John Doerrs talk yesterday at VentureBeat’s “How to manage your start-up in the downturn&# roundtable event. Over-communicate with employees, investors, customers. All cash in most secure possible instruments.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

APRIL 26, 2009

Its a key lean startup concept. Its an amazing thing when you can hire an employee who knows more about your code base than you do, and this turned out to be a big source of advantage. In the end, I believe they co-created our product with us. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JANUARY 12, 2009

There is a stark difference between both types of employees. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. . The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

PHP 166

PHP Software Review Ruby San Francisco 166

betashop.com

OCTOBER 8, 2012

When we pivoted from fabulis to Fab, we pivoted towards building a business around the unique tastemaker talents of one of our founders, Bradford Shellhammer. Have amazing co-founders who are better at what they do than you could ever be. Founders need to personally own something big themselves. It’s that important.

Technical Review 108

Technical Review Technology Software Review Valuation 108

Reid Hoffman

JUNE 8, 2021

While many travel industry leaders chose to “go dark,” as Airbnb CEO and co-founder Brian Chesky put it , while they decided how to navigate next steps, Chesky took a different approach: He got candid. Today, we are thrilled to have Airbnb CEO and co-founder Brian Chesky with us. And I also think about regulation.

Silicon Valley 69

Silicon Valley Hosting Rhode Island Design 69

Startup Lessons Learned

MARCH 24, 2009

March 26, 2009 12:18 AM 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?) Expo SF (May.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

JUNE 23, 2009

Lessons Learned by Eric Ries Tuesday, June 23, 2009 Join the lean startup discussion at Facebook on Thursday I recently agreed to join Facebook s fbFund incubator as a mentor. Part of that includes giving a presentation for the fbFund companies on the lean startup methodology. The Lean Startup Intensive is tomorrow at Web 2.0.

Lean 74

Lean San Francisco Continuous Deployment DC 74