Steve Blank

SEPTEMBER 7, 2009

Finally, I’ll write about 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. Without the revenue to match its expenses, the company is in now danger of running out of money.

Customer Development 224

Customer Development Developer Customer Silicon Valley 224

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# This basic pattern is useful in all aspects of product development. The same process works in Interaction Design. April 23, 2010 in San Francisco.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Steve Blank

NOVEMBER 5, 2009

It should go without saying that this post is not advice, nor is it recommendation of what you should do, it’s simply my observation of how companies using Customer Development positioned themselves to successfully raise money from venture investors. Reply Charlie Crystle , on April 8, 2010 at 12:31 pm Said: brilliant post.

Customer Development 262

Customer Development Developer Customer Silicon Valley 262

Steve Blank

FEBRUARY 23, 2009

This product development diagram had become part of the DNA of Silicon Valley. That’s in stark contrast to the traditional Product Development Model where it’s expected a customer is already there and waiting and it’s simply a matter of [.] familiar with Customer Development you should be.

Product Development 143

Product Development Developer Silicon Valley Product 143

Steve Blank

NOVEMBER 2, 2009

Which seems to offer an understanding of “customer development&# that’s quite different the Four Steps to the Epiphany approach. The Customer Development Model is designed to minimize the risk of launching a product for a market that does not exist. Theme: Digg 3 Column by WP Designer.

Lean 244

Lean Silicon Valley Startup RSS 244

Startup Lessons Learned

APRIL 25, 2011

If you somehow missed SLLCONF 2010 , you can get caught up with a complete video recording here.) And this year, we’re going to talk not just about business and product development, but we’ll be exploring one of the Lean Starutp movements next big frontiers: the role of design. Design + Lean Startup = Lean UX.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

The Next Web

DECEMBER 2, 2013

With mobile development agencies and product incubators on the rise and more corporate “labs” spinning out each day, there’s no shortage of talent to help you build the next great Web or mobile app. Werdelin equates building a successful product to building a nightclub. 1) Twitter. 5) Uber.

Cost 168

Cost San Francisco New York City Ruby 168

Startup Lessons Learned

MARCH 25, 2010

Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? 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. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Steve Blank

JUNE 25, 2009

Their engineering teams didn’t have the expertise using off-the-shelf microprocessors (back then “real” computer companies designed their own instruction sets and operating systems.) They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors.

Technology 138

Technology Silicon Valley Fractional VPE Part-Time VPE 138

Startup Lessons Learned

SEPTEMBER 27, 2010

Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?) 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.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

SoCal CTO

DECEMBER 1, 2010

aka: An Open Letter to the Next Big Social Network) - 500 Hats , November 1, 2010 I've held off writing this post for a long time, because I couldn't quite get my head around all the issues. When It’s Darkest Men See the Stars - Steve Blank , November 24, 2010 When It’s Darkest Men See the Stars. but: Something is Still Missing.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? 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.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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 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. May 30, 2010 1:34 AM Poker Workout said. Its incredibly hard to do.

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.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

MARCH 9, 2010

Lessons Learned by Eric Ries Tuesday, March 9, 2010 Startup Lessons Learned - the Conference (April 23, 2010 in SF) Today we are opening up registration for the first ever Startup Lessons Learned Conference on April 23, 2010 in San Francisco. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

San Francisco 151

San Francisco Lean Continuous Deployment Startup 151

Hearpreneur

JANUARY 7, 2022

Since I began in 2010, there have been ups and downs, but I wouldn't have it any other way. By establishing a company dedicated to inventive and speedy product development, I am able to use cutting-edge technologies and consistently innovate faster than competitors. Thanks to Emily King, EJM Design ! #22- 22- Enjoy life.

Entrepreneur 114

Entrepreneur Technical Review Software Review Non-Compete 114

YoungUpstarts

AUGUST 4, 2015

by Melissa Lincoln, Senior Product Marketing Manager at Leadspace. Leadspace was founded in 2010 and maintains offices in both San Francisco and just outside Tel Aviv in Hod HaSharon, Israel. San Francisco and Tel Aviv are two of the greatest cities in the world for tech, each with a distinct culture and unique benefits to offer.

B2B 100

B2B San Francisco Semantic 100

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. Ken Yagen (@kenyagen) KenAtYagenDotCom January 3, 2010 1:38 PM Paramendra Bhagat said. November 25, 2009 9:54 AM Danny Wong said. Blew my mind.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Steve Blank

SEPTEMBER 24, 2009

on July 9, 2010 at 12:50 pm Said: [.] Theme: Digg 3 Column by WP Designer. Fire might be a strong word. Reply Play Wack-a-Mole – gently, now – With Your ‘Bad’ Customers | CityOf.com – More Local… FASTER. , Blog at WordPress.com.

Customer 195

Customer Silicon Valley RSS California 195

Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. Kent is a significant figure in the field of software development. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 22, 2008

For Neopets, its simply a side-effect of their game-like product design. Either way, you can use any marketing channel thats available to bring in new customers, including word of traditional advertising, SEO, SEM - wherever you can find prospects who are going to find your product addicting.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Steve Blank

MAY 28, 2009

Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, product development may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention. Theme: Digg 3 Column by WP Designer.

Vertical 144

Vertical Silicon Valley Marketing Customer 144

Steve Blank

JULY 30, 2009

We talked about some simple design rules and I remember him thanking me for coming, saying we were the only chip company who cared enough to call on him (little did he know.) Long gone from Zilog I saw the picture of the original Macintosh design team. Theme: Digg 3 Column by WP Designer. Blog at WordPress.com.

Silicon Valley 131

Silicon Valley RSS California Customer Development 131

steveblank.com

JULY 8, 2011

AgileZen – project management visually see and interact with your work Kanbanery – Simple online team or personal kanban board LeanKit Kanban – Great for visualizing work of product development Kanban Pad – “Nice and lean” and free online Kanban tool Banana Scrum – A tool simple as Scrum itself.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

Startup Lessons Learned

JANUARY 30, 2009

Build a truly mainstream product. Insist on high levels of usability, UI design, and polish. Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. Great post!!!

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

SEPTEMBER 15, 2008

This kind of result is typical when you ship a redesign of some part of your product. The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

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

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. So far, 2010 is shaping up to be an even more amazing year; read on to find out why.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

During a lull in her practice she got a serendipitous opportunity to shift gears completely and ended up leading software product development teams. But now she has the vision and ability to design her own software, capitalizing on modern trends (e.g.

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Startup Lessons Learned

AUGUST 1, 2009

Apple has a track record of creating lots of interesting enabling infrastructure, like Quicktime and Bonjour, which sometimes become key to their products and othertimes not. My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

femgineer.com

JULY 18, 2010

HOME About the Femgineer Speaking Engagements Reading List Recruiting Startup Engineers With the startup market taking off, there is always a clamor to find good engineers, developers, and designers. If they’re coming up to speed with the product, development cycle, and company dynamics is good to let them ramp up slowly.

Engineer 41

Engineer Software Review Startup Technical Review 41