TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Automation != Leverage

58 点作者 sethkim超过 3 年前

10 条评论

pydry超过 3 年前
I worked for a company once that was trying to let people book something online that people often did by talking to salespeople in a shop. These companies were slowly dying as people started to do it more online.<p>Their initial strategy was to automate the crap out of everything. They would try to to keep margins low and part of that was to try to avoid having people talk to non-scaleable customer sales agents.<p>They did pretty poorly in the beginning until they decided to do a 180 and allow people to have full control in the sales funnel over when they would like to use the website and when to talk to a person (including not using the website the whole way if they so chose).<p>When they did this sales and profits took off like a rocket.<p>They then hired enough customer service agents to service demand this way (which was a lot).<p>I thought it was interesting that they kind of stumbled from 100% automation to a kind of hybrid model that hit an amazing sweet spot.<p>They did try to reduce certain types of call volume by A&#x2F;B testing website copy and the like but they always made it super easy to pick up a phone and give a code and instantly talk to someone who could see all their details and never tried to discourage anybody even if doing it online was trivial.
评论 #29095185 未加载
评论 #29093305 未加载
评论 #29096787 未加载
icebraining超过 3 年前
This sounds a lot like pg&#x27;s Do Things that Don&#x27;t Scale: <a href="http:&#x2F;&#x2F;paulgraham.com&#x2F;ds.html" rel="nofollow">http:&#x2F;&#x2F;paulgraham.com&#x2F;ds.html</a>
评论 #29096801 未加载
fitzn超过 3 年前
&gt; sometimes it requires doing great work manually before you should ever consider automating the task<p>I&#x27;d say this is the crux of it. You (or someone before you) should _always_ do something manually before automating it. If you see existing automation, make sure that it solves exactly the problem you have before you implement it. And the best way to see exactly the problem you have is... to do it manually.
评论 #29085290 未加载
rambambram超过 3 年前
This article couldn&#x27;t come at a better time for me. I have a list of websites&#x2F;businesses in my area that could profit from a redesign, which I happen to offer with my website builder. I&#x27;m now contemplating if I should automate this and go shotgun-method in the hopes some prospects turn into customers, or I could put in more time but also quality to convince only a small percentage of the list to become customers.<p>Stuff for thought. Thanks for the article.
评论 #29094161 未加载
dgb23超过 3 年前
Good article! Two things popped into my head when reading it. First the talk &quot;Programming with Hand Tools&quot; by Tim Edwald[0]. It&#x27;s a very cool, entertaining talk with emphasis on the craftsmanship side of things and provokes thinking about which parts to automate (or maybe abstract away) and which parts to craft by hand when we&#x27;re building stuff. Aside: also reminds me of Casey Muratori&#x27;s Handmade Hero project [1]. He is a strong advocate for structuring things bottom up and building them ourselves.<p>[0] <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ShEez0JkOFw" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=ShEez0JkOFw</a><p>[1] <a href="https:&#x2F;&#x2F;handmadehero.org" rel="nofollow">https:&#x2F;&#x2F;handmadehero.org</a><p>---<p>Secondly when reading this:<p>&gt; Regardless, the basic idea is that companies are often faced with the decision of doing N units of shitty work or far fewer than N units of great work.<p>This is obviously oversimplified, but there is an important point that wants to emerge from this line of thought.<p>As someone who grew up on open source, standardized technologies and the Web, I have been empowered to build a livelihood on Web development, mostly &quot;self-taught&quot; (or rather self-directed). All of this Web stuff is very accessible and gives you actual _leverage_. You can build something useful very quickly and the community around it is happy to share so much knowledge and work. I&#x27;m _very_ thankful for that.<p>But I think as the wider web development community we&#x27;re losing sight of what that essence is. We started to think of the Web as merely a vehicle for pure scale as in &quot;how to reach the most people and annoy them with notifications&quot; and &quot;how to produce cheap software very fast&quot;.<p>Maybe we, or some of us, should slow the fuck down a notch and think about producing valuable things for the specific needs, pain points or taste of actual people. What the article describes is a process of thinking about the real people and building a human connection. The &quot;top 100&quot; costumers in the article are most likely people who _actually_ need&#x2F;want&#x2F;use the damn thing if they see your point. Instead of trying to manipulate the masses to buy a lot of crap (excuse my meta), we should be building relationships. One very good reason for this is that only the latter is sustainable - on all the axis of what &quot;sustainable&quot; means.<p>I&#x27;m writing this &quot;out loud&quot; partly because I started to drift into this abstraction&#x2F;automation mindset myself more and more. But yes, leverage is solving real problems.
jcutrell超过 3 年前
I take some issue with the comparison as an either-or.<p>Automation in its correct place shouldn&#x27;t replace human effort - it should augment that effort.<p>In this case, it seems one step removed to just do both of these approaches, starting with the first. During the process of finding those 100 high-confidence matches, you could identify the ones that have the most general cases, and reuse the email copy from those.<p>I think the idea that automation is intended to replace human effort wholesale is improper. We should rely on automation to handle where computers are better than humans, to give the human more time to do things humans are better at.
评论 #29097361 未加载
debarshri超过 3 年前
People often mix automation and abstraction. In some cases it is interchangeable. In lot of scenarios it is not. In my opinion there is true automation, for example automatic bank account creation, automated sales etc and then there is abstraction where you thinking you are automating but in reality you are adding n+1 tools. For instance, automated chatbot is an abstraction of a customer rep, if 90% of inbound ends up with an customer rep.
评论 #29096932 未加载
MrBurnsKin超过 3 年前
Seems like the author is comparing apples and oranges. There is speed and quality, your automation can process a task faster than an human, but lack quality. Automation can be also slower than an human but create more quality work. If the automation is slower and produces less quality, so of course you don&#x27;t want that
Msw242超过 3 年前
Mantis is 30&#x2F;mo?<p>OP can you tell us more about pricing model? 30 seems quite low, especially given that it is audio.<p>That only buys like 10 hours of time in the Philippines, for example.<p>How does pricing scale and what is included?
评论 #29094840 未加载
amelius超过 3 年前
Reminds me of:<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9087819" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=9087819</a>
评论 #29097203 未加载
评论 #29093087 未加载