Reading Response #1 to Artful Design - Chapter 1: "Design Is ______"

Felipe Rocha Campos
9/29/2026
Music 256A / CS476a, Stanford University

Reading Response:

From this week's reading, I am responding to Artful Design Principle 1.7 from Chapter 1, which states:
Principle 1.7: Design is an Articulation of Preference

I'm specifically interested in "Ease of Use vs. Expressiveness", which Professor Wang frames as relating to the skill floor (how easy something is to learn - e.g. learning curve on a DAW, programming language, instrument) and a skill ceiling (how deep experts can go - e.g. custom automations and device chains in a DAW, writing your own software abstractions, when someone's familiarity with a guitar reaches a point where it's as if it were a second language they speak).

The diagram in the textbook presents skill floor and ceiling as properties of design, fixed at the moment something is shipped to the user. However, in my experience, they describe something more dynamic, the arc of a relationship between person and system changing over time, reflecting a continuous design process that the user develops beyond what the creator may have even imagined or intended. I believe some of the most well designed and powerful systems achieve ease of use *with* depth. However, I believe part of the job of the user community is to introduce abstractions that guide beginners to depth combined with accessible ease of use. Making the first steps possible and rewarding the user for staying, such that over time ease of use combines with depth to achieve "ease of self-expression (through this new medium)" which I see as a richer kind of ease that comes later in the relationship.

My clearest example is the DAW. The first time I opened Ableton Live I was overwhelmed by a blank slate without clear entrypoints to expression. Session View made no sense to me, I didn't know how to even start playing notes, tune a synth, or setup an audio effect rack, and the idea in my head for whatever sound and arrangement I wanted was lost in the confusion. Years later Ableton feels effortless, not because it got simpler, but because I built a learned vocabulary with it that lets me iterate quickly from musical/artistic inspiration to a bounced track.

I see many generative AI tools as a counterexample to this philosophy, *INSANE* ease of use combined with a sealed abstraction fundamentally limiting of self expression. Nothing to cut up, no reverse engineering, no depth or dexterity to the toolkit. In a paradigm where day 1 = day 100, the relationship stalls, and one ends up travelling nowhere in this co-design process. As evidence of this paradigm, if you look at companies like Suno's product arc, they are effectively rebuilding Ableton Live and other DAWs' functionality (e.g. https://help.suno.com/en/articles/13674305, https://www.ableton.com/en/manual/automation-and-editing-envelopes/) around a limiting text->audio generative functionality advertising ease of use but (in my opinion) cutting out the depth and nuance of self expression you get when there is dexterity in the toolkit being used.

Seymour Papert argued that good learning environments should have a "low floor, high ceiling" and Mitchel Resnick (creator of Scratch) later added "wide walls" (https://mres.medium.com/designing-for-wide-walls-323bdb4e7277). A question for our own designs in Artful Design: how does a designer optimize for the first hour vs the thousandth? What are the first abstractions / doors one should present to users to bring them into a richer world of self expression. Can AI tools as we've built them offer or aid in this, or are they doomed to restrict us to easy input easy output with no rich process in between?