You won't, and you'll always be "too busy" to think about UX—unless you carve out time for it.

There's a reason that Jeff Bezos has a team in Amazon who work exclusively on 'papercuts' (what they call the small UX things that often get ignored).

Good UX takes time, but doesn't necessarily take a huge amount of dev work.

i.e., once you truly understand the problem, and what your customers are trying to achieve, it can be as simple as a single line of context.

The best products iterate slowly, not in major overhauls.

So get stuck in. Find the first 5 quick wins, then the next, then the next.

It depends (sorry).

If you understand not just what's wrong, but why it's wrong, then you're halfway there.

Most teams have a long list of "things we'll fix one day", but neither prioritise them, or really understand what the easiest solution is.

Hint: if you find yourself craving a full redesign, it usually means you don't understand the problem in enough detail.

It doesn't need to be.

I've worked with teams who've made tens of millions in additional revenue, from a handful of UX changes that probably took hours, not even days.

Heads-up; not everything is quick and easy. But some stuff is.

I don't think so.

More than 50% of my audience are not designers. Seriously, odd right?

Except it's not, because UX feeds into every product role.

Knowing just that little bit more about design empowers developers to make decisions, it improves the lens of QA testers and it helps product managers prioritise.

It feeds into every role from customer support, right the way up to CEO.

The way to think about it is this: most of Built for Mars is industry agnostic.

You've already looked at your main competitors. What you need is to understand how people are fixing your problems, in other industries, and in other parts of the world.

Sure, if you're in FinTech, that's a great filter to apply—but that's not the end goal.

You can draw inspiration, ideas and techniques from almost anywhere.

This is usually a great sign, as it means you're starting to recognise patterns and principles.

In fact, you might already know a lot of UX psychology, without being able to name any.

The day you read Built for Mars and think it's "just the same stuff", is the day you've graduated to Senior Martian.

A portfolio of trendy designs can only get you so far—employers want to know that you understand the business side of design.

That means psychological principles, understanding customer behaviour and how to convert that into measurable results.

I get sent jobs all the time that ask for candidates to have read Built for Mars.

(Annoyingly they get removed once the place is filled, but Google it).

Absolutely not. Great UX is iterative.

The sooner in the product pipeline you fix the issues, the more money you'll save.

But, as products evolve, audiences grow and competitors emerge, your context will change.

That's why it's so important to understand the principles—so you can think on the fly.

Yes, complete this form.

Absolutely, most product teams even have an internal budget for educational resources (i.e., research, courses, user testing).

It's simple; if you change your mind and want your money back, email me on help@builtformars.com within 7 days of purchase.

You'll be refunded in full, regardless of which package you purchased.