The the most pragmatic solutions (and cheapest), come when you lack resources.

Summary: Minimize scope as much as you can when solving engineering problems. Why? Because our resources are not infinite.

Let’s unpack the above with a real life example:

An Example of Scope Reduction

I created a fledgling app. Nobody provides me with any feedback. None. Trying to talk to users is like pull out teeth: they never book appointments, and are very uncooperative when they do. The only way to get usability feedback is by standing there, looking over their shoulder.

It’s a sobering experience to watch a user, muddle their way through your UI designs. They’re confused. They don’t know what to do. They seem unable to see the big “send” button, flashing in the middle of the screen.

“What do I do now?” they ask.

“Where’s the send button?”

I feel like tearing my hair out.

Some users do nonsensical things (to my mind). It’s bizarre watching them try to get from Melbourne to Sydney via Buenos Aires. Why do they do it like that? They do not seem to read anything. Or them seem to click things at random, and hope for the best etc.

These are serious problems which need to be solved, otherwise users get frustrated.

Your current solution will most likely be like a blunt rock. You need to make it as sharp as a samarai sword. Usability studies are paramount.

How you gonna do that?

(1) Hotjar or equivalent apps

Paid service. The cost is astronomical, and you need a Phd to use it. Hotjar will definitely need Hotjar. I found that it slowed down my site considerably, and the recordings, while useful, were not helpful.

It was far too expensive for the benefit.

(2) Write my own library

It doesn’t look too difficult to write some javascript to stream a user’s experience. No record. No frills. This would have to clear some legal loopholes, some privacy, but it could be done.

But writing code takes time, and I imagine, hiccups along the way. But I think there is scope for an OpenSource version of HotJar, without the bells and whistles. The raison d’etre for a class of apps might be less compelling with an Open Source version on hand.

(3) The Cheapest and Fastest Alternative:

…but then I stumbled upon a better idea…I have a captive audience who are using my “product”, and are making good money from it, without paying a dime. I could demand that they call me on Skype, and share their screen, whenever they need to use my app. The problem? They would never accede. It’s a pain for them, but very useful for me. A solution to that problem? To receive an automatic email everytime someone logs in. Then I would call them and ask them to share their screens.

Is it hacky? Absolutely.

Is it cheap and effective? Absolutely.

Is it ethical? Sure, you get their consent.

Will people ditch the app? No chance: they make too much money from it.

Will it make my app better? Absolutely.

The scope was reduced from 30+ hours, down to zero.

Do this a million times, and you’ve got a product, which generates cash, with zero equity given away.

Turn that lump of steel into a razor sharp sword.

Moral: Cut the scope, any way you can, and you’re half-way there.