Startup Lessons Learned

NOVEMBER 8, 2008

When creating a new market, expect to spend as long as two years before you manage to get traction with early customers, but enjoy the utter lack of competition. Our goal in product development is to find the minimum feature set required to get early customers. Tom Peters called the Management By Walking Around - MBWA.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

APRIL 26, 2009

The idea of leverage is simple: for every ounce of effort your product development team puts into your product, find ways to magnify that effort by getting many other people to invest along with you. It has to be found and managed. Amazing lean startup resources Is Entrepreneurship a Management Science?

Product Development 88

Product Development Developer San Francisco Product 88

Up and Running

MAY 6, 2015

Twenty-three year-olds in New York City running a small business. Also think about, Jonathan, you manage our social media presence among other things and so you understand more than ever it’s really about getting those specific posts out to people through those channels, through email and that’s very much the same thing.

SBA 60

SBA Technical Review Software Review Small Business 60

trada.com

APRIL 7, 2010

Every new thing you take on requires time and effort. Not just to create but to constantly manage and evolve forever in an ongoing fashion. those who won’t give you a break if you screw up), you need process and infrastructure to manage this. You have to get involved and involvement takes time. Email and phone cover the rest.

Stealth 40

Stealth PPC Advertising Conversion 40

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. Managing timelines instead of queues. Inflexibility.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 29, 2008

Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. Communication.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. The last thing you need is a manager telling you how to do your job. If youve ever been abused by a bad manager in your career, its easy to become traumatized.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Seeing Both Sides

SEPTEMBER 15, 2015

This post was co-authored with Omri Stern and originally appeared in Harvard Business Review. The common approach is to incubate the business locally in Israel with a small development team, prove early product/market fit, and then build a sales and marketing organization abroad, usually in the U.S.

Cofounder 20

Cofounder Technical Review United States 20

techcrunch.com

OCTOBER 23, 2010

SVASE or Founder Dating in Silicon Valley, First Tuesday in London and Hackers and Founders in New York all come to mind. Team with co-workers at your current job or that internship you did last summer. Other cities like New York, Boston, Seattle, LA and Austin TX also have pretty strong startup communities.

Cofounder 66

Cofounder Founder Silicon Valley Technical Cofounder 66

Both Sides of the Table

MAY 7, 2011

Joel moved to Seattle, and worked at Microsoft for three years as a program manager on Excel 4.0 Joel met his co-founder for Fog Creek software and learned a valuable management lesson. While it was not a widespread problem, there was an element of micro-management at the wrong levels. 15 minutes. Pricing information.

Software Review 285

Software Review Software St. Louis API 285

sivers.org

JUNE 25, 2010

They log in to translate the documents, one at a time, marking each finished when done, which sends the file back to the company for review.” Also important: Only go for providers who have great reviews from many past customers. Decline bids from providers without many great reviews. The translator rejects or approves.

CTO Hire 84

CTO Hire Hiring Software Review Technical Review 84