small_Fcsqb5pWQAAzPIK.jpeg

thumbnail_Fcsqb5pWQAAzPIK.jpeg

Adobe acquires Figma, cue the memes 🤪

large_Crossover Series NFTs.png

medium_Crossover Series NFTs.png

small_Crossover Series NFTs.png

thumbnail_Crossover Series NFTs.png

From Photography to NFT Art: Twisted Digital Landscapes with Nate Hill

large_featuredImage

medium_featuredImage

small_featuredImage

thumbnail_featuredImage

What Is the Open Web?

From Design System to ‘NFT Design System’: Creating TinyFaces

Published on <a href="https://blog.prototypr.io/galls-law-93c8ef8b651e?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> Jorge Arango 
<h4>A rule of thumb for designing complex systems that work.</h4>
<img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BM5SjKr3whSCUbSrlSJbmw.jpeg">Image by <a href="https://www.flickr.com/photos/bitterjug/7670055210">Mark Skipper</a>
I’m often in meetings with stakeholders who are either overwhelmed with the complexity they’re facing or entranced by the possibilities before them and yearning to explore them all. In either case, I ask them to focus on the core of the system we’re designing by quoting Gall’s law:
<blockquote>“A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works and cannot be patched up to make it work. You have to start over with a working simple system.”</blockquote>
This useful rule-of-thumb was articulated by John Gall in his book <a href="http://amzn.to/2xpUFf2">Systemantics</a>, which is where I first saw it. (There’s lots more wisdom in this book; it’s worth looking into.)
The idea of starting small and evolving from there strongly resonates with my experience. You may have a clear vision of what the environment should be, but that doesn’t mean you know all the implementation details. There are also assumptions in the vision that should be tested against reality, and it’s essential that you test the critical ones before you get to the details.
Determining which aspects of the system are central and which are trivial is something of an art, and easier to do in some projects than in others. This is one of the reasons why it’s so important to <a href="https://jarango.com/2017/09/29/start-with-a-conceptual-model/">start with a conceptual model</a> instead of the user interface; UI discussions can be rife with important yet non-critical issues. Getting the big stuff right first in a smaller release allows the team to start in the right direction towards their vision, whereas aspiring to get everything right in the first iteration is often a waste of time and resources.
Jorge Arango is an information architect and a partner in <a href="http://futuredraft.com/">Futuredraft</a>, a design consultancy based in Oakland, CA. He is one of the co-authors of “<a href="http://shop.oreilly.com/product/0636920034674.do">Information Architecture: For the Web and Beyond</a>” (aka “the polar bear book”) for O’Reilly. You can follow him on Twitter <a href="https://twitter.com/jarango">@jarango</a>.
This post was originally published on <a href="https://jarango.com/blog/">jarango.com</a>.
<img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=93c8ef8b651e" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="https://blog.prototypr.io/galls-law-93c8ef8b651e">Gall’s Law</a> was originally published in <a href="https://blog.prototypr.io">prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Gall’s Law

Gall’s Law

A rule of thumb for designing complex systems that work.

Top Stories