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. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. That meant getting designers, programmers, and QA folks to cross-train and work together as peers. .

San Francisco 113

San Francisco Silicon Valley Startup Continuous Deployment 113

Startup Lessons Learned

OCTOBER 4, 2008

In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. my startup is Blank Label (www.blank-label.com), which is a provider of custom dress shirts that empowers consumers to become the designer of their own product.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 15, 2008

The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

JULY 30, 2009

Traveling to new startup hubs is one of my favorite things about being able to do this full-time. I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. For what its worth, I like Silicon Mountain. Brad Feld also had some thoughts on this event on his blog.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. It strokes your ego. You might get a bunch of inbound emails from other press and partners, and all of these things can contribute to a feeling that you’re on your way to getting tons of traffic. .

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

APRIL 14, 2009

Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule. In fact, this company hasn’t shipped any new products in months. Go on an agile diet quickly. That leads to cashing many checks.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JANUARY 18, 2010

Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009. My transition to Continuous Deployment Prior to adopting continuous deployment, I used to release software on a weekly schedule (come rain or shine) which I viewed as pretty agile, disciplined, and aggressive.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

www.smashingmagazine.com

MAY 5, 2011

Most designers are familiar with the conventional ways. In this article, we’d like to present a couple of new ideas that might be useful for your next designs. Ask for a User Name After The User Has Signed Up Sign-up forms typically ask users to create a name that is unique to the website.

AJAX 104

AJAX Security Design Naming 104

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. Its one of the hardest things to see while its happening, and its one of the hardest mistakes to undo, because of the human and emotional costs of layoffs. Expo SF (May.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JUNE 5, 2009

We're starting our new business, fanminder.com, to help small merchants instantly communicate with their customers, and I'm increasingly hearing your name and reading your keen insights. I also think you're spot-on with the solution - viewing spreadsheets as big holes to fill in with early learnings. Expo SF (May.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Steve Blank

JUNE 1, 2017

By the end of the 19 th century mass circulation papers had developed the characteristics that your parents would recognize today—headlines, illustrations, entertaining stories – all designed to shortcut critical thinking, and stir passion and emotion to sell newspapers and, of course, advertising. And that was in New York City.

North Korea 252

North Korea Social Media .Net Europe 252

Hearpreneur

JUNE 21, 2017

My name is Lauren Pawell, and I’m the founder and owner of Bixa Media, a digital marketing agency focused on helping entrepreneurs generate and nurture more leads through their WordPress & Shopify websites. #15 I own a brand strategy agency in New York. Thanks to Harshit Jain, Hobbiesphere ! #10

Entrepreneur 51

Entrepreneur Africa Cofounder CTO Hire 51

Hearpreneur

SEPTEMBER 14, 2015

Not being caught up in a corporate management structure gives me the freedom and agility to be at the top of our game. I’ve taken a major risk (both financially & mentally) and surrendered my 15 year career in architecture & design, but my heart and mind are in this project every waking moment. 15 – Freedom.

Entrepreneur 48

Entrepreneur Fresno LLC Community 48

Duct Tape Marketing

JUNE 20, 2023

He is co-leader of the McKinsey Digital Practice, a senior partner based in New York, and a member of McKinsey’s Shareholders Council, the firm’s board of directors. He's a co-leader of the McKinsey Digital Practice, a senior partner based in New York, and a member of McKinsey's Shareholders Council.

Technical Review 66

Technical Review Silicon Valley Generative AI Arizona 66

crowdSPRING Blog

JANUARY 4, 2013

These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! Is Agile Marketing the Future of Search in 2013? The New York Times Paywall Is Working Better Than Anyone Had Guessed | Bloomberg – [link].

Social Media 100

Social Media Small Business Design Media 100

Startup Lessons Learned

AUGUST 3, 2009

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. MVP, despite the name, is not about creating minimal products. Revisiting the Software Design Manifesto (and what. Thank you. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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. Product development deals in designs, which are fundamentally intangible.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

FEBRUARY 7, 2010

If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. You can read about the latest iteration of the proposal at StartupVisa.com.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Eric Names matter. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. Rules of thumb can be infuriatingly unhelpful. And it’s really hard.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

FEBRUARY 11, 2009

The same is true of brand-name products in almost every category (and it can be measured ). Perceived value - This is the extra value a customer perceives as a result of good marketing, product design, product quality, or exception product/market fit. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 102

San Francisco Continuous Deployment Lean DC 102

Startup Lessons Learned

FEBRUARY 10, 2009

Heck, thats what it says right there in the agile manifesto. In a lot of cases, thats just a fancy name for revenue or profit, but not always. Labels: agile , continuous deployment , lean startup , product development , Test-driven development 4comments: Nivi said. But, unfortunately, startups cant afford to adopt that standard.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

bhargreaves.com

MARCH 7, 2010

Plus, most decent dev shops can point to at least a couple names of well-known previous clients. Actually any shop that does agile development with daily and weekly releases should. Scissor.com is another agile option. Agile dev shops should bring discipline and quicker results. I’m talking to them.

Hiring 40

Hiring Technical Review Agile Software Review 40

Startup Lessons Learned

MARCH 13, 2009

New York Times, Wall Street Journal, CNN, the works. Who doesnt want to see their name in print? Now that were beginning our first marketing, the key partners we need have heard our name long enough to trust us. Combining agile development with customer developm. See if their answer is about tactics or strategy.

San Francisco 168

San Francisco PR Lean Early Stage 168

Startup Lessons Learned

JULY 31, 2009

lets you post a description of a job without having to reveal the name of the company who is offering it, or the contact information of the hiring manager. Its incredibly simple, and its called joblink.tw. Think of it as a bit.ly Using it to recruit takes less than a minute. Who wants that stuff posted on the internet? Expo SF (May.

San Francisco 68

San Francisco Lean Startup Continuous Deployment 68

Startup Lessons Learned

OCTOBER 7, 2008

If necessary, consider doing this under a different brand name than the one you are wedded to using. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down?

San Francisco 68

San Francisco Lean Retention SEM 68

Startup Lessons Learned

AUGUST 1, 2009

My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Those new capabilities must translate into a constant stream of prototypes - most of which turn out to be utterly bad ideas. Discover whats in customers heads, and tackle problems where design is a differentiator.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

JULY 9, 2009

All the good domain names were taken, all the good ideas were being implemented. If Id bought just a handful of the "best of the rest" domain names that were available at the time (for a whopping $70 each), I probably could have just retired right then. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 94

San Francisco Lean Continuous Deployment DC 94

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible. “Who is this guy?&#

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JULY 2, 2009

Pay attention to whether people are comfortable “naming names&# in the meeting. Five Whys is designed to avoid these nebulous arguments. If new employees are causing problems, that will be a routine topic. Why didn’t our tests/QA/immune system catch and prevent the problem? Expo SF (May.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

DECEMBER 14, 2009

I had a lot of use for this concept back when I worked on game design and virtual worlds. In order to maintain game play balance, game designers have to take into account the needs of customers who have an excess of four different assets: time , money , skill , and passion. Having a balanced ecosystem is what game designers strive for.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

SEPTEMBER 22, 2008

We had all the tools in place but we didn’t actually practice agile development. No fancy tools needed here — it’s about the mentality, attention to detail, and the actions that foster agile development, not the tools & systems you set up in place to facilitate this. 1 comments: Josh Moore said. Expo SF (May.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 68