9 ms·
Removing stuff is never obvious yet often better
- deleted 2y ago[deleted]
- v9v 2y agoAlso see Muntzing: https://en.m.wikipedia.org/wiki/Muntzing https://en.m.wikipedia.org/wiki/Muntzing
- cynicalpeace 2y agoSoftware Engineers (a large portion of HN community) inherently have a hard time with this. We're always taught to consider edge cases. Oftentimes handling the edge cases can be more work than the rest of the project. But when we handle them, we give ourselves a pat on the back, without thinking can I just ignore the edge case and shrug if someone runs into it? In the case of the OP, the edge case is the occasional user who might want to project their exact costs.
- jclulow 2y agoPerhaps removing a pricing scheme so complicated that it literally can't be modelled usefully by the customer would be even better?
- kmoser 2y agoThe article states that the biggest factor was user misunderstanding of the options, not so much the number of different options. In other words, if they offer option A at $x and option B at 10*$x, if most users mistakenly think they need option B, the calculator is misleading. Also, I'm a big fan of "contact us for pricing." It's annoying for users who are window-shopping and want a quickie ballpark, but it helps you identify cases where standard pricing (or pricing which can't easily be described online) can be negotiated, and which the user would have otherwise overlooked. This doesn't work for things like most ecommerce, of course.
- bdw5204 2y agoMany users will see "contact us for pricing" and assume that means you can't afford it. That's fine if your customers are enterprises but definitely not for consumer products that middle class people might actually buy.
- parpfish 2y agoor the product is still being built out and they don’t know how to price something in beta
- dhosek 2y agoA lot of time when there’s something like that, I’m fine not having a firm number, but it’s nice to have at least a ballpark idea of cost. (I found this particularly egregious with musical instrument pricing where I didn’t know if I was looking at a $1000 instrument or a $20,000 instrument, so I generally assumed that these would be cases where I clearly couldn’t afford it so best not to wonder—not to mention the cases where the list price was often as much as double the actual street price for an instrument).
- ramshanker 2y ago>>> I'm a big fan of "contact us for pricing." <<< I have opposite feeling about them. They are like open invitation to give the sales guy a window of opportunity to look up your company website, and markup the price accordingly.
- Cerium 2y agoYep, I will exhaust every option with transparent pricing before even calling the best looking option with "contact us for pricing".
- citizenpaul 2y agoExactly. Its an invitation to the used car salesman circus. I do t have time to play games with a salesman for the next two weeks. If a company doesnt have at least ballpark pricing available upfront they never hear from me and dont even know they lost a potential customer. Only huge entrenched companies can get away with that long term. That and single suppliers.
- deleted 2y ago[deleted]
- ta8645 2y agoOne could argue this is exactly the prescription that the Gnome project embraced. Remove, simplify, excise. To mixed reviews.
- forthac 2y agoI believe the quote is to "Make things as simple as possible, but no simpler".
- ineedaj0b 2y agoi think of this lesson often (i don't remember who told me) elon building something at spacex and ruthlessly cutting out pieces they initially thought were needed. less complexity meant cheaper and faster construction so = more tests. i use this in day to day to life: making plans, buying things, managing others - reducing has led to more accomplished.
- kqr 2y agoThis is how China Lake made the Sidewinder missile also, and a large part of how Skunk Works operated under Kelly Johnson. Also to some extent Toyota. I believe shrinking the feedback loops is the most effective form of envelope-pushing.
- rashidae 2y agoThis is a beautifully designed blog interface. It’s one of the best I’ve seen, making it a pleasure to read.
- cratermoon 2y agoAccording to the metadata in the html, the site is built on ghost.org
- gk1 2y agoYes, with the default theme. I deserve zero credit for it.
- kevmo314 2y ago> Except for one person, it never occurred to this very smart group of people that removing the source of confusion could be a good option. Reminds me of the quote: "It is difficult to get a man to understand something when his salary depends on his not understanding it." That applies to us as software engineers too, our salary depends on having projects to write code for so it's not so surprising that a very smart group of people don't often consider that doing nothing or removing something is a valid solution. I like the author's observation on this too: it would be nice if removing things were rewarded. I wonder of the employee who questioned the calculator's necessity got any reward.
- 0cf8612b2e1e 2y agoRemoving features is deeply unpopular. The millisecond it is released, someone is going to make it a load bearing part of their workflow. A removal is now breaking the contract with the customer. Which may/not matter, but it requires more politics and negotiation to suddenly be dropped.
- makeitdouble 2y agoThe general message is interesting. This specific bit kinda gives pause though: > One slight misinterpretation and wrong input and you'd get an estimate that's overstated by as much as 1,000x. Does it also mean that in real world usage, one slight misinterpretation or misevaluation of your metrics and you're liable to 1000x more than you planned to ? I totally see this as a reality of online billing systems. I've misconfigured GCP prototypes and ended with 100+ bills where I though it would be 2 or 3 at most and didn't care to watch for a few days. But I'd understand a client bailing out when they realize slight changes to the sliders result in wild increases in the planned pricing. And removing the tool would sure help for registration, but not help the customer if they hit these kind of issues down the line.
- gk1 2y ago(Author here) > Does it also mean that in real world usage, one slight misinterpretation or misevaluation of your metrics and you're liable to 1000x more than you planned to? Unlikely. You can see why in these two examples that really happened: One user I spoke with said they assumed "queries per second" is calculated by (number of searches) x (top-k for each search), where "top-k" is the number of results they want back. I don't remember their top-k but let's say it's 10 -- so they were entering a value for "queries per second" that was 10x higher than it should be and they'd see an estimate around 10x higher than they'd really be charged. Another user thought you get "number of vectors" by multiplying the number of embeddings by the embedding dimensionality (1,536 is a common one). So they were entering a value literally 1,536x higher than they should've. Their actual usage would be calculated (by Pinecone) correctly and not be that high. Vector dimensionality is a basic concept for AI engineers and QPS is a basic metric for DB admins, but Pinecone sees lots of users who are either new to AI or new to managing DBs or both.
- makeitdouble 2y agoThanks ! > where "top-k" is the number of results they want back. Some systems will do that, so I get the confusion. I think the YouTube API for instance has a quota system that takes internal operations into account, so getting back 10 results in a query effectively weights 10+ credits. I better understand the kind of issues you are facing, as these kind of subtilities are inherently hard to explain. For better or worse, that's another advantage of starting with a small trial account and actually see how the operations are billed for typical operations.
- ibash 2y ago> Before long, a dedicated Slack channel was created, which accrued over 550+ messages representing opinions from every corner of the company. Another few thousand words and dozens of hours were spent in meetings discussing what we should add to the calculator to fix it. This is a symptom of over hiring. Too many people removes agency. When people lose sight of what's actually important and feel that they must reach consensus by committee then there are too many people.
- imoverclocked 2y ago> This is a symptom of over hiring. Perhaps. It's also a symptom of bike shedding which can happen with as few as two people.
- FridgeSeal 2y agoTrue, but at least the communication overhead between 2 people, and the time for them to either agree, compromise, or punt, can be a lot lower, which is a significant win for getting things done.
- andyferris 2y agoAs few as one - I'm pretty sure I manage that all on my own sometimes!
- Osiris 2y agoHow did you reach the conclusion that the company has too many employees from that one sentence?
- ibash 2y agoTwo lines of reasoning. First: A lot of time was spent building consensus. No individual felt they had unilateral power to remove the calculator. Instead the behavior was to seek approval. That's probably because of unclear ownership, which often happens because of too many people. Second: Too many cooks in the kitchen. At any stage of a company there's a limited amount of important work. Work that is mission critical and provides outsized value to the company. When people feel their own work is not important they seek other work that appears to be important. So, you get the behavior of a lot of opinions on a pricing calculator.
- roenxi 2y ago> In an internal poll, 7 of every 10 people in the company thought the version with the calculator would do better. An interesting and pretty classic dynamic - I liked the article overall but I think this point didn't get the highlighting it deserved. If 30% of the people involved think that the calculator is a bad idea that signals a potentially huge problem even if the majority think it is fine. Be alert to the politics here. Although it seems otherwise, people generally don't like to criticise other teams in the business unless there is a political gain to be had. By extension, if I polled the company and asked "is this thing my team did a net positive?" I'd expect the default position to be "yes" as people wouldn't want to stir the pot for no reason. 30% of people signalling that it might be value-destructive is much more significant than it seems because of that. It should trigger some fairly thoughtful consideration of why exactly they thought that. In this case they seem to have indeed been alert to all that and the story has a happy ending, which is nice. But this poll result was always evidence of a serious problem.
- 0cf8612b2e1e 2y agoI agree in principle, but I am struggling on how you could quantifiably evaluate the contentiousness of a change. No feature will ever get 100% consensus. 30% does not seem great, but is it meaningfully different from 20%? Even better if you have mixed incentives: sales wants any and all dark patterns enabled, customer support is sick of issuing refunds because the cart auto adds extended warranty to the purchase, etc I smiled in the article when they claimed that removing the calculator might be better for users because more sales are completed. Ignoring that maybe the users were getting the appropriate amount of sticker shock, and bailing was the correct choice.
- kqr 2y ago> No feature will ever get 100% consensus. 30% does not seem great, but is it meaningfully different from 20%? Nobody is saying a feature should be automatically removed when it has 30 % detractors, just that it is a useful signal to investigate further. The specific % threshold doesn't matter. Pick one that makes you chase false positives rarely enough. The exact number will vary from organisation to organisation.
- danybittel 2y agoYAGNI: You aren't gonna need it. “Perfection is achieved not when there is nothing left to add, but when there is nothing left to take away” “Less is more” “The value of a creative product doesn’t lie in how much is there, but in how much has been discarded.” rttm: Reduce to the max "Kill your darlings" ...
- imoverclocked 2y agoIt feels redundant to agree with this comment. I will anyway. "Any fool can make something complicated. It takes a genius to make it simple." "I apologize for such a long letter - I didn't have time to write a short one." -- As for the calculator, I think it points to a bigger problem. Customers need to know what the platform will charge and a way to compare platforms in general. If the only way to truly know how much something will cost is to run their code on it, then maybe that's the thing that someone needs to implement. There are big issues with this in the most-naive implementation in that people can easily abuse the ability to run code. That suggests that perhaps we need a benchmark-only environment where benchmarks themselves are the only thing allowed out of the environment. This may require a fair-amount of engineering/standards effort but could be a game-changer in the space. A framework for being able to run this on many platforms to compare performance and pricing would lead to customers generating packages for vendors to compete. Though, I suppose it could also hide some devilish details like step-changes in rates. This same framework would be useful for other things too, like testing how implementation changes affect future bills. Also, how pricing changes between vendors might become more-advantageous over time. Of course, the sales folks might balk because they would rather have a conversation with everyone they can. Maybe I'm just advocating for a more advanced and complex calculator? ¯\_(ツ)_/¯
- mquander 2y agoI don't know if this calculator was good or bad, but the rationale sounds superficially ridiculous. > Visitors who didn't see the calculator were 16% more likely to sign up and 90% more likely to contact us than those who saw it. There was no increase in support tickets about pricing, which suggests users are overall less confused and happier. Of course if you hide the fact that your product might cost a lot of money from your users, more of them will sign up. Whether they are better off depends on whether they end up getting a bill they are unhappy with later at some unspecified future date, or not. That's not something you will figure out from a short-term A/B test on the signup page. So this seems like totally useless evidence to me. I see this dynamic frequently with A/B tests. For example, one of my coworkers implemented a change that removed information from search result snippets. They then ran an A/B test that showed that after removing the information, people clicked through to the search result page more often. Well, obviously, it makes sense that they might click through more often, if information they wanted which was previously in the snippet, now requires them to click through. The question of which is actually better seemed to have been totally forgotten.
- imoverclocked 2y ago> Whether they are better off depends on whether they end up getting a bill they are unhappy with later at some unspecified future date, or not. How is that a function of the overly-simplified and often-wrong calculator? If the user is never there to be happy/unhappy about it in the first place, then how would you test this anyway? By closing the loop and increasing engagement, you are increasing the chance that you can make the customer happy and properly educated through future interactions.
- afro88 2y ago> often-wrong The author was very careful with their words: they didn't say the calculator was wrong. They said it was confusing and sensitive to small adjustments. It's likely that the same confusion and variable sensitivity exists during usage. IMHO they should have bit the bullet and revised the pricing model.
- 2y ago
- FridgeSeal 2y ago> We assume that if something exists then it exists for a good reason I suspect that this often exists because people have tried this, and been summarily burnt by either politics, or some form of Chestertons-Fence. Which leads to the question of: how and when do we discern the difference? How do we design our teams and engineering to do things like, - ensuring the psychological or political safety to suggest slimming down systems without having every other team come down on your head. - incentivise “svelte” systems at a product level, without falling into Google-levels-of-“lmao this is going away now thanks bye” - engineer for slimmer systems. There’s lots of ink spilled on the topic of making things extensible, or able to have stuff added to it, but seemingly little about the opposite. Is it the same engineering practices, or are there other concerns you’d need to take into account, if so, what are they? - would you as a customer pay for something that was better at its purpose but didn’t have every single feature under the sun? I sure would, how many other people/orgs would, if given the option? I semi-controversially think that too many tools providing too much flexibility mostly encourages orgs to paint themselves into wacky processes, just because they can. I doubt this entirely goes away, but if given less feature/flexibility bloat, how much “fat” (process/overhead/friction/etc) could be trimmed out?
- android521 2y agoYour biggest next TODO is to rethink how you price the usage and make it 1000% simpler.
- xiphias2 2y agoMay be the problem is just having so many people (the real cost). Pinecone is just generally thought as something extremely overpriced: https://www.timescale.com/blog/pgvector-vs-pinecone/ https://www.timescale.com/blog/pgvector-vs-pinecone/ Until they can solve the feeling (or cut down on their own overhead), I don't see that great future for the company.
- gk1 2y agoThere's a simpler explanation: The authors of your linked post purposefully set up Pinecone to be as expensive as possible in their test. No pricing calculator or benchmark post (from a competitor, no less) will replace just trying the service yourself.
- redskyluan 2y agoInteresting case study, but I'm skeptical of the broader implications. Pinecone is notoriously expensive compared to other vector database services. A horizontal price comparison reveals several better options in the market. Removing the calculator doesn't solve the core issue - it just obfuscates costs and makes it harder for users to compare options upfront. In my view, this approach merely reduces the comparison stage, potentially leading more uninformed users to upload data without fully understanding the pricing implications. While simplification can be valuable, in this case it seems to benefit the company more than the users. A better approach might be to improve the calculator's accuracy and usability rather than removing it entirely. Transparency in pricing is crucial, especially for B2B services where costs can scale quickly.
- jmathai 2y agoNot only is it often better but it can literally enable you to get to market an order of magnitude faster (at with higher probability of success). I'm working on a tool that makes running wire inside residential homes easier. It requires carving a channel on the back side of the baseboard. My original idea required a mechanical tool with a motor [2]. We prototyped a working version of this but always felt that the manufacturing challenge would be large. We ended up adapting the system to existing routers. That meant our product was just a series of extruded parts with almost no moving parts [1]. [1] https://trywireshark.com https://trywireshark.com [2] https://www.youtube.com/watch?v=DTzsU9gMF3I https://www.youtube.com/watch?v=DTzsU9gMF3I
- nxicvyvy 2y agoWireshark is a pretty bad name to choose.
- jmathai 2y agoYeah - I didn't think there would be confusion with the networking tool but based on feedback we're receiving...I was wrong. We're considering options including changing the name.
- imoverclocked 2y agoThe HN feedback is likely heavily biased… even if you are deploying your product in Silicon Valley. Most people that will be fishing wire through their home have never heard of the networking tool. ie: You might consider not changing it too :)
- neonz80 2y agoI guess Ethereal is available :)
- teqsun 2y agoYou're in a niche(ish) space, that doesn't have a lot of general overlap with HN. I can say "I wish someone made a cheaper alternative to the Domino" and anyone in the space will understand what you mean instantly. But from an original analysis others might of told Festool that it was a bad name that will confuse people.
- raylad 2y agoI experienced something similar. We had a website with several products that seemed fairly similar, so we were concerned that people might have trouble deciding which one to get, and not buy as a result. So we made a product advisor applet where the user would answer a few questions and it would suggest one or two products that would be best for them. Getting the applet right took a bit of work, but once it was done it worked very well. We put it live on the site and.... conversions dropped precipitously. We A/B tested it and yep, it definitely hurt conversions. I still don't know why it hurt conversions, but it did. So we moved it from the homepage to a FAQ section of the site, and hardly anyone ever used it at all.
- lathiat 2y agoThat is the value of testing things. Sometimes the result is non obvious :)
- quectophoton 2y agoSo maybe your advisor applet actually helped people, they were not buying just because it was the best choice for them given all the additional information you were now giving them? > I still don't know why it hurt conversions, but it did. Maybe people were indecisive and you just saved them trouble of trying stuff to find out for themselves. If it was a service, then maybe they were signing up just to try because they weren't sure, and then taking advantage of sunk cost fallacy by pulling out an Amazon Prime strategy. Or, maybe without the advisor applet they might sign up thinking they can get away with the cheapest version (e.g. like people who purchase 3-5 EUR/month VPS), but with the applet you deny those hopes right away. If it was physical products, then you might have helped them out of a bad purchase. > So we moved it from the homepage to a FAQ section of the site, and hardly anyone ever used it at all. Yeah I wouldn't expect to find it there. In the footer, maybe. But not in the F.A.Q., so there's that.
- Onavo 2y agoThis is how you end up with cars with no stalk and no shifters (cough, Tesla).
- refibrillator 2y agoUpvoted to spread the immense wisdom in this post. But golly I must say the line can get blurry quickly. > Would anything of value be lost if this or that chunk of it was removed? In early stage projects I’ve seen this mentality backfire occasionally because it’s tough to estimate future value, especially for code and data. For example, one time in a greenfield project I created the initial SQL schema which had some extra metadata columns, essentially storing tags for posts. The next week, a more senior engineer removed all those columns and associated code, citing the YAGNI principle (“you aren’t gonna need it”). He was technically correct, there was no requirement for it on our roadmap yet. But the original work had taken me maybe an hour. And the cost of keeping the data around was approximately zero. It seemed he didn’t consider that. Guess who needed the columns to build a feature a year later? Yeah me, so I found myself repeating the work, with the additional overhead of prod DB migrations etc now that the product had users. I guess my point is, sometimes it’s also wise to consider the opposite: Would anything of value be gained if this or that chunk of it was removed? In this article the evidence is clearly affirmative, but in my case, well it wasn’t so clear cut.
- pentaphobe 2y agoThanks for this balanced (and IMO necessary) reminder. It's all too easy to get caught either doing way too much defensive/speculative stuff, or way too little. one person's "premature optimisation" is another person's "I've seen roughly this pattern before, I'll add this thing I wished I had last time" - and AFAICT there's no _reliably_ helpful way of distinguishing which is correct.
- dmacj 2y agoWhat was the DB migration required for those particular columns? I presume this was not the only time such a migration needed to be done to add columns. Is it possible that as new features emerge, new columns and migrations will need to be done anyway and one more or less migration would make less of a difference on the grander scale?
- shubhamjain 2y agoIn most cases though, anticipating requirements results in building things you don't need. And if you do need them, you usually end up needing a very different form of it. The worst codebase I have worked on is the one that was designed with some complex future-use in mind. In your example as well, the codebase only required columns a year later. So I think removing all chunks of code that anticipate a future need sets the right precedent, even if you end up needing it eventually.
- jaimex2 2y agoListened to a Lex Fridman podcast and wrote an article on it. Nice.
- jaimex2 2y agoYes - the Elon Musk one!
- whakim 2y agoI don’t get it. Presumably the pricing model didn’t change, so all you’ve done is push the burden of doing the math onto the user (or more realistically, hope they just don’t even bother?) If users are frequently estimating costs that are off by orders of magnitude, surely the correct response is to change the pricing model so it’s easier for customers to understand?
- gk1 2y agoOnce they’re using the product they can see their actual usage and cost metering. So they can either extrapolate that to larger scale or test it at scale for a short time to see hourly/daily cost and then extrapolate for the month or year. In other words it’s not much of a burden and they get much more reliable information.
- whakim 2y agoBut they can still do that even if there's a cost calculator upfront. Removing the calculator simply obfuscates the ability to estimate cost with the happy justification that fault lies with the customers who all seem to be bad at estimation.
- olejorgenb 2y agoIt's not a burden to actually spend time setting up the system? This is usually a non-trivial amount of work.
- duped 2y agoTo be a sociopath for a second: Up-front pricing is only good for the buyer and never good for the seller. And while being an advocate for the user is a good thing in general, it's not a good thing if the result is less revenue. And if you want to present a pricing estimate your incentive is always to lowball and underestimate. Businesses that are successful tend to exploit information asymmetry. This is frustrating as a consumer but if you can guarantee that the user doesn't know their final cost you can always sell them a sweeter picture than reality and play off the cost of switching to a competitor, if one exists. Total aside but this is why housing prices are insane, at the most micro level no buyer has any idea over the final cost until the last possible moment at which point the cost of undoing the transaction probably outweighs the risk of continuing - psychologically, at least. (I may or may not have been the victim of this recently and thought about it from the seller's side)
- shahzaibmushtaq 2y agoWe, as humans, always carry a few types of things with us on a journey. Things we like, things we don't like, things that are totally useful, things that are somewhat useful etc. There comes a point where we need to let go of the thing(s) we like - I called them the precious payload where we are most reluctant - and in this case the 'calculator' was the precious payload so many people in the company were unwilling to remove this feature except for one person. In business, adding a completely new feature or subtracting an age-old feature is extremely difficult but oftentimes, this is where growth comes from.
- nercury 2y agoI hope the wages of sales people are lower than that of a calculator.
- sylware 2y agoSoftware is finished when there is nothing else to remove.
- julienreszka 2y agoDubious claims with really terrible arguments. Simply removing a feature without addressing the root cause of confusion will lead to other problems down the line, such as increased customer support demands or user dissatisfaction when actual costs differ from expectations.
- lonelyasacloud 2y agoIs not just true within product design, but is even more of an issue with regards to the rules that our societies live under.
- scotty79 2y ago> The calculator also gave users a false sense of confidence, which meant they were unlikely to double-check the estimate by reading the docs, contacting the team, or trying it for themselves. How dare they think that a thing called calculator is accurate and not double check!
- gk1 2y agoThat’s the point, nobody should expect them to.
- sethammons 2y agoIs it standard to use percents of percents in conversion tracking? Going from 20 to 23% conversion rate is not a 15% increase in conversions, it is 3%. If that is the kind of shenanigans being played, there is something else to remove
- Rastonbury 2y agoIt is. To simplify, if every conversion makes the company makes $1 and 100 prospects enter this funnel, going from 20 to 23% means they make $23 instead of $20
- unregistereddev 2y agoAgreed, and to stress for clarity: Adding 3 percentage points to the conversion rate increases revenue by 15% in this example.
- adamtaylor_13 2y agoI just finished Elon Musk’s biography by Walter Isaacson and I was struck by how often this actually works. Whether you’re actually sending humans to the ISS, or building cars removing requirements and complexity is a surprisingly effective tactic. I love his “algorithm” for getting shit done. The final step is, “If you don’t put back at least 10% of what you take out, you aren’t removing enough.”
- john_minsk 2y agoGreat post and Elon Musk has similar rule in his thinking. For anyone who liked the trick in the post consider checking out TRIZ: https://en.m.wikipedia.org/wiki/TRIZ https://en.m.wikipedia.org/wiki/TRIZ There are too many interesting ideas in this framework, but one of the first steps in the algorithm of solving a problem is to "Formulate ideal final result", according to TRIZ. Now the "Ideal final result" has a specific definition: The part of the system doesn't exist but the function is still performed. I'm having a lot of fun with this and other tools coming from TRIZ when solving problems every day. You might like it as well! As for A/B testing and getting unexpected results: inside TRIZ there is explanation why it works - it is called "Psychological innertion". i.e. when engineer is getting a problem it is usually already formulated in a certain way and engineer has all kinds of assumptions before he even starts solving a problem. This leads to him thinking along specific "rails" not getting out of box. Once you have algorithm like TRIZ, it allows to break through psychological innertion and look at the problem with clear eyes. Some other trick one might use to find interesting solutions to the problem from the post: "Make problem more difficult". I.e. instead of how to make calculator simple and unrestandable, formulate it in a different way: "how to make calculator simple and unrestandable, visual, fun to use and interact with, wanting to share with your collegues?" "Turn harm into benefit". calculator in the post is treated as a necessary evil. Flip it. Now we have a calculator, but we could show some extra info next to prices, which our competitors can't do. We can compare with competitors and show that our prices are better, calculator can serve as a demo of how customer is always in control of their spending as the same interface is available after they become customer to control their spend etc. Formulating this way already gave me some ideas what could be added to calculator to make it work. Hope it helps someone.
- zuckerma 2y agono doubt about it.
- draw_down 2y ago[dead]
- latexr 2y agoHere’s a followup for the author: follow your own advice. Remove the “Psst... Get the next post in your inbox” interruption midway through your post. Dare to remove the stupid button that follows you around as you scroll. I counted five obvious ways to subscribe on that page alone. Five! Do you really need to shove them in our faces and in the middle of the freaking content? Do you think you get more subscribers by interrupting people and being annoying? Are those the kind of subscribers you want? Removing stuff is often obvious, you just have to take your mind out of the “more more more, make money, attract customers, more more” gutter mindset and think “what is respectful to users, how can I help them while simultaneously treating them like human beings instead of wallets to be milked”.
- blueboo 2y agoIIUC the lesson of blog SEO is that, if you want to grow your readership, copious attention-co-opting calls to action are unambiguously worth the annoyance foisted on discerning readers. What’s respectful to users is a separate (but not wholly unrelated) question…
- latexr 2y agoEven if that’s true (I’m not convinced it’s unambiguous), my points still stand: Are undiscerning readers the kind of subscribers you really want? Perhaps so if you are, as per my last paragraph, the kind of person concerned with profit over quality. If you are, it shouldn’t come as a surprise that you don’t see removing stuff as obvious and your mind only thinks of adding more junk.
- btbuildem 2y agoMy employer has something like 250 products. Five of them are responsible for 80% of the revenue. Dev teams of those five are stretched thin, barely able to keep up with bug fixes, and struggling to add new, important features -- so much so that getting anything on the roadmap is an impossible battle, no matter who is asking. There are thousands of devs at the company, most of them attached to the products that contribute relatively nothing to the revenue stream. I don't know if it's not obvious -- it must be obvious -- that to move forward the right thing is to cut most of the products and refactor the teams to drive the remaining money-makers. Yet, this has not happened, and I see no indications, no murmurs of it happening. Corp politics are wild.
- PaulHoule 2y agoI never feel more productive than on the days when I can delete a whole lot of code.
- james_marks 2y agoReminds me of the advice that, if you need to join two mismatched pieces together, you have two options. 1)Add an adapter that’s customized on both ends, or 2) subtract the differences so they mesh directly. Always look for opportunities to subtract, rather than add. Your system gets easier to understand over time as it becomes the purest representation of itself, instead of a collection of gap-fillers.
- snarfy 2y agoThe sad truth is, nobody ever got promoted for removing stuff.
- deleted 2y ago[deleted]
- iamleppert 2y agoWhy stop there? Why not just remove all pricing completely, and let your clients contact sales for the shake down? That model seems to work great for many SaaS companies.
- bob1029 2y agoThe last approximation of this that really stuck with me was The Bitter Lesson. It would seem a common thread is our inclination to embed part of our ego into everything we do.
- deleted 2y ago[deleted]
- ivanjermakov 2y agoHow common is dropping a feature because of A/B testing results? I feel like it should have a lower priority on such business decisions. My guess is that calculator removal was approved before A/B testing have started.
- isoprophlex 2y agoI love how this lesson applies to AI software products: it might not be obvious at first, but removing that dedicated vector database (which is only there because everybody's using one in the first place) often improves things :^)
- HiHelloBolke 2y agoremoving unobvious bugs makes things better
- kazinator 2y ago> If there's a big backlash from the team then you're on the right path. People hate the proposal to remove the microwave ovens and free coffee from the kitchen, so it must be the right idea!
- nothackerfox 2y agoI can see how this can be so useful across the board. Well explained with something as tiny as a calculator. And, yes, removing things should be rewarded. It's a cognitive bias to reward just for adding things.