The other aspect of IKEA that is criminally underrepresented in software that I really feel like should be a part of this article is having an incredibly succinct and universal DSL for documentation. Say what you will about the memes about people not being able to build IKEA furniture because they can’t follow the documentation. Once you understand the DSL, you’ll truly understand how incredible their documentation really is. It is incredibly succinct. They can guide you in less than 10 pages on assembling virtually any kind of furniture they sell. Think of how powerful something similar like that could be for software. How often have you dove into terribly written or overly long and dry documentation?

It is universal and approachable. Worldwide, IKEA has one set of documentation for assembly. It spans education, language, and cultural boundaries.

There is a huge value add in building software in a similar way in order to speak a certain way about that software. In some cases this may be untenable but in the vast majority of business cases I would venture that software and documentation inefficiency is born out of ignorance than necessity. I don’t mean that as a sleight, more that from a business perspective there’s generally a push for “new” and “more” instead of investments in refactoring and optimization.

The more that I am working with organizations looking for areas to improve in order to help them scale, the more the points in this article ring true for me. Thank you for writing it. It was a great read.