Startup Lessons Learned

MAY 14, 2009

Take a look: This full-day Master Class focuses on how to build a startup from the ground up to focus on customers, markets, and speed of iteration. I have contacts within the university and entrepreneurial communities and would be happy to help you set up something if interested. Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

JUNE 8, 2009

Because of the extreme unknowns inherent in startup situations, we are all blind – to the realities of what customers what, market dynamics, and competitive threats. I suddenly lose my ability to judge if our marketing programs are being effective. It was pretty ugly, the marketing and design sucked, and I was embarrassed by it.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

Startup Lessons Learned

AUGUST 24, 2009

Now, helping potential customers discover new things they might like is the job of the discipline of marketing. But that job is changing dramatically, and this brings us to the next major problem facing traditional media organizations: Media companies are failing at marketing. There are too many products clamoring for attention.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

SEPTEMBER 15, 2009

Lessons Learned by Eric Ries Tuesday, September 15, 2009 Testing the new Disqus comment system The recent and overwhelming influx of comments on The cardinal sin of community management. Testing the new Disqus comment system The recent and overwhelming influx of comments on The cardinal sin of community management.

San Francisco 84

San Francisco DC Continuous Deployment Lean 84

Startup Lessons Learned

SEPTEMBER 3, 2009

After some general lessons, he then proposes his first product idea, complete with flip charts, business plan, and marketing plan. ► 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.

San Francisco 104

San Francisco DC Continuous Deployment Lean 104

Startup Lessons Learned

SEPTEMBER 14, 2009

We'll have IDCEE conf on October 28-29, [link] If you could come any other day we'll organize small event at #kievstartup community. ► 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.

San Francisco 84

San Francisco DC Finland Washington 84

Startup Lessons Learned

SEPTEMBER 19, 2009

Lessons Learned by Eric Ries Saturday, September 19, 2009 Support the Startup Founders Visa with a tweet Its been an exhilarating first day here in Washington DC for the Geeks on a Plane tour. We can remedy it by creating a special visa for startup founders. We can remedy it by creating a special visa for startup founders.

San Francisco 150

San Francisco Founder DC Washington 150

Startup Lessons Learned

SEPTEMBER 28, 2009

► 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 103

San Francisco Lean DC Continuous Deployment 103

Startup Lessons Learned

AUGUST 8, 2009

In particular, we would cover customer development, continuous deployment, minimum viable product, and actionable metrics. In between sessions, this cohort of companies would have the opportunity to act as a learning community, sharing what theyve learned and supporting one another as they try to put the techniques into practice.

Lean 102

Lean Programming San Francisco Continuous Deployment 102

Startup Lessons Learned

JANUARY 27, 2009

For founders, I think it also has another big attraction: the ability to avoid a lot of " free vs paid " arguments. We're keeping ourselves free for the community that has helped us build our product; premium vs basic seems wrong to us. Case Study: Continuous deployment makes releases n.

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

SEPTEMBER 9, 2009

Why Continuous Deployment? * ► 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. Case Study: Continuous deployment makes releases n. As for top posts we have: * 10.0

San Francisco 84

San Francisco Continuous Deployment Lean DC 84

Startup Lessons Learned

SEPTEMBER 15, 2009

► 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 92

San Francisco DC Washington Lean 92

Startup Lessons Learned

NOVEMBER 19, 2008

At that early stage, it was the companys first glimpse of what a crossing the chasm strategy might look like: use these early adopters to build a whole product for the education market. I would recommend periodic surveys, along with some kind of forum or other community tool where the most passionate customers can congregate.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

FEBRUARY 11, 2009

Heres the short version: hire people from the online communities that develop free software. Its obvious that can lower your development costs, but I think its even more important that it can reduce your time to market. Another unexpected benefit comes when you hire people who are part of the same online coding community.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

DECEMBER 14, 2009

And passionate players are often the backbone of game communities – especially online. We cultivated a passionate community that nurtured a skilled set of developers. Companies use that money to market the product or service to more customers. Founders struggle with this question. Successful startups don’t.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

SEPTEMBER 8, 2009

So heres my simple question: What do folks in Washington need to know about the global community of entrepreneurs? The US was once known as a free market democracy that could make the trains run on time. The new administration has helped some of their ranks to cross over into the Federal community too. There are and we do.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

MARCH 3, 2009

Everything else is only marketing. If your marketing team actually uses data to make decisions, your engineering team will be impressed. ► 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.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

OCTOBER 11, 2008

As the size of your community and economy grows, youll be able to solve them as they arise, as long as you know what to look for. In other words, a marketing department. Case Study: Continuous deployment makes releases n. If you know what youre getting into, you really dont need to solve those problems in advance.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

NOVEMBER 22, 2008

Theres a lot of controversy surrounding NPS in the customer research community, and I dont want to recapitulate it here. Even if you have a very large community, I dont think this number needs to be higher than 100. In other words, we committed the one cardinal sin of community management. Heres how Ive set it up in the past.

.Net 158

.Net Operations San Francisco Lean 158

SoCal CTO

JANUARY 5, 2011

Steve Blank , January 25, 2010 10 Tips for Adding Game Mechanics to a Non-Gaming Service - ReadWriteStart , September 21, 2010 Startups & VCs: Learn How to Design, Market, & Eat Your Own. - . - 500 Hats , February 1, 2010 When to Use Facebook Connect – Twitter Oauth – Google Friend Connect for Authentication? First Principles.

Silicon Valley 378

Silicon Valley Startup Term Sheet Venture Capital 378

Startup Lessons Learned

JANUARY 2, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an internet connection. Ive been blown away by the level of demand you all have expressed in having a forum for the whole community to come together and share what were learning.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

JANUARY 12, 2009

The number one reason I keep coming back to PHP is that it has overwhelming community support. Ive written elsewhere that success in creating a platform is "becoming a function not of the size and resources of the company that builds it, but of the size of the community that supports it." Lets start with some circular reasoning.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

Lessons Learned by Eric Ries Friday, September 11, 2009 The cardinal sin of community management Once you have a product launched, you will the face the joys – and the despair – of a community that grows up around it. This probably sounds illogical. After all, people rarely say they are mad because they are not being heard.

Community 158

Community Management Lean Software Review 158

Startup Lessons Learned

NOVEMBER 5, 2008

We were building a community, open to anyone who shared its values, and that mission inspired volunteers and staff to try and reach out to as many people as possible. The Obama campaign was also very impressive on the online marketing front - their ads were everywhere. Case Study: Continuous deployment makes releases n.

Campaign 84

Campaign San Francisco Lean Agile 84