The concept of Big Design and Small Design is particularly critical to consider in open source. Far too often, the process required to get an open source project chosen/installed/running (i.e., an example of Big Design) is not given the same amount of attention as the actual user interface components of the project (i.e., an example of Small Design), leaving many less tech-savvy potential users behind.

In relation to my own FOSS **Docsify-This.net** project, here are example aspects for both big and small design👇🏼

Thinking Big, Thinking Small

Big Design:

✅ Barriers to open publishing

✅ Outcomes over outputs

✅ Problems and opportunities

✅ People + Systems

✅ Mapping user journeys

✅ Prioritizing job stories

Small Design:

✅ First-use experience

✅ Optimizing key task flows

✅ Reducing barriers of use

✅ Harnessing the power of microcopy

✅ Applying progressive (workflow) disclosure

✅ Using docs as part of UX design

There might also be a case for using the viewpoint of Large/Small/Micro design, for example with Docsify-This👇🏼

Large Design: