Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

YoungUpstarts

APRIL 21, 2013

Through rapid experimentation, short product development cycles, and rigorous measurements of the right metrics, they can ascertain what customers really want. Customer development (the understanding of customer needs) must be married to agile development (a process which drives waste out of product development).

Lean 193

Lean Technical Review North America Startup 193

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. Eric, Is this post about Architecture? Good luck, engineering manager.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

The Next Web

DECEMBER 2, 2013

With the existing product in mind, the $500,000 would be broken out evenly over the nine months with the first two months dedicated to design, specifically user architecture, brand and polish design. But if you were to replicate the product exactly, all those decisions are made for you.

Cost 168

Cost San Francisco New York City Ruby 168

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Steve Blank

MAY 28, 2009

Market Risk vs. Invention Risk - Click to Enlarge For companies building web-based products, product development may be difficult, but with enough time and iteration engineering will eventually converge on a solution and ship a functional product - i t’s engineering, not invention.

Vertical 167

Vertical Silicon Valley Marketing Customer 167

Feld Thoughts

MAY 5, 2011

The first version of the product was based on an architectural approach that didn’t aptly satisfy all players in the ecosystem and wasn’t flexible enough. I expect we’ll look back on 2011 as the year that Gnip went from a highly product development focused company to a company that was firing on all cylinders.

CTO Hire 131

CTO Hire Cofounder Architecture Product Development 131

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

YoungUpstarts

APRIL 14, 2014

Not too long ago, German software giant SAP blew up the management framework for its 20,000-person development department and replaced it with “mini-teams” of roughly 10 people. As a result, product development time was cut nearly in half in a three-year period.

Agile 196

Agile Leadership Architecture Product Development 196

Andrew Payne

FEBRUARY 17, 2020

But this data highlights why the debate continues: highly productive developers (10x or otherwise) are problem-solving at a much higher level. They’re designing key abstractions that will pay dividends through the life of the project.

Software Review 111

Software Review Dividend Architecture Agile 111

Startup Lessons Learned

NOVEMBER 29, 2008

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. and going into a long diatribe about how insecure the ActiveX architecture was compared to Javas pristine sandbox. what happens if we have a pipelined architecture?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Steve Blank

JUNE 25, 2009

They couldn’t keep up with the fast product development times that were enabled by using standard microprocessors. So their management teams were insisting that they OEM (buy from someone else) these products. Convergent Technologies was one of those OEM suppliers. I was surprised to see that they were in the room.

Technology 145

Technology Silicon Valley Fractional VPE Part-Time VPE 145

Startup Lessons Learned

JUNE 17, 2010

I suggested that we change the underlying architecture of our UI system so that the artists would be able to build their own UI pieces themselves and then integrate them into the product without requiring new code every time. The engineering team wasn’t happy either. The engineering team wasn’t happy either.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Version One Ventures

APRIL 11, 2019

Architectural and software design integrity is very important to us. Typically, the solution will be presented in graphical form, such as a system architecture with flow diagrams. Above all, the purpose of product development is to create value for customers. Technical design quality. Not all code needs to be scalable.

Part-Time VPE 99

Part-Time VPE Software Review Engineer Technical Review 99

Hearpreneur

FEBRUARY 8, 2023

11- Architectural professional group Photo Credit: Claudia Torres Your CV will appear better, and you'll have the chance to network with other people who work in the architecture field if you join a professional club for architects. Thanks to Michael Dodd, Planning hub ! #11- Thanks to Claudia Torres, TheFab20s ! #12-

Community 117

Community Architecture Entrepreneur Networking 117

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. Wish I could figure out how to apply it to the average data warehousing project which has a single shareed database right at the heart of the entire solution.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 7, 2008

I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. When the architecture needs modifying - why do we need a meeting? Building a good application architecture is not just coding. The "just fix it" mentality is counter-productive here. Just change it.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

NOVEMBER 14, 2013

For example, in an enterprise context, moving to continuous delivery can mean making significant architectural changes and changing the culture of development, testing, and operations teams. Often the biggest problem is building up trust between the developers and the people who deploy and operate the systems.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Business Plan Blog

AUGUST 20, 2013

If you plan on doing it inhouse your CTO and the founders should be able to put together system requirements, technical specs and system architecture for you and then build wireframes and MVP if applicable. A technology plan can consist of: Technical Specs/High Level System Architecture (Web/Mobile, etc). Product Development Team.

CTO Hire 55

CTO Hire Fractional CTO Architecture Cofounder 55

Venture Chronicles

AUGUST 2, 2013

If we did anything egregiously wrong at Get Satisfaction in the 2010-1012 time period it was to under-invest in the product with the assumption that the existing product was good enough. and by framing it as a binary choice I am perpetuating the problem in many ways.

Product 62

Product CTO Hire Architecture Startup 62

Mike Michalowicz

SEPTEMBER 27, 2012

– born CEOs and heads of product development at successful companies, and learned that the average age of successful founders was 39. In the article ” The Case for Old Entrepreneurs ”, Stanford professor and Washington Post columnist Vivek Wadhwa shared a 2008 study researching the backgrounds of nearly 700 U.S.

Entrepreneur 123

Entrepreneur SBA Architecture Washington 123

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.)

Software Review 87

Software Review Design Software San Francisco 87

crowdSPRING Blog

OCTOBER 20, 2010

Information Architecture 101: Techniques and Best Practices – [link]. Amazon’s Approach to Product Development – [link]. Full Set Of Credit Card Icons By Graphicpeel – [link]. 10 Useful Free WYSIWYG HTML Editors For Web-Based Application – [link]. 4 Concepts for Simplistic Web Design – [link].

Social Media 91

Social Media Small Business Design Media 91

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

The Startup Magazine

FEBRUARY 12, 2024

Assurance of Quality The testing stage of the software product development process is vital. ZTA, or zero-trust architecture ZTA models differ from standard cyber security models, which depend on ongoing verification. It functions by causing the system to halt any strange or questionable transactions.

Artificial Inteligence 88

Artificial Inteligence Software Review Web API 88

Startup Lessons Learned

DECEMBER 28, 2009

Thats a perfectly reasonable reaction, given that most releases of most products are bad news. Even worse, the sad state of product development generally means that the new "features" are as likely to be ones that make the product worse, not better. Its likely that the new release will contain new bugs.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

ctotodevelopers.blogspot.com

JULY 11, 2012

The implementation and architecture can also suffer if the team under or over invests engineering time, implementation of standards, or testing discipline in the wrong areas. Left on its own, product owners and development teams just may make debatable and sometimes questionable decisions on priorities or implementation strategy.

Agile 40

Agile Architecture Offshore Software Developers 40

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

www.lanceglasser.com

MAY 13, 2012

Product development. Queuing theory and product development. The Essential Product Investigation Phase Gate. So you want to ship the product early? For how to manage that see, for instance, Queuing theory and product development or take some time to investigate resource management tools.)

CTO 40

CTO CTO Hire Technical Review Architecture 40

Startup Lessons Learned

JUNE 15, 2009

Both sides start to think of their point of view in moralistic terms: “those guys don’t see the economic value of fast action, they only care about their precious architecture diagrams&# or “those guys are sloppy and have no professional pride.&#

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Steve Blank

AUGUST 27, 2012

And the rule was we weren’t changing anything about the product architecture until Ben and I agreed. Second, that he needed to recognize that changing the value proposition – the features of the products/services he was offering – was a lot more traumatic for a startup than changing other parts of the business model. .”

Founder 323

Founder Cofounder Advisory Board Burn Rate 323

Startup Professionals Musings

MARCH 21, 2022

Everyone is predicting a rise in massive open online courses (MOOC) , that will drive the need for new course content, architecture, and delivery approaches. These shifts are independent of technology innovations, but certainly will drive the application of key product developments. Immigration: Continuing on the rise.

Architecture 258

Architecture Forecast Demand Technology 258

Startup Lessons Learned

FEBRUARY 16, 2009

This is one of the most powerful aspects of web architecture, and it often gets lost in other client-server programming paradigms. As you suggest, Thought Experiment Part II is going to involve lots of changes to the classic MMO architecture that makes it more like the web. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

femgineer.com

JULY 18, 2010

If they’re coming up to speed with the product, development cycle, and company dynamics is good to let them ramp up slowly. Yes, building software is cheap and fast unlike other products. Remember people only have two hands! But there is still the overhead of testing, scaling, and securing.

Engineer 41

Engineer Software Review Startup Technical Review 41

Startup Professionals Musings

JUNE 16, 2019

Everyone is predicting a rise in massive open online courses (MOOC), that will drive the need for new course content, architecture, and delivery approaches. These shifts are independent of technology innovations, but certainly will drive the application of key product developments. Education: More students and different classes.

Architecture 209

Architecture Forecast Demand Technology 209