Software is no longer sold; it's adopted
orbit.love
orbit.love
Search "shutting down" on HN for a list: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
It reminds me of what is important in life.
Problem Discovery - listen to users to understand where they struggle, but ignore their proposed solution and desires (except to the point it helps you understand the problem they are attempting to communicate).
Solution Discovery - design a solution that addresses the problem, and validate it with real usage. Importantly not just talking, but users need to actually try it out.
Cooper and Vlaskovits - The Entrepreneur’s Guide to Customer Development
You don't have to do exactly what they suggest, but following that advice I'd expect to see a lot of solutions that miss the mark in subtle ways that would be really frustrating as a user. Sometimes people don't fully understand why "Do thing Y instead" would make it better, so it's not in their "Problems" section, but they for sure know that having the button do Y instead would solve it. It's probably worth thinking about and not ignoring.
I had one set of legacy workflows I once replaced that rough went like:
1) Export data from system A to a CSV.
2) Remove/reorder a few columns manually in excel
3) Get manual approval from a manager
4) Email to different department
5) Upload to system B via their import function
The request was to just give us an "export with the right format," thus replacing step 1 & 2. But we also heard complaints from the team doing step #5 that it was pointless and could be automated, and from the managers in #3 that really they used a simple rule that if X < Y approve otherwise deny.
So we thought we could build a workflow automation that connected the two systems via API, with an automated approval and flag those that didn't meet the rule for manual review.
So we propose this, everyone agrees. We build a pilot, test it, everyone likes it. Then go to release it and find out that this ignores any number of cases where in #2 there where hidden workflows like "any time you see scenario W, send it to Jenny and she runs a formula on these columns to adjust" or "actually the manager never approves anything from this department related to an acquisition because of factor x, and it needs to go to this different group." There was about a dozen similar requirements. Could we have identified these sooner? On other projects we usually did, but this project went further than most before they were detected.
We ended up temporarily building that export button requested by the users originally and were planning to fix the API based workflow ... but then there was a reorg and priorities shifted. We never came back to project and AFAIK those groups still work via email. But they don't do nearly as much excel busywork as before ¯\_(ツ)_/¯
A generalization is not the same as a universal claim, which can be disproved with a single exception.
A generalization is about the shape of some statistical cloud. We have to show that it's not shaped that way to disprove it. So find enough exceptions and we're there. But how many are enough?
It's usually easiest (imho) to disprove these by showing a different generalization that is true, but conflicts with the given one.
No other shell or programming language comes close out of the box at the versatility that Bash has. I say this after having searched high and low for shell programming languages, maintaining big bash projects for a multiple organizations.
There are idiosyncracies to java, c, go and rust too. This monoculture of bash is bad is tiring. Paired with the monoculture of go is the new hotness. I rewrote at 500 line python project in 100 lines of bash for more functionality, but at a cost of more external dependencies but they are system deps with a standard abi without having to deal with python. APL has its strengths where Go/Rust is terrible.
Just use the correct tool for the job. And no more of this monoculture. Diverse problems need diverse solutions
A lot of people love bash, and a lot of people bash bash, but I'm personally aware that not "virtually everyone" hates it.
Standing up an idea well enough to change how people see a need is an incredible accomplishment but it's entirely different from single-handedly knowing how to make it work best for people who use it. Or for anybody other than you, really.
But underestimating the importance of, or even disdain for deliberate usability work is pervasive in FOSS. Most developers see interfaces as a place to expose the user-facing functionality so people can interact with your software. To a user, the interface is the software. In their estimation, bad interface=bad software.
When projects ignore that, they end up making Gimp.
You'll have a hard time selecting a sample of serious photo editors where fewer than 80% have tried Gimp— yet maybe %5 use it. Fewer will have heard of the younger commercial Affinity, but more will use it. (edit: obviously pulling those numbers out of my ass but I've been editing photos on computers since the early 90s and do so professionally to this day.)
However, in the adjacent and oft-overlapping world of vector art, the FOSS project Inkscape is very, very popular— even among professionals. They aren't hostile to usability changes, actively seek outside interface design perspectives and have a usable application because of it.
Inkscape does more good for a broad swath of vector artists because of their good design habits. Gimp has a product enjoyed by open source enthusiasts with light photo editing needs.
Free + great enough to generate word of mouth will trump expensive + great + advertising in almost every case.
They're talking about a bottom-up model of sales rather than top-down.
Selling to the end users of a platform rather than selling to the CIO/CTO.
This is particularly important now in the age where lots of SWEs won't take a job if the company is using teams/outlook and not slack.
it's not necessarily the best approach, but as long as there's money to be made out of it, there will be customer tailored software.
This is not a new thing. Microsoft famously said something like "we don't like software piracy, but we'd rather you pirate Windows than use something else". Adobe said the same about Photoshop.
Let me give you an example.
California.
I was given a pretty terrible impression of state workers, government employees generally, for a very long time. And I still hear stories about many of them being really lazy, but that I've actually witnessed firsthand, dude, 5.0000 stars. Let me jog my memory and think when no...but that I can talk about...well the police at least, just awesome police. But that's just what I see with my own eyes, of course you have to take into account news. With police, them earning what they earn just doesn't seem that fucking expensive. The public libraries, just amazing, people don't realize the value of a library because they're everywhere in US and in Latin America they're not as good (fewer, farther between, less resources). There's more examples.
So at one point when filling out HR forms I notice the person I'm talking to skipped over two entries filled in by default with 0.00, and I asked what they were. Extra taxes! Do you want to pay extra taxes? Nobody fills them out!
I said yes, definitely, and it was great. I felt good knowing I supported the system that supported me, without exclusion. Like everyone says "the government should do this, I want this from the government, I shouldn't have to pay for this myself, my entitlement is not enough." What about, hey let's give the government what it needs on our end, like actually produce the wealth and be tax-docile instead of making it audit us (and let someone else come up with ideas of how to spend it).
It goes for everything, I pay even once the horse is out of the barn.
Your government hates you and doesn't give a fuck about you. They misuse every dollar they get and use whatever means necessary to shove it into the bank accounts of their rich friends.
Please correct me if I'm just seriously misunderstanding you. Please!
You, for some reason, believe that willfully giving your government even more money is going to actually help you and other people around you.
I'm sorry ... what?
Yeah exactly, that's what I used to believe. Couldn't have put it better myself. And all my sources confirm it, except for all my actual personal experiences. It's an internet versus real life thing. Depends on where you live.
The most useful software communities I engage with tend to be the organically curated ones.
Hey I like rats, but he's not wrong in his choise of words.
Now rats are paying restitution as lab test animals and making us healthier.
This feels like the 2000s again with the annoying enterprise software companies of that era. Perhaps the hangover of this will be another decade of new comers making software people actually want to use.
Sure, you'll eventually need a salesforce when you get to that company size (330M in revenue in one quarter in 2022 for Snowflake: https://investors.snowflake.com/news/news-details/2021/Snowf... ).
The same is true with the other ones you mentioned. This post does a great job of explaining why: https://bothsidesofthetable.com/one-of-the-biggest-mistakes-...
But for most companies starting out you can't hire an enterprise sales force (nor would they be effective). I don't know what size it makes sense to start hiring sales folks (don't have a ton of context) but my guess is by the time you have $10M/year in revenue, you have some kind of sales team.
But how can you drive adoption at the early-mid stages of a business? That's the question this post answers.
There's a large number of small (<5) person companies that work entirely like that. They're not _sexy_ and they're never going to be unicorns, but they make a good amount of money for the people involved when they inevitably get purchased by some larger group.
I know a couple of consulting companies that are doing just fine, but I agree, they'll need a sales team. Will they need an enterprise sales team? Probably not, it'll be the founders and once they get to a certain size a sales team. But not the kind of sales team that Snowflake has.
Then there would be the real sales team who were out visiting customers and supported by the internal team. A lot of their work is keeping existing customers happy.
My gut feeling is you wouldn't have much success selling consulting via an internal team. Because of the nature of the work it is always going to be closer to the second group, more like enterprise sales.
What I find interesting now is how big some companies can get on the back of the first example. Google seems to be built on that.
For others I guess VC money will be used to jump start the business although I have no experience of that.
>In this product-led world, folks won't simply use whatever tool they're given. They want to use the same tools at work as they choose to use in their own time.
I do think PLG is taking over most software
I loathe subscriptions. It is the mental overhead. Since the shift to subscriptions, my personal spending on software is down something like 80% from what it was ca. 2015.
Replacements mainly have been open source software or things I've written.
Business likes it though.
On the consumer side Office 365 offers a lot of functionality that requires a server component.
On the other hand, who will work on polished software for end users for free?
Man we're so over that... do you know what FLOSS means? Most FLOSS used today (and it is used in or to develop mostly everything you use) is developed by paid developers.
You sound like bill gates in his open letter to hobbyists: "What hobbyist can put 3-man years into programming, finding all bugs, documenting his product and distribute for free?" https://en.wikipedia.org/wiki/Open_Letter_to_Hobbyists
But, where is the open source popular equivalent to Office365 and Adobe’s software suite - the user facing software?
And companies that were trying to create a business around open source software are rapidly retreating to close source licenses like ElasticCo and MongoDB.
FLOSS is an enabler of almost all SaaS there is today. With regards to support or consultancy, that's is how Canonical, SuSE and (for the most of its existence) RedHat survived. There also minor examples, like Collabora maintaining LibreOffice or OnlyOffice. These are just from the top of my head.
> But, where is the open source popular equivalent to Office365 and Adobe’s software suite - the user facing software?
Equivalent to these... I really fail to provide, but consider many user-facing polished FLOSS like Blender, Krita, Inkscape, Firefox, Chromium, Audacity... Some of them have sustainable market segments, some of them are not as advanced as proprietary options; but most important: some of them are more popular/used them proprietary alternatives and a good enough for most people.
It's all "licensed", which isn't the same as "sold".
When I sell you something, it's yours.
When I license you something, it's still mine but you're allowed to use it.
> From Slack to Figma, Typeform to Twilio, Atlassian to Airtable... many of today's fastest-growing companies are those who are not only product-led but community-driven.
Atlassian is clearly not product-led today and they are clearly not one of today's fastest growing company
> vendors have had to adapt to this new landscape. Go-to-market strategies have changed with sales-led replaced with product-led. [...] they've adjusted their budgets accordingly. Take Atlassian, for example; in 2020, their Sales and Marketing spend was 18.6% of revenue compared to an industry average of 38.7%
Atlassian as always been famous for being no-Sales, so this is clearly not a shift for them
Prominent examples are Figma, Slack and Zoom.
More info: https://www.getcorrelated.com/blog/what-is-product-led-growt...
The market is filled with tons of products that fulfills the needs of users. But very few of them have a community of enthusiastic users that want to recommend it to others.
and good products without a mascot have been recommended in the past, just because they are good products.
That’s why all these companies build silos: to make changing painful.
Well, there was a time when this used to be the other way round. (Insert your preferred version of o tempora o mores here.)