It's interesting (and mildly embarrassing) how much I used to think this too. Holy fuckola, how wrong I was.

Don't get me wrong, our storage engine is the rock upon which everything rests.

As the market matures over the next few years, our strategy and differentiation will shift away from "only we deliver o11y" to exploiting all the unusual capabilities of our storage tier. 😈🐝
Subsecond ad hoc querying over weeks of webscale traffic.. unsampled? ✅

Drill down from high level SLOs to see all of the dimensions, diffed in order of their degree of outlieriness vs the baseline? ✅

The raw speed and flexibility unlocks soooooo many product daydreams.
But that's just good engineering. How to build a product that helps our customers achieve meaningful observability...that is a design problem.

Teaching people to lean into their curiosity and follow the signal? Design (and product) problem.
This time last year, we were hiring our first product leader, our very first design leader. We had ~9 people writing code.

We've been busy 🙃 we now have four in product, seven in design, and just doubled our engineering firepower. Every single one of them is ✨😍amazing 🔥🤩🐝
What I'm saying is, I'm not just yapping; we really are putting our chips down big on design this year.

We will succeed largely to the extent that our design, product and engineering teams are equal players of equal caliber who love the shit out of each other.
Speaking from within my own little domain of R&D, that is. 🙃 and as a product-led company, getting this right is huge. But not everything.

In some ways, for a company like us, getting the product right is the easy (😩!) part. When you're creating a category, GTM is FUCKING HARD
Our customer success team is going to bear the brunt of helping users navigate their observability journey while helping our product folks make it better, faster, easier.

Our sales team is the only one I know of in software that is 0% threatened by our generous free tier 🙃🌷
Our marketing team (and mighty devrel) have to span worlds effortlessly and invisibly; building the demand gen engine, building enduring partnerships, pushing the industry forward with OTel, educating and explaining. Oh, and positioning can be one of the hardest parts of product.
Did I mention how small but mighty our sales team is? It is hard to build a high performing sales org, but it's harder when so many of your prospects show up already acting like they hate you.

"Your sales folks are the only ones I'm ever genuinely happy to hear from" - a user 🌷
Fact: it is easier to hire world class biz folks when you don't casually demean them or their work.

If an engineering candidate exoticizes or dismisses sales or marketing, they get an auto thumbs down from me.
One of the (many) things I love about @lizthegrey is how easily she agreed to put devrel with product marketing. (This also put her multiple hops away from the C*O, a devastating blow at a hierarchical org).

I can say this shit all day, it's actions like these that make it real.
Each of these functions has to be individually stellar at executing and course-correcting, respect each other and resolve conflict productively, and they need a strategy that is mostly correct and under continuous alignment...

It's basically impossible. We're probably doomed. ☺️

More from Internet

A thread of resources for aspiring & new Product Managers:

(should also be useful for Eng, Design, Data Science, Mktg, Ops folks who want to get better at PM work or want to build more empathy for your PM friends ☺️)

(oh, and pls also share *your* favorite resources below)

👇🏾

1/

Product Management - Start Here by @cagan
(hard to go wrong if you start with Marty Cagan’s

2/

Tips for Breaking into PM by @sriramk
(I’ve recommended this thread in my DMs more often than any other thread, by a pretty wide


3/

Top 100 Product Management Resources by @sachinrekhi
(well-categorized index so you can focus on whatever’s most useful right

4/

Brief interruption.

It’s important to understand your preferred learning style and go all in on that learning style (vs. struggling / procrastinating as you force a non-preferred learning
There are lots of problems with ad-tech:

* being spied on all the time means that the people of the 21st century are less able to be their authentic selves;

* any data that is collected and retained will eventually breach, creating untold harms;

1/


* data-collection enables for discriminatory business practices ("digital redlining");

* the huge, tangled hairball of adtech companies siphons lots (maybe even most) of the money that should go creators and media orgs; and

2/

* anti-adblock demands browsers and devices that thwart their owners' wishes, a capability that can be exploited for even more nefarious purposes;

That's all terrible, but it's also IRONIC, since it appears that, in addition to everything else, ad-tech is a fraud, a bezzle.

3/

Bezzle was John Kenneth Galbraith's term for "the magic interval when a confidence trickster knows he has the money he has appropriated but the victim does not yet understand that he has lost it." That is, a rotten log that has yet to be turned over.

4/

Bezzles unwind slowly, then all at once. We've had some important peeks under ad-tech's rotten log, and they're increasing in both intensity and velocity. If you follow @Chronotope, you've had a front-row seat to the

You May Also Like