Steve Blank

NOVEMBER 24, 2010

the failure rate of new ventures (startups had no formal rules and were a hit or miss proposition), the slow adoption rate of new technologies by the government and large companies. The founders were simply wrong about their assumptions about customer needs. The effort that went into making all those unused features was wasted.

Silicon Valley 335

Silicon Valley United States Venture Capital Software Review 335

Steve Blank

JULY 13, 2021

That is until 1947 when Myles Mace taught the first entrepreneurship course “Management of New Enterprises” at Harvard Business School. In 1953 Peter Drucker offered an Entrepreneurship and Innovation class at New York University, and in 1954 Stanford’s business school offered “Small Business Management” its first small business course.

Lean 433

Lean Agile Business Model Business Plan 433

Startup Lessons Learned

APRIL 25, 2011

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. The number of Lean Startup meetup groups has crossed 100, spreading out from traditional startup hubs like San Francisco and New York to a wide variety of places.

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

crowdSPRING Blog

APRIL 13, 2010

These posts and videos are about design, startups, entrepreneurship, small business, leadership, social media, marketing, and more! 5 Photoshop & CSS Tricks for Killer Web Designs – [link]. The Dying Art Of Design – [link]. 30+ Excellent Photoshop Web layout Design Tutorials – [link]. – [link].

Social Media 95

Social Media Small Business Design Media 95

crowdSPRING Blog

APRIL 13, 2010

These posts and videos are about design, startups, entrepreneurship, small business, leadership, social media, marketing, and more! 5 Photoshop & CSS Tricks for Killer Web Designs – [link]. The Dying Art Of Design – [link]. 30+ Excellent Photoshop Web layout Design Tutorials – [link]. – [link].

Social Media 95

Social Media Small Business Design Media 95

Startup Lessons Learned

JULY 9, 2010

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. Are we solving the right problem? Are we solving the right problem? Expo SF (May.

San Francisco 161

San Francisco Management Founder Lean 161

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 argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Steve Blank

JULY 7, 2015

My guests on Bay Area Ventures on Wharton Business Radio on Sirius XM Channel 111 were: Eric Ries , entrepreneur and author of the New York Times bestseller, The Lean Startup. Jon Sebastiani , founder and CEO of KRAVE Jerky , a company that got its start in my class at Berkeley back in 2011 and was recently acquired by Hershey.

Lean 120

Lean Technical Cofounder Silicon Valley Channel 120

www.women2.org

MARCH 8, 2012

female founders. founder friday. Lessons learned from female founders and women entrepreneurs. WHATS HOT: EVENTS NEWS LEARN CAREER VIDEOS ESPAÑOL. Startup Quote: Wendy Tan White on Building a Successful Startup » FounderDating: How I Found My Co-Founder. Scoring Founder “Dates” On My Own.

Cofounder 47

Cofounder Technical Review San Francisco Founder 47

Steve Blank

NOVEMBER 15, 2010

In previous posts I’ve talked about what the combination of Business Model Design, Customer Development and Agile Methodologies mean to startups and intrapreneurs in large companies; it’s the beginning of entrepreneurship as a science with its own rules and methodologies. Teaching In the Big Apple.

Customer Development 270

Customer Development Business Model Developer Design 270

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 same process works in Interaction Design. This basic pattern is useful in all aspects of product development. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

mashable.com

JUNE 11, 2013

Or maybe the co-founders have a poisonous relationship that will hinder the companys growth. Check out the tips below from founders, CEOs and investors alike. Then remove half." — Jonathan Wegener , Founder, Timehop and ExitStrategy. ." — Jonathan Wegener , Founder, Timehop and ExitStrategy. Hiring Poorly.

Cofounder 111

Cofounder Technical Review Startup Software Review 111

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

JUNE 2, 2010

And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. No departments The Five Whys for Startups (for Harvard Business R.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

JANUARY 30, 2009

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. Labels: agile , customer development 5comments: William Pietri said.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Product development deals in designs, which are fundamentally intangible.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Thank you. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. A/B testing is set-based design. A/B testing is set-based design.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Ive attempted to embed the relevant slides below. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

NOVEMBER 8, 2008

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. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Austin Startup

MARCH 21, 2018

Four tips for any UX designer joining a start-up In January 2016 I joined one of the fastest-growing startups in surgical education. Here’s my advice for anyone designing a new product for a start-up: 1. I also meticulously dissected all the research that previous designers had done before me. Don’t wait?—?get

Design 54

Design Agile New York Programming 54

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

MAY 31, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Although many of the non-technical folks in the room didnt understand what was happening in the moment, plenty of hackers were on high alert.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. I will come back for more. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Your CTO might be a great architect, evangelist, interface designer or incredible debugger. Great piece!

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: 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. February 9, 2009 7:45 PM Joseph Flahiff said. Expo SF (May.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. Luckily for me, my co-founders eventually prevailed and we went on to build a product that customers actually wanted. Expo SF (May.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167