Product

A 8-post collection

It just works

There’s a saying, much popularised by Apple, that distinguishes certain products:

"It just works."

It seems like a very low bar on the surface, doesn’t it?

Surely every product works, to some extent.

“It just works” only becomes a selling point when you consider how much hassle most products are to use.

Remember the last time you bought anything significant — was it entirely effortless? Was it a pleasure? Was it obvious at every step what you needed to do to start getting value from it?

I think this concept applies to services and experiences as well as products. I've written before about the experience of using my gym for the first time. And there are plenty of restaurants and hotels I've been to that fall short of the mark when judging them by the "it just works" assessment.

I don’t believe these are exhaustive, but here are a few principles that come to mind for building a product or service that just works:

  1. “It just works” means a lack of cruft and complexity.
  2. "It just works" means the product is reliable and consistently so over its lifetime.
  3. “It just works” means the maker has an opinion.
  4. “It just works” cuts to the chase, and gets the user to their desired outcome as quickly as possible.
  5. “It just works” eschews end-user choice for simplicity and obviousness.
  6. “It just works” means prioritising the primary function of the product above all else, even if that is at the expense of other meaningful uses.

These are easy to write, but very hard to achieve in a team building a real product.

It begs the question, then, why do so many products and services not “just work”?

I believe most products on the market exhibit some combination of the following:

  • A lack of care. The designers and makers just don’t care enough about the end user.
  • There is a misunderstanding of the core purpose of the product.
  • Feature creep. In a drive to make the product more attractive to more people, extra features are added in.
  • Short-term financial incentives drive cost-cutting and profit over product quality.

There are too many products that fall short of the "it just works" goal. Fortunately, that leaves tremendous opportunity for makers willing to go the extra mile.

A few products I’ve used recently that just work:

  • Granola — we’ve all been on a Zoom call that has had some form of AI note taker unexpectedly join. We’ve all experienced how useless a transcription can be. And we’ve all tried taking notes from a meeting only to find we either weren’t paying attention or missed a critical piece of information. Granola is the first note taker I’ve found that truly “just works”. You install it on your Mac, there are no awkward bots, and the results I've seen have been exactly what I wanted. It just works!
  • The Journal app — one of Apple's more recent new apps. I've

The joy of creation

Lately I have been conflicted in where I spend my time.

I love creating things. But I also love building a team, leading, marketing, and selling.

There have been patches of time where I have done very little creation, and in those periods I realise I quickly become demoralised.

I find joy in creation.

For as long as I can remember, I have been in awe of the idea that anyone can grab a computer, connect it to the internet, and build something. And that someone else on the other side of the world can then utilise and benefit from that thing.

Anyone can create something of value, and you don't need to ask anyone else for permission.

Creating vs publishing

I don't just like creating, I like publishing.

Don't get me wrong, publishing can induce immense fear.

But I get a kick out of directly creating something and then putting it live.

Getting feedback is addictive — whether it's seeing usage, receiving comments, or simply knowing "it's out there".

I sense that the act of creating is never complete, but publishing (or shipping) is a marker to say: I've completed the first step.

"Publishing" can mean anything here — deploying to production, putting a blog post live, hitting send on a Tweet or Thread, or even just writing an idea down and sharing it with your team.

The critical benefit of "publishing" is that you not only get to call your work "done" for now, you get to receive at least a little feedback: did anyone care?

Speed vs perfection

There's a study I read a while back in the book Art and Fear that summarises the dichotomy of aiming for perfection:

The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality.

His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: fifty pound of pots rated an “A”, forty pounds a “B”, and so on. Those being graded on “quality”, however, needed to produce only one pot – albeit a perfect one – to get an “A”.

Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity. It seems that while the “quantity” group was busily churning out piles of work – and learning from their mistakes – the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay.

Ever since I read this, it changed my views on perfection.

"Quick and scrappy" is often viewed as "not the proper way". The proper way is to do X and Y and Z in a specific order.

In reality,

Thready or not, here I come

As you’ve probably seen, Meta launched their newest app today, Threads.

It’s like Twitter, only considerably slimmed down.

For day one, it seems it couldn’t have gone better for the makers of Instagram.

As someone who geeks out on tech products all the time, I find the Threads launch fascinating, so I jotted a few notes and observations down about it.

Timing is everything

It’s no coincidence that Threads is launching in the same week that sentiment towards Twitter is at an all-time low.

Elon Musk decided to enforce aggressive rate limiting for all users, made Tweeetdeck redundant for many, and obliterated the value of public URLs by preventing tweet embeds for non-logged-in users.

It’s clear Threads could be better.

It could have more features.

It’s not quite ready when you compare the feature checklist.

But launching this week while Twitter is in the dumps (more than usual) may just give it the strong gust of goodwill that helps this spark of a product turn into a full-blown, roaring fire of a platform.

Ship early, iterate

Many “critical” features aren’t in at launch, but is the app and experience solid? Is it easy for new users to onboard? Is the experience reaching a threshold that the majority of users will enjoy and trust? Yes.

You want the ability to filter your feed, you want better search, you want to have more clarity on who’s following you. You want an API. You want the app if you’re in the EU!

But all of those are trade-offs between shipping now or shipping later.

Someone had to make that call. The easy option is always to wait. Waiting always feels safer.

Shipping this week looks like it was the right call. The rest can come later.

Aside: If you’re interested, a while ago I wrote about the importance of shipping early, and often.

Nothing to lose

What I’ve enjoyed most so far as an observer of the Threads launch today has been seeing Meta operate like they have nothing to lose.

Launch today. Move fast. Share the numbers. Integrate with the open standards (eventually).

It seems unlike many of Meta’s most significant big launches: Instagram Stories was a bolt-on to not lose out to Snapchat, Reels is another tab to avoid losing out to TikTok, and Instagram itself was an acquisition.

Threads, though, is a joy to see: Zuck and the team building something that doesn’t just compete, but that could genuinely be better than Twitter. Making something people want. With a beautiful blank slate.

Maybe I am just relieved to not have another tab, view, or swipe in the Instagram app. Or perhaps it’s that my trust in Twitter has dwindled.

Whatever the reason, I’m rooting for Threads. If you’re on it, join me!

Sign up for your own product

"You don't get a second chance to make a first impression."

If you work at a gym, you know where the changing rooms are.

If you’re joining a gym for the first time, and you’re heading in for your first session, everything is alien.

You don’t know where the changing rooms are, and if the signs don’t point you in the right direction, you’re lost.

When I signed up for a gym session recently, I felt totally lost and a little foolish, wandering around trying to find somewhere to get changed into my kit. I almost left out of sheer embarrassment before I plucked up the courage to return to the reception desk and ask.

Whether you build software, build physical products, own a restaurant, or run a gym, nothing beats using your service as a first-time user to find out how you can improve it.

It’s always great to get feedback from customers but sometimes they don’t tell you everything. Sometimes they may not even care as much as you do about the experience.

It’s easy to even get frustrated that customers don’t “get” the thing you’ve built. You’re so proud of certain elements you can easily get blinded from the areas you’ve overlooked.

A while ago, I gave a talk on user onboarding, and one of the recommendations was to sign up for your own product every week. I even paused to encourage the audience to put a recurring event in their calendars!

Several years on, I feel that suggestion is as relevant as ever, and it’s advice that’s easy for me to give and seemingly hard to follow.

When did you last sign up for your own product?

Why would Apple make a VR headset?

A quick sketch of my dream Apple headset

The silence is deafening — Apple is going to announce a VR headset imminently.

The very fact Apple hasn’t denied any rumours, and the increasing nods towards a big launch, are evidence enough. If they weren’t, then we’d know by now.

The feeling is very reminiscent of the run-up to the launch of both the original iPhone and Apple Watch — both products were widely expected to be unveiled, but the knowledge of exactly what they would entail was almost entirely unknown.

We’ve been here before

My sketches of the proposed Apple Watch ahead of its announcement.

While I never wrote about that feeling before the iPhone launch, I wrote a piece just before the Apple Watch was announced: “Why would Apple make a Watch?” in which I tried to get into the mind of the decision makers at Apple and understand why they would enter the watch market and what the device might enable.

Looking back at that piece, I feel quite proud. While I was not the only person pondering such concepts, I proposed the Apple Watch (or iWatch as I believed it’d be called at the time!) would:

  • Enable you to pay on the Subway, and allow for contactless payments — before Apple Pay came along.
  • Have easily detachable / swappable straps.
  • Become a key health companion, continuously monitoring your activity and heart rate.
  • Enable you to sleep better and wake up at the optimum time.
  • It’d prioritise telling the time at all costs, despite its smart features.

I got many things wrong too — I thought the Watch would:

  • Have incredible, unbelievable battery technology.
  • Rethink the concept of a display: “I will eat my metaphorical hat if we see a full colour backlit Retina display on the device”.
  • Be the “magic wand” remote to your Apple TV.
  • As you can see from my sketches — the physical appearance of the Watch I believed Apple would make was more akin to a Fitbit activity band.

I love reflecting on that post because it’s what makes following a secretive company like Apple so fun — you can dream and imagine, and you get to find out eventually if you were right. You get to decide if you felt Apple lived up to, exceeded, or missed your expectations.

So with an entirely new device and category just around the corner, what do we hope to see from the Californian giant?

Let’s dig in…

What will it be called?

I don’t believe Apple will call this a “headset” at all. Apple has never referred to the iPhone as a “handset” even though it’s how carriers and many consumers referred to phones before the iPhone.

Normal people don’t buy “headsets”. Headsets are for gamers and geeks.

Apple makes products for people who want the best, and they, of course, charge prices aligned with that approach.

There are numerous rumours and trademark filings, and even supposed confirmations in various code

Episode 8 of Lost and Founder — How soon should you launch?

Lead Forms by GoSquared

This week we just launched a new product at GoSquared: Lead Forms.

Launches are always exciting, and every time we do a launch we learn from it, so I decided to focus this episode of Lost and Founder on the topic of launching.

As I’ve written in the past, I feel launching is a bit like inviting your friends or relatives over to your house. Inviting someone over forces you to get your house in order — to tidy, to prepare for a deadline, and to prioritise unfinished tasks.

When launching a product or a feature, or even launching a whole new business, it’s often difficult to know when to do it. You’re pretty much always going to launch too early or too late — from my experience, it’s almost impossible to launch “perfectly on time”.

If you’re getting ready to launch something, I hope this episode is helpful for you.

Actions / take aways

I’ve outlined some key actions and take-aways for those too busy to listen to the full thing:

  • Set a deadline for your launch — every time you do this you learn how to get better at setting deadlines.
  • Assign an owner if you're in a team — if more than one person “owns” a project, then no one actually owns it.
  • Be clear on your priorities — ensure everyone is aware of what is most important to the launch and the company.
  • If in doubt, optimise for speed — moving faster tends to solve more problems than it creates. Speed means you learn faster.

Subscribe for future episodes

If you haven't already, it'd mean the world to me if you subscribe to Lost and Founder wherever you get your podcasts — find all the links to subscribe here.

Thanks and see you next time!

Launching is like inviting your friends over

For the last year, very few of us have had the chance to have anyone over to our homes, but I was recently casting my mind back to those happier times, and I made a connection in my mind.

I am not sure about you, but in our house, whenever we invite someone over, it’s always a deadline – a fixed point in time to get our house presentable.

I am not saying my house is a mess, but when people come over I want to present the best version of myself and my house to my guests. And when we don’t have guests, sometimes those standards can slip a little. The handful of cups on the kitchen counter. The stack of 5 letters on the kitchen table. The extra pair of shoes left out in the hall.

Having people over pushes me to tidy all these little things up – to wash the cups, to sort the letters, to hide the shoes.

In my mind, that’s exactly what launching / shipping does: you may not be ready, but you have to get your product or feature presentable – ready for others to experience it. It focuses you.

Who care where the shoes go, or whether the cups are in the dishwasher or hidden in the sink. What matters is the place looks good and feels warm and welcoming.

When shipping – who cares if the extra settings option can’t make the cut, or the secondary heading on that alert modal isn’t precisely following the style guide. What matters more than anything is you hit the launch date and ship.

Having a deadline (like knowing a friend is coming to visit) forces you to tidy, focuses you, and restricts you from tackling anything too ambitious. External judgement and validation can be a powerful motivator to prioritise.

Talk it through

When was the last time you talked someone through your product or website?

Try it now. Try talking through – even to yourself – how to do a specific action in your product.

Hard, isn't it?

I find this to be one of the best ways to quickly get a feel for usability problems, and to discover opportunities to make our products better.

If you can't talk it through simply, you probably haven’t simplified it enough.