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? ) In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Yet there’s a lot of mystery around pivots, and entrepreneurs ask all the time how you know it’s time to commit to a new direction.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 2, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Steve Blank

JULY 30, 2009

Your Customers are Not Who You Think For years I thought this “million unit chip sale by accident&# was a “one-off&# funny story. That is until I saw that in startup after startup customers come from places you don’t plan on.

Silicon Valley 131

Silicon Valley RSS California Customer Development 131

Startup Lessons Learned

SEPTEMBER 10, 2008

I have been thinking a lot about what a new version of this test would look like, given what Ive seen work and not work in startups. There was a time when "web content" was considered "not code" and therefore not routinely source controlled. are the parts of the Joel Test I think are most out-of-date. Its incredibly hard to do.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May. . Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 12, 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?) Expo SF (May. . Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 2008

October 17, 2009 10:34 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. .

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 14, 2008

It required hearing customers say it over and over again for us to take a serious look, and eventually to realize that social networking was core to our business. Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. Dont confuse passion with volume.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Can they tell a good release from a bad one?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 1, 2008

In almost all Agile Development systems, thousands of automated tests are run against every change to the software. These tests are written by the engineers themselves, and they must all pass every time. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Expo SF (May.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 8, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 Waves of technology platforms I still remember the first time I switched to LAMP. I was building a new startup in 1999, and wanted to do it right. So one of the first things we did was to hire an Oracle expert and get to work. Looking back, that was a special moment.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

rob.by

MARCH 8, 2012

He argued that software engineers don’t finish what they start, and that you’re better off paying a technical person than partnering with one. Twelve months into my startup journey I had four half-built websites that had been built by my four ex-technical co-founders. Finding Technical Cofounders Is Hard.

Technical Cofounder 42

Technical Cofounder Cofounder Software Engineering Fractional CTO 42

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?) Expo SF (May. . Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 10, 2008

I see startups struggle with this all the time. You have customers, they are using your product, and you are trying to help them. Update : bonus thought from Dharmesh Shahs 8 Startup Insights Inspired By The Mega Mind of Seth Godin: 6. No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

SEPTEMBER 16, 2008

Read more at How to Usability Test your Site for Free | Noah Kagans Okdork.com Labels: listening to customers 1 comments: HKagan said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May. .

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 6, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 2, 2008

A growing startup with a well-run product team will have a history of steady progress. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

SoCal CTO

DECEMBER 1, 2010

I continue to collect great content that is the intersection of startups, products, online and technology. aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. but: Something is Still Missing.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

SEPTEMBER 18, 2008

I want to get an idea of how startup guys think. This is a good sign for you! :) I subscribed because I was inspired by the O'Reilly video, and feel I want to go deeper into the customer development field. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

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. Those who have the endurance are the ones that tend to lead teams and join startups, because you just cant be successful in a startup situation without empathy.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MAY 7, 2009

For people we hired from larger companies especially, this was challenging. When a new engineer started at IMVU, I had a simple rule: they had to ship code to production on their first day. We always assigned them a "code mentor" from the ranks of the more established engineers. We didnt have that many customers, after all.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

David Teten

OCTOBER 1, 2015

I’ve been looking for suggestions for an initial deal structure that is appropriate for the theoretical case of a trusted dev shop putting in $100k in market-value of services over a 6 month period in time. How would one set up such a startup to eventually raise capital from outside VCs, who will be wary of ‘dead equity’ (i.e.,

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

Startup Lessons Learned

SEPTEMBER 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. I struggle to try and make the students actually experience how confusing and frustrating startup environments are.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

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

techcrunch.com

OCTOBER 23, 2010

Problem was, I seemed to suck at the whole startup thing. Rather, I didn’t have anyone around me familiar enough with startups to tell me that I was doing it all wrong. One of the things I do as a founder of a later stage startup is to meet with early stage entrepreneurs to help them get their companies going. Sorry, folks.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Startup Lessons Learned

SEPTEMBER 18, 2008

After Ive built my first successful app, and all kinds of competitors have copied me and have similar apps right next to mine in the store, how will I continue to get new customers? How will new customers know that my apps are superior? Labels: iPhone , search engine marketing 3comments: Blake Engel said. Expo SF (May. .

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 22, 2008

Lots of engineers are busy checking in and deploying their work. Meanwhile, a dozen other engineers are getting annoyed, because this constant bouncing is making it harder for them to work (they cant deploy changes while tests or the cluster are in red-alert mode). No departments The Five Whys for Startups (for Harvard Business R.

Product Development 68

Product Development Developer San Francisco Product 68

Up and Running

MAY 23, 2016

If you want a slice of the pie, there isn’t a better time to get involved. To give you a better idea of what entrepreneurs in this industry are thinking about during each phase of the startup process, I interviewed SaaS entrepreneurs from all over the world, including our own COO Noah Parsons. The business model. or even be a U.S.

Software Review 74

Software Review Software Delaware Forecast 74

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?) Expo SF (May. . Expo SF (May.

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 You dont need as many tools as you think Im always excited to see someone else writing about lessons learned from their startup, and wanted to link today to Untitled - Startup Lessons Learned -- Take it with a grain of salt. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 29, 2008

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. The new startup arms race (for Huffington Post) For Startups, How Much Process Is Too Much?

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Non-Technical Co-Founders Co-Founders Technical Co-founders Finding Co-Founders Startups & "How Important Are Ideas?" " Web Development Startups Solo Founders I am a creative guy with a startup idea. Rockstar v.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Team Configuration 500 Startups Guerilla Marketing Organizations Entrepreneurship Startup Founders & Entrepreneurs Startups Startup Incubators and Seed Programs Seedcamp Y Combinator TechStars Lean Startups What is the perfect startup team?

Technical Review 51

Technical Review Startup CTO Hire Cofounder 51

Startup Lessons Learned

JANUARY 12, 2009

But by the time I was building my first websites for commercial use , PHP had taken over. Since then, PHP (as part of the LAMP stack ) has really been the dominant development platform, at least in the free software and startup worlds. Which makes them exactly the kind of programmers companies should want to hire.

PHP 166

PHP Software Review Ruby San Francisco 166