TillyGen and Miro

What this is about

Miro is an endless whiteboard: sticky notes, frames, uploaded images and PDFs, several cursors moving at once. Agencies run their kickoff workshops on it — the client dumps wishes, references get pinned, themes get clustered live. That board is pre-pre-production: it holds everything a film could be. The workflow with TillyGen is a act of distillation. The clustered board becomes a written briefing, the briefing enters TillyGen, and TillyGen turns it into shot list, storyboard and schedule. The plan PDF then returns to the board, pinned beside the original stickies — the loop from idea to commitment, visible on one surface.

An integration is good when nobody talks about it any more: the data is where it is needed and nobody exports anything.

What runs differently here

In planning terms, that means:

• The workshop board collects everything unfiltered; clustering at the end marks what survives into the briefing and what stays a sticky
• The distilled briefing text is written once, next to the board, and becomes the input TillyGen plans from
• The exported plan PDF gets uploaded back onto the board, so the client sees wish and consequence side by side
• In the next call, the board answers 'why is this not in the film' — because it stayed in the cluster that was cut

Step by step

This order gets you there fastest:

1. Run the kickoff on a Miro board: collect wishes, references and constraints without judging, several people writing at once.
2. Cluster at the end of the session and decide live which clusters enter the film — the client watches the cut happen and owns it.
3. Write the briefing from the surviving clusters as one text, and feed it into TillyGen as the planning input.
4. Let TillyGen produce shot list, storyboard and schedule, and upload the exported plan PDF back onto the board next to the stickies.
5. Walk the client across that board in the follow-up: this wish became these shots, this one was cut here, by us, together.

Common pitfalls

What most often goes wrong in practice:

• The board never gets distilled: planning starts from someone's memory of the workshop, and the client's favorite idea is the one that got lost
• The plan evolves in TillyGen while the board still shows version one — the client keeps quoting a state that no longer exists

With TillyGen

Miro holds the possibility space, TillyGen the commitment. The briefing is the border crossing between them, and the plan PDF pinned back on the board documents where the border ran.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.