Advice from Jason Cohen, founder of WP Engine & Smart Bear Software.
We’re constantly told to make decisions quickly, because that speeds up the production and learning loop.
But some decisions really should be made slowly.
How do you know which way to go, with a given decision? Here’s a framework to answer that question.
We’re constantly told to make decisions quickly, because that speeds up the production and learning loop.
But some decisions really should be made slowly.
How do you know which way to go, with a given decision? Here’s a framework to answer that question.
Pricing is often more about positioning and perceived value than it is about cost-analysis and ROI calculators that no one believes.
As a result, positioning can allow you to charge many times more than you think you can. Here’s how.
WP Engine just announced passing $100M in annual recurring revenue and a $250M investment from Silver Lake. We’ve never been in a stronger position!
We’re tired of hearing how small software companies usually fails.
The data show that the two most common causes are (1) the product just isn’t useful to enough people and (2) problems with the team.
But what about the cohort that dies even though it did sell some copies of software to a few people, and where the founding team isn’t dysfunctional?
I don’t have data for that cohort (tell me if you do!), but informally I see things like the following, which is useful to list because there’s a pattern common to each of them, which furthermore is possible to counteract
No you can’t “have it all.” You can have two things, but not three.
Idealistic founders believe they will break the mold when they scale, and not turn into a “typical big company.” By which they mean: Without stupid rules that assume employees are dumb or evil, without everything taking ten times longer than it should, without wall-to-wall meetings, without resorting to hiring anything less than the top 1% of the talent pool, and so on.
Why do they never succeed? What are the fundamental forces that transform organizations at scale?
I happened to be sitting on the tarmac, delayed, when a tweet came in asking for some ideas for what to do on a company retreat that would be strategic.
In the confines of six square feet of personal space, I sent a few answers.
These are useful exercises any time!
Though inevitable, change is uncomfortable and exhausting. Even we who relish change, who love bragging that “it’s hard but every day is different,” reach a breaking point after years of adaptation and fake-gleefully exclaiming that “failure is how you learn!” Yeah, but all this learning is fricking tiring.
How do you manage change?
Product teams have been repeating the MVP (Minimum Viable Product) mantra for a decade now, without re-evaluating whether it’s the right way to maximize learning while pleasing the customer.
Well, it’s not the best system. It’s selfish and it hurts customers. We don’t build MVPs at WP Engine.
This is the right way.
Using common metaphors makes your product UI identical to all the others. There’s no personality, no brand, solidifying the notion that this product is “just another tool” rather than a new way of interacting with a computer. Surely technology can be better than that.
But this is an egocentric view. Your customers don’t want to figure out some newfangled damn thing just to navigate a dialog box.
Which way is the right way?
For every clear example that proves “X is right,” there’s another equally compelling story of success where the mantra was “X is wrong.”
So the question is: Which advice is right for me?
Let’s answer that question.
“Maximizing” means expending time and effort to ensure you’ve solved something as best as possible. It typically needs lots of exploration and analysis to ensure “the best” option hasn’t been overlooked, and that we have confidence in our evaluation of all options.
“Satisficing” means picking the first option that satisfies some given criteria. It’s less time exploring & analyzing, more time acting. It’s not getting paralyzed by the pursuit of “perfect,” but it often doesn’t result in finding the very best.
In software and startups we can choose when we maximize, and when we satisfice. It might seem like maximizing is best especially when you have teams of smart people who can do the maximizing. But not necessarily.
Look for this icon in my blog posts for the audio versions, or subscribe to my iTunes podcast feed.
