Startup Lessons Learned

NOVEMBER 7, 2008

Most of the time, the experiments you run will have a zero percent conversion rate - meaning no customers were harmed during the making of this experiment. I would aim to get no more than 1o0 clicks per day - over the course of a week or two, youll get pretty good conversion data. Measure conversion rates. Expo SF (May.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

ConversionXL

FEBRUARY 28, 2017

You will also likely need help along the way, whether it comes in the form of a co-founder or a product team. This type of agile thinking is what matters. Most of the time, the experiments you run will have a zero percent conversion rate – meaning no customers were harmed during the making of this experiment.

Product 48

Product Audience Stock Conversion 48

Startup Lessons Learned

MARCH 25, 2010

Heres an excerpt: The Startups Rules of Speed - The Conversation - Harvard Business Review Every startup that achieves success eventually faces a critical moment — whether to speed up or slow down. Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. This is the speed-up-or-slow-down moment.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. 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. Side-effects that reduce agility are the most damaging symptoms of technical debt.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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.) Their engineers hated us. The Customer is a Genius Then instead of talking about our products he segued the conversation into their products.

Technology 143

Technology Silicon Valley Fractional VPE Part-Time VPE 143

Startup Lessons Learned

JANUARY 7, 2010

Id be honored to have you join the conversation. The Conversation - Harvard Business Review For most of us, the phrase management science conjures up a decidedly non-entrepreneurial image, and for good reason. Read the rest at The Conversation - Harvard Business Review. Id be honored to have you join the conversation.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

MAY 31, 2010

I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. Nothing is more demoralizing to an engineering team. Ive been there: is it me or my cofounder thats crazy? jellytheory : Ask WHY?

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

MARCH 17, 2009

Im excited that well get more than the usual few minutes of Q&A, so come with a healthy appetite for conversation. If you or your company is interested in sponsoring someone with a scholarship to travel to the expo and contribute to the conversation, please leave a comment or let me know. You heard me right. Expo SF (May.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. This is an incredible skill, one that most engineers overlook. These founders have not managed, to borrow a phrase from Steve Blank , to create a scalable and repeatable sales process.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JULY 5, 2010

I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. It is written in a conversational tone, doesnt take itself too seriously, and avoids extraneous fluff. I think theyve succeeded. The Entrepreneur’s Guide is an easy read. Expo SF (May.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

OCTOBER 28, 2008

whos on the engineering team? Most important slide: demo (if the product solves an obvious problem), engineering resumes (if the product is nearly impossible to build), " day in the life of a customer " (if neither of the above) Breakthrough technology Key questions: who owns the patents? how do you know anyone would want it?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

www.women2.org

MARCH 8, 2012

female founders. founder friday. Lessons learned from female founders and women entrepreneurs. Startup Quote: Wendy Tan White on Building a Successful Startup » FounderDating: How I Found My Co-Founder. Tweet By Elizabeth Knopf (Co-Founder & CEO, Sorced). Conference 2012.

Cofounder 47

Cofounder Technical Review San Francisco Founder 47

Startup Lessons Learned

JANUARY 15, 2010

Two Ways to Hold Entrepreneurs Accountable - The Conversation - Harvard Business Review Way back when the money was doled out, the team made a compelling pitch about the large market that was going to adopt their new innovative product or service. Leave a comment or reply to someone else. Fostering that dialog is important. Expo SF (May.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Hearpreneur

JANUARY 21, 2017

They do a great job at building an amazing culture, and they are able to keep a small company feel in terms of speed and agility because they keep the teams small and have basically broken the company up into a whole bunch of companies. 11 – US Army Classified as a Computer Engineer. That exit conversation was memorable.

Entrepreneur 48

Entrepreneur Investment Bankers PR Social Media 48

SoCal CTO

FEBRUARY 13, 2013

I did a presentation this week at Coloft that looked at how Non-Technical Founders can go about getting their MVP built. Examples might be a recommendation engine, search engine, matching engine or something with a complex interface. And the back-end is something that a non-technical founder can manage.

Technical Cofounder 338

Technical Cofounder Technical Review CTO Hire Fractional CTO 338

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

SEPTEMBER 15, 2008

It was actually my co-founder Will Harvey who taught me to present this data in the simple format weve discussed in this post. You need to make sure you dont get away from trying bold new things, using some combination of your vision and in-depth customer conversations to come up with the next idea to try. Expo SF (May.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MAY 14, 2009

Through case studies, exercises, and discussions, Eric Ries will guide entrepreneurs of all stripes through the key areas that determine success for startups: product, engineering, QA, marketing, and business strategy. We changed our model to B2B and adopted Agile around 2002. Twitter about it or post it to a social media site?

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

JUNE 5, 2009

I think this idea is particularly appealing to those of us from an engineering background. For example, say that your business model calls for a 4% conversion rate – as ours did initially at IMVU. After a few months of early beta at IMVU, we discovered that our actual conversion rate was about 0.4%. Expo SF (May.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

MARCH 29, 2010

Weve gone from total obscurity to something people are beginning to misunderstand and even co-opt. The way forward requires getting everyone together in a room, and having a conversation about where were headed. If a relatively small number of highly-motivated entrepreneurs attend, then well have an intense and intimate conversation.

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

JANUARY 19, 2009

Returning to our example of the beleaguered founder who still has the pager, before hiring an operations guy, try promoting someone from within to take on the job. Given that most recruiting channels are pay-for-performance, its usually cheaper, too, because it has a lower conversion rate. Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

MAY 22, 2020

They co-founded it with former U.S. Jen is the founder and former executive director of Code for America. She was an engineering and product executive at Stripe and Facebook. You can listen to our conversation on Apple Podcasts , Google podcasts , or wherever else you like to download podcasts. Digital Response.

New Jersey 60

New Jersey Government CTO America 60

Startup Lessons Learned

APRIL 2, 2010

By all accounts, the conversation was a success. By all accounts, the conversation was a success. ► 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. Expo SF (May.

San Francisco 149

San Francisco Continuous Deployment Lean DC 149

Austin Startup

FEBRUARY 25, 2019

Their mission is to allow scientists and engineers to focus on the fundamental research needed to solve complex problems without the expensive and difficult data management usually required. This includes co-founders, management, team member, board members, investors, clients, etc. CEO Higinio O.

Open Source 48

Open Source Startup Caching Database 48

SoCal CTO

APRIL 28, 2014

I guess it should not be a surprise that Founders have lots of challenges working with developers. Challenges I started by asking the founders in the room to tell me some of the challenges they have working with developers. Developers (and Founders) are challenged to know how much is okay in terms of bugs.

Technical Cofounder 280

Technical Cofounder Developer Fractional CTO CTO Hire 280

Startup Lessons Learned

AUGUST 24, 2009

So I generally feel right at home in these conversations. If you want to get ahead in this new world, agile is already not agile enough, lean is too fat and investing money in processes which tell you whether you're doing the right thing will put you on the right track but not out in front. Expo SF (May.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MARCH 11, 2010

The Conversation - Harvard Business Review : Still, startups develop some kind of process — whether its disciplined, haphazard, bureaucratic or empowering — because building a great product depends on it. The Conversation - Harvard Business Review For Startups, How Much Process Is Too Much? Expo SF (May.

San Francisco 120

San Francisco Continuous Deployment Lean DC 120

A Smart Bear: Startups and Marketing for Geeks

OCTOBER 4, 2017

Idealistic founders believe they will break the mold when they scale, and not turn into a “typical big company.” Or it’s fatal because that was a co-founder. “The future is inherently unpredictable,” insists the small company, spurred on by Lean and Agile mindsets. It never works like that.

Government 223

Government Startup Cofounder Technical Support 223

Startup Lessons Learned

MARCH 28, 2010

This conference will be the first of its kind: an opportunity to have a conversation about the future of the lean startup movement. We want everyone who can contribute to that conversation to be there, regardless of their ability to pay. Im hopeful that other companies will step up and become scholarship sponsors, too. Expo SF (May.

Lean 109

Lean Programming San Francisco Continuous Deployment 109

Startup Lessons Learned

MARCH 6, 2010

Lessons Learned by Eric Ries Saturday, March 6, 2010 Startup Visa update As I write this, I am traveling at 30,000 feet on Virgin Americas excellent IAD->SFO nonstop, following an intense few days of conversations in Washington, DC about the Startup Visa. No departments The Five Whys for Startups (for Harvard Business R. Expo SF (May.

San Francisco 113

San Francisco DC Washington Startup 113

Startup Lessons Learned

AUGUST 16, 2010

Rashmi Sinha, co-founder and CEO of SlideShare , describes an early version of the analytics package that’s part of the Pro accounts the company announced today. ’&# They removed the core plan, and conversions went up. Eric] “The first user experience was actually terrible.&#

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 8, 2010

Entrepreneurs: Beware of Vanity Metrics - The Conversation - Harvard Business Review : The idea is simple. Read the rest of Entrepreneurs: Beware of Vanity Metrics at The Conversation on Harvard Business Review. Entrepreneurs: Beware of Vanity Metrics - The Conversation - Harvard Business Review : The idea is simple.

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

ConversionXL

AUGUST 12, 2020

Hayes explained how to persuade the C-suite when data alone isn’t enough: If you can’t win the argument on data alone, I’ve found that modeling an improved conversion rate based on incremental customer experience improvements can get the wheels in motion. agile methodologies, aligning tools stacks). Image source ).

Customer 74

Customer Conversion Dividend Software Review 74

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. Thats why its so essential to have a co-equal problem team.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

OCTOBER 30, 2008

Everyone from the receptionist to engineers is selling. How do you drop a phrase like "voluntary salary reduction tool" and then not describe it :) Unless youre simply talking about the standard "hey, take less cash and Ill give you more options" type conversation. Reprioritize & rerationalize all R&D. Expo SF (May.

Lean 121

Lean San Francisco Continuous Deployment DC 121

SoCal CTO

DECEMBER 1, 2010

Equity-Only CTO and Equity-Only Developers - SoCal CTO , November 1, 2010 I had a recent email dialog with the founder of a company looking for a CTO for their startup. And I tried to evaluate the idea and figure out: What did the founder really need here? Was it a Startup Founder Developer Gap ? This post is an accusation.

Technical Review 175

Technical Review Technology Product CTO Hire 175