Drafting a technical essay for the ITP 30 show catalog

Writing for an interactive catalog asks for clarity, curiosity, and a careful balance of context and detail. The reader might be a designer in Melbourne, a coder in Brisbane, or someone browsing the archive from Hobart on a quiet weekend. Each arrives with a different sense of what technology can do, and the writer has to respect that diversity without losing the thread of the project.

A technical essay for a catalog is neither a research paper nor a marketing blurb. It sits between documentation and storytelling, asking the author to explain how something works while describing why the making mattered. That dual responsibility shapes every paragraph, from the framing to the closing reflection.

For members of the NYU Interactive Telecommunications Program community, the catalog functions as both portfolio and record. A studio in Sydney might use it to scout collaborators, while a visitor from Perth could find a project that reframes a familiar interface. Writing with that breadth of readership in mind is part of the discipline.

Defining the project and its technical core

Before any sentence is written, the project needs a clear centre. The author should be able to describe the work in a single paragraph, identifying what it does, what powers it, and what makes it distinct. Without that anchor, the essay drifts into a feature list or a vague celebration of novelty. A short pitch, refined over several drafts, becomes the spine for everything that follows.

The technical core often lives in the unglamorous parts of a build. Sensor calibration, data flow, hardware choices, and accessibility decisions all deserve space. In Australia, projects that collect environmental data must also reckon with the Privacy Act 1988, especially when handling personal information through networked displays. Naming those constraints openly signals rigour and earns trust.

Equally important is describing what the project does not do. Catalog readers appreciate honesty about limitations, the conditions under which a prototype fails, and the audience it leaves out. A frank paragraph on boundaries often does more for credibility than a triumphant summary.

Gathering sources and technical references

A strong essay rests on its sources. Reading across disciplines, from sensor documentation to recent academic work, gives the writer a wider vocabulary and a sharper sense of where the project sits. For Australian writers, dipping into local sources pays off: a Brisbane incubator's white paper, an Adelaide research institute's report, or a local council's accessibility guidelines all offer useful framing.

Other catalog entries can serve as case studies. A recent journal piece exploring the story behind a weather powered digital painting shows how atmospheric data and generative aesthetics can be explained without drowning the reader in jargon. Reading such pieces helps the writer calibrate their own tone.

Reference notes should be organised as the research progresses, not at the end. A simple system, a folder of PDFs, a spreadsheet, or a notebook, prevents the late-stage scramble for a citation. That habit also makes the editing pass smoother.

Outlining the narrative arc

Once the research is in hand, the essay needs a shape. A reliable structure moves from context to mechanism to reflection, opening with why the project exists, walking through how it works, and closing on what it revealed. This three-part rhythm helps both skimmers and close readers.

The opening paragraph should answer the question of why. What gap does the project fill, what conversation does it join, what inspired its creation? A few sentences of context give the reader a reason to keep going. For Australian creators, situating the work within local conditions, such as the public transport rhythms of Melbourne's tram network or the seasonal weather of coastal towns, can sharpen the sense of place.

The middle section carries the technical explanation. Diagrams, code excerpts, and short lists all help, but they should serve the prose, not replace it. Each technical element needs a sentence that ties it to the project's intent, so the catalog entry never reads like a manual.

Drafting with both clarity and voice

Drafting is where the essay finds its voice. The first pass should prioritise momentum over polish, getting the ideas down before worrying about rhythm. Many writers find that a quiet hour at a desk in Sydney or a corner of a Canberra library helps them write without self-censorship. Editing cannot begin until the draft exists.

Clarity comes from concrete nouns and active verbs. Replace "a system was utilised" with "the system logged the values". Avoid stacking adjectives in front of technical terms. Read each paragraph as if explaining it aloud to a friend in another field, and rework any sentence that requires too much background knowledge.

Voice is what separates the catalog essay from a spec sheet. A line about a late-night debugging session, a confession about the wrong component ordered, or a note about what the maker would change next time brings the writer into the text. Catalog readers respond to that human presence, and the projects remembered later are usually the ones where the writer allowed themselves to be seen.

Reviewing, editing, and preparing the final piece

Editing is a separate skill from writing, and treating it that way helps. A first revision should focus on structure, asking whether each section earns its place. A second pass trims repetition, tightens sentences, and standardises terminology. A third read, ideally aloud or after a break, catches the small errors that hide between paragraphs.

For projects involving public installations or consumer devices, a quick check against the Australian Consumer Law guarantees is worthwhile. Catalog text mentioning warranties, expected lifespans, or replacement parts should reflect the standards set by the ACCC, so readers are not led astray. A short note about the prototype status of the work can prevent misunderstandings and protect the maker.

Before submission, the essay benefits from one final read in the format it will be published. Spacing, image captions, and link placement all read differently on a final page than in a draft document. Writers who want to document a related build, perhaps something like how to build a socially responsive light display, can use the catalog essay as the conceptual companion to that more procedural entry. Together, the two formats give the reader a fuller picture.

When the catalog entry is ready, share it through the program channels, attend the showcase if possible, and follow up with collaborators and mentors. The catalog is a record, but it is also a door, and a careful technical essay opens it for the next reader.