YoungUpstarts

FEBRUARY 28, 2018

by Steve Owens, Founder and CTO of Finish Line Product Development Services. This functional team philosophy is in contrast with the idea of a single person who, being smarter than all the rest makes all the crucial decisions. He has experience in Internet of Things, M2M, Oil and Gas, and Industrial Controls.

Startup 133

Startup Product Development Revenue Distribution 133

Startup Professionals Musings

JANUARY 12, 2018

The problem is that professional investors (angels and venture capital) want a proven business model before they invest, ready to scale, rather than early projections and product development. For the rest of us, the following suggestions will help you survive the valley of death: Accumulate some resources before you start.

Intellectual Property 134

Intellectual Property Technical Review Startup Incubator 134

Startup Lessons Learned

OCTOBER 5, 2008

I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Lets start with what the product manager does. This post has been removed by the author.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. Labels: product development Speed up or slow down? (for This is the speed-up-or-slow-down moment.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

OCTOBER 4, 2008

So if youre new, consider not paying any attention to the rest of this post, and just diving into the archives, if you havent already. Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 8, 2008

Ive been guilty of this many times in my career - its just so easy to focus on product and technology instead. True, there are the rare products that have literally no market risk; they are all about technology risk ("cure for cancer"). Our goal in product development is to find the minimum feature set required to get early customers.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 5, 2010

You can easily take from it whatever makes sense for your business, and leave the rest. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. You can easily take from it whatever makes sense for your business, and leave the rest.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

AUGUST 2, 2008

but rest assured they would be. 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. Take a look and let me know what you think.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

NOVEMBER 7, 2008

We run a web development company and we start by creating a splash page very similar to what is describe here. If we don't get a certain amount of signups on that splash page, we don't develop the rest of the site becuase they will not have any customer. June 22, 2009 6:30 AM Anonymoussaid.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

JUNE 2, 2010

One such technique is called Five Whys, which has its origins in the Toyota Production System, and posits that behind every supposedly technical problem is actually a human problem. Read the rest of The Five Whys for Start-Ups. Read the rest of The Five Whys for Start-Ups. Applied to a start-up, heres how it works.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

AUGUST 1, 2009

Even if SJ has some unique "process" that enables him to come up with killer products (I suspect he is just wired differently from most people and probably has no real idea of how he does it to a point where it is teachable), that doesn't mean that the Lean Startup/Steve Blank's ideas etc have less of a value for the rest of us.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JANUARY 7, 2010

Read the rest at The Conversation - Harvard Business Review. Read the rest at The Conversation - Harvard Business Review. So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. Is Entrepreneurship a Management Science? Take a look and let me know what you think.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

OCTOBER 6, 2008

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. The opportunity was just mind-bogglingly huge.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

MAY 31, 2010

You can read the rest of his posts on his blog : Introduction , Part 1 , Part 2.) You can read the rest of his posts on his blog : Introduction , Part 1 , Part 2.) All I can tell the folks who attended the simulcasts is that I’m not missing either the time or the money. Take a look and let me know what you think.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Entrepreneurs-Journey.com by Yaro Starak

OCTOBER 25, 2010

I felt a bit stagnant with what I was doing, so I decided that it was time to release a new product. This decision was made after listening to a podcast about product development and realizing that I really didn’t have a product. A few weeks ago, I decided to take on a new venture.

Product 87

Product Affiliate Advertising Technical Review 87

Startup Lessons Learned

FEBRUARY 22, 2009

We spent the rest of our time pretending to work on the assigned homework, but really trying to do interesting side projects, like sending juvenile messages across the school network or building primitive video games. No logins, no codes, just raw uncensored internet access. Take a look and let me know what you think.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

NOVEMBER 17, 2008

This technique rests on three things: identifying the kinds of work that need to get done, creating the right type of teams for each kind, and steering the company by allocating resources among them. Strategy - startups first encounter this when they have the beginnings of a product, and theyve achieved some amount of product/market fit.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JUNE 15, 2009

As a consumer internet company with millions of customers, it may seem to have little relevancy for an enterprise software company with only a handful of potential customers, or a computer security company whose customers demand a rigorous audit before accepting a new release. So new conflicts appear. Then the fun part begins.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Steve Blank

AUGUST 24, 2009

It’s been thirty years, but every once an awhile I still wonder what happened to the rest of their lives. Anybody with a sense of how the Internet works should have known that they couldn’t commit such open fraud on this scale and expect to get away with it. Instead, this is a culture clash.

Silicon Valley 215

Silicon Valley PR Technical Review RSS 215

Startup Lessons Learned

JANUARY 15, 2010

Read the rest here. Read the rest here. For a little while, the team can resort to the last defense of entrepreneurs in trouble: the promised hockey-stick. One thing that is often overlooked about the hockey-stick growth shape: its most distinctive characteristic is the long, flat part. Take a look and let me know what you think.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

AUGUST 24, 2009

But, as any startup can tell you, this opens up a tremendous set of opportunities for the rest of us. As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

MAY 7, 2009

Starting instead from a position where feedback cycle time is the priority and allowing quality to ratchet up as the product matures provides a more natural lead in to continuous deployment. The rest of the post, which you can read here , discusses the application of these principles to other contexts. I recommend you take a look.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

JULY 30, 2009

.&# In 2002 I became exposed to the idea of “agile software development&# and subsequently was a first round investor in Rally Software which is now the market leader in Agile application lifecycle management software. Read the rest. Weve got slides , video , audio and twitter commentary.

Lean 68

Lean San Francisco Continuous Deployment DC 68

www.kalzumeus.com

FEBRUARY 6, 2013

They permitted attackers to execute arbitrary code on virtually ever Ruby on Rails application, without requiring that the application do anything to enable the attack other than “be hooked up to the Internet.” In the worst case, attackers root every unpatched Rails app on the Internet. Was anyone actually compromised?

Security 101

Security Software Review Ruby Startup 101

adam.heroku.com

MAY 18, 2012

Everyone has to be a generalist and able to work on any kind of problem - specialists will be (at best) somewhat bored and (at worst) highly distracting because they want to steer product development into whatever realm they specialize in. Stage 2: The first hires.

Developer 92

Developer Database Architecture API 92

Startup Lessons Learned

MARCH 13, 2009

Here was our experience at IMVU, which I have seen replicated at many other consumer internet startups. Luckily, if your product isnt good enough to have traction, you simply cannot alienate very many customers - because you cant get them engaged with the product. The rest can believe what they want. Cannon said.

San Francisco 168

San Francisco PR Lean Early Stage 168

Hearpreneur

JULY 19, 2021

When everything rests on your shoulders, the fate of your company is in your control. The Internet wasn't as robust or developed as it is today. I never know if I will be wearing my marketing hat, my finance hat, my product development hat, or my lawyer hat. Photo Credit: Jeff Cooper. 27- The diversity it brings.

Entrepreneur 139

Entrepreneur Jordan Non-Compete Community 139

Startup Lessons Learned

SEPTEMBER 10, 2008

Heres my favorite part: If youve got a team, part of the team should obsess about the backlist, honing it, editing it and promoting it, while the rest work to generate (as opposed to promote) the frontlist. Thoughts on scientific product development Lo, my 5 subscribers, who are you? Take a look and let me know what you think.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

JANUARY 18, 2010

Unneeded features are waste and not only create more work but can needlessly complicate the product and prolong the "customer validation" phase. Build in response to a signal from the "customer", and otherwise rest or improve. Build in response to a signal from the "customer", and otherwise rest or improve.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Take a look and let me know what you think.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

JANUARY 2, 2009

For the rest of us, there is an alternative: to create credibility by building a lean startup. At IMVU, we were terrified by how early we shipped (and charged for) our first product. Frankly, we were embarrassed by how many bugs, crashes, and defects it had. Take a look and let me know what you think.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

DECEMBER 30, 2008

When doing the post-interview team meeting, it was common for the first opinion expressed about a candidate to become the prevailing opinion of the rest of the team members. The engineering team varied from 5-8 people, with a variety of skill-sets and personalities. The two rounds of questioning is a good idea for avoiding that.

San Francisco 83

San Francisco Lean Continuous Deployment DC 83

Software By Rob

MAY 21, 2010

They thought people would flock to their idea, fumbling for their credit cards the moment they heard someone had developed a re-tweeting cloud app for Facebook fan pages. But alas, being heard above the din of the internet is a tricky thing. Follow me Startups for the Rest of Us. Ask any startup founder.

Software Review 55

Software Review Startup RSS Software Development 55

Startup Lessons Learned

MARCH 4, 2009

If you are willing, please take a moment to fill it out before proceeding with the rest of the post; itll mean less biased results, and youll have a better idea what Im talking about later. It connects to the internet to automatically download the necessary codes. Before I go any further, heres the link to the new survey.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Professionals Musings

NOVEMBER 6, 2015

Once the rest of us reach a certain age, we know too many things that can go wrong, so we avoid the path entirely. The realities of new product development may require living on ramen noodles and sleeping on a cot in the back room for a week. The rest of us are waiting expectantly to see what you can do.

Entrepreneur 120

Entrepreneur Restful Social Media Community 120

37signals.com

DECEMBER 5, 2011

But don’t act like there wasn’t years of leveraging your online presence and your blog followers before that product launched. Most Internet marketing does not work that way. You’re essentially saying “Don’t worry about Internet marketing. it should relate to your product directly or indirectly.

Product Name 44

Product Name Naming Product Software Review 44

Software By Rob

NOVEMBER 18, 2008

It may wind up for sale on SitePoint , or it may be relegated to the bone yard of failed software products. The Upside The flip side to all of this is what you’ve already heard on the blogs of successful product developers. Once a product hits critical mass you’ve conquered the hardest part of the equation.

Software Review 42

Software Review Software Product Salary 42