Tracing Design Thinking Models Through Archived Conference Papers

For most of its history, the story of design thinking has been told through tidy retrospective accounts: a charismatic origin at Stanford, a neat sequence of five stages, a wave of business case studies. The NCBDS proceedings archive tells a messier and far more useful story. Across roughly twenty-five years of annual conferences on beginning design education, the papers record what was actually attempted in introductory studios — which tasks were set, which stages were named, and which borrowed models collapsed when they met a room of eighteen-year-olds at nine in the morning.

Digitised proceedings offer something rarer than commentary: a chronological record of pedagogy captured at the moment it was practised. That matters in Australia, where design thinking arrived as imported vocabulary and was quickly reshaped by local conditions — crowded studios in Melbourne, service briefs in Adelaide, community projects in regional Queensland. Reading the archive well, though, needs a method rather than a browsing habit.

Why the proceedings record beats retrospective accounts

Conference papers are not neutral histories, because they were written as promotion. A session abstract exists to attract attendees, and a working group report exists to demonstrate that a method worked. Read naively, that advocacy bias produces a rosy picture in which every model succeeded. Read critically, the bias becomes the evidence: an author who claims a stage "transformed" the room is telling you something about how fragile the model felt in practice.

What the archive preserves is unusually specific. Session titles, task briefs, timetables, descriptions of the physical artefacts students produced, and occasionally transcripts of studio conversation. Journal literature on design thinking tends to preserve the polished argument about a model. The proceedings preserve the working version — the version with sticky notes on the wall and a tutor improvising under time pressure.

Following the vocabulary of the stages

The fastest way into a corpus like this is lexical. Track the words themselves as they move across years: empathise, discover, define, ideate, prototype, test, and later make, build, learn. Note the spelling. Australian proceedings of the early 2000s sit in the middle of the transatlantic orthographic tug-of-war, and the movement from empathize to empathise dates a paper to a particular subculture of design education, if not a particular country.

The stage names also reveal which model is doing the work. A session built around empathise, define, ideate, prototype, test is borrowing from Stanford; one built around discover, define, develop, deliver is citing the British Design Council's Double Diamond; one organised as inspiration, ideation, implementation is leaning on industrial practice. Even outside the archive, the beginner's voice is well documented in collections of novice designer biographies, and the conference equivalent — the first-year student meeting a task for the first time — appears in the proceedings in concentrated, dated form.

Reading the classroom evidence inside the papers

Stage names alone will not settle whether a model was taught or merely mentioned. The substance sits in the task briefs: a bicycle for a pensioner, a waiting room in a regional hospital, a backpack for a Year 9 science class. Compressed timelines are a recurring tell. When a session announces "empathy in fifteen minutes," a full five-stage model has been compressed past the point of usefulness, and the resulting artefacts show it in bent cardboard and vague problem statements.

Assessment language is equally revealing. Rubrics that reward "process documentation" imply a model with an inspectable process; rubrics rewarding a single polished artefact imply something closer to a design competition. The shift in what beginning students are asked to submit is often the clearest trace of how the models themselves developed.

Comparing the canonical models side by side

Several frameworks recur across the literature and the proceedings, and they align less closely than their shared diagram suggests:

Model Stages or phases Primary emphasis How it surfaces in proceedings Typical Australian setting
Stanford d.school five stages Empathise, define, ideate, prototype, test Product and service design Session titles, workshop logs, student task briefs First-year studios in Melbourne and Sydney
Double Diamond (Design Council) Discover, define, develop, deliver Service, policy, systems Appears when authors discuss public-sector briefs Service electives in Adelaide and Brisbane
IDEO design thinking Inspiration, ideation, implementation Organisational practice Cited in industry partnerships and placements Live briefs with Australian design firms
Human-centred design Research, concept, prototyping Community and social design Workshops run with NGOs and community groups Regional and community-based projects
Nature-led and biomimicry framing Observe, emulate, evaluate Sustainability Grows in later proceedings as climate topics expand Sustainability-focused Queensland courses

Where Australian settings rewrite the model

Australian conditions did not merely host the imported frameworks; they altered them. Melbourne's RMIT and Swinburne programs, with their emphasis on making and fabrication, tend to shorten the front end of the model and lengthen the prototyping stage. Sydney institutions have folded design thinking into service contexts and into programs anchored by the Powerhouse Museum's public programmes. Adelaide's Lot Fourteen precinct has pushed practice toward systems and precinct-scale briefs, which sits comfortably with Double Diamond vocabulary rather than Stanford's.

Classroom language is local too. In a Queensland studio, an afternoon session is an arvo of work, a good idea is keen as mustard, and a broken prototype is simply a bit of a shame, not a failure to be corrected. These habits leak into the papers, and students frequently reframe "users" in terms of family, footy club and mates. The national school curriculum, with its Design and Technologies strands in Years 7 to 10, further compresses the model into a term of study. Material culture also survives outside the archive: browsing vintage design collectibles turns up the objects that Australian modernism produced in the 1970s, and those same objects, adapted as classroom props, recur in session descriptions.

A coding protocol for the archive

Build the dataset before reading widely. One row per session, with columns for year, host institution, declared model, stage vocabulary used, task type, assessment language, and whether artefacts were exhibited. Search the digitised text for stage terms and their variants, then read the surrounding paragraphs, because abstracts are generous and bodies are candid. Expect OCR errors on early scans, particularly with hyphenated words like "co-design".

Two confounds deserve attention. First, the conference theme changes with each host, so an apparent surge in a model may reflect a theme rather than adoption. Second, papers are advocacy documents, and failure is rarely reported. Where a session claims an "amazing" result, look for the evidence of process. And the materials remain subject to copyright: cite carefully, quote minimally, and use the archive for study and teaching rather than redistribution.

From reading towards re-use

The value of the archive is cumulative. Each coded session tightens the account of how a model travelled, what it did to beginners, and where it broke down. That account is more useful to Australian educators than the origin myth, because it shows adaptations rather than inventions — including the ones already made in local studios, under local constraints, with local vocabulary.

The next step is deliberately narrow: pick one model, open the proceedings for a single decade, and code every session where its stage vocabulary appears, alongside every session where it was quietly replaced by something else. That spreadsheet will show more about the development of design thinking than another retrospective account ever will.