Startup Lessons Learned

SEPTEMBER 10, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Professionals Musings

FEBRUARY 15, 2011

I come from a high-tech software background, and only a few years ago, it would cost at least a million dollars ($1M) for a team of professionals to produce any commercial software product. Now, with open source software components, and low-cost development tools, the same job can be done by one good hacker for a few thousand dollars.

Entrepreneur 235

Entrepreneur Burn Rate SEM Social Network 235

Startup Lessons Learned

SEPTEMBER 12, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 14, 2008

In the very early days, the trick is to find anyone at all who can understand you when you are talking about your product. In our first year at IMVU, we thought we were building a 3D avatar chat product. As product people, we thought of competition in terms of features. that we learned different.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. He wrote it in 2000, and as far as I know has never updated it. Completely necessary.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

www.forentrepreneurs.com

FEBRUARY 2, 2010

Blog About Log in Register Startup Killer: the Cost of Customer Acquisition In the many thousands of articles advising entrepreneurs on what they have to focus on to build successful startups, much has been written about three key factors: team, product and market, with particular focus on the importance of product/market fit.

Acquisition 103

Acquisition Cost Customer Entrepreneur 103

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. These tests are written by the engineers themselves, and they must all pass every time.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas. Do they measure?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 8, 2008

Our open source counterparts who did solve the scale problem, had some serious hardware costs to deal with. So did I when I finally found myself building an app with real scalability, a few years later, but a combination of our just-in-time scalability technique and great open source scaling tools, made it manageable.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Gust

JUNE 10, 2012

I come from a high-tech software background, and only a few years ago, it would cost at least a million dollars ($1M) for a team of professionals to produce any commercial software product. Now, with open source software components, and low-cost development tools, the same job can be done by one good hacker for a few thousand dollars.

Cost 139

Cost Burn Rate SEM Startup 139

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 18, 2008

You can find out what it would take for them to adopt your product, and then follow up a week later and see if they did. Same with finding out what it would take to get them to recommend your product to a friend. Thoughts on scientific product development Lo, my 5 subscribers, who are you? You can even meet the friend.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. This kind of result is typical when you ship a redesign of some part of your product. Without split-testing, your product tends to get prettier over time. First of all, why split-test? One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 10, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

mashable.com

MAY 28, 2010

There’s a spectrum from descriptive names which speak directly to a product benefit or attribute, to empty vessel names, where it doesn’t mean anything about the product that we’re talking about.&# Johnson also says that search engine issues have affected the style of names. He says that intentional Web 2.0

Naming 94

Naming Technical Review Social Media Startup 94

Startup Lessons Learned

SEPTEMBER 2, 2008

A growing startup with a well-run product team will have a history of steady progress. For readers concerned about the chasm, I recommend reading Seth Godin's thoughts on "Being remarkable" and finding a unique edge/twist for your products and marketing (edgecraft). How do you plan for it?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 16, 2008

Usability testing is great for coming up with ideas about what to change in your product, but dont forget to split-test those ideas to make sure they work, too. Thoughts on scientific product development Lo, my 5 subscribers, who are you? How to listen to customers, and not just the loud. Seth Godin: How often should you publish?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 10, 2008

You have customers, they are using your product, and you are trying to help them. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Waves of technology platforms The lean startup Customer Development Engineering Greasemonkey compiler Great open source scalability tools from Danga Ideas.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 6, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? SEM on five dollars a day Andrew Chen: Growing renewable audiences Marc Prensky's Weblog: Cell Phones in Class A new version of the Joel Test (draft) Smarticus — 10 things you could be doing to your c. Seth Godin: How often should you publish?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Professionals Musings

FEBRUARY 13, 2010

I come from a high-tech software background, and only a few years ago, it would cost at least a million dollars ($1M) for a team of professionals to produce any commercial software product. Now, with open source software components, and low-cost development tools, the same job can be done by one good hacker for a few thousand dollars.

Burn Rate 125

Burn Rate SEM Social Network Angel Investor 125

www.cscyphers.com

MARCH 8, 2012

That’s is the problem for a business person trying to find a techie co-founder; the techie probably has an idea of his own, can launch a rudimentary minimally viable product (MVP) over a weekend and host it on Amazon for free. open source. And… what else?”). I Don’t Need You Anymore. and other activities.

Cofounder 40

Cofounder Technical Review Founder Software Review 40

Startup Lessons Learned

SEPTEMBER 5, 2008

Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. You can find the 2005 version here.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. So dont just kill the feature - iterate.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

SEPTEMBER 18, 2008

Many of them have really cool products shipping or about to be released, and I wholeheartedly agree with my friends at the iFund that the next generation of applications is going to be amazing. The store determines which products sit on which shelves, and which yours sits next to. Ive also been playing around with the App Store.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 28, 2008

The entrepreneurship progarms of the business, engineering, and undergraduate schools are all tackling the subject this semester, and Im honored to be part of it. hitchens - theyre not open to the public as far as I know, but if you have an affiliation with Stanford engineering, undergrad, or GSB, its possible you could come audit.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

SEPTEMBER 22, 2008

Most engineers are terrible visual designers, but if the designer on their team is struggling, maybe they can help out with an icon or two. Thoughts on scientific product development Lo, my 5 subscribers, who are you? And wait until you see a "non-technical" designer writing simple code to try and speed up a release.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 29, 2008

Question 1: When youre adding features to a product used by an existing user base, do you still do split testing to determine usage patterns? Existing customers already have an expectation about how your product works, and its important to take this into consideration when adding or changing features. Absolutely, yes.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68