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. This engineering manager is a smart guy, and very experienced.

Software Review 164

Software Review Engineer Management Technical Review 164

Hearpreneur

DECEMBER 30, 2020

I realized that this was an opportunity to solve a huge problem for an entire generation of parents and their kids using technology. 3- Create a unique product. Thanks to Jen Ohlson, Interactive Health Technologies ! #5- Due to business, I am free to spend my time and money as I see fit. the golden era of technology.

Technical Review 144

Technical Review Entrepreneur Software Review SEO 144

David Teten

AUGUST 19, 2019

We have a special program if you are pre-seed and need product development. Since 2017 we’ve managed $3 million in revenue-based financing, which helps cash-strapped technology companies grow. Investment Criteria: B2B SaaS or tech-enabled services with proven, recurring contracts. Alternative Capital. “

Revenue 60

Revenue Technical Review Software Review Equity 60

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Five Whys has its origins in the Toyota Production System. Five Whys has its origins in the Toyota Production System.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Steve Blank

APRIL 23, 2018

A version of this article appeared in the Harvard Business Review. Sloan Foundation , the Sloan School of Management at MIT , the Sloan program at Stanford , and the Sloan/Kettering Memorial Cancer Center in New York. Elon Musk, Alfred Sloan, and entrepreneurship in the automobile industry. There’s the Alfred P.

Michigan 291

Michigan Cofounder Stock Forecast 291

Transformify

MARCH 14, 2020

These days, due to coronavirus outbreak, many businesses have asked their employees to work from home. At the same time, the stock markets collapsed, and most businesses already report skyrocketing losses, unmet revenue targets and insufficient stock due to production slow down in China, India and the rest of the world.

Hiring 98

Hiring Bulgaria Italy Spain 98

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. What started as a technical problem actually turned out to be a human and process problem. We didnt even practice TDD across our whole team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Steve Blank

NOVEMBER 24, 2010

The United States is now a debtor nation to China and that the bill is about to come due. This doesn’t mean just more technology stuff, though we’ll get that. Over the last half a century, Silicon Valley has grown into the leading technology and innovation cluster for the United States and the world. Starting now.

Silicon Valley 335

Silicon Valley United States Venture Capital Software Review 335

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. This is the approach of test-driven-development (TDD).

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 7, 2010

Lessons Learned by Eric Ries Thursday, January 7, 2010 Is Entrepreneurship a Management Science? for Harvard Business Review) Im excited to have just published the first of several articles on entrepreneurship for the Harvard Business Review online. Is Entrepreneurship a Management Science? - Without further ado.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

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. Its common to find a hacker at the heart of almost any successful technology company. The last thing you need is a manager telling you how to do your job.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 11, 2009

Lessons Learned by Eric Ries Friday, September 11, 2009 The cardinal sin of community management Once you have a product launched, you will the face the joys – and the despair – of a community that grows up around it. This probably sounds illogical. We were totally unprepared for the magnitude of what happened.

Community 158

Community Management Lean Software Review 158

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. As a technical fix, it was brilliant.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

mashable.com

JUNE 11, 2013

Contact Contact Us Submit News Submit a Bug. If you dont manage this expectation upon hiring, you will be managing employee issues six months down the line. Those issues will eat into your time, and time is money for a new CEO." — Kellee Khalil , Founder/CEO, Lover.ly. "How Follow @mashable. see more > Search.

Cofounder 111

Cofounder Technical Review Startup Software Review 111

Hearpreneur

FEBRUARY 14, 2018

Thanks to Cynthia Brown, Only Top Reviews ! #4- 4- Home technologies. I run an early stage-startup called Smarthome NX that helps consumers discover Smart home technologies through content, collaborative partnerships and commerce. Due to the need of having to market myself, I learned social media and SEO. 14- Fiverr.

Entrepreneur 73

Entrepreneur Technical Review SEO New York City 73

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. Let me quote an example that I used recently: Remember IMVUs initial IM add-on product?

Software Review 87

Software Review Design Software San Francisco 87

David Teten

OCTOBER 1, 2015

You’ve got a great idea and domain expertise, but limited money and insufficient technology resources. Should you co-found your company with a software development shop? incubators, e.g., the many options in New York. intrapreneurs, e.g., the employee of GE who is tasked with launching a new business.

Software Developers 60

Software Developers Software Development Software Review Technical Cofounder 60

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. 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. If thats true, its primarily due to your hard work, building companies and testing new ideas.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. Amazing lean startup resources Is Entrepreneurship a Management Science?

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

AUGUST 3, 2009

We have to manage to learn something from our first product iteration. Without further ado, the video: Slides are below: Minimum Viable Product View more presentations from Eric Ries. Labels: minimum viable product , slides , video 13comments: Alan Pinstein said. Thanks Eric. Robert August 25, 2009 5:25 AM Bernard said.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

JANUARY 12, 2010

Rather, I see it as a reflection of a worldwide openness to new ideas about entrepreneurship. Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JULY 2, 2009

The person running the meeting does not have to be a manager or executive. That’s because Five Whys will often pierce the illusion of separate departments and discover the human problems that lurk beneath the surface of supposedly technical problems. This should make it easy to get buy-in from other managers or executives.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Good managers work hard to create an environment where this courage thrives.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JANUARY 15, 2010

Lessons Learned by Eric Ries Friday, January 15, 2010 Two Ways to Hold Entrepreneurs Accountable (for Harvard Business Review) The next part in the series I am writing for Harvard Business Review is online. Safely because it is clear that the manager in question didnt do his homework. Leave a comment or reply to someone else.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JANUARY 30, 2009

Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. 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.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

bhargreaves.com

MARCH 7, 2010

The reasons why I am not a big fan of development shops are too numerous to go into here. In brief, startups succeed because there is strong alignment of interests among all parties, especially with the people who are actually building the product. You probably aren’t the best person to hire and manage a developer.

Hiring 40

Hiring Technical Review Agile Software Review 40

Hearpreneur

DECEMBER 24, 2017

We managed to automate 25% of our bookings and achieved higher ratings than before. I’m no stranger to startups, having launched my digital marketing agency Creative Click Media from the ground up in 2011, but tackling an ecommerce yoga business was a completely new entrepreneurial adventure for me. Photo Credit: Rune Sovndahl.

Las Vegas 88

Las Vegas Entrepreneur Software Review Community 88

Startup Lessons Learned

FEBRUARY 11, 2009

Heres the short version: hire people from the online communities that develop free software. Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Ignore the famous people who are busy giving lots of speeches about how technology X will change the world.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

NOVEMBER 17, 2008

Id like to talk about a technique Ive used to help manage this growth without slowing down. Playing with new technologies. Managers in this area have to take a portfolio approach, promoting ideas that work and might make good candidates for further investment. Seeing whats possible. Building and testing prototypes.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. Or follow all of the New York Times columnists equally? There are too many products clamoring for attention.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

FEBRUARY 10, 2009

Code reviews and pairing Great practices. They’ll increase code quality, prevent defects and educate your developers. This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. If a feature worked, wed keep it. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

FEBRUARY 20, 2009

Similar results apply in product management, design, testing, and even operations. So when we start checking in code more often, release more often, or conduct more frequent design reviews, we can actually do a lot to make those steps dramatically more efficient. Interesting post. February 21, 2009 4:10 PM Anonymoussaid.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Amazing lean startup resources Is Entrepreneurship a Management Science? Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

MARCH 22, 2010

Part of this is due to their determination to overtake us, but part is due to structural changes in the nature of entrepreneurship. The United States is locked in a new arms race for that most precious resource -- the future entrepreneurs upon whom economic growth depends. But today, it is getting harder and harder to maintain.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

OCTOBER 5, 2009

Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. Managing these situations is hard for any company, but potentially lethal for a startup. Lessons Learned by Eric Ries Monday, October 5, 2009 The curse of prevention Beware!

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133