Startup Lessons Learned

SEPTEMBER 30, 2008

If the CEO wants to completely change the product in order to serve a new customer segment, you need someone in the room who can digest the needs of the new (proposed) business, and lay out the costs of each possible approach. Labels: product development 15comments: mukund said. Case Study: Continuous deployment makes releases n.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JUNE 8, 2009

Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. I had it all set up to a jury-rigged SurveyMonkey - PayPal minimum viable product. So the product development team was busy creating lots of split-tests for lots of hypotheses.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

APRIL 14, 2009

This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months. What’s going on?

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. MVP, despite the name, is not about creating minimal products. We have to manage to learn something from our first product iteration.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

APRIL 18, 2010

Lean Startups waste less money, because they use a disciplined approach to testing new products and ideas. Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation. Myth: The Lean Startup methodology is only for Web 2.0/internet/consumer

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

SEPTEMBER 9, 2009

First OODA reference: Ideas. Why Continuous Deployment? * Minimum Viable Product: a guide You can see and even install the Top Posts widget yourself if you like (simple install for blogger blogs): [link] Not bad, dude. 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

JULY 31, 2009

A common question I get asked is "do you know someone amazing that we can hire?" I do my best to play matchmaker, but as those of you who have ever tried to fill a job in a startup know, the most important and elusive quality for a startup hire is fit. Great startups are always hiring, if the fit is right.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

FEBRUARY 22, 2010

To be clear, though, this diversity refers only to diversity of opinion, not necessarily to demographic diversity. After all, if you already have an all-male startup, you’re already at a disadvantage when it comes to hiring the very women that could fix that imbalance. Beyond hiring, our actual work process matters, too.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JULY 2, 2009

Five Why’s rarely works for general abstract problems like “our product is buggy&# or “our team moves too slow.&# The net effect of all this was to make new engineers incredibly productive right away – in most cases, we’d have them deliver code to production on their very first day.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

DECEMBER 30, 2008

Lessons Learned by Eric Ries Tuesday, December 30, 2008 Assessing fit with the Wisdom of Crowds When I wrote earlier about how to conduct a good technical interview , I had only a few things to say about how to assess if the candidate fits in with the team, including this: This responsibility falls squarely to the hiring manager.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Startup Lessons Learned

MARCH 3, 2009

Now he really thought I was nuts, replying "from the recruiter who hired me, of course!" If youre hiring creative, resourceful and smart people (and you are screening for that , right?) Take a failed product launch. post) is very similar, I think the key is to hire smart people first, though. Are you hiring sysadmins?

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

SEPTEMBER 5, 2008

So, for reference, I am Adam, of [link]. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. What were you referring to? Case Study: Continuous deployment makes releases n. September 9, 2009 5:56 AM Dr. Bobsaid.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

JANUARY 4, 2009

In this scheme, all of the data related to a specific feature of a product are stored on the same machines. And in MMOs, of course, it was a fiction-derived term for parallel servers which has managed to stick (many people refer to parallel VW servers as "shards" now). Case Study: Continuous deployment makes releases n.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

NOVEMBER 22, 2008

You could conduct an in-person usability test, which is very useful for getting a view of how actual people perceive the totality of your product. The tracking survey asks one simple question: How likely are you to recommend Product X to a friend or colleague? Case Study: Continuous deployment makes releases n.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

OCTOBER 19, 2009

Take this fictional example of a Seedcamp attendee (actually a composite), which I will refer to as Hairbrush 2.0. Take this fictional example of a Seedcamp attendee (actually a composite), which I will refer to as Hairbrush 2.0. Case Study: Continuous deployment makes releases n. But only startups combine all three.

San Francisco 111

San Francisco Lean Continuous Deployment DC 111

Startup Lessons Learned

FEBRUARY 12, 2009

To wit: achieving product/market fit , getting customer validation , making something people want , things that matter , and of course the many excellent books on the topic, of which Ill mention just two of the best, Crossing the Chasm and The Innovators Dilemma. Is a market a set of paying customers? There are four: Existing market.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

MARCH 20, 2009

Each of these companies were fortunate to have enough time, resources, and patience to endure the multiple iterations it took to find a successful product and market. Case Study: Continuous deployment makes releases n. They were shocked to discover their online games company was actually a photo-sharing site.

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. It took me a long time to understand that benefit of our product. This probably sounds illogical.

Community 158

Community Management Lean Software Review 158