Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

SoCal CTO

DECEMBER 1, 2010

I continue to collect great content that is the intersection of startups, products, online and technology. Equity-Only CTO and Equity-Only Developers - SoCal CTO , November 1, 2010 I had a recent email dialog with the founder of a company looking for a CTO for their startup. Call it facts for hire.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

SEPTEMBER 2, 2008

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. Seth Godin: How often should you publish? Want to learn more about me?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

OCTOBER 4, 2008

(Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He previously co-founded and served as Chief Technology Officer of IMVU. Please email me if you are interested. My first time at your blog. Your "startup-lessons-learned" are very valuable.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you? It strokes your ego. Seth Godin: How often should you publish?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 2008

This simple feedback loop has proven its worth to me time and again. 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.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 10, 2008

Labels: Test-driven development 0comments: 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?)

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 5, 2008

October 13, 2008 9: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?) Want to learn more about me?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 14, 2008

is something like "yes, I personally answer the customer support emails." For example, my experience with teenagers is that they are very reluctant to call or email asking for support, even when they have a severe problem. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

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.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

JULY 30, 2009

If that’s you, by all means hire a VP of Sales with a great rolodex and call on established mainstream companies – and ignore the rest of this post. Look for some “ skunk works &# project where the product developers are actively seeking alternatives to their own engineering organization. Does this help?

Silicon Valley 133

Silicon Valley RSS California Customer Development 133

Startup Lessons Learned

SEPTEMBER 13, 2008

There is much work that I need to do (the only developer so far) before we have something customers can use. Thoughts on scientific product development Lo, my 5 subscribers, who are you? How to get distribution advantage on the iPhone How to Usability Test your Site for Free The one line split-test, or how to A/B all the tim.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: 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?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 10, 2008

Among his ideas are that todays kids should be taught in class in a way that is relevant to their actual lives, which necessarily means allowing them to use technology. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Seth Godin: How often should you publish? Want to learn more about me?

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 1, 2008

Labels: Test-driven development 0comments: 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?)

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 15, 2008

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. Seth Godin: How often should you publish? Want to learn more about me?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 2, 2008

We talk a good game about technology adoption curves and crossing the chasm, but most of us dont seem to recognize when its happening. 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).

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 16, 2008

thanks for the mention:) September 17, 2008 11:56 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?)

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 6, 2008

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. Seth Godin: How often should you publish? Want to learn more about me?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 10, 2008

0comments: 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?) Seth Godin: How often should you publish?

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

JUNE 22, 2009

The more work youve sunk into a product or vision, the harder it is to let it go. As the CTO/VP Engineering, I was the worst offender. Most engineers naturally think about repurposing the technology platform, and this is a common pattern. Thats why its so essential to have a co-equal problem team. Want to learn more about me?

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JANUARY 12, 2009

At IMVU, when wed hire a new engineer, we could get them to ship code to production on their first day, even if they had never programmed in PHP before. Which makes them exactly the kind of programmers companies should want to hire. In my role as a CTO, Ive always tried to choose the right tool for the right job.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 29, 2008

Lessons Learned by Eric Ries Monday, September 29, 2008 Q&A with an actual reader One of my favorite things about having a blog is the feedback I get in comments and by email. 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?

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 18, 2008

If you have a minute, post your answers in a comment, or email me. Heard about O'Reilly video from "So you want to be an entrepreneur" blog 3)I subscribed in spite of the fact that I just pruned my email , twitter and Google reader feeds down to the bone. How annoying!) May 4, 2009 6:36 PM acheekymonkey said.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 28, 2008

Drop me an email (startuplessonslearned-eric@sneakemail.com) if youre interested and Ill see what I can do. of course, the most convincing narrative usually belongs to the hippo: [link] and when you remove objectivity from your startup, you are going to have a hard time sustaining successful decision making. wow, dead on.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

SEPTEMBER 22, 2008

As a lot of work seems to progress using email, Google Docs is a natural progression, while allowing our team to upload items and progression without meeting face to face or sending off a number of repetitive emails. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Want to learn more about me?

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 18, 2008

April 27, 2009 10:55 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?) Want to learn more about me?

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Up and Running

MAY 23, 2016

If you don’t yet have a team yet, list the roles you need to hire for. If you don’t yet have a team yet, list the roles you need to hire for. Another great way to test your idea is to create a minimum viable product, or MVP. This is the simplest version of your product minus the frills and frosting. The business model.

Software Review 74

Software Review Software Delaware Forecast 74

techcrunch.com

OCTOBER 23, 2010

But six months in, you’re gonna cry when you see someone else put out that same product you’re pitching me right now. Like I said, forget everything else and just get your product out the door. Inevitably, the excuses begin: I need to hire people to build the product. I don’t know any developers. No phone system.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

www.quora.com

JANUARY 16, 2011

Developer, engineer, CTO, or technical co-founder? If you have an idea and either customers waiting for the product to be built, or a startup success under your belt already, skip to step 2. How many things on this list require technology? Nor does picking apart 200 web products and analyzing what works and doesn't.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

ConversionXL

JANUARY 17, 2017

LawnStarter is one such company, so we sat down with their CTO, Jonas Weigert , to learn about how they experiment across their product and communication and how they deal with optimization as a company. We also put a lot of effort into testing product communication (emails, SMS, and push notifications) to drive users into our product.

Algorithm 48

Algorithm CTO Hire Distribution Engineer 48