Theory
The fest with empty seats
The fest committee spent weeks organising events, then watched registrations trickle in far below expectation. Not because students did not WANT to come: because FestConnect's confusing registration made them give up halfway.
Here is the uncomfortable truth for anyone who thinks UI/UX is just "making it pretty": a bad experience did not just annoy users, it FAILED THE PRODUCT. Empty seats. This lesson is the business case: why good UI/UX is not decoration but a driver of success, in numbers a manager cares about.
Theory
What good UX actually buys
Good UI/UX pays back in outcomes you can measure:
- satisfaction → adoption and retention: users who find it easy stay, return, and recommend it; frustrated users abandon and never come back
- fewer errors and lower support cost: an intuitive product needs less help, less training, fewer complaints
- trust and loyalty: a product that respects the user's time earns credibility and repeat use
- competitive advantage: between 2 similar products, the one that feels better wins
- higher conversions: more students who START registration actually FINISH it
Each is a lever on the product's success, not a nice-to-have.
At a glance
Good UX vs poor UX (the outcomes)
| Dimension | Good UX | Poor UX |
|---|---|---|
| User feeling | Satisfied, confident | Frustrated, confused |
| Behaviour | Completes tasks, returns, recommends | Abandons, complains, leaves |
| Support load | Low: product is self-explanatory | High: users need help constantly |
| Reputation | Trust, good word-of-mouth | Bad reviews, lost credibility |
| FestConnect result | Full fest, smooth sign-ups | Empty seats, abandoned registrations |
Theory
The cost-of-change curve
One principle every product manager knows, and every exam rewards: problems are dramatically cheaper to fix EARLY.
A flaw caught in a wireframe is a 5-minute edit. The SAME flaw caught after FestConnect is fully coded means rewriting screens, retesting, redeploying: hugely more expensive. Caught after LAUNCH, when real students have already abandoned it, it also costs lost users and reputation.
This is why UI/UX work happens UPSTREAM, before code: not because designers are precious, but because fixing the experience on paper is the cheapest it will ever be. (The exact cost multipliers vary by source; the direction: earlier is far cheaper: is universal.)
Quiz
Beyond looking nice, why does investing in UI/UX matter for a product's SUCCESS?
- It has no measurable business impact; it is purely cosmetic
- It raises satisfaction, adoption and retention while cutting errors and support costs: driving real outcomes
- It only matters for games, not for practical apps like registration
- It matters only after the product has already failed
Show the answer
It raises satisfaction, adoption and retention while cutting errors and support costs: driving real outcomes
Good UX drives measurable outcomes: users who are satisfied adopt, stay, return and recommend, while errors and support costs fall and conversions rise: the FestConnect registration that gets FINISHED versus abandoned. Option A is the it-is-just-cosmetic myth this whole lesson refutes (a confusing flow lost real sign-ups). Option C is false: practical apps live or die on usability even more than games. Option D inverts the cost-of-change principle: UI/UX matters MOST early, to PREVENT failure, not to mourn it. The business case: experience is a lever on success, not paint on the surface.
Think first
Make the case to the committee
The fest committee says 'FestConnect already works, why spend time on UX?' Give a 2-point business argument that would convince a non-designer. Then tap.
Show the answer
1: More sign-ups for the same effort. Every student who abandons a confusing form is a lost registration; a smoother flow converts more of the SAME visitors into filled seats: directly serving the committee's goal. 2: Less work for you. A confusing app floods the committee with 'how do I register?' messages; an intuitive one is self-explanatory, cutting the support load to near zero. Framed this way: UX is not extra polish, it is MORE registrations and LESS hassle: outcomes the committee already cares about. The skill is translating design value into the audience's language: sign-ups and saved effort, not 'delight'.
Watch out
Significance-answer slips
Vague 'delight' talk: name MEASURABLE outcomes: adoption, retention, fewer errors, lower support, higher conversions.
Ignoring poor-UX cost: the argument has 2 sides: good UX gains AND bad UX losses (abandonment, bad word-of-mouth, support load).
Inventing statistics: speak directionally ("far cheaper early", "more conversions"); do not fabricate specific percentages or ROI multiples.
Treating it as end-stage: the cost-of-change curve means UX matters MOST early, before code.
Theory
Unit 1 closes: now the real work
You can now say WHAT UI/UX is (surface vs experience), WHY the user is central (UCD), and WHY it matters commercially (satisfaction and success). That is the foundation. Unit 2 rolls up its sleeves and starts the actual process on FestConnect: user RESEARCH: because you cannot design for users you have not bothered to understand. First up: why research matters, then personas and interviews to do it.
Summary
Key takeaways
- Good UI/UX is a business driver, not decoration: it enhances user satisfaction and product success.
- It raises satisfaction, adoption, retention and recommendations; poor UX causes frustration and abandonment.
- It cuts errors, support and training costs, and builds trust, loyalty and competitive advantage.
- It increases conversions: more users who start a task actually finish it.
- Cost-of-change: fixing problems in design is far cheaper than after development or launch.
- Make the case in the audience's terms: more sign-ups, less support, prevented failure.
- Memory hook: a confusing FestConnect means empty seats; experience is a lever on success.