Haystack

DECEMBER 29, 2018

More and more angels will be minted as the 2019 IPO class emerges. Also during this time, the underlying metrics in that business can change positively, potentially trapping companies to accept the initially-agreed upon valuation. Traditional seed funds have gotten bigger, many armed with opportunity funds on top.

Technical Review 165

Technical Review Venture Capital Russia China 165

Startup Lessons Learned

SEPTEMBER 22, 2008

Master of 500 Hats: Startup Metrics for Pirates (SeedCamp 2008, London) This presentation should be required reading for anyone creating a startup with an online service component. He also has a discussion of how your choice of business model determines which of these metric areas you want to focus on. Choose one.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

ReadWriteStart

JULY 18, 2011

Jeff Clavier was the first tech investor I ever met; he was introduced to me years ago by some hip engineers in a bar as "one of the few cool VCs." Kedrosky: "In the 90's I was an analyst through all this [tech investment and IPO] madness. You want to build your own IPO and exit. Think about when LinkedIn went public.

Investment Bankers 153

Investment Bankers Technical Review Cofounder Due Diligence 153

crowdSPRING Blog

JANUARY 18, 2013

Thanks To Facebook, Strongest Year For IPOs Since 2000 With $21.5 The 6 Marketing Metrics Your CEO Actually Cares About [Cheat Sheet] | Hubspot Blog - [link]. Facebook Has Some Tips | Search Engine Land - [link]. The 6 Marketing Metrics Your CEO Actually Cares About [Cheat Sheet] | Hubspot Blog - [link].

Social Media 94

Social Media Small Business Design Media 94

David Teten

JANUARY 19, 2021

This structure allows for alignment on the front end, and real-time flexibility for performance metrics,” says Samira Salman , a family office investor and advisor. . Flexible VCs have created structures based on other company performance metrics than revenues, such as profits or founder salaries. Flexible VC 102: Variations.

Cofounder 78

Cofounder Technical Review Equity Dividend 78

Startup Lessons Learned

APRIL 4, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 15, 2008

See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. Since that time we've seen a massive change from product engineering to financial engineering. Seth Godin: How often should you publish?

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

JUNE 17, 2010

I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. The engineering team would then build that feature, mimicking the UI as close as they could using the current primitives supported by the system. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

FEBRUARY 8, 2010

Lessons Learned by Eric Ries Monday, February 8, 2010 Beware of Vanity Metrics (for Harvard Business Review) The next article in my series on entrepreneurship for Harvard Business Review is live today. Once again, we revisit the topic of Actionable metrics and their nemesis: Vanity metrics. Remember "metrics are people, too."

Metrics 121

Metrics San Francisco Lean Continuous Deployment 121

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JUNE 2, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Read the rest of The Five Whys for Start-Ups. Speed up or slow down? Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

MARCH 25, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 30, 2008

So I initially gravitated to the CTO title, and not VP of Engineering. But since I spent a long time in a hybrid CTO/VP Engineering role, I still have this nagging question. I want to add one last idea, even though I recognize it is controversial, bordering on the boundary between the CTO and VP Engineering. Heres my take.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. I help lead the Engineering Leadership SIG at SDForum and wonder if you would be interested in speaking to our group about lean starups. hope to hear from you.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Reid Hoffman

DECEMBER 10, 2020

With Airbnb’s IPO, I thought the time was right to take a look back at the past decade (Greylock led Airbnb’s Series A in November 2010) and reflect on what I learned from the journey. it took years for Airbnb’s metrics to really start accelerating. This essay is based on a Greymatter podcast episode, which you can listen to here.

Hosting 69

Hosting Hockey Stick IPO Silicon Valley 69

Startup Lessons Learned

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 16, 2009

In a startup, rather than think of ourselves as having a marketing department and an engineering department, I now believe its better to think of ourselves as focusing our energies on unknown problems and unknown solutions. Agile is one way to succeed, because pursuing unknowns iteratively is a good way to mitigate risk.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Every time an engineer checks in code, they are batching up a certain amount of work. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 26, 2009

Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. You can learn more about that by reading The engineering managers lament.) leanstartup We organized our engineering team at IMVU to try and maximize cross-functional collaboration. Articulate, inspirational.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

SEPTEMBER 10, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 15, 2008

Focus on the output metrics of that part of the product, and you make the problem a lot more clear. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Max Levchin of Slide and Paypal has noted that 10% of Slides headcount is devoted to metrics only.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

AUGUST 8, 2009

I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

JANUARY 15, 2010

Behind this analysis is a spreadsheet model, complete with detailed metrics for a set of customer behaviors that show just how valuable the new product will be. They are on-schedule and on-budget, but their gross metrics are way off. They are on-schedule and on-budget, but their gross metrics are way off.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

SEPTEMBER 12, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

OCTOBER 5, 2008

The VP Engineering spends all of his time trying to make sure the programmers understand and implement the spec. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Frustration is mounting.

San Francisco 158

San Francisco Management Software Review Product 158

YoungUpstarts

APRIL 7, 2013

They’re using metrics that are often unworkable in the current business environment, causing growing businesses to look elsewhere for capital and increasingly towards alternative forms of financing. Case in point: It took Amazon six years to earn a dime, during which it consumed huge amounts of venture funding and issued an IPO.

Advisory Board 249

Advisory Board Entrepreneur Portland Oregon 249

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Startup Lessons Learned - the Conference (April 23.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

AUGUST 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

JUNE 5, 2009

I think this idea is particularly appealing to those of us from an engineering background. In a startup context, numbers like gross revenue are actually vanity metrics, not actionable metrics. Luckily, we also discovered that certain other metrics, like LTV and CPA were much better than we initially projected.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

DECEMBER 28, 2009

The second shift in mindset required is to separate the concept of a marketing release from the concept of an engineering release. Engineers working in a continuous deployment environment are much more likely to get individually tailored feedback about their work. Thats good for QA and for engineers.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

OCTOBER 28, 2008

whos on the engineering team? Most important slide: demo (if the product solves an obvious problem), engineering resumes (if the product is nearly impossible to build), " day in the life of a customer " (if neither of the above) Breakthrough technology Key questions: who owns the patents? how do you know anyone would want it?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Processes are always deteriorating or self-regulating. Do they measure?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JULY 28, 2010

“Some people weren’t comfortable because it wasn’t as fun, and one senior engineer thought we’d be losing the part of kaChing that was an enabler for anyone who wanted to make it as a pro,&# Rachleff recalls. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

SEPTEMBER 10, 2008

At IMVU , our engineering team accumulated thousands upon thousands of tests, and we had a build cluster (using BuildBot ) that ran them. Thats possible now, and it means that the historical ratio of QA to engineering is going to have to change (on the other hand, QA is now a lot more interesting of a job). Completely necessary.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

NOVEMBER 18, 2008

At Toyota , they are called Chief Engineer : Toyota realizes that the Chief Engineer job is probably the most important one in the company because the Chief Engineer listens to the customer and then determines what the functions need to do to address the customer’s desires.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JANUARY 7, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Startup Lessons Learned - the Conference (April 23.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119