When was the last time a junior animator on your team surprised you?
Every animation studio eventually faces the same challenge: you need to grow your junior talent, but you cannot afford to let the production schedule slip.
The instinct is often to hold juniors back until there is a "safe" moment to involve them. Meanwhile, senior animators are overloaded, and juniors are underleveraged and aren't building the skills the studio needs from them.
On-production mentorship solves this.
When training is deliberately designed around real shot work, juniors develop faster, seniors spend less unplanned time on correction, and the production pipeline absorbs the load more evenly.
This article covers how to build an effective upskilling system for junior animators from the ground up.
Why Training Junior Animators Matters More Than You Think
Every unstructured junior is a slow tax on your senior team. Without deliberate mentorship, juniors will absorb whatever habits are around them, meaning more revision rounds, shot continuity issues that ripple across sequences, and a quiet but constant drain on supervisor time that never shows up in a project budget.
Studios tell themselves they'll invest in junior development once the deadline pressure eases. It doesn't ease. The weakest link gets weaker each cycle, and the people best equipped to fix it are too buried in work to notice until it becomes a talent retention problem.
The good news is, structured mentorship has a fast return on investment. Studios that formalize even a lightweight feedback process see measurable improvement in junior output within four to six weeks, before the next production ramp even begins.
Here are 12 best practices we identified to help you get started.
1. Onboarding Before Production Starts
Before a junior animator touches a single shot, a short onboarding phase of two to three days prevents the first week from becoming chaotic for everyone involved.
This phase should cover studio software configuration, animation walkthroughs, a viewing session of approved shots with commentary from a lead, and a full read-through of the style guide. The goal is to remove the basic friction that slows a junior down in their first days. When a junior spends their first morning figuring out where scene files live or how the naming convention works, a senior artist inevitably gets pulled in to help.
If you use our production tracker Kitsu, setting up the junior's account and walking them through the task board before day one removes that friction without requiring any senior time to explain it.
2. Mentorship Structure
The most effective structural decision a studio can make is to assign each junior a dedicated senior mentor.
A consistent point of contact accelerates trust, which directly accelerates feedback loops. When a junior knows exactly who to go to, they ask questions earlier and surface problems before they become wasted work. Rotating feedback means each reviewer has to re-establish context every time, and juniors often hesitate to ask questions of someone they only see occasionally. Assigning the dedicated mentor in Kitsu means all task assignments, feedback threads, and revision history are automatically linked to both persons to make the mentoring relationship accountable inside the pipeline.
Mentor selection deserves more attention than it usually gets. Not every senior artist is a good mentor. A senior who is an exceptional animator but impatient with questions can do real damage to a junior's confidence and slow their development. Mentoring should be instead based on intentional volunteering.
Once assigned, mentors should set clear weekly goals tied to real shots rather than exercises. A goal like "get blocking approved on shot 042 by Thursday" is more actionable than "practice weight and overlap," because it anchors the learning to a concrete deliverable with a visible quality standard.
3. Integrate Training Into Real Production Work
Junior training programs should use actual production shots as the learning vehicle from the start. It doesn't mean throwing juniors into complex shots without support. You can design an incremental progression where the complexity of the shot increases as skills build up. For example:
- Weeks 1 to 2 - Breakdowns and in-betweens on existing scenes. The junior is learning the studio's spacing and arcs without carrying the pressure of owning a shot. They can observe how approved animation moves and start calibrating their eye to the style.
- Weeks 3 to 4 - Simple shots with minimal characters or limited camera movement, reviewed closely at each pass. The junior now owns something real, but the scope is controlled enough that errors are easy to catch and correct.
- Month 2 onward - Progressively complex shots with decreasing check-in frequency as consistent first-pass quality is established. The junior earns more independence shot by shot.
The structure needs to match the learning load to the junior's current ability. A junior who is overwhelmed by a complex scene in week two will develop bad habits under pressure. Using Kitsu's task status workflow to flag a junior's early tasks with a distinct status like "supervised" makes it easy for supervisors to see at a glance which shots are on a training track versus a standard production track without any separate spreadsheet to maintain.
4. Daily and Weekly Feedback Loops
Feedback frequency and format have a direct impact on how quickly a junior improves. Too infrequent, and problems accumulate uncorrected for days. Too frequent and unstructured, and feedback becomes noise that disrupts the senior's own work.
A daily standup check-in of five to ten minutes is enough to surface blockers and confirm that the junior is moving in the right direction. Is the junior stuck on something that will waste the rest of the day? Is there a technical issue that needs to be escalated? Short and regular is more valuable than long and occasional.
Weekly playblast reviews are where the real work happens. For studios with remote or hybrid teams, Kitsu's comment system lets mentors leave timestamped, frame-specific notes directly on a review playlist, so async feedback works the same way whether the senior and junior are in the same room or different time zones without needing a live call.
End-of-week reflection rounds out the cycle. A junior who articulates what they tried, what feedback they received, and what they would do differently is actively consolidating what they learned. This reflection does not need to be formal, it can be a short written note or a two-minute verbal summary at the end of a session.
5. Build a Shot Approval Pipeline
Blocking is the early stage of animation where the animator establishes the core structure of the shot before refining it: key poses, timing, spacing, staging, composition, performance choices, etc.
One of the most common causes of wasted revision time on junior shots is moving into spline or polish before the blocking has been properly signed off. A clear three-stage approval pipeline prevents new animators from skipping the basics. Mapping those three stages to Kitsu's customizable task statuses means a shot cannot move forward without an explicit status change:
- The blocking pass is reviewed and approved before any spline work begins. This is the most important gate in the pipeline because blocking defines the timing, spacing, and primary poses.
- The spline pass confirms that rough curves are cleaned up and that the overall rhythm of the shot is correct before polish detail is added.
- The polish pass receives final notes before submission to the supervisor or director.
The key principle is that skipping blocking sign-off is never acceptable, even when the junior feels confident or the schedule is tight. The pipeline exists precisely to prevent the cost of downstram revisions from accumulating.
6. Reference and Research Habits
A junior animator who starts blocking without gathered reference has already made their first error.
Reference should be gathered before animation begins. Making it a requirement for blocking submission means the habit is systemic rather than optional. If a junior submits a blocking pass without attached reference, the submission should be treated as incomplete to create the expectation without relying on the junior's self-discipline alone.
Simple phone recordings are widely available and make reference gathering practical.
7. Style Guide and Shot Continuity
Without a style guide, junior animators default to habits they developed in school or in personal projects, which rarely match the specific style of the production. A studio-specific style guide covering spacing conventions, arc behavior, and rig-specific characteristics, among other guidelines, gives juniors a concrete target to work toward and a reference to check their work against.
The format of the style guide matters. A video-based guide that shows examples in motion is considerably more useful than a text document with static screenshots. Annotated playblasts of approved shots, with commentary on why specific choices were made, give juniors access to the reasoning behind the style rather than just the surface result. Creating those playblasts directly from the relevant sequence or episode entries in Kitsu means juniors can pull up the style reference and check adjacent scenes from the same place they're working without going through multiple shared drives.
Shot continuity is a related concern that is easy to overlook when assigning junior work. Pairing a junior's shot with adjacent scenes in the sequence so they can check their work in context prevents inconsistencies.
8. Psychological Safety in Critique
A junior who is afraid to show rough work will hide problems until they are expensive to fix. It's important for studios to build a culture where early review is framed as efficiency rather than weakness.
Feedback methodology matters. Specific, actionable notes build skills faster than vague impressions. A note like "stretch the anticipation from two frames to five and check that the weight reads correctly in the hip on frame 34" gives the junior exactly what they need to act. Kitsu's threaded comment history means that kind of feedback is written down and permanently retrievable: juniors can re-read a note at the exact moment they're applying it, and a specific written note tends to land less harshly than real-time verbal critique under pressure.
Mentors who are precise in their feedback also make their own thinking visible: juniors are more likely to apply the same reasoning to future shots independently when they understand why a note was given.
9. Use Screenshare and Live Annotation
Occasional live review sessions where the mentor demonstrates a solution directly on the rig are great uses of mentorship time. Watching a senior animator work through a problem in real time shows not just the outcome but the decision-making process: the way a problem is diagnosed, the order in which adjustments are made, and the criteria used to evaluate whether the result works.
Recording these sessions builds a library of in-context fixes that juniors can return to later. Attaching the recording directly to the shot's task as a revision in Kitsu means it remains findable in context. A two-minute recording of a mentor correcting a specific weight issue on a specific rig is worth more than a general tutorial on the same topic, because it is grounded in exactly the kind of work the junior is doing.
Even one or two recorded live sessions per month creates a reference library that benefits every junior in the studio, including those who join later.
10. Documentation and Knowledge Capture
Juniors who document what they tried and what feedback they received are building something that has value beyond their own development. A shot journal or internal wiki page logging decisions, revisions, and the reasoning behind feedback creates an onboarding resource that future juniors can use and that supervisors can reference when evaluating progress. The running comment thread on each Kitsu task effectively serves as this journal automatically: every status change, note, and revision upload is timestamped and persistent, so the documentation habit requires almost no extra overhead from the junior.
This documentation habit also surfaces patterns. If a junior's journal shows the same type of note appearing across three consecutive shots, that is useful information for the mentor to act on.
The format does not need to be elaborate. A short note at the end of each day, recording what was submitted, what feedback was received, and what will change on the next pass, is enough to accumulate useful insight over time.
11. Mentor Workload Protection
This point is often missing from discussions regarding junior development, despite being directly relevant to whether the system works at all. If mentoring is structured in a way that constantly interrupts seniors, the most committed mentors will eventually burn out or begin to resent the role.
Capping mentor time at a defined ceiling, roughly one to two hours per day, protects the senior's own production output. Batching feedback sessions rather than allowing random interruptions throughout the day is practical for both parties. Kitsu's notification settings can also be configured so mentors are only pinged on explicit status changes, blocking the constant stream of incidental updates that interrupt focus and making it practical to batch feedback into defined windows. A mentor who knows that feedback happens at 10am and 4pm can plan their own work around those windows. A junior who knows when feedback is coming will hold their questions and deliver more complete work rather than surfacing every small uncertainty in real time.
Other animators can absorb overflow when a junior's shot has problems that exceed the scope of a normal mentorship session. The mentor's role is not to solve every problem personally but to guide the junior's development.
12. Gradual Autonomy and Measuring Progress
The goal of on-production training is to reach a point where the junior can be assigned a shot and deliver it through all three approval stages without major revisions or unplanned intervention. Getting there requires a deliberate reduction in check-in frequency as the junior's first-pass quality improves.
"Consistently approved" needs a concrete definition to be useful as a threshold. A reasonable benchmark is first-pass blocking approval on three consecutive shots without major revisions to give both the mentor and the junior a clear signal that the transition to more independence is warranted. Pulling a junior's task history in Kitsu makes that count straightforward.
Moving to more complex shots follows the same logic. A junior who is consistently delivering clean blocking on simple shots is ready for more characters, more camera movement, or more emotionally demanding scenes. The progression should be driven by output, not by time.
13. When to Escalate or Reassign
Not every junior will progress at the same pace, and a system that assumes otherwise will leave supervisors without a plan when someone falls behind. Establishing a protocol in advance is more effective than addressing each situation as a unique crisis.
Signs that a junior is not progressing as expected include repeated notes on the same technical issue across multiple shots, blocking that consistently requires major revision before moving to spline, and a pattern of not using reference despite it being a stated requirement. Again, Kitsu's comment history makes the pattern easy to recognize and show to a supervisor.
The first response is a direct conversation between the mentor and the junior, framing the issue specifically and asking the junior what they need. Sometimes the problem is a gap in understanding that a targeted session can address. Other times the junior is struggling with something outside of work that is affecting their focus.
If the pattern continues after a targeted intervention, the supervisor needs to be involved. This may result in a temporary change in the type of shots assigned, a more intensive review schedule, or in some cases, a reassignment to a different part of the pipeline. The important thing is that the decision is made on the basis of clear criteria and handled with directness and respect, not allowed to drift indefinitely while the production absorbs the cost.
Conclusion
Training junior animators on-production is not a compromise between talent development and production output. It's a mandatory phase for studios to maintain quality, reduce senior burnout, and build the bench strength it will need for the next project.
Start with a short structured onboarding before production contact. Assign dedicated mentors who are chosen for their communication skills as much as their technical ability. Integrate real shot work from the first week with increasing complexity over time. Protect the feedback pipeline with a clear three-stage approval process. And define the thresholds for progression so that every decision is grounded in observable output.
The studios that get this right are not doing anything exotic. They just apply the same discipline to talent training that they apply to shot production: clear goals, defined checkpoints, and consistent accountability. This is how a team grows together instead of having senior animators carry everyone else indefinitely.
If you want to make the process simpler though, make sure to give Kitsu a try!
