Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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

NOVEMBER 17, 2008

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? Using AdWords to assess demand for your new online. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

NOVEMBER 18, 2008

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? Using AdWords to assess demand for your new online. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

OCTOBER 26, 2009

Customers kept demanding that we add this or that IM feature, and we were routinely refusing. We were afraid that this was just the tip of the iceberg, and that once we “gave in&# to these five demands there would be five more, ad infinitum. You can read how well that went in another post here.) Expo SF (May.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

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. Revisiting the Software Design Manifesto (and what. Gatekeepers are overloaded. Expo SF (May.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

APRIL 26, 2009

Making UGC work requires good tools, open standards, and proper incentive design. It allowed me to assess the market demand for that offline product before I had the final product baked. On-demand utility pricing for services (aka "cloud computing"). The response has been nothing short of amazing (thank you all so much!).

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JUNE 8, 2009

Periodic or on-demand reports are one possibility, but we can do much better. It was pretty ugly, the marketing and design sucked, and I was embarrassed by it. Because of the extreme unknowns inherent in startup situations, we are all blind – to the realities of what customers what, market dynamics, and competitive threats.

San Francisco 84

San Francisco Lean Continuous Deployment DC 84

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. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

MARCH 11, 2010

High-profile startup Friendster had first-mover advantage in the social networking space, but created openings for competitors when it could not scale to meet demand. High-profile startup Friendster had first-mover advantage in the social networking space, but created openings for competitors when it could not scale to meet demand.

San Francisco 120

San Francisco Continuous Deployment Lean DC 120

Startup Lessons Learned

OCTOBER 4, 2010

Many journalists and conference organizers attempt to fill this demand by giving successful entrepreneurs the opportunity to tell their stories: in magazines, on blogs, and on stage. And the kinds of failures that do get airtime are usually failures to adequately plan, anticipate, or design in advance.

San Francisco 167

San Francisco Lean Metrics PR 167

www.ere.net

JULY 15, 2012

If you’re targeting top performers or poaching from competitors, the remaining steps of the recruiting process must be designed to “fit” the needs in the job search process of your targeted candidate if you expect to even gain their attention. Keith Halperin. May 11, 2010 at 4:31 pm.

Hiring 57

Hiring Metrics Search Widget 57

Startup Lessons Learned

NOVEMBER 5, 2008

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? Using AdWords to assess demand for your new online. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Iterate quickly to uncover true market demands. Revisiting the Software Design Manifesto (and what. Without a doubt, this is the most forward thinking process/solution/methodology/post I've seen in quite awhile.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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

NOVEMBER 29, 2008

The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. To probe for agility, you have to ask the candidate questions involving something that they know little about. Does their personality bring something new?

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

NOVEMBER 19, 2008

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? Using AdWords to assess demand for your new online. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 60

San Francisco Lean Continuous Deployment DC 60

Startup Lessons Learned

NOVEMBER 11, 2008

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? Using AdWords to assess demand for your new online. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Silicon Valley 68

Silicon Valley San Francisco Lean Continuous Deployment 68

Startup Lessons Learned

OCTOBER 5, 2009

In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. In other words, a principled way to combine agility with stability. In other words, you can always invest in process, batch size reduction, and agility as an alternative to preventing a specific problem.

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

FEBRUARY 10, 2009

It’s important to note that system I’m about to explain evolved organically in response to new demands on the system and in response to post-mortems of failures. Heck, thats what it says right there in the agile manifesto. Nobody gets here overnight, but every step along the way has made us better developers. But it worked.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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

NOVEMBER 17, 2008

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? Using AdWords to assess demand for your new online. Expo SF (May. Conference streaming, sponsors, discounted tickets.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

NOVEMBER 13, 2008

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. 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? Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

JULY 2, 2009

Five Whys is designed to avoid these nebulous arguments. oh, and on the book front, you'll be able to get all of my essays so far in ebook, print-on-demand, and kindle editions - coming soon. In fact, even the investigation itself is considered too much work. If new employees are causing problems, that will be a routine topic.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

DECEMBER 7, 2008

As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. Even if, in a previous life, you were a world expert in some functional specialty, like in-depth market research or scalable systems design, the compressed timeline of a startup makes it irrelevant. But life is not easy, either.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

NOVEMBER 22, 2008

Doing in-depth customer research, with long questionnaires with detailed demographic and psychograpic breakdowns, is very helpful for long-range planning, interaction design and, most importantly, creating customer archetypes. Designing the survey The NPS question itself (again, "How likely are you to recommend X to a friend or colleague?")

.Net 158

.Net Operations San Francisco Lean 158

Hearpreneur

SEPTEMBER 15, 2021

The fashion industry is always ripe for disruption since every consumer has their taste and style, and designers work round the clock to develop unique trends. Different designers produce garments based on body shape, size, skin color, season, and many other factors. Thanks to Harriet Chan, CocoFinder ! #6- 12- Manufacturing.

Artificial Inteligence 109

Artificial Inteligence Entrepreneur Technical Review Security 109

Startup Lessons Learned

JANUARY 2, 2010

This is just like a startup to me, complete with distribution and product development challenges, ecosystem design and many, many customers. Ive been blown away by the level of demand you all have expressed in having a forum for the whole community to come together and share what were learning. Startup Lessons Learned conference.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

FEBRUARY 12, 2009

(a guide for hackers) (This post was inspired by a conversation with Nivi from Venture Hacks , but is otherwise not his fault) There has been a proliferation of frameworks and metaphors lately that are designed to help startups avoid the all-too-common fatal mistake of failing to find a market. Tough sell. Expo SF (May.

San Francisco 89

San Francisco Continuous Deployment Ruby Lean 89

Startup Lessons Learned

NOVEMBER 5, 2008

Obama understood the two concepts that are essential for building a high-performance, highly adaptable, agile organization: 1) rapid iteration and 2) clear values-based objectives. Wed train them on-demand as they came in, and send them into the world (or onto the phones) with written instructions and voter contact data. Expo SF (May.

Campaign 84

Campaign San Francisco Lean Agile 84

Startup Lessons Learned

SEPTEMBER 11, 2009

or their privileging of only certain designers featured in Showcase and promos. until I couldn't seem to find a way from getting away from all these nasty, vulgar teens (or people pretending to be teens) demanding explicit sex every time I went there. Running a platform is a public trust and a publicly-accountable act.

Community 158

Community Management Lean Software Review 158