Startup Lessons Learned

JUNE 8, 2009

For example, I quickly learned that when I twittered about the event, more often than not I would make a sale. So the product development team was busy creating lots of split-tests for lots of hypotheses. And here is the howto for your sales bell: [link] Have fun! :-) June 9, 2009 1:42 AM David Skillern said.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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. Case Study: Continuous deployment makes releases n.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

SVPG

NOVEMBER 22, 2013

But one of the real advantages from a product point of view is that there’s no legacy to drag along, there’s no revenue to preserve, and there’s no reputation to safeguard. However, once your product develops to the point that it can sustain a viable business (congratulations!), Protect Employees and Customers.

Product 67

Product NDA Continuous Deployment Reputation 67

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. Of course, the sales folks had new features as their #1 priority.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 17, 2008

Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Is that a lot? Is that good?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 4, 2009

But if that piece-parts solution is great, then its unlikely they are going to need to buy any additional products. Because this language may lead you to believe this concept is for enterprise sales only, I thought Id walk you through an example from the world of consumer electronics. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

FEBRUARY 7, 2013

A few of the detailed case studies include: Tech legend Bill Gross building an MVP in 1999 to test demand for online car sales, which grew into CarsDirect.com. PayPal, under the leadership of David Marcus and Bill Scott, re-defining and re-engineering itself by embracing Lean Startup to improve the product experience.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

OCTOBER 30, 2008

This can take the form of a traditional sales pipeline or a registration-activation-revenue chart. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

OCTOBER 19, 2009

But instead of spending the time and money to develop products on spec, TPGTEX creates mocked-up webpages that list the features of a potential new product -- such as a system for making radio-frequency identification, or RFID, labels -- along with its price. Case Study: Continuous deployment makes releases n.

San Francisco 137

San Francisco Product Lean Continuous Deployment 137

Startup Lessons Learned

AUGUST 16, 2010

Meanwhile, individuals and smaller companies emailed by the hundreds to say that they wanted the features of custom channels, but the sales model—arranged like a media buy—didn’t make sense to them. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 28, 2009

And while its true that metrics sometimes can lead to a better product, in my experience just as often they had led to no insight whatsoever, like fancy reports that nobody reads or after-the-fact rationalizations (with graphs!) We set sales targets from day one, $300 the first month. Labels: product development 4comments: Doug said.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

APRIL 9, 2009

Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge. So instead of having sales, marketing, and business development, we have a problem team implementing customer development. Case Study: Continuous deployment makes releases n.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

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. Similarly, government purchasing is a frustrating series of hoops, even compared to enterprise sales.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. Does this sound familiar?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MARCH 13, 2009

In particular, a marketing launch can help you do three things (courtesy, as is most of my marketing advice, of The Four Steps to the Epiphany ): Drive customers into your sales pipeline. Case Study: Continuous deployment makes releases n. In the right situation, its a very useful tactic, too.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

OCTOBER 11, 2008

Sales depend on being right (whereas in UGC we can pretty much try anything, and promote the winners). Your platform may require you to staff up a large production department to crank out enough content to satisfy your customers. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

DECEMBER 16, 2008

I wrote about this challenge for iPhone developers, in an essay on retention competition : the battle over what icon the user will click when they go to the home screen. At that point, theres no opportunity for marketing or sales; the battle is already won or lost in the persons mind. Case Study: Continuous deployment makes releases n.

Viral 140

Viral San Francisco Lean Continuous Deployment 140

Startup Lessons Learned

OCTOBER 23, 2009

We got instantaneous feedback on the validity of the idea and started our sales process concurrently. LOIs, while clearly not as good as signed sales contract, do have meaning and are valuable. I encourage B2B startups to keep them in their customer development arsenal. Case Study: Continuous deployment makes releases n.

San Francisco 144

San Francisco Customer Wiki Lean 144

Startup Lessons Learned

JANUARY 28, 2009

Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Most importantly, I encouraged the leaders of the company to bring awareness of the business challenges to the product development team. Great post, Eric.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

MARCH 22, 2010

These companies produced over $52 billion dollars in sales in 2005, and employed 450,000 workers that year. These companies produced over $52 billion dollars in sales in 2005, and employed 450,000 workers that year. Case Study: Continuous deployment makes releases n. Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

FEBRUARY 12, 2009

Without a basis for comparison, you first have to drive home the need, then you will have an easy time making the sale (after all, youre the person who they trust to bring it to their attention). Toughest part of the sale is to get agreement that you really can deliver benefits that they didnt previously know were possible.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

SEPTEMBER 11, 2009

It took hundreds of years for newspapers to learn to behave as worthy holders of this public trust and cover the news without fear or favour, and create a firewall between news and views and the ad-sales side of the operation. Since LL took over xstreet, they have seen a 34% DROP in users and sales, why? YOU and ONLY YOU.

Community 158

Community Management Lean Software Review 158