Kavya's college arts festival

A second-year art student, a committee that has never run anything, no records from last year's disaster, a city watching. The framework leaves the ground it was born on and still stands.

Planned for release phase 2. The page is complete as a draft; interactive parts run in the browser and do not yet save to an account.

In brief

This case is laid out against the eight steps of the framework. Jump to Step 1 to see how the end state was defined, or to Step 8 to see what integration caught.

  1. Define the End State

    Not "what do you need" — "what is it for?" Imagine the last night. Someone walks out of the college gate. Who are they, and what do they say to the person next to them? A second-year girl from a small town who came half believing the art world was a locked room, walking out thinking maybe there's a place in here for me too. The girl at the gate. Every rupee, every wall, every name on the poster held up against her.

  2. Map the Flow

    Everything that has to happen between today and that girl, as it falls out of her head — forty-odd things in no order. Then one question: which of these can't start until another is finished? The lists that had refused to connect for weeks begin, one join at a time, to connect.

  3. Assign Tasks

    Of each piece: is this a thing only you can do? The eye, the taste, which student's work goes on which wall, the conversations with the artists — hers, and no tool on earth. Reconstructing a budget from nothing, finding how festivals in other cities solved the sponsor problem, turning forty tasks into a dated timeline, the first ugly draft of a vendor email — "the intern, not the artist."

  4. Select the Tool

    A conversational tool, used the way she was shown: not asking it what to do, but asking it to help her see what she could not see.

  5. Prepare and Direct

    Full context every time, the specific thing she wanted back, and — before looking at any output — the standard she would judge it against, written down, so a polished answer could not seduce her into calling it good.

  6. Execute

    Week one: a credible budget benchmarked against three other college festivals, with untrusted lines flagged for a human; a sponsor approach drafted and then rewritten twice in her own voice; a timeline with real dates. "I got back four evenings this week. I drew instead."

  7. Evaluate

    Week two: the team. She had been doing everything herself out of fear anything handed over would come back wrong. Asked which tasks needed her judgement and which only needed doing well, she gives directionless people direction, each piece defined well enough that they cannot drift.

  8. Integrate and Stress-Test

    Week three: the identity, handed to a subcommittee told only to "make it striking", comes back slick and dead. Not a poster problem — an end-state problem, further down the line. She gives them the girl at the gate and lets them redo it. Three days later it is unmistakably this festival. The event is the best the college has seen in a decade. The art on the walls stayed entirely human; her professor calls it "the right line".