Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

ConversionXL

OCTOBER 7, 2021

These are the four stages of a product we’ll be focusing on. . However, on a more granular graph, the introduction phase would be preceded by a product development stage. This stage is used to determine the viability of your product and confirm when it should go to market. It also gives you a product to market.

Product 142

Product Marketing Software Review Social Media 142

Startup Lessons Learned

APRIL 25, 2011

If you somehow missed SLLCONF 2010 , you can get caught up with a complete video recording here.) The Lean Startup movement has made tremendous progress in the past year. It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo to explain the lean startup concept to a larger audience. The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

ConversionXL

JUNE 14, 2021

Because that’s the audience they’ve dedicated to serving, which happens to be a segment of the market that nobody else was directly talking to when they first launched. They developed features with their specific audience in mind. Amazon gift vouchers) unless you know your audience responds well to them.

Software Review 158

Software Review Audience Differentiation Framework 158

Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Expo SF (May. for Harvard Business Revie.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JUNE 9, 2009

Lessons Learned by Eric Ries Tuesday, June 9, 2009 The Lean Startup Tokyo edition I had a blast speaking at Startonomics Tokyo , which was organized to foster ties between the startup cultures in Japan and Silicon Valley. leanstartup #goap It was great to be in an audience of entrepreneurs who recognized the value of iteration and speed.

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. Sean Murphy has an excellent and comprehensive roundup of resources about the conference: all of the slides, videos, summaries, notes and write-ups are listed on his blog here.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

ConversionXL

FEBRUARY 3, 2022

This philosophy comes from The Lean Startup methodology , which relies on testing hypotheses to better understand your customers’ pain points and goals. It outlines four major growth strategies: market penetration , market development , product development , and diversification. Product development.

Marketing 115

Marketing Framework Metrics Channel 115

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. Sure, Id be delighted to.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

SEPTEMBER 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. Labels: events , lean startup 5comments: Hitchens said. The Lean Startup Intensive is tomorrow at Web 2.0.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

SEPTEMBER 22, 2008

What those sites have in common (despite their very different audiences) is that something is causing their customers to become addicted to their product, and so no matter how they acquire a new customer, they tend to keep them. The Lean Startup Intensive is tomorrow at Web 2.0. This has led to exponential growth. Expo SF (May.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. “We had to ignore them, because they weren’t our target audience – and were never likely to become customers.&#

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test? Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Five Whys has its origins in the Toyota Production System. Five Whys has its origins in the Toyota Production System.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. This belief led me to the lean startup, and to an amazing 2009.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

AUGUST 14, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference, who has created content for a number of startups. In our ongoing exploration of how people actually implement Lean Startup methods in their workplaces, we’re asking practitioners to share their techniques. Steph: Segmentation and timing.

Lean 167

Lean Conversion Audience Design 167

Startup Lessons Learned

SEPTEMBER 30, 2008

Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard. But I think in a lean startup, the development methodology is too important to be considered "just management." Expo SF (May.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. That’s the local maximum.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 2, 2008

The Lean Startup Intensive is tomorrow at Web 2.0. ► April (11) Video update on the Startup Visa Act Lean Enterprise Institute webinar, April 28 Four myths about the Lean Startup Sneak preview, KISSmetrics (and more) Sneak preview, Grockit The Lean Startup Intensive at Web 2.0 Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

AUGUST 26, 2009

If you watch the video/audio below, youll get to see some of the questions I was asked after my presentation. I did my best to capture video and audio; a YouTube playlist and Slideshare slidecast are below: Slides (with audio): 2009 08 19 The Lean Startup TechStars Edition View more presentations from Eric Ries.

San Francisco 113

San Francisco Silicon Valley Startup Lean 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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. At a recent talk, an audience member asked me about the impact of continuous deployment on morale.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

SEPTEMBER 13, 2008

July 20, 2009 1:44 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Up and Running

JULY 26, 2017

You have a new, out-of-the-box idea and you need to find out if your target audience is ready for it. Before devoting resources to building a full version, consider launching an MVP (minimal viable product) first. Learn more about validating your business idea and product concept here. Video plays. Button clicks.

Mobile 81

Mobile Application Development Web Software Review 81

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

NOVEMBER 29, 2008

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. Still, a startup product development team is a service organization. Labels: hiring , product development 5comments: TedHoward said. Expo SF (May.

San Francisco 146

San Francisco Lean Agile Java 146

Hunter Walker

OCTOBER 25, 2020

What they’ve done is use their content to assemble an audience and then create a space for that audience to create content with each other — aka community. For example, Lenny Rachitsky writes a newsletter devoted to technology and product development. Most typically in Slack, Facebook, WhatsApp or Discord. Notes and More.

North Carolina 112

North Carolina Community Media Video 112

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. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 14, 2008

(For more on earlyvangelists and why they are so important, see Steve Blanks The Four Steps to the Epiphany ) Heres the suggestion from Seth Godin I want to emphasize: And heres one thing Id do on a regular basis: Get a video camera or perhaps a copy machine and collect comments and feedback from the people who matter most to your business.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 5, 2008

October 13, 2008 9:44 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 18, 2008

Another thought would be to outline who the intended audience for your blog is and the topic areas you will focus on. Lean Start-up SlideShare prez at Web 2.0 2) Watched O'Reilly video which lead me here. The Lean Startup Intensive is tomorrow at Web 2.0. September 19, 2008 4:54 PM SkyHammer said. Hacker News 3.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

DECEMBER 14, 2009

Probably not – you need to be finding an audience, making sure that audience will trade you their attention for your content, and – most importantly – establishing a baseline for how much that attention is worth to advertisers. These concepts have important implications for any lean startup. Expo SF (May.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

APRIL 26, 2010

Lessons Learned by Eric Ries Monday, April 26, 2010 Lean Enterprise Institute webinar, April 28 I can barely write, as Im still recovering from the amazing but overwhelming Startup Lessons Learned conference last Friday (great summary here ). Want to learn more about lean startups? Details are below.

Lean 113

Lean San Francisco Continuous Deployment DC 113

Hearpreneur

APRIL 13, 2022

One of the most important lessons entrepreneurs can learn from Dropbox is to adopt the lean start-up methodology and start. The platform offers low subscription prices, HD quality, and a new perspective to audiences with respect to TV shows and movies. Thanks to Fletcher Wimbush, The Hire Talent ! #2- 2- Dropbox. 14- The Farmstand.

Artificial Inteligence 76

Artificial Inteligence Entrepreneur Technical Review Software Review 76