How to Build Things People Use

And why it's a better goal than 'build things people want'

Enjoying the newsletter? Please forward to a pal. It only takes 18 seconds.

Conventional Wisdom

Says you need to build things people want.

I actually think it’s incomplete.

You can build things someone wants, but in a way that stops them from using it.

This is called friction.

When it Matters

WordRobin is a service built on top of a platform (X).

This means all of my customers use the platform X.

By building my app as a standalone web app (with a dashboard, login interface etc)

I am effectively asking people to build a new habit.

Not a good move.

How to Fix it.

Instead, I have launched a chrome extension which sits on top of the X website.

It let’s you reply to posts, write, edit - the same features I have in the platform, just much easier to access.

What Next?

WordRobin’s Chrome extension counterpart is in-review.

While it’s being approved, I’ve decided to work on something slightly different.

For multiple reasons, but one of which is that I have validated demand for this project already by talking to people in the target audience (CMO and marketing managers).

It’s already largely ready for testing. Gotta love quick prototypes!

What am I doing?

Next week will be focused on honing in the Chrome extension and getting feedback for it (if it’s approved)

If people love it - then I know what to focus on! 🙂 

Have a great week all.

Ben

(apologies for the delay! I was distracted working on code)

Enjoying the newsletter? Please forward to a pal. It only takes 18 seconds.

If you want to keep up with any progress - come join me on X!