Get your team ready.
Put AI to work responsibly.
Bring your production to life.

The problem to solve

When procedures live in scattered documents or in a department lead’s head, newcomers have to guess who to ask, which tools to use, and what good work looks like. Repeating the same explanations also makes a consistent welcome harder to deliver. A course can organize that knowledge without pretending to replace role-specific supervision.

What the project demonstrates

The example separates orientation, working practices, team connections, and a first-month plan into modules. A competency map connects those topics to what the learner should be able to do. The visible lesson sample turns a broad goal into a specific activity, a takeaway, and a self-check.

Video and reading formats sit alongside an example checklist, goals worksheet, directory, and buddy guide. The public outline also describes matching activities and a final plan. Together, these show how instruction, useful resources, and evidence of learning can support the same outcome—not simply fill a library with videos.

Apply the approach to your project

• —Production onboarding: organize approved information about departments, communication, resources, and first-day expectations into a reusable welcome path.
• —Role-based training: turn a subject-matter expert’s procedure into a short demonstration, practice activity, accessible job aid, and practical check.
• —AI workflow learning: teach an agreed process for source records, review, and escalation through examples relevant to your team’s actual work.

The problem to solve

AI use can become difficult to reconstruct when asset sources, tool details, approvals, and edits are spread across people and applications. A producer or reviewer may receive a finished image or sequence without enough context to understand its provenance or the decisions behind it. Waiting until delivery makes those gaps harder to resolve.

What the project demonstrates

The public checklist groups the work into Identify, Document, Generate, and Export. Its input section asks about ownership, licenses, performer consent where applicable, and supporting evidence before material is uploaded to a tool. It then prompts teams to identify tools and flag likeness or voice use.

Later steps describe recording tool versions, departments, usage details, timecodes, human oversight, named reviewers, and subsequent human modifications. Consent, disclosure preparation, and a documentation packet appear as later tasks. This offers a concrete way to discuss responsibilities and missing records; it does not establish that every project meets a recipient’s requirements.

Apply the approach to your project

• —Workflow review: trace one representative AI-assisted asset, identify missing evidence, and assign an owner to each follow-up.
• —Production practice: define when inputs are logged, which uses need approval, and how review decisions and human changes are recorded.
• —Delivery preparation: organize a project-specific evidence index and disclosure materials around a named recipient’s requirements, with qualified review where needed.

The problem to solve

A visitor may like a film’s premise but leave without a clear way to stay involved. Story information, updates, participation opportunities, and signup can also feel disconnected when they are spread across channels. The design challenge is to make the next step understandable and appropriate to the project—not add features for their own sake.

What the project demonstrates

The public homepage introduces the film and its characters, then presents a community model built around collectible tarot ranks and referral-based participation. It describes behind-the-scenes content and rewards. The relevant design lesson is the connection between the world of the story, the invitation, and the reasons presented for returning.

The linked join page asks for a name, public community name, account details, an optional referral code, and a choice about updates. Navigation also points to community recognition through a leaderboard and builders page. Those visible entry points illustrate an intentional participation journey; they are not proof of conversion, reward fulfillment, or private-account behavior.

Apply the approach to your project

• —Film or documentary community: bring the project story, approved artwork, updates, and an appropriate participation path into a consistent experience.
• —Project-specific journeys: scope a useful way for people to join, contribute, learn, or access resources instead of copying another film’s feature list.
• —Owner-ready delivery: move from a journey blueprint to a working pilot, agreed functionality, release checks, and an operating guide with an owner walkthrough.