Steve Blank

FEBRUARY 25, 2010

Customer Development is a technique startups use to quickly iterate and test each part of their business model. How you execute Customer Development varies, depending on your type of business. In my book, “ The Four Steps to the Epiphany ” I use enterprise software as the business model example.

Customer Development 270

Customer Development Web Developer Customer 270

Startup Lessons Learned

NOVEMBER 6, 2008

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

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.&# The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Up and Running

AUGUST 8, 2018

But, here at Palo Alto Software, we’ve found one meeting that is simply indispensable. It only takes an hour each month, keeps the management team up to speed on everything that’s going on in the company, and helps us plan and manage in a lean and effective way. This meeting is our monthly plan review meeting. Are we there yet?

Software Review 65

Software Review Business Plan Product Forecast 65

Steve Blank

OCTOBER 30, 2012

The Lean LaunchPad Class. You may have read my previous posts about the Lean LaunchPad entrepreneurship class. The class teaches founders how to dramatically reduce their failure rate through the combination of business model design, customer development and agile development using the Startup Owners Manual.

Startup 335

Startup Lean Incubator Business Model 335

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. Do you fix bugs before writing code? Please leave feedback!)

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

A Smart Bear: Startups and Marketing for Geeks

JULY 19, 2010

No wait, I forgot, actually the question is: What happens when employee #2 makes off with your code and roadmap and marketing data and customer list, moves to Bolivia, and starts selling your stuff world-wide at one-tenth the price? You don't have an "edge" just because you're passionate, hard-working, or "lean.". Like what??

Software Review 325

Software Review Technical Review Development Team Review Bolivia 325

Steve Blank

OCTOBER 15, 2019

This article previously appeared in the Harvard Business Review. Once upon a time every great organization was a scrappy startup willing to take risks – new ideas, new methods, new customers, targets, and mission. And by product, I mean the creation of new hardware, services, software, tools, operations, tradecraft, etc.

Government 319

Government Technical Review Acquisition Metrics 319

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. Step 1: Start with a lean plan. A description of the problem you’re solving for your customers, and your solution to the problem, which is usually your product or service.

Software Review 74

Software Review Software Delaware Forecast 74

A Smart Bear: Startups and Marketing for Geeks

MAY 31, 2010

We scoff at their inability to innovate and for prioritizing shareholders over customers, but still we quiver in fear. What if a huge company with a hundred software developers and a million dollars in marketing budget decides to copy my idea? Dozens of people on Answers.OnStartups ask about it so I know I'm not alone.

Software Review 243

Software Review Development Team Review Technical Review Software Developers 243

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Up and Running

DECEMBER 6, 2012

Today, I want to introduce you to a new concept for starting and growing successful companies: Lean Planning™. Before I dive too deeply into the Lean Planning methodology, it makes sense to talk about its history and where it comes from. Determine your target market: You need to know and understand your customers.

Lean 147

Lean Silicon Valley Forecast Technical Review 147

Startup Lessons Learned

OCTOBER 20, 2008

He has a good team, and theyve shipped a working product to many customers. If engineers want more time to spend making their old code more pretty, they are invited to do so on the weekends. The idea is that once we move to the new system (or coding standard, or API, or.) Its become "legacy code" and part of the problem.

Software Review 164

Software Review Engineer Management Technical Review 164

Both Sides of the Table

NOVEMBER 1, 2009

As organizations we have become more open and I believe this is great for businesses and their customers. We spent time out in the marketplace talking with customers, looking at their solutions, comparing ourselves with our competition and then squirreling ourselves away in our offices designing our next set of features.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

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. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did).

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

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

ConversionXL

AUGUST 5, 2021

App automation can remove bottlenecks, save time and money, help you provide a better customer experience, and improve internal collaboration. We’ll also explore examples to apply across the customer journey and tools you can experiment with and invest in today. Start by mapping the customer journey before your automation workflows.

Software Review 143

Software Review Technical Review San Diego Retention 143

ConversionXL

OCTOBER 7, 2021

For this reason, it could be a good idea to get a minimum viable product (MVP) as early as possible to show how your product will work to investors and customers. Then we ship it to customers way before it’s ready. And we charge money for it.” – Eric Ries, The Lean Startup. Image source.

Product 142

Product Marketing Software Review Social Media 142

Startup Lessons Learned

SEPTEMBER 30, 2008

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. If not, whos going to insist we switch to free and open source software?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

The Startup Magazine

OCTOBER 2, 2018

A startup by nature is a small, agile company which is innovating to solve a problem. Start-ups are lean and designed to grow or scale up quickly. However, you can’t pitch to potential partners or customers in your garage workspace. Including testimonials and positive customer reviews can also boost your credibility.

Startup 115

Startup Software Review Social Media Agile 115

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. If we accept the verdict of customers instead of pundits, I think these claims are easy to dismiss.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

OCTOBER 5, 2008

Each specialist takes up his part of the spec (UI, middleware, backend) and cranks out code. So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. In exchange, the team agrees to show each piece of working code to the product manager for his approval.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

FEBRUARY 10, 2009

Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Code reviews and pairing Great practices. That’s 6 deploys an hour.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. Four Steps primarily centers its stories and case studies on B2B hardware and software startups. You can imagine how well that worked.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. But there is more to technical debt than just the interest payments that come due. Unfortunately, customers hated that initial product.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

wordsting.com

APRIL 4, 2013

Rigorously simple copywriting for software products. Fat startup: Learn the lessons of my failed Lean Startup. by Word Sting in Lean Startup , Software copywriting , Copywriting for startups. Many software copywriters or developers dream of building their own company. April 1, 2013. My co-founders and I did.

Lean 61

Lean Startup Software Review San Francisco 61

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. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

DECEMBER 7, 2008

When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look. Hes just as comfortable writing code as racking servers, debugging windows drivers, or devising new interview questions. He throws off volumes of code, and it works.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. I have a lot of good news to report on this front. You can click here to learn more.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Hearpreneur

DECEMBER 29, 2021

This will help those who lost work due to the pandemic. 7- Providing employee engagement software. My #1 goal for 2022 is to help my company become the number one provider of employee engagement software. It's important to keep business agile. Your customer is the determining factor in whether or not you succeed.

Entrepreneur 137

Entrepreneur Social Media Employee Los Angeles 137

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

steveblank.com

JULY 8, 2011

Home Books for Startups Guide Secret History-Bibliography Steve Blank Startup Tools Steve Blank Entries RSS | Comments RSS Email Subscription Get Steve Blank via your RSS Feed RSS - Posts RSS - Comments Categories Air Force (12) Ardent (10) Audubon (1) Big Companies versus Startups: Durant versus Sloan (39) Business Model versus Business Plan (..)

Software Review 110

Software Review Startup Silicon Valley Analytics 110

A Smart Bear: Startups and Marketing for Geeks

APRIL 5, 2010

When we demand overwhelming customer outcry before committing to the slightest product change, we're in danger of losing the value of creating a cool feature that takes too much effort but people just love. We're "lean" but we're not stirring hearts. Code Historian was my first product. We're effective but not playful.

Software Review 226

Software Review Metrics Lean Algorithm 226

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. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.

San Francisco 133

San Francisco Lean Technical Review Software Review 133