Startup Lessons Learned

SEPTEMBER 22, 2008

is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. The AARRR model (hence pirates, get it?) Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

ConversionXL

MARCH 7, 2017

The first, according to Dr. David Travis at UserFocus , was agile development : Dr. David Travis: “‘Development’ teams morphed into ‘design’ teams. To use the agile terminology, design teams wanted to get a ‘shared understanding’ of their users and they were suspicious of any attempt to set requirements in concrete.”.

Software Review 102

Software Review Design Agile Analytics 102

Startup Lessons Learned

FEBRUARY 10, 2009

Heck, thats what it says right there in the agile manifesto. In a lot of cases, thats just a fancy name for revenue or profit, but not always. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. If a feature worked, wed keep it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

YoungUpstarts

JUNE 10, 2018

For manufacturers, this means having the capability to establish fully connected and digitized supply chains where product development, marketing, production, and distribution are all fully connected, thus increasing efficiency and output. Start planning on how to adapt to Industry 4.0 Be Updated. Invest in Cyber Security.

Agile 100

Agile Analytics Cloud Bankruptcy 100

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Sounds very similar to agile development which is the way. Interesting post. February 21, 2009 7:39 AM Rocky1138 said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. If youre making revenue, you should be finding ways to grow it predictably month-over-month; if youre focused on customer engagement, your product should be getting more sticky, and so on.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

SEPTEMBER 13, 2008

And one day a remarkable thing happened: we started making more than five dollars a day in revenue. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. In fact, SaaS industry revenue is projected to grow from $49 billion in 2015 to $67 billion in 2018, a compound annual growth rate of approximately eight percent.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

MARCH 27, 2009

To increase the number of iterations you have left, you can either increase cash on hand (by raising money or increasing revenues), reduce burn rate, or increase the speed of each iteration. Customer Development : a disciplined approach to finding out if there is a market for your product before its too late. Expo SF (May.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

JANUARY 15, 2010

Usually, they are delivering only a fraction of the revenue they promised. Usually, they are delivering only a fraction of the revenue they promised. Lets return to our team thats failing to hit their targets. They are on-schedule and on-budget, but their gross metrics are way off. Expo SF (May.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JANUARY 2, 2009

We were even more embarrassed by the pathetically small number of customers we had, and the pathetically low amount of revenue we had earned so far. We’d always cringe as we admitted that, no, we really only had a few thousand customers and a few thousand dollars in monthly revenue. Retention cohort analysis. I am chugging along.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

JANUARY 28, 2009

Still, theyre not really hitting it out of the park, because their product isnt growing new users as fast as theyd like, and they arent making any money from the current users. Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

AUGUST 1, 2009

Most executives, especially in startups, dont have the courage to hold their teams to a high standard for new products or features. Not even if its generating revenue. The only efforts a new product team should be expending are those that lead to validated learning about customers. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. When we’re optimizing, product development teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

DECEMBER 23, 2009

They were accustomed to measuring their progress primarily by gross revenue compared to their targets. They were accustomed to measuring their progress primarily by gross revenue compared to their targets. Naturally, they had just raised money, and their new investors were understandably pissed. Expo SF (May.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

JUNE 5, 2009

And so the spreadsheet is built with conservative assumptions, including a final revenue target. No matter how low we make the revenue projections for this new product, it’s extremely unlikely that they are achievable. In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. What is the right revenue model? In other words, what is the minimum viable product ? My blog has over 14000 subscribers, for example. Is that a lot? Is that good? Just like with startups, this is a hybrid question.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JUNE 15, 2009

The agile software movement has made numerous contributions: continuous integration, which helps accelerate feedback about defects; story cards and kanban that reduce batch size; a daily stand-up that increases tempo. It lets the customer and development team spot problems with calculations almost immediately. . Expo SF (May.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. We just add up the revenue we've made in the past few months from Win98 users, and compare to the pain that Win98 has caused as identified in 5Ys. Leave your thoughts in a comment. I’ll do my best to help.) Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 28, 2008

In fact, in the early days, when IMVU would experience unexpected surges of revenue or traffic, it was inevitable that every person in the company was convinced that their project was responsible. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

mashable.com

MAY 24, 2011

May 23, 2011 by Christina Warren 20 Share on Tumblr email share Share on Tumblr email share The Mobile App Trends Series is supported by Sourcebits , a leading product developer for mobile platforms. Sourcebits offers design and development services for iOS, Android, Mobile and Web platforms. My 2 cents.

Mobile 90

Mobile Web Social Media Software Review 90

Startup Lessons Learned

SEPTEMBER 29, 2008

Either way, you would have been better off focusing your split-test on high level metrics that measure how much customers like your product as a whole. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

DECEMBER 14, 2009

Now, Andrew’s excellent piece that I quoted from above correctly diagnoses two situations where consumer internet companies often get in trouble: They focus too much on short-term revenue, getting caught in a local maximum via constant optimization. The real value we create is learning how to craft profitable ecosystems. Expo SF (May.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

OCTOBER 30, 2008

Not just about expenses, about increasing revenue. Make sure for planned revenues you have "leading indicators" to know if you will hit it. This can take the form of a traditional sales pipeline or a registration-activation-revenue chart. And its hard to know if youre truly succeeding without a focus on revenue.

Lean 121

Lean San Francisco Continuous Deployment DC 121

Startup Lessons Learned

NOVEMBER 22, 2008

The whole episode cost us hundreds of thousands of dollars in lost revenue. In fact, it was the revenue trends that eventually alerted us to the magnitude of the problem. Unfortunately, revenue a trailing indicator. Its a great time to increase revenues without spending money on acquiring new customers. Expo SF (May.

.Net 158

.Net Operations San Francisco Lean 158

Startup Lessons Learned

JANUARY 27, 2009

These are companies that generate revenue by offering a free product with an upsell or premium version. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

San Francisco 148

San Francisco Lean Continuous Deployment DC 148

Startup Lessons Learned

AUGUST 16, 2010

Realizing it had taken a wrong turn, SlideShare rethought its approach to premium accounts and ultimately performed what we’d call a value capture pivot , one where the company changes the way it collects revenue from customers. The process started with a few moving parts. The process started with a few moving parts. Expo SF (May.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

SoCal CTO

DECEMBER 1, 2010

Storm Clouds - A VC : Venture Capital and Technology , November 12, 2010 We have enjoyed an amazing run in the web startup and investing space over the past five or six years. Today, brands are hiring social media specialists for customer support, crowdsourced product development, promotions and even leads generation.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

MAY 1, 2009

LIKED: Y startups fail, cont deployment vs waterfall vs agile, small batches & learn fr biz metrics #leanstartup As concise a summary as Ive ever seen. I covered a few of them on twitter already: Q: "Do you reccomend removing features that youve launched but dont movethe needle on engagement or revenue?" A: yes, absolutely.

Lean 60

Lean San Francisco Startup Continuous Deployment 60

Startup Lessons Learned

JULY 9, 2009

We were focused on revenue, but we didnt understand that revenue is not important for its own sake in an early stage company. Maybe, but the thought never even entered our minds. You can even see the humiliating evidence of my smug incompetence in this absurd article from 1999.) Expo SF (May. Take a look and let me know what you think.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

SEPTEMBER 11, 2009

This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline. "This single decision wound up costing the company significant revenue and over the course of several months sent its customer growth into decline." Expo SF (May.

Community 158

Community Management Lean Software Review 158