40. Intangible Scaffolding

It’s well-known that Michelangelo Buonarroti had to construct a scaffolding system to paint the Sistine Chapel.

What is less known is that this scaffolding system was designed by Michelangelo himself after other experts failed in the attempt or proposed solutions that damaged the chapel’s ceiling (the very canvas on which Michelangelo would create his masterpiece).

In truth, the design and construction of the scaffolding was a project in itself. Filled with challenges, resource needs, and pressure from Michelangelo’s patrons who were eager to see the completed work.

The scaffolding system built for the original painting was so complex and sophisticated that it was impossible to reconstruct for centuries to maintain and restore the paintings.

Similarly, it’s not possible to construct an arch without the scaffolding that supports it.

You need scaffolding to build a building, but the building is not the scaffolding.

Scaffolding provides the structure to access places that are otherwise inaccessible.

It makes their construction possible.

In the same way: workflows, wireframes, prototypes, and many other intermediate pieces of projects should contribute to accessing where the product is needed.

They should help us shape it, build it.

Just as scaffolding is indispensable, it’s equally crucial to show sponsors the value of the scaffolding. Sponsors often face pressure from various stakeholders who urge them to see the product available immediately, without delays, without by-products, only the product, and if possible: only the benefit expected from the product.

This urgency doesn’t make the sponsors insensitive to the “artist’s” work, uneducated in appreciating the “art”, or ignorant of the user-centered product development process.

How do you resolve the dilemma? By communicating the value of the “scaffolding”. Providing rational arguments that inform the savings produced by the “scaffolding”. Demonstrating why our “scaffolding” is a necessary part of the product. In this regard, we have an advantage over real scaffolding. Our “scaffolding” can serve multiple projects at the same time (prototypes, UI kits, digital files, etc.).

They are “scaffolding” that teach us and provide value that must be absorbed project after project, increasing our knowledge, reducing design and development times.