Gust

APRIL 27, 2014

This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. If you are contracting or outsourcing, this is even more important.

Startup 187

Startup Institutional Investors Angel Investor Bootstrapping 187

David Teten

APRIL 1, 2021

Nick Kim , Crosscut’s Head of Platform, in his presentation at the 4th Annual VC Platform Summit, shared their Platform development methodology, which he viewed as an exercise in product development. For example, recruiting writ large is useful at all stages of development. Organize events in your vertical.

Private Equity 78

Private Equity Venture Capital Portfolio Equity 78

YoungUpstarts

JUNE 11, 2015

Once upon a time, your company may have been able to shake it off if you threw a marketing idea against the wall and found it didn’t stick, or developed a line of products customers didn’t seem to like. Develop products customers want. That’s not true anymore. The bottom line?

Analytics 100

Analytics Customer Acquisition Metrics 100

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. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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

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. Although it costs to pay down the principal, we gain by reduced interest payments in the future.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Steve Blank

MARCH 4, 2014

These groups are adapting or adopting the practices of startups and accelerators – disruption and innovation rather than direct competition, customer development versus more product features, agility and speed versus lowest cost. They measure their success on metrics that reflect success in execution, and they reward execution.

IRR 335

IRR Startup Business Model Agile 335

Startup Lessons Learned

APRIL 29, 2013

Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. Most commonly, that’s uncertainty about whether you can build the product at all (what MBAs call “technical risk”) or whether anybody will use or buy it (“market risk”).

Lean 165

Lean Technical Review Startup Software Review 165

Up and Running

JULY 26, 2016

Just for reference, Slidebean is a SaaS presentation software where users can add content, and a finished presentation is designed automatically. 1x hacker in charge of product/development. 1x hipster working with both product and growth. Nov-15: Graphic Designer (growth/product).

Revenue 60

Revenue Acquisition Channel Campaign 60

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 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

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

APRIL 14, 2009

Every board meeting, the metrics of success change. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. And what of the product development team? Our cost to acquire a customer on AdWords was only a few cents. Go on an agile diet quickly.

Customer 167

Customer San Francisco Lean Hockey Stick 167

YoungUpstarts

JULY 7, 2017

To put a finer point on it, we have found that when you adhere to the following three demand-based priorities companies can drive growth while saving 20% or more of total costs – costs that are often completely overlooked through traditional cost-savings mechanisms. Complexity in the system explodes, as do costs.

Green 133

Green Demand Dividend Metrics 133

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. Thats why we need continuous integration and test-driven development.

Software Review 164

Software Review Engineer Management Technical Review 164

Steve Blank

MARCH 11, 2015

And worse, even if someone does manage to start something new, our management structure has so many financial, legal and HR hurdles that every initiative needs to match our existing business financial metrics, processes and procedures. Startups have finite time and resources to find product/market fit before they run out of money.

Widget 120

Widget Lean Business Model Metrics 120

Startup Professionals Musings

MAY 4, 2014

This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. If you are contracting or outsourcing, this is even more important. Marty Zwilling.

Startup 268

Startup Institutional Investors Angel Investor Bootstrapping 268

Startup Lessons Learned

NOVEMBER 14, 2013

Starting on the evening of December 11 and running through December 13—for VIP pass holders only—we’re partnering with UP Global’s Startup Weekend to offer a two-day Lean Startup immersion program , specially designed to teach you how to put Lean Startup theory directly into practice.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

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

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

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 133

Silicon Valley RSS California Customer Development 133

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. Startup Lessons Learned - the Conference (April 23.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

AUGUST 2, 2008

It costs not just the time of the actual meeting, but the time getting there and back, and the time preparing for it beforehand and thinking about it afterward. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Professionals Musings

JANUARY 31, 2013

This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. If you are contracting or outsourcing, this is even more important. Marty Zwilling.

Institutional Investors 230

Institutional Investors Angel Investor Bootstrapping Database 230

Startup Lessons Learned

JANUARY 14, 2015

Instead of taking one big swing with the launch of a new product—devoting months to the design of one technical feature or spending years in stealth mode developing a product without evidence that customers want it—it is an iterative approach to learn who the customer actually is, and what’s honestly required to delight them.

Stealth 60

Stealth Engineer Leadership Design 60

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

NOVEMBER 7, 2008

We spent weeks working on this new product, racing the clock so it would be done in time for the real presidential debates. We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. I used to use $.05,

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Seeing Both Sides

FEBRUARY 25, 2016

By viewing product development and marketing as integrated functions, not silos, leading tech companies like Facebook and Pinterest are rethinking their approach to driving growth and achieving breakthrough results. Cost to execute the test. Confidence that the test will yield a successful result.

Management 20

Management Analytics Technical Review Framework 20

Seeing Both Sides

FEBRUARY 25, 2016

By viewing product development and marketing as integrated functions, not silos, leading tech companies like Facebook and Pinterest are rethinking their approach to driving growth and achieving breakthrough results. Cost to execute the test. Confidence that the test will yield a successful result.

Management 20

Management Analytics Technical Review Framework 20

Startup Lessons Learned

AUGUST 24, 2009

As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. Despite all the energy invested in talking to authors about the size of their platform, very few gatekeepers have a rigorous set of metrics for measuring it. Ever-more artists and authors are petitioning them.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Lean startups have the ability to use this commodity stack to lower costs and, more importantly, reduce time to market.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Professionals Musings

SEPTEMBER 7, 2011

This will include the first version of many critical processes that can be split out later, including market opportunity, requirements, product definition, business model, sales process, and organization. Product development process. Hobbies can be a lot of fun, but they usually cost money rather than make money.

Startup 255

Startup Institutional Investors Angel Investor Bootstrapping 255

ConversionXL

AUGUST 30, 2018

It slows product development. It costs money. The key is to connect user research to an improved user experience and, in turn, an increase in customer retention, leads, or any other metric for which C-suite members are accountable. When you want to fine-tune your design by testing prior decisions.

Design 111

Design Framework Product Development Technical Review 111

Startup Lessons Learned

MARCH 29, 2010

"If you just throw a minimum viable product out the door to see what sticks, wont that necessarily be ugly and badly designed? Is design important to lean startups? And do I still need to get out of the building if Ive got great metrics and surveys?" Is design important to lean startups?

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

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. Startup Lessons Learned - the Conference (April 23.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

JULY 3, 2009

If your practice is not designed to cope with uncertainty, it has no place in a startup - even if your startup is located in government or enterprise. Although there is cost and overhead associated with continuous deployment, the benefits are immense. Yet, I think this definition is too important to leave out. Danger, Will Robinson.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

A Smart Bear: Startups and Marketing for Geeks

MAY 1, 2012

Many more die that way than die because the product sucks or doesn’t have enough features or because they don’t have a staff designer. For example, the average cost of customer acquisition diminishes. If the cost of support is high, A will kill profitability and B wins.

Customer 320

Customer Revenue Acquisition Cofounder 320