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.

Vertical 147

Vertical Silicon Valley Marketing Customer 147

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. Reinertsen is the book for you.

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. After all, the worst kind of waste in software development is code to support a use case that never materializes.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JUNE 17, 2010

The team hired only the best and the brightest. They are leaders, visionaries, founders and managers having tremendous success. They either had to hire a developer onto the art team itself (unthinkable) or learn those development skills themselves (which was, to be fair, really hard).

Technical Review 164

Technical Review San Francisco Lean Software Review 164

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. Eric, Is this post about Architecture? Good luck, engineering manager.

Software Review 164

Software Review Engineer Management Technical Review 164

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

Steve Blank

SEPTEMBER 25, 2014

When I heard that Larry Ellison was stepping down as Oracle ’s CEO I asked Kathryn to think about the skills she saw in a young Larry Ellison that might make today’s founders winners. He reeled out that technical vision, described the product architecture in a way that computer science people found compelling and turned on the charm.

Technical Review 334

Technical Review Venture Capital Software Review Database 334

Startup Lessons Learned

SEPTEMBER 8, 2008

So one of the first things we did was to hire an Oracle expert and get to work. You dont need to invent a new architecture, and you dont need to even build your architecture up-front. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Were in a new wave of platform evolution.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

femgineer.com

JULY 18, 2010

If you’re a founder who is still trying to grasp the product roadmap and create a company vision its probably not a good time to hire an engineer. There are a lot of engineers out there who have been burned by founders who pull and push them in a variety of directions. Sweat equity or salary?

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.)

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

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

Startup Lessons Learned

JUNE 15, 2009

Both sides start to think of their point of view in moralistic terms: “those guys don’t see the economic value of fast action, they only care about their precious architecture diagrams&# or “those guys are sloppy and have no professional pride.&# No departments The Five Whys for Startups (for Harvard Business R.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

NOVEMBER 29, 2008

Lessons Learned by Eric Ries Saturday, November 29, 2008 The ABCDEFs of conducting a technical interview I am incredibly proud of the people I have hired over the course of my career. This second objective plays no small part in allowing you to hire the best. Hiring decisions are among the most difficult, and the most critical.

San Francisco 146

San Francisco Lean Agile Java 146

Seeing Both Sides

AUGUST 3, 2012

Technical founders Tom Leighton and Danny Lewin built the original prototype at their lab at MIT starting in late 1996 before raising capital, so in a sense Akamai’s Minimum Viable Product (MVP) was a prototype with the basic architecture and traffic mapping in place that validated algorithms for the founders and investors alike.

Distribution 49

Distribution Lean Massachusetts Cofounder 49

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? And we cant hire new engineers any faster, because you cant be interviewing and debugging and fixing all at the same time! Just change it.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Transformify

MARCH 5, 2020

Jordan Husney is the CEO & Founder of Parabol. He leads multiple facets of Parabol’s growth and success by overseeing new talent acquisition, funding and product development. Jordan, why do you hire gig workers and freelancers ? So again, we contract the work to someone outside of our internal team.

Hiring 80

Hiring Jordan Los Angeles Architecture 80

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

adam.heroku.com

MAY 18, 2012

Founders and early employees tend to be very self-directed so the need for management is nearly non-existent. Stage 2: The first hires. For example: full-fledged SCRUM, heavyweight tools like Jira, or hiring a project manager or engineering manager. Separately, you should have found your product/market fit by this point.

Developer 92

Developer Database Architecture API 92

Startup Lessons Learned

FEBRUARY 16, 2009

This is one of the most powerful aspects of web architecture, and it often gets lost in other client-server programming paradigms. As you suggest, Thought Experiment Part II is going to involve lots of changes to the classic MMO architecture that makes it more like the web. Thanks for the comments. Expo (and a call for he.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. ► 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.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

www.quora.com

JANUARY 16, 2011

Find Questions, Topics and People Add Question Add Question Non-Technical Co-Founders Co-Founders Technical Co-founders Finding Co-Founders Startups & "How Important Are Ideas?" " Web Development Startups Solo Founders I am a creative guy with a startup idea. Rockstar v.

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

Startup Lessons Learned

SEPTEMBER 8, 2009

I'll add two ideas: The modern structure of university patent licensing and technology transfer works really well in the life sciences and other fields with expensive product development processes. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

DC 90

DC Washington San Francisco SBIR 90

techcrunch.com

OCTOBER 23, 2010

So for this first post, here’s the best advice I can give you: join an awesome founding team and get your product out the door ASAP. One of the things I do as a founder of a later stage startup is to meet with early stage entrepreneurs to help them get their companies going. I don’t know any developers. and Google.

Technical Review 84

Technical Review Cofounder Technical Cofounder Software Review 84

Software By Rob

AUGUST 18, 2010

Before: After: And thenI ran into a Mixergy interview where 37signals founder, Jason Fried, talks about their free plan (6:00 into the interview): “… The majority of the revenues for our products come from people who sign up for the paid versions upfront. I saw that 37signals had hidden theirs. But is it the right data?

Software Review 78

Software Review Software Revenue Cofounder 78

Scalable Startup

FEBRUARY 1, 2013

In the last five years, there’s been this sort of acknowledgment of the consumerization of the enterprise, which is consumer product development, design methods applied to business software, of which SaaS and cloud and all these things are examples. It became very hard to get businesses to adopt new stuff.

Software Review 22

Software Review Startup Venture Capital Stock 22

Startup Lessons Learned

JANUARY 30, 2009

Hire the absolute best and the brightest, true experts in their fields, who in turn can hire the smartest people possible to staff their departments. By hiring experts, conducting lots of focus groups, and executing to a detailed plan, the company became deluded that it knew what customers wanted. We can skip the chasm.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Steve Blank

OCTOBER 26, 2020

He also said, “The most important hire I made in my time at the JAIC was the chief technology officer, Nand Mulchandani.” Nand changed the culture of the JAIC, bringing in Silicon Valley tools for product development, product management and for the first time a culture that focused on UI/UX, MVPs and continuous integration and deployment.

Artificial Inteligence 396

Artificial Inteligence Fractional CTO Technology CTO 396

Startup Lessons Learned

JANUARY 28, 2009

The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. On the other, they already have a team fully engaged on making their product architecture better.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79