Session 4 2025-26 Production Project

SUMMARY

Role

  • Place your MAIN ROLE TITLE for the production here…

Intention (SMART Goal) for the Session

  • Copy and paste your SMART Goal from the class PTS, Project Tracking Sheet, here…

PRODUCTION

THE (FILM, SOUND, or GAME)

Link the final version of the film, game, or song from your Google Drive (FILM & ROCK) or itch.io (GAME). Make sure it is publicly viewable.

Write a descriptive sentence (ya’know, give me some unique details) about the embedded or linked project above.

SKILLS COMMENTARY

Link the team slideshow with your role, SMART Goal, and evidence of your SMART Goal for this session.

Write a sentence about your role in the slideshow and MAIN creative and technical contributions to the project. (Think of it this way – state what impact you made, and if you didn’t do your job, the project would not have succeeded or been as good – show off a little)

POST-PRODUCTION

21st CENTURY SKILLS BEST PRACTICES

Write  SPECIFIC examples of HOW you demonstrated the skills below…

Ways of Thinking (Creativity, Innovation, Critical Thinking, Problem Solving)

How did you GROW in expressing your creativity, innovation, critical thinking, and or problem-solving during this project? Pick one and EXPLAIN.

Ways of Working (Communication & Collaboration)

How did you GROW as a communicator and collaborator during this project? Pick one and EXPLAIN.

Tools for Working (Info & Media Literacy)

How did you GROW in any of the industry technology tools (game engine, DAW, camera, video editor, etc. ) you used during this project? Pick one and EXPLAIN.

Ways of Living in the World (Life & Career)

How did you GROW in preparation for life or for a career during this project? Pick one and EXPLAIN.

REACTIONS TO THE FINAL VERSION

Place at least one comment from the PEER review and cite only the student’s first name.

Place at least one comment from the ADVISOR review and cite the advisor’s name.

SELF-REFLECTION

Pick one of these types of reflection: action points, evaluative, intentional, or retrospective, state which one you picked, and write your reflection here…

GRAMMAR AND SPELLING

Place the name of the grammar and spelling tool you used to create this blog post.

EDITOR

Name the person who reviewed your blog post for grammar and spelling issues. First name only.

DID YOU DELETE ALL OF MR. LE DUC’s INSTRUCTIONS ABOVE? <— DELETE THIS INSTRUCTION, TOO!

NAME OF PROJECT Postmortem Document TEMPLATE for FILM

This document reviews the film production project. Its purpose is to facilitate collective learning by analyzing the pre-production, production, and post-production processes, celebrating successes, and identifying key areas for improvement in future projects.

Field Detail
Project Title: [Insert Film Title Here]
Production Team: [List All Team Members]
Production Duration: [e.g., 4 weeks pre-pro, 3 days shooting, 2 weeks post-pro]
Equipment/Software Used: [e.g., DSLR Camera, DaVinci Resolve, Boom Mic]
Date Completed: [Date]

I. Team and Production Analysis

This section examines the structure, communication, and performance of the production team, with a focus on the five core roles.

A. Roles and Responsibilities

Team Member Primary Role Key Responsibilities and Deliverables
[Name] Director [e.g., Final creative vision, Actor performance, Master shot list]
[Name] Screenwriter [e.g., Final script, Dialogue clarity, Scene structure/pacing]
[Name] Cinematographer [e.g., Lighting design, Camera movement, Frame composition]
[Name] Sound Designer [e.g., Location sound recording, Sound effects (Foley), Mix balance]
[Name] Editor [e.g., Assembly cut, Pacing/Rhythm, Color correction/grading]

B. Collaboration and Handoff Effectiveness

Reflect on how the team worked together across the entire production cycle.

Communication: 

How did the Director communicate the vision to the Cinematographer and Screenwriter? 

 

What tools (e.g., group chat, storyboards) were used? 

 

What communication style worked well, and what was missing during intense production moments?

 

Pre-Production Handoff (Script to Shoot): 

How smoothly did the final script translate into the shot list and storyboards?

 

Did the Cinematographer feel they had enough time and detail from the Screenwriter and Director to prepare?

 

Production Handoff (Set to Post-Production): 

How organized were the camera files (dailies) and sound files when they were given to the Editor and Sound Designer? 

 

Highlight any issues with missing metadata (e.g., scene numbers, good takes).

 

C. Individual/Team Lessons Learned

Identify specific, actionable takeaways about the process of filmmaking.

 

Scheduling & Time Estimation (Production): 

Which scenes or setups took significantly longer than expected (e.g., complex lighting, actor blocking)? 

 

Which took less time? 

 

What changes should the team make to its shooting schedule next time? (e.g., “We must double the estimate for all close-up setups.”)

 

Skills Development:

What new technical skills did individuals learn (e.g., pulling focus, complex three-point lighting, advanced editing shortcuts)?

 

General Takeaways: 

What advice would you give a new film crew starting this project? (e.g., “Always have extra batteries,” “Do a full sound check before every take.”)

 

II. Film Analysis & Review

This section reviews the final product against the initial design vision, broken down by department.

A. Project Goals vs. Final Outcome

List the major goals set at the beginning of the project and assess their completion status.

Goal (e.g., 3-minute run time, use of dolly shot, single location) Status (Achieved/Partial/Failed) Rationale/Explanation
Overall Assessment of Scope: [Was the initial scope too ambitious, too simple, or just right? What percentage of the initial vision (script/shot list) was completed in the final cut?]

B. What Went Right (Successes)

Identify the most successful elements of the project—the things that should be repeated in the future.

Role Success Element Why it Worked
Screenwriter [e.g., The dialogue felt natural; the plot twist was effective.] [e.g., We read the lines out loud before finalizing; the outline was strong.]
Cinematographer [e.g., The low-key lighting in the climax was powerful; the handheld camera felt motivated.] [e.g., Excellent gaffer support; practiced the camera movement several times.]
Director [e.g., The actor performances were convincing; the emotional tone was consistent.] [e.g., Thorough rehearsal process; the Director had a clear, single vision.]
Sound Designer [e.g., The location audio was clean; the music transitions were seamless.] [e.g., Used professional external recorder; paid close attention to room tone.]
Editor [e.g., The film’s overall pace felt tight; the color grade matched the mood.] [e.g., Good shot coverage allowed for choices; set up the project folder cleanly.]

C. What Went Wrong (Challenges)

Analyze the major problems and roadblocks encountered during development.

Screenplay Issues: 

Did any scene not work on set because the dialogue was too long or the location was impractical as written? 

 

Explain the necessary on-set rewrite or cuts.

 

Cinematography/Technical Issues:

Describe the hardest technical problem (e.g., light flicker, focus hunting, bad white balance).

 

Why was it difficult to solve? How did it impact the final look?

 

Sound Design Issues (Production & Post): 

Describe the single biggest sound problem (e.g., traffic noise ruined a take, microphone placement was visible, final mix felt empty).

 

How much time was lost fixing it in post-production?

 

Editing/Post-Production Flow: 

Did poor organization of footage or sound assets cause delays? 

 

Did the Director or Screenwriter change their mind late in the process, requiring extensive re-editing? 

 

Explain the impact.

 

III. Key Takeaways and Future Best Practices

Provide actionable advice for the next film project, focusing on the best practices learned.

Focus Area Future Best Practice (Specific Actionable Advice)
Screenwriter [e.g., “Write with specific locations in mind,” “Never exceed 25 words of dialogue per shot.”]
Director [e.g., “Always get two different takes for every scene—one fast, one slow,” “Block actors before setting any lights.”]
Cinematographer [e.g., “Take a reference photo of the lighting setup before striking a set,” “Use an exposure meter for every key light.”]
Sound Designer [e.g., “Always record 30 seconds of clean room tone for every location,” “Monitor audio with headphones at all times during takes.”]
Editor [e.g., “Never start the assembly cut until all dailies are correctly labeled and organized,” “Get feedback on the first 1-minute cut within 48 hours.”]

 

NAME OF PROJECT Postmortem Document TEMPLATE for ROCK

This document is a formal review of our recent performance project. Its purpose is to facilitate collective learning by analyzing the process, celebrating successes, and identifying key areas for improvement in future performances.

  • Project Title: [Insert Song Title Here] 
  • Band/Group Name: [e.g., The Tantrums, Band 2, etc.] 
  • Project Duration: [e.g., 3 weeks] 
  • Performance Date: [Date]

I. Band Analysis and Collaboration

This section analyzes the structure, communication, and performance of the band.

Roles and Responsibilities

Team Member Primary Role Key Responsibilities
[Name] Drums Setting the tempo, maintaining feel, and arranging rhythmic hits.
[Name] Bass Locking in with the drummer, creating melodic foundation/grooves.
[Name] Guitar Rhythm/Lead parts, tone shaping (pedals/amp settings).
[Name] Keyboards Harmony/Pad textures, specific solo or hook parts.
[Name] Vocals Melody execution, stage presence, clear lyrical delivery.

Collaboration Effectiveness

Reflect on how the team worked together across the project timeline.

Communication: 

How often did the band communicate about the song parts outside of class? 

 

What tools (e.g., shared sheet music, recordings, chat) were used? 

 

What worked well (e.g., clear section leaders), and what was missing (e.g., not enough feedback on volume balance)?

 

Conflict Resolution (Creative Differences): 

Describe any disagreements or creative differences that arose (e.g., tempo choice, solo section, instrumental arrangement). 

 

How were they resolved, and was the final process effective for everyone?

 

Task Integration (Arrangement Flow):

How smoothly did the individual parts fit together during rehearsal? 

 

What challenges arose when one person’s part depended on another’s (e.g., the guitarist needed the bassist to change their rhythm)? 

 

Highlight any issues with learning parts before rehearsals.

Individual/Team Lessons Learned

Identify specific, actionable takeaways about the rehearsal process.

Time Estimation & Rehearsal Efficiency: 

Which parts of the song (e.g., the bridge, the drum solo, the vocal harmony) took significantly longer to perfect than expected? 

 

What changes should the band make to its warm-ups or time management next time? (e.g., “We must spend the first 15 minutes checking everyone’s tone/levels.”)

 

Skills Development: 

What new musical skills did individuals learn (e.g., advanced strumming pattern, better microphone technique, using a new keyboard patch)?

 

General Takeaways: 

What advice would you give a new band starting this project? (e.g., “Define the instrumental dynamics first,” “Record yourself every practice.”)

II. Performance Analysis & Review

This section reviews the final performance against the initial musical goals.

Project Goals vs. Final Outcome

List the major goals set at the beginning of the project and assess their completion.

Goal (e.g., Maintain consistent tempo, Execute the Guitar Solo perfectly, Nail the dynamics) Status (Achieved/Partial/Failed) Explanation
 
 
 
Overall Assessment of Arrangement Scope: [Was the song too complex for the time we had? What percentage of the initial vision (e.g., adding backup vocals, creating an outro) was completed?]

What Went Right (Successes)

Identify the most successful elements of the performance—the things that should be repeated in the future.

Core Musicality / Feel: 

What specific section (e.g., the second verse, the final chorus) felt the most tight, energetic, or musically solid? 

 

Why did it work? (e.g., The drummer and bassist were perfectly “locked in.”)

 

Tone, Dynamics, or Stage Presence: 

Which visual or auditory elements looked/sounded professional (e.g., the guitarist’s clean tone, the lead vocalist’s confidence, the band’s use of dynamics)? 

 

Why was this area successful?

 

Specific Technical Achievements: 

Did the band successfully execute a complex musical passage or fix a major mid-performance mistake seamlessly? 

 

Describe it briefly.

What Went Wrong (Challenges)

Analyze the major problems and roadblocks encountered during the rehearsal and performance.

Scope Creep or Arrangement Flaws: 

Did the song arrangement get too complex? 

 

Did a core musical idea not work out once we played it live? 

 

Explain the impact (e.g., it felt rushed, it confused the audience) and what content was cut or simplified.

 

Technical Issues (Gear/Sound): 

Describe the single hardest gear issue or sound problem (e.g., microphone feedback, a specific patch stopped working, unable to hear the click track). 

 

How much time was lost fixing it?

 

Part Consistency Issues: 

Did missing or poorly organized parts cause confusion or errors during the live performance (e.g., the backing vocalist forgot the entrance, the guitarist misread the chart)?

Key Design Takeaways

Provide advice for the next band project, based on what went well.

Focus Area Future Best Practice (Specific Actionable Advice)
Arrangement [e.g., “Always define the tempo and dynamics before writing individual parts,”]
Rehearsal [e.g., “Use a metronome for all rehearsals,” ]
Performance/Gear [e.g., “Always check instrument levels with the soundboard operator before the show,”]

 

NAME OF PROJECT Postmortem Document TEMPLATE for GAME

  • TITLE THIS BLOG POST: [NAME OF PROJECT] Postmortem Document
  • PLACE A CREATIVE COMMONS IMAGE RELATED TO THE PROJECT
  • FOLLOW THE DIRECTIONS IN THE POST
  • REVIEW THIS POST EXAMPLE:
    • Coming Soon
  • DELETE ANY TEXT THAT HAS THESE BRACKETS [stuff inside these brackets]

This document is a formal review of the game development project. Its purpose is to facilitate collective learning by analyzing the process, celebrating successes, and identifying key areas for improvement in future projects.

Project Title: [Insert Game Title Here]
Development Team: [List All Team Members]
Development Duration: [e.g., 6 weeks, 40 hours]
Engine/Software Used: [e.g., Unity, Godot, Construct]
Date Completed:

I. Team Analysis

This section analyzes the structure, communication, and performance of the development team.

Roles and Responsibilities

Team Member Primary Role (e.g., Lead Programmer, Artist) Key Responsibilities
[Name]
[Name]
[Name]
[Name]

Collaboration Effectiveness

Reflect on how the team worked together across the entire development cycle.

Communication:
How often did the team communicate? 

 

What tools (e.g., chat, in-person) were used? 

 

What worked well, and what was missing?

 

Conflict Resolution:
Describe any disagreements or creative differences that arose. 

 

How were they resolved, and was that process effective?

 

Task Integration:
How smoothly did assets (art, sound) and code merge together? 

 

What challenges arose when one person’s work depended on another’s? 

 

Highlight any issues with version control.

 

Individual/Team Lessons Learned

Identify specific, actionable takeaways about the process of making the game.

Project Management & Time Estimation:
Which tasks took significantly longer than expected? 

 

Which took less time? 

 

What changes should the team make to its scheduling/timeline next time? (e.g., “We must double our estimate for UI polish.”)

 

Skills Development:
What new technical skills did individuals learn (e.g., advanced scripting, animation techniques)

 

General Teamwork Takeaways:
What advice would you give a new team starting this project? (e.g., “Define the core mechanic first,” “Don’t ignore documentation.”)

 

II. Game Analysis & Review

This section reviews the final product against the initial design vision.

Project Goals vs. Final Outcome

List the major goals set at the beginning of the project and assess their completion status.

Goal (e.g., 3 levels, 2 enemy types, unique mechanic) Status (Achieved/Partial/Failed) Rationale/Explanation
Overall Assessment of Scope: [Was the initial scope too large, too small, or just right? What percentage of the initial vision was completed?]

What Went Right (Successes)

Identify the most successful elements of the project—the things that should be repeated in the future.

Core Mechanic / Gameplay:
What specific game element or mechanic feels the most fun, polished, or unique? 

 

Why did it work?

 

Art, Sound, or UI/UX:
[Which visual or auditory elements look/sound professional?

 

Why was this area successful (e.g., good planning, strong individual skill)?

 

Specific Technical Achievements:
[Did the team successfully implement a complex piece of code or fix a difficult bug?

 

Describe it briefly.

What Went Wrong (Challenges)

Analyze the major problems and roadblocks encountered during development.

Scope Creep or Design Flaws:
Did the project get too big? 

 

Did a core design idea not work out once implemented? 

 

Explain the impact and how much content was cut.

 

Technical Issues:
Describe the single hardest bug or technical problem. 

 

Why was it so difficult to solve? How much time was lost?

 

Asset Pipeline Issues:
Did missing or poorly organized assets (art files, sound files) cause delays or confusion?

 

Key Design Takeaways

Provide actionable advice for the next development project, focusing on best practices learned here.

Focus Area Future Best Practice (Specific Actionable Advice)
Design [e.g., “Always prototype paper levels first,” “Only design features that can be completed in the first 50% of the project time.”]
Programming [e.g., “Comment all code clearly,” “Use a separate branch for testing new features before merging to the main build.”]
Art & Production [e.g., “Establish a mandatory asset naming standard on Day 1,” “Minimize the resolution of non-critical textures for better performance.”]

 

Ideological Edits Project TEMPLATE

  • TITLE THIS BLOG POST: Ideological Edits: [Your Film Title]
  • PLACE A CREATIVE COMMONS IMAGE RELATED TO THE PROJECT
  • FOLLOW THE DIRECTIONS IN THE POST
  • REVIEW THIS POST EXAMPLE:
    • Coming Soon
  • DELETE ALL OF MR. LE DUC’s INSTRUCTIONS ABOVE AFTER COMPLETING THEM

Summary

Write a one-sentence summary of this project. Write this sentence for somebody who has no idea what this project is.

My Film

Publically Link your final ideological edit of the scene from your Google Drive, YouTube, or Vimeo here…

Chosen Filmmaker and Style: State the name of the filmmaker (Kuleshov, Eisenstein, or Tarkovsky) and the style (Juxtaposition, Collision, or Duration) that you chose for your final edit.

Link to the “Straight Cut” (Comparison Edit): Publically Link the simple, chronological “Straight Cut” version of your scene here for comparison.

Problems I Solved

Describe in complete sentences the problems that you solved to complete this project. Please be detailed. This could include technical issues (software, rendering, exporting) or creative challenges (achieving the correct rhythm, maintaining the long take, finding the right juxtaposition).

Most Proud of…

Describe in complete sentences what you are most proud of after completing this project. This should focus on the aesthetic, ideological, or technical choices that made your final edit successful.

DELETE ALL OF THE INSTRUCTIONS ABOVE AFTER COMPLETING THEM

My GTD Trusted System: NAME THE SYSTEM – TEMPLATE

  • TITLE THIS BLOG POST: My GTD Trusted System: NAME THE SYSTEM
    • EXAMPLE: My GTD Trusted System: Google Tasks and Calendar
  • PLACE A CREATIVE COMMONS IMAGE RELATED TO YOUR TRUSTED SYSTEM, MAYBE THE LOGO?
  • FOLLOW THE DIRECTIONS IN THE POST BELOW:
    • Answer the questions
    • Publish post
  • REVIEW THIS POST EXAMPLE:
    • Coming soon!
  • DELETE ALL OF MR. LE DUC’s INSTRUCTIONS, AFTER COMPLETING EACH SECTION

Notes from Learning about the Brain and GTD

PLACE NOTES FROM WHAT YOU LEARNED ABOUT DAVID ALLEN’S GETTING THINGS DONE BOOK, JAMES CLEAR’S ATOMIC HABITS BOOK, AND RESEARCH ABOUT THE BRAIN’S ABILITY TO FOCUS ON ONE TASK AT A TIME AND THE INEFFICIENCY OF MULTITASKING

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS ABOVE

My GTD Trusted System Screenshot

INCLUDE A SCREENSHOT OF YOUR TRUSTED SYSTEM TOOL

SELECT these keys on your computer keyboard to take a screenshot:

COMMON + SHIFT + 4, then drag your mouse over the area you want to take a screenshot. When you let go, the picture will appear on your desktop.

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS ABOVE

Five GTD Steps for Your Trusted System

WRITE AT LEAST ONE SENTENCE FOR EACH OF THE FIVE STEPS BELOW, CLEARLY DESCRIBING HOW YOUR SYSTEM HELPS YOU DO EACH ONE OF THESE STEPS…

Collects

 

Processes

 

Organizes

 

Keeps Track & Adjusts

 

Completes

 

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS ABOVE

Chocolate Film Audio and Editing Project TEMPLATE

Summary

Write a one-sentence summary of this project. Write this sentence for somebody who has no idea what this project is.

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS AFTER COMPLETING THEM

My Film

Publically Link your final edit of the movie from your Google Drive here…

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS AFTER COMPLETING THEM

Problems I Solved

Describe in complete sentences the problems that you solved to complete this project. Please be detailed.

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS AFTER COMPLETING THEM

Most Proud of…

Describe in complete sentences what you are most proud of after completing this project.

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS AFTER COMPLETING THEM

Game Engine Research & Recommendation TEMPLATE

Summary

Write a one-sentence summary of this research project.

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS ARE DETAILED AFTER COMPLETING THEM

Research Resources Cited

Link the resources you used in your research. These might be YouTube videos, webpages, podcasts, etc.

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS AFTER COMPLETING THEM

Comparison Chart

Fill in the chart below with evidence for each of the categories. You may add more categories.

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS AFTER COMPLETING THEM

Topic UNITY GODOT CONSTRUCT.net
Ease of Learning/Beginner-Friendliness
Supported Game Types (2D/3D)
Required Programming Language
Available Tutorials
Cost/Licensing
Community Size
Other
Other
Other
Other
Other

Recommendation

Write a one-paragraph conclusion of your research and findings, AND make your recommendation.

DELETE ALL OF MR. LE DUC’s INSTRUCTIONS AFTER COMPLETING THEM

Music Will Instrument Focus: NAME INSTRUMENT for Session # TEMPLATE

  • TITLE THIS BLOG POST: Instrument Focus: NAME INSTRUMENT for Session # 
    • EXAMPLE: Instrument Focus: Guitar for Session 1
  • PLACE A CREATIVE COMMONS IMAGE RELATED TO THE PROJECT
  • FOLLOW THE DIRECTIONS IN THE:
    • Answer the questions  below
    • Publish post
  • REVIEW THIS POST EXAMPLE:
  • DELETE ALL OF MR. LE DUC’s INSTRUCTIONS ARE DETAILED BELOW AFTER COMPLETING THEM

Instrument Focus for Session

Which instrument are you going to focus on for this session?

 

Which Music Will resource are you going to use?

 

What is your goal by the end of the Session?

 

Resources

Film Viewing Reflection TEMPLATE

  • TITLE THIS BLOG POST: Film Viewing Reflection: NAME OF FILM
    • EXAMPLE: Film Viewing Reflection: Surf’s Up 
  • PLACE A CREATIVE COMMONS IMAGE RELATED TO THE PROJECT
  • FOLLOW THE DIRECTIONS IN THE:
    • Answer the questions  below
    • Publish post
  • REVIEW THIS POST EXAMPLE:
  • DELETE ALL OF MR. LE DUC’s INSTRUCTIONS DETAILED BELOW AFTER COMPLETING THEM

Reflections

How does the film (various scenes) affect you? (Remember, every scene is like a mini-movie)

 

Which scene best represents the film, for you? Why?

 

Second Viewing

Notice the cinematography, mise en scene, actor movement, wardrobe, sound (diegetic, non-diegetic, music, etc.), choices

Review the Big List of Film Terms for cinematic elements, mise en scene (what’s represented on screen), and sound

Write notes (below in this post)

Film Elements to Consider