HN user

lukestevens

794 karma

i enjoy lurking on this website

Posts27
Comments124
View on HN
colossus.com 4mo ago

We Have Learned Nothing

lukestevens
89pts58
lukestevens.co 1y ago

Show HN: Founder Vision (Book) – Positioning and Narrative for B2B Founders

lukestevens
1pts0
www.forbesindia.com 4y ago

He wanted make his revolutionary code free. But Ali Ghodsi is now a billionaire

lukestevens
16pts0
www.notion.so 4y ago

Migrating Notion's marketing site to Next.js

lukestevens
3pts0
helenmin.com 5y ago

Developer ‘Marketing’

lukestevens
1pts0
www.theguardian.com 5y ago

Almost third of UK Covid hospital patients readmitted within four months

lukestevens
2pts0
www.forbes.com 5y ago

Chris Sacca Unretired: Why He’s Back Investing in Climate Startups

lukestevens
3pts0
www.wnycstudios.org 5y ago

Radiolab: The Ceremony

lukestevens
2pts0
sparktoro.com 5y ago

SaaS Churn and Short-Term Customers: The Contrarian View

lukestevens
2pts0
www.intercom.com 5y ago

Product Judgment: How some people can repeatedly create product success

lukestevens
1pts0
www.inputmag.com 5y ago

iPhone 12 Pro Max review: Extremely overhyped camera

lukestevens
2pts1
journals.plos.org 5y ago

Systematic A/B testing of digital messaging cut hospital no-show rates

lukestevens
2pts0
www.crikey.com.au 5y ago

The great Google-Facebook heist

lukestevens
2pts0
medium.com 6y ago

The Curious Case of Japan in Covid Times: Where It Went Wrong for the Abe Admin

lukestevens
3pts1
www.smh.com.au 6y ago

Thousands of medical histories exposed in data breach

lukestevens
1pts0
blog.amp.dev 7y ago

AMP as Your Web Framework

lukestevens
2pts2
dejanseo.com.au 7y ago

How I recorded user behaviour on my competitor’s websites

lukestevens
766pts309
github.com 8y ago

Transparency and the AMP Project

lukestevens
21pts3
www.appcues.com 10y ago

Your User Onboarding Flow Is Too Shortsighted

lukestevens
1pts0
thatsanicepage.com 10y ago

Tesla's Model X Product Page: A Surprisingly Lazy Effort

lukestevens
1pts0
thatsanicepage.com 10y ago

Tesla's Model X Product Page: A Surprisingly Lazy Effort

lukestevens
1pts0
thatsanicepage.com 10y ago

Oculus Rift – Product Page Teardown [slides]

lukestevens
3pts0
thatsanicepage.com 10y ago

Amazon’s Kindle Oasis 3000-word Product Page Is a Weird 90s Throwback [slides]

lukestevens
1pts1
thatsanicepage.com 10y ago

Show HN: That’s a Nice Page – Teardowns of Product Pages Worth Talking About

lukestevens
1pts1
philippkuehn.github.io 10y ago

Gridilydidily – Sass based flexbox grid with inline-block fallback

lukestevens
1pts0
www.filamentgroup.com 11y ago

Research: First Render Times of Popular JavaScript MVC Frameworks

lukestevens
10pts0
responsivenews.co.uk 13y ago

BBC News' Response-ish Web Design

lukestevens
1pts0

Indeed. Is there a word or phrase where the outcome of your actions is the exact opposite of your stated goal or motivation?

Closest I can think of is destroying the village to save it, and I think that's very much the territory we're in here.

As a dabbler in startup punditry (I've written a couple of books on startup positioning), I find Jerry's take very thought provoking.

The crux of the issue for me is what Dr Iain McGilchrist highlighted — we attend to the world in two very different ways. One mode of attention is a broad, open awareness to what's 'out there' and the other mode is a much more narrow focus on the parts and pieces.

For startups, when you look at the actual cases, many successful founders, almost by definition, had to stumble across their insight in some emergent fashion. They either experience some pain and set about solving it (Dropbox); see some opportunity on the horizon (OpenAI); or stumble onto some idea while working on something else (Slack).

If you want to do a startup, or your current idea isn't working, and you don't have that vision of emergent opportunity, then what do you do? "Just look for some emergent opportunity" isn't very compelling advice (even if it's probably the most accurate).

This is where the punditry emerges. You have to use your other mode of attention in an attempt to brute force some insight through narrow-focused analysis, and that analysis is inherently constrained to your (by definition) barren environment. That gives you the Lean Startup, customer development, etc etc. This far more analytical approach requires (a) intense discipline; (b) a lot of luck because you're starting from a point of no opportunity; (c) enough volume to actually do the interrogation of reality.

And it may not work because it's simply using the wrong mode of attention, anyway!

Nevertheless, frameworks that exist in this realm all sound reasonable because, on one level, they are: what else can you do but interrogate reality in some methodical way? But the question TFA raises (in my mind) is whether shaking the tree like this — IF you even can with appropriate discipline — reveals emergent opportunity for startups at a scale that's reflected in the broad outcome data, and the answer appears to be no.

Interestingly, the book The Heart of Innovation[1] tries to tackle this by going to the extreme. It's not about finding some clues in fast iteration or mapping out a canvas with a nice value prop, it's about finding 'authentic' demand that's so compelling it's something users can't not do. (The 'not not' concept is hard to explain but creates a much more rigorous bar for innovation IMO.)

That's their backward-looking observation for innovations that stick (and reflects most of the cases in the book), but they're still faced with the same dilemma of what to do if you aren't blessed with emergent opportunity.

In that case, their solution is to ramp up the analysis even harder, with 150-200 "Documented Primary Interactions" observations. I.e., brute force observations even harder. Some of the authors are part of a startup accelerator with an (apparently) high hit rate, so it's not just speculation.

All told, it's amazing that billions and billions of dollars are allocated to startups and so little is invested in studying innovation itself, especially given how slight the predominant frameworks are. Yet new ways of thinking exist (like McGilchrist, or the Heart of Innovation approach), so I wonder if frameworks for innovation are still in their absolute infancy, really, where the ones that succeed suffer the memetic curse: simple enough to travel; too simple to be effective.

[1] Excellent overview here: https://commoncog.com/the-heart-of-innovation-why-startups-f...

But it is AI! Or, at least, it's been run through it. (Staccato sentences; Not X. Not Y. Z...) It's a shame for a personal reflection. It's hard to imagine what the (I'm guessing) Claude-isms add that improve what would otherwise have been a nice unmolested personal essay.

Bugs Apple loves 6 months ago

The most egregious bug/s I've encountered in recent years is the utterly cursed tab management in iOS Safari.

A couple of times a year it will just nuke all my open tabs (450-500) and present me with a delightful blank screen. Before that it will mislabel the active tab group on and off before giving up entirely.

Quick action on my part stops the destruction syncing & I usually end up recovering them on my Mac & then save them as a tab group.

But literally just an hour ago, iOS Safari looked like it nuked ALL MY TAB GROUPS. Ugh. They were gone; swiping right led to the "New tab group" screen. Frantic backing up and a restart later, and the tab groups are back, as though the phone was like "just kidding!". FML. So much for that backup plan.

UI bugs are one thing, but how is that level of data loss acceptable in a modern operating system? Boggles the mind.

(And don't get me started on the UI track wreck that is the iOS-inspired/inflicted bookmark management on macOS Safari, where all Mac UI conventions went out the window for some reason.)

Bugs Apple loves 6 months ago

The emoji picker refusing to be summoned drives me up the wall. There's a dedicated key for it! And yet...

I've used Time Machine for years with a cheap HD hanging off an old Airport Extreme, until today, incidentally.

MacOS had started warning that this approach won't be supported in the future. After upgrading to Tahoe, Time Machine kept saying backup failed, no matter what I did, despite the fact it should still work. Oh well, I'll just delete the old backup and create a new one.

I delete the old backup, click "Add Backup Disk...", select the backup disk, and get blocked with "[Drive] can only be used if it contains existing Time Machine backups for this Mac." It did! You broke them!

UGH.

I thought I'd get another year out of it. Apple in their wisdom has decided otherwise. Now I have no historical or ongoing backups.

Any recs on what to use instead?

I don't mean to be rude but this idea that there's some decisive, authoritative data vs. sketchy anecdotal claims kind of drives me up the wall.

What data would or could exist in this case beyond the hundreds of calls the author is apparently basing their observations on? That seems like a reasonable qualitative data set to me.

On the other hand, what you're asking for doesn't make much sense. Any push/pull strategy difference is going to change who takes a call in the first place. You're not doing a RCT on a random sampling of the population.

The point is simply that you're going to have a better time doing sales if your supply matches some pre-existing demand. You don't need a quantitative study to understand why that may well be the case.

It's the same reason that, despite being bombarded with advertisements, we don't all go out and buy 16 meals a day or 10 cars a year simply because someone tried to sell those things to us. We act when we have a need, and founders need to understand that as a physical reality when trying to sell their products.

Fellow OCD-ish charge watcher here. Has worked great for my aging iPhone.

What grinds my gears though is the AirPods. I have AirPods Pro that I want to last a long time, but out of the case the earbuds are always 'on' and drain battery relatively quickly (much faster than a phone left idle); put them in their case and they're almost always* charged to 100%. I want to be able to leave them out, off, and disconnected. I almost never need 100% battery in my day-to-day use and there's no replacing the batteries in them once they're worn out.

An 80% max charge limit would be great.

*They do offer 80% overnight charge protection, but that's irrelevant as I don't keep them plugged in overnight

Yeah, in this case, from memory, the spec author had a list of class names from a scraped HTML data set. He looked at the most common classes — nav, header, footer, and so on — and declared they should be made native elements.

Which would have been fine, except even the most obvious ones (header, footer) were given very idiosyncratic definitions, and others (article, section, aside) were seemingly thrown in at random.

This led to absurd examples where, as is still in the spec, a blog comment is an <article> and the comment's header is a <footer>. This of course undermined the original premise -- that these elements were just 'paving the cowpaths' of how people were authoring HTML, but the spec author would have none of it and shipped them all the same. And here we are. :)

A decade ago, in an act of extreme futility, I wrote a book about HTML5. I did the mailing list archaeological dig to discover the logic behind these and other new (at the time) elements. There really wasn’t any. The spec editor just made them up on a whim with very eccentric definitions. I found that very frustrating as I saw it as inflicting a whole array of meaningless choices on front end folks for years to come. A decade later, and folks are still earnestly trying to divine the wisdom of the spec. No need — there isn’t any. There’s no there there. I don’t blame the author for trying, but I do blame the spec author for a very silly rabbit hole that people are still falling down to this day.

That's really fascinating, thanks so much! I like the sound of your two cycle pitch approach -- kind of putting 'measure twice, cut once' into practice. And I admire your ability to wrangle a larger betting table & bring others into the pitching process!

(Of course, we don't do Shape Up in exactly the way described in the book: rather than cargo-culting, we've tailored the process to fit our business, which is a very different business to Basecamp. Happy to offer more detail if anyone is interested.)

Sure, would love to hear more about your use of Shape Up. What have you found that has worked in your context that goes beyond the initial framework, for example? :)

It’s a strange pattern [0]:

[Sophie Zhang] joined Facebook in 2018 after the financial strain of living on part-time contract work in the Bay Area had worn her down. When she received Facebook’s offer, she was upfront with her recruiter: she didn’t think the company was making the world better, but she would join to help fix it.

“They told me, ‘You’d be surprised how many people at Facebook say that,’” she remembers.

[0] https://www.technologyreview.com/2021/07/29/1030260/facebook...

Yes, I'd love to see a more robust approach to novelty decay rates (to make up a metric) in A/B testing, especially around engagement.

You'd think that would be of interest to the business to know that X "successful" intervention had a typical average lifetime of Y before reverting to the mean, for example.

Then again, there's the idea that competitive advantage for social networks is just finding enough novel interventions before the novelty of the platform itself is exhausted, and FB has no short supply of other platforms to milk in that regard.

The SaaS Org Chart 5 years ago

I don't know, it sounds like you've got a pretty myopic view of marketing if you think FB/PPC ads ('tactics that work') are what should drive strategy. Combine that with experience with PMMs who are too far removed from the customer (!) and I can see why you think product marketing is pointless.

From the other side of the B2B marketing fence, I see demand gen burning loads of cash on "high converting", highly "tested" ads that look great in reports, except that those leads never turn into customers, because the PPC marketers never track their revenue that far, and those lowest common denominator leads aren't a great fit for many B2B products anyway.

I suspect that if your argument is "Well, they should build the product that those leads want" I can see why (a) that view would indeed be unpopular, and (b) why you would be in conflict with product marketers who want leads that match the positioning, not positioning that matches the leads.

When all you've got is a hammer...

Not sure why you’re being downvoted — many people would and indeed did find that useful vis a vis Sony’s Aibo. In fact, when those robotic dogs became unrepairable, some people would have a funeral for them: https://www.theguardian.com/world/2018/may/03/japan-robot-do...

Many of the dogs are accompanied by notes written by their former owners. “I feel relieved to know there will be a prayer for my Aibo,” one said. Another wrote: “Please help other Aibos. My eyes filled with tears when I decided to say goodbye.”

Just wanted to say that is an exceptionally well-written launch post.

- Solid summary

- Novel solution (omg AIDA in a CRO tool!)

- Clear benefits spelled out vs the competition

- Relatable use cases

- Jumping off points to explore the rest of the product

The product of years spent thinking about the problem I guess! Good stuff :D