Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. This is the magic of sales: by learning about each customer in-depth, they can convince each of them that this product would solve serious problems.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries.

Agile 111

Agile Customer Development Developer San Francisco 111

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

NOVEMBER 7, 2008

So, if youre interested in helping avoid mistakes like that, here are the steps: Get a domain name. It doesnt have to be the worlds catchiest name, just pick something reasonably descriptive. If youre concerned about sullying your eventual brand name, dont use your "really good" name, pick a code name.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

ConversionXL

AUGUST 24, 2021

As you can see, there are many names for marketing managers and many niches for marketing managers. Marketers can be involved in product development to ensure the product aligns with the customers’ needs, in communicating price points, in finding the best angles to keep customers coming back, and so on. Know the magic.

Management 141

Management Marketing Campaign Social Media 141

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.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. It strokes your ego.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

JULY 30, 2009

I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. a is name, b is address, and c is tax percentage.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. Then, create an encouraging environment for early-stage companies. Instead, focus on getting them ready for that stage. Articulate, inspirational.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. Phases of product & company growth. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JUNE 5, 2009

In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics. As the product got better, we could see the rate getting closer and closer to the mythical “ one percent rule.&# .&# I think the problem with this approach is not the presence of the spreadsheet, but how it’s used.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

OCTOBER 4, 2008

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. He previously co-founded and served as Chief Technology Officer of IMVU. Startup Lessons Learned - the Conference (April 23.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

OCTOBER 26, 2009

The key to successful integration of customer feedback is to make each kind of collection part of the regular company discipline of building and releasing products. Anyone who has worked in a real-world product development team can tell you how utopian that sounds. Startup Lessons Learned - the Conference (April 23.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

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

Up and Running

MAY 23, 2016

If you don’t yet have a team yet, list the roles you need to hire for. If you don’t yet have a team yet, list the roles you need to hire for. Another great way to test your idea is to create a minimum viable product, or MVP. This is the simplest version of your product minus the frills and frosting. The business model.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. You can learn more about the event here. Its hosted by Kontagent and sponsored by Intel.

Metrics 88

Metrics San Francisco Lean Viral 88

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. Market Type also affects the market size as well as how you launch the product into the market.

Customer Development 220

Customer Development Developer Customer Silicon Valley 220

Hearpreneur

OCTOBER 20, 2017

Besides the general focus on customer and product development, an entrepreneur should foresee the next moves that will serve to guide him on the right path.When an entrepreneur can forecast his next moves, even his/her employees become part of the moves the business makes. . #1- 1- Converting more leads and offering more SEO packages.

Forecast 60

Forecast Artificial Inteligence Entrepreneur SEO 60

Startup Lessons Learned

JULY 6, 2011

Inspired by lessons from lean manufacturing, it relies on “validated learning,” rapid scientific experimentation, as well as a number of counter-intuitive practices that shorten product development cycles, measure actual progress without resorting to vanity metrics, and learn what customers really want. It's self-serving.

Lean 167

Lean Startup Metrics Private Equity 167

Startup Lessons Learned

JANUARY 18, 2010

Recently, he was bitten by the lean startup bug and has started writing about his experiences attempting to apply lean startup and customer development principles. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. Startup Lessons Learned - the Conference (April 23.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

K9 Ventures

OCTOBER 10, 2017

If the Micro-VCs are looking for Series A-like metrics, what does a company do when it’s just getting started? If it doesn’t have the product fully baked yet? There are a now a handful of funds, K9 included, that are Pre-Seed funds in name and practice. This has been pretty much what K9 has been doing since 2013.

Seed Stage 82

Seed Stage Finance Later Stage Equity 82

Startup Lessons Learned

AUGUST 3, 2009

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. MVP, despite the name, is not about creating minimal products. There is a distinction between product and offering.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

A Smart Bear: Startups and Marketing for Geeks

MARCH 11, 2014

Edwin: Correct, I fully agree and the name MeetingKing already says that my initial focus definitely was on meetings, right? You have your general management meeting and in your general management meeting you talk about product development, about marketing and about finance. But we’re just not going to name them as ideal.

Technical Cofounder 220

Technical Cofounder Cofounder Software Review Management 220

ConversionXL

APRIL 3, 2018

Amazon has hired more people for their Alexa division than Google has for the entire company – it’s not hunch, this is going to be the focus. Map out each lifecycle stage and variations, and name each. Hire & fire – tools to do a job. Work hard to define meaningful product metrics – enabler of team success.

Retention 106

Retention Artificial Inteligence Channel Email 106

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. You can read about the latest iteration of the proposal at StartupVisa.com.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Naturally, we already know the standard of quality that they will use to judge our product.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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

APRIL 7, 2010

At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. For example, I’m a big believer in split-testing.

San Francisco 154

San Francisco Lean Metrics Design 154

conversionxl.com

SEPTEMBER 10, 2013

So What is Customer Development? Steve Blank, a serial entrepreneur in Silicon Valley, developed a methodology for creating businesses that runs in parallel with the traditional product development process. The core idea behind customer development is that the assumptions you make about a target market are only guesses.

Customer Development 60

Customer Development Conversion Developer Customer 60

maplebutter.com

JANUARY 8, 2013

You are here: Home » Hiring » Crazy! Written By Dan Martell on February 2nd, 2012 | Category: Hiring LeanStartup Marketing Metrics Startup Life | 6 Comments. Building Product 2. Building Metrics / Usage Reports / KPI 3. Those are the only 2 metrics you need initially. you can hire for those.

Technical Review 44

Technical Review Startup Cofounder Software Review 44

Startup Lessons Learned

FEBRUARY 10, 2009

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. It would be hard to argue against this product development strategy, in general.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev. Startup Lessons Learned - the Conference (April 23.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

OCTOBER 11, 2009

Ironically, meetings like this had given data and experimentation a bad name inside this company. Every experiment has to be evaluated based on a single standard report of 5-10 (no more) key metrics. True split-test experiments are easy to classify as successes or failures, because top-level metrics either move or they don’t.

San Francisco 133

San Francisco Lean Metrics Continuous Deployment 133

Startup Lessons Learned

FEBRUARY 22, 2010

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. Now, whenever I screen resumes, I ask the recruiter to black out any demographic information from the resume itself: name, age, gender, country of origin.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

DECEMBER 16, 2009

As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Eric Names matter. By pulling in a web of associations, names help people quickly assess ideas. There is a dark side to naming. The naming question has been raised about the "lean" in Lean Startups. Eric Names matter.

Lean 140

Lean San Francisco Continuous Deployment Startup 140