Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

YoungUpstarts

JANUARY 7, 2013

What will the future of InfoComm Technology (ICT) be like? Painting the scenario of how things will evolve, Cort Isernhagen of IDC Insights forecasted at the recent Infocomm Technology Roadmap Symposium 2012 that the ICT landscape over the next 10 years needs to consider four macro trends supported by four key pillars of technology.

Technology 174

Technology Singapore Malaysia Indonesia 174

YoungUpstarts

JULY 2, 2020

Another common mistake that marketing teams are making is using the same metrics for success that they have used in the past. If you use these same metrics, you’re going to be sorely disappointed in the results. Boris Pfeiffer is CEO and Founder of Riddle Technologies. Don’t focus on old measurements for success.

Marketing 262

Marketing Metrics Channel Differentiation 262

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 30, 2008

What does your Chief Technology Officer do all day? When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Heres my take.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

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.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 2, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 15, 2008

Focus on the output metrics of that part of the product, and you make the problem a lot more clear. I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. Whatever its purpose, try measuring it only at the level that you care about.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Professionals Musings

MAY 4, 2014

This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. Leverage information technology. Don’t try this without a formal process.

Startup 268

Startup Institutional Investors Angel Investor Bootstrapping 268

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. There are too many products clamoring for attention. I’ve met a lot of gatekeepers in the past few months.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

SEPTEMBER 2, 2008

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. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. but rest assured they would be. Startup Lessons Learned - the Conference (April 23.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

www.lanceglasser.com

MAY 13, 2012

Metrics for cyclical businesses. Product development. Queuing theory and product development. The Essential Product Investigation Phase Gate. What does a CTO (Chief Technology Officer) do in a high-tech company? First it is to ensure that the company has the best technology. Stock buybacks.

CTO 40

CTO CTO Hire Technical Review Architecture 40

Startup Lessons Learned

SEPTEMBER 10, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms. Thanks to the anonymity of the internet , I landed a few jobs, and did quite a bit of writing.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 12, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JANUARY 7, 2010

So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. Read the rest at The Conversation - Harvard Business Review. Take a look and let me know what you think.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

NOVEMBER 4, 2008

As Ive written previously , lean startups are built upon three main trends: Technology commoditization. It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO).

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

NOVEMBER 8, 2008

Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. 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.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. However, a technological solution cant necessarily resolve all human root causes. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 14, 2008

If youre just getting negativity from someone, they are more likely a internet troll - not an earlyvangelist. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Seth Godin: How often should you publish?

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Professionals Musings

JANUARY 31, 2013

This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. Leverage information technology. Don’t try this without a formal process.

Institutional Investors 230

Institutional Investors Angel Investor Bootstrapping Database 230

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

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit. Growth - when you have existing customers, the pressure is on to grow your key metrics day-in day-out. Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JANUARY 12, 2010

Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it. I continue to believe that the explosion of interest in the lean startup has very little to do with me.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

OCTOBER 28, 2008

Now there was nothing wrong with their analysis: anyone who invents a technology as sophisticated as The Transformers is definitely going to make a lot of money. Turns out, they were incredibly well-credentialed graduate students who had, in fact, developed some interesting new robotics technology. is this team the one to back?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

SEPTEMBER 2, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Professionals Musings

SEPTEMBER 7, 2011

This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. Leverage information technology. Don’t try this without a formal process.

Startup 255

Startup Institutional Investors Angel Investor Bootstrapping 255

Startup Lessons Learned

SEPTEMBER 18, 2008

As a shoestring entrepreneur with a SaaS (well, not really, but sort of) offering that we present to very large companies (think 10K+), I love your common sense suggestions about metrics and testing. My background isnt metrics, but we came to it as a matter of practicality. 4) More posts about metrics, scaling, and online games.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

JANUARY 2, 2009

The core of the article is my first attempt to articulate the key metrics (in graph form) that I believe demonstrate customer value. My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. January 2, 2009 11:54 AM Daniel Davie said.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

abovethecrowd.com

OCTOBER 1, 2013

Over 13 years ago, in March of 2000, I wrote a blog post titled “ The Most Powerful Internet Metric of All. ” The key thesis was this: if an Internet company could obsess about only one metric, it should be conversion. The most obvious form of this, and by far the easiest to implement, is Google AdWords.

Metrics 93

Metrics Conversion Internet Acquisition 93

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? Startup Lessons Learned - the Conference (April 23.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

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. Good luck, engineering manager. It was painful for a lot of people.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 1, 2008

Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

MAY 27, 2009

Im going to be speaking on June 3rd at an event sponsored by the Technology Entrepreneurs Exchange (TeXchange), "the premier networking organization in Texas for business executives and entrepreneurs to meet, exchange ideas and share experiences." It uses principles of agile software development, open source and web 2.0,

Lean 60

Lean Austin San Francisco Continuous Deployment 60