📝Lowering the friction may increase the usage exponentially
Decreasing the barrier for using something may lead to more of that something being used. This happens non-linearly and the usage may unexpectedly jump from almost not usage to use all the time.
Examples
- LLMs lower the friction of prototyping, so prototyping is now more attractive in tech design
- By default, org-roam requires a note title when creating a new note. I noticed that it’s hard to come up with a good title upfront (creates a slight barrier to create a note). I have added a command to create a note without title and I noticed that I have started creating more notes.
- Bit.dev decouples components and packages to lower the barrier to create a new component. This leads to creating much more (and much smaller) packages.
- Process boundaries are harder to violate than module boundaries. The reverse when process isolation (increasing the barrier) leads to significantly less boundaries violation.
See also
- Defaults matter is a specific instance of this when one alternative is easier to use than the other one.
- Text source code is adding friction to some programming constructs
- If you want to encourage usage, work on lowering the friction
Backlinks
- 📝 If you want to encourage usage, work on lowering the friction
- 📝 LLMs lower the friction of prototyping, so prototyping is now more attractive in tech design
- 📝 Text source code is adding friction to some programming constructs
- 📝 How to involve team into design?
- 📝 Bit.dev decouples components and packages to lower the barrier to create a new component
- 📝 Defaults matter
- 📝 Process boundaries are harder to violate than module boundaries