Design that's so bad it's actually good

16 May 2024

Shreyas Prakash headshot

Shreyas Prakash

Recently, a relative sought my help to tweak a badly designed poster on Microsoft Paint.

This was meant to be circulated on Whatsapp as an advertisement for the handyman services his friend was offering in his locale.

He wanted to ‘jazz’ it up and asked if I could help. I quickly fired my Figma and started working towards revamping the layout.

Before pushing some pixels, I took a brief pause—What if crappy design is sometimes good?

Does everything have to be ‘designerly’ with a better sense of aesthetic? I started searching online, and elsewhere for ‘terribly bad but good design’ examples.

Craigslist is an example of a successful company with a website that might make Dieter Rams roll in his grave.

usertesting.com

Craigslist website is sprinkled with various UX violations. Lack of responsiveness. No clear hierarchy. Dense information architecture. Lack of contrast. Missing helper text for images. No advanced filters for search.

Despite all this, it’s hugely successful attracting millions of users each month to put their local listings. And I’m inclined to think that the so-called ‘crappy’ design has played a role in achieving the business outcomes of Craigslist.

Part of the reason why it’s clicked is the bare-bones design which gives the impression that it requires minimal development and maintenance resources.

The ‘crappy-design’ effect makes Craigslist resemble a thrift store more than a high-end boutique, catering to users seeking affordable items.

Let’s take another example.

Most of Japanese websites can also be considered under the ‘terribly-bad-but-good’ category.

Take Kakaku—A popular price comparison site with a text-heavy design displaying. Kakaku is not bad design, per se. It’s just so different and unusual compared to western design principles. Just like several other Japanese websites, there is a lot of information condensed into a single page, with multiple columns and minimal white space.

Dense nature of Japanese websites violating the usual western design principles

A video that inspired me to write this. Good design is a relative term and is subjected to the culture and context. What Japanese consider as ‘good design’ is way different compared to Western design principles.

The definition of what ‘good design’ means not only changes from region to region as shown in our earlier examples, but it also changes year to year.

Google homepage changing every year (courtesy: Web Design Museum)

Image

Batman cape changing year to year

Coming back to the poster for handyman services. I’m beginning to think that there is a particular context in which even the current Microsoft Paint poster might fly well.

If I make the poster too pristine and professional would it then hurt the business? The opposite of what this poster intends to achieve.

If we work backwards from the business outcomes, the perspective around good design changes completely.

And sometimes, the design of the website can be so bad, that it’s actually good for the business. Good design is a relative term. And context is everything.

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Notes on Londontravel
  2. 18 key ideas from reading Henrik Karlsson this monthwriting
  3. Stop arguing, and start drawing circles togethermathematics
  4. The whole world is just the snake eating its own tailmental-models
  5. Life lessons and hot takes from my 30slifestyle
  6. Building a skill for coherent science illustrationsscience
  7. My agentic engineering workflow (step by step)agentic-coding
  8. Hammock driven developmentagentic-coding
  9. Peculiar ways number three fits into our funny little brainsmental-models
  10. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  11. Authority in the guise of evidencecritical-rationalism
  12. Map is not the territoryphilosophy
  13. Self hypnosis as a manifestation ritualmeditation
  14. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  15. How I prepare for tough negotiations nowadaysnegotiation
  16. When should we steelthread somethingproduct-development
  17. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct
  18. Healthy conflict in teams have a tipping pointteam-building
  19. How I deslopify AI writingwriting
  20. How I started building softwares with AI agents being non technicalagentic-coding
  21. Read raw transcriptswriting
  22. Legible and illegible tasks in organisationsproduct
  23. L2 Fat marker sketchesdesign
  24. Writing as moats for humanswriting
  25. Beauty of second degree probesdecision-making
  26. Boundary objects as the new prototypesprototyping
  27. One way door decisionsproduct
  28. Finished softwares should existproduct
  29. How I periodically rank my rough draftsobsidian
  30. Flipping questions on its headinterviewing
  31. Vibe writing maximswriting
  32. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  33. How I build greenfield apps with AI-assisted codingagentic-coding
  34. We have been scammed by the Gaussian distribution clubmathematics
  35. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  36. I was wrong about optimal stoppingmathematics
  37. Thinking like a shipmental-models
  38. Hyperpersonalised N=1 learningeducation
  39. New mediums for humans to complement superintelligenceagentic-coding
  40. Maxims for AI assisted codingagentic-coding
  41. Virtual bookshelvesaesthetics
  42. It's computational everythingtrends
  43. Public gardens, secret routesdigital-garden
  44. Git way of learning to codeagentic-coding
  45. Style Transfer in AI writingagentic-coding
  46. Understanding codebases without using codeagentic-coding
  47. Vibe coding with Cursoragentic-coding
  48. Virtuoso Guide for Personal Memory Systemsmemory
  49. Writing in Future Pastwriting
  50. Publish Originally, Syndicate Elsewhereblogging
  51. Poetic License of Designdesign
  52. Idea in the shower, testing before breakfastsoftware
  53. Technology and regulation have a dance of ice and firetechnology
  54. How I ship "stuff"software
  55. Writing is thinkingwriting
  56. Song of Shapes, Words and Pathscreativity
  57. How do we absorb ideas better?knowledge
  58. Read writers who operatewriting
  59. Brew your ideas lazilyideas
  60. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  61. Compound Interest of Private Noteswriting
  62. Conceptual Compression for LLMsagentic-coding
  63. Meta-analysis for contradictory research findingsdigital-health
  64. Proof of workproduct
  65. Gauging previous work of new joinees to the teamleadership
  66. Task management for product managersproduct
  67. Beauty of Zettelswriting
  68. Stitching React and Rails togetheragentic-coding
  69. Exploring "smart connections" for note takingwriting
  70. Deploying Home Cooked Apps with Railssoftware
  71. Repetitive Copypromptingwriting
  72. Questions to ask every decadejournalling
  73. Balancing work, time and focusproductivity
  74. Hyperlinks are like cashew nutswriting
  75. Brand treatments, Design Systems, Vibesdesign
  76. How to spot human writing on the internetwriting
  77. Can a thought be an algorithm?product
  78. Opportunity Harvestingcareers
  79. Everything is a prioritisation problemproduct
  80. How I do product roastsproduct
  81. The Modern Startup Stacksoftware
  82. In-person vision transmissionproduct
  83. How might we help children invent for social good?social-design
  84. The meeting before the meetingmeetings
  85. Design that's so bad it's actually gooddesign
  86. Lessons learnt interview prepping for product rolesinterviewing
  87. Obsessing over personal websitessoftware
  88. English is the hot new programming languagesoftware
  89. Better way to think about conflictsrisk-management
  90. The role of taste in building productsdesign
  91. Dear enterprises, we're tired of your subscriptionssoftware
  92. Products need not be user centereddesign
  93. World's most ancient public health problemsoftware
  94. Pluginisation of Modern Softwaredesign
  95. Let's make every work 'strategic'consulting
  96. Making Nielsen's heuristics more digestibledesign
  97. Startups are a fertile ground for risk takingentrepreneurship
  98. Insights are not just a salad of factsdesign
  99. Minimum Lovable Productproduct
  100. Methods are lifejackets not straight jacketsmethodology
  101. How to arrive at on-brand colours?design
  102. Minto principle for writing memoswriting
  103. Importance of Whytask-management
  104. Quality Ideas Trump Executionsoftware
  105. Why I prefer indie softwareslifestyle
  106. Use code only if no code failscode
  107. Self Marketing
  108. Personal Observation Techniquesdesign
  109. Design is a confusing worddesign
  110. A Primer to Service Design Blueprintsdesign
  111. Rapid Journey Prototypingdesign
  112. Visualise detailed file structures on CLIcli
  113. Do's and Don'ts of User Researchdesign
  114. Design Manifestodesign
  115. Complex project management for productproducts
  116. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  117. Pedagogy of the Uncharted — What for, and Where to?education
  118. Future of Equity with Ludovick Petersinterviewing
  119. Future of Ageing with Mehdi Yacoubiinterviewing
  120. Future of Tacit knowledge with Celeste Volpiinterviewing
  121. Future of Mental Health with Kavya Raointerviewing
  122. Future of unschooling with Che Vanniinterviewing
  123. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  124. Future of work with Laetitia Vitaudinterviewing
  125. How might we prevent acquired infections in hospitals?digital-health
  126. The why to endure any howentrepreneurship
  127. Design education amidst social tribulationsdesign
  128. How might we assist deafblind runners to navigate?social-design