[{"data":1,"prerenderedAt":290},["ShallowReactive",2],{"faq-en-change-management":3},{"id":4,"title":5,"body":6,"description":269,"extension":281,"meta":282,"navigation":285,"path":286,"seo":287,"stem":288,"__hash__":289},"faq/faq/en/change-management.md","\"Our Team Won’t Adopt Another Tool\"",{"type":7,"value":8,"toc":268},"minimark",[9,14,18,21,37,40,43,47,50,64,67,70,72,76,79,82,96,99,101,105,108,111,125,128,130,134,137,140,154,157,159,163,166,169,183,186,188,192,195,209,212,215,218,220,224,227,230,244,247,249,253,256,259,262,265],[10,11,13],"h2",{"id":12},"the-real-risk-isnt-the-software-its-adoption","The Real Risk Isn’t the Software. It’s Adoption.",[15,16,17],"p",{},"Most production tracking failures don’t happen because of missing features.",[15,19,20],{},"They happen because:",[22,23,24,28,31,34],"ul",{},[25,26,27],"li",{},"Artists don’t use the tool.",[25,29,30],{},"Supervisors revert to spreadsheets.",[25,32,33],{},"Producers maintain parallel systems.",[25,35,36],{},"Training was rushed or unclear.",[15,38,39],{},"Kitsu is designed to reduce resistance — not create it.",[41,42],"hr",{},[10,44,46],{"id":45},"designed-for-artists-not-just-producers","Designed for Artists, Not Just Producers",[15,48,49],{},"Kitsu focuses on clarity and usability.",[22,51,52,55,58,61],{},[25,53,54],{},"Clean, readable interfaces",[25,56,57],{},"Simple task views",[25,59,60],{},"Clear status workflows",[25,62,63],{},"Minimal configuration overhead",[15,65,66],{},"Artists should understand what to do in seconds — not after a 2-hour onboarding session.",[15,68,69],{},"When a tool feels intuitive, adoption happens naturally.",[41,71],{},[10,73,75],{"id":74},"structured-onboarding-for-every-role","Structured Onboarding for Every Role",[15,77,78],{},"We don’t treat “the studio” as one block.",[15,80,81],{},"Different roles need different training:",[22,83,84,87,90,93],{},[25,85,86],{},"Producers: project structure, reporting, planning",[25,88,89],{},"Supervisors: review flows, validation, approvals",[25,91,92],{},"Artists: task updates, uploads, feedback loops",[25,94,95],{},"Technical teams: API and automation",[15,97,98],{},"We provide live onboarding sessions and role-based guidance to ensure everyone knows exactly what matters to them.",[41,100],{},[10,102,104],{"id":103},"progressive-rollout","Progressive Rollout",[15,106,107],{},"Adoption improves when change is staged.",[15,109,110],{},"Instead of switching everything overnight, many studios:",[22,112,113,116,119,122],{},[25,114,115],{},"Start with one project",[25,117,118],{},"Pilot with one department",[25,120,121],{},"Train team leads first",[25,123,124],{},"Expand gradually",[15,126,127],{},"This approach builds internal champions who help the rest of the team transition smoothly.",[41,129],{},[10,131,133],{"id":132},"documentation-that-people-actually-use","Documentation That People Actually Use",[15,135,136],{},"Training doesn’t end after onboarding.",[15,138,139],{},"Kitsu provides:",[22,141,142,145,148,151],{},[25,143,144],{},"Clear written documentation",[25,146,147],{},"Searchable knowledge base",[25,149,150],{},"Tutorial videos",[25,152,153],{},"Practical examples",[15,155,156],{},"New hires can onboard themselves without requiring senior staff to repeat explanations.",[41,158],{},[10,160,162],{"id":161},"support-during-the-transition","Support During the Transition",[15,164,165],{},"Change creates questions.",[15,167,168],{},"During rollout, we remain available to:",[22,170,171,174,177,180],{},[25,172,173],{},"Answer workflow questions",[25,175,176],{},"Adjust configurations",[25,178,179],{},"Clarify best practices",[25,181,182],{},"Help production leads refine processes",[15,184,185],{},"The goal is not just to install software — it’s to stabilize usage.",[41,187],{},[10,189,191],{"id":190},"reducing-fear-of-change","Reducing Fear of Change",[15,193,194],{},"When teams resist new tools, it’s usually because they fear:",[22,196,197,200,203,206],{},[25,198,199],{},"Losing time",[25,201,202],{},"Breaking their workflow",[25,204,205],{},"Being monitored",[25,207,208],{},"Increased complexity",[15,210,211],{},"Kitsu is structured around clarity and collaboration — not control.",[15,213,214],{},"It centralizes communication, reduces email noise, and eliminates spreadsheet duplication.",[15,216,217],{},"Most teams feel relief once the transition is complete.",[41,219],{},[10,221,223],{"id":222},"adoption-is-a-design-principle","Adoption Is a Design Principle",[15,225,226],{},"Kitsu was built specifically for animation and VFX studios.",[15,228,229],{},"That means:",[22,231,232,235,238,241],{},[25,233,234],{},"Familiar production structures",[25,236,237],{},"Clear shot and asset hierarchies",[25,239,240],{},"Real-world workflow logic",[25,242,243],{},"Focused feature set (not overwhelming toolboxes)",[15,245,246],{},"The result: faster learning curves and higher adoption rates.",[41,248],{},[10,250,252],{"id":251},"a-tool-everyone-actually-uses","A Tool Everyone Actually Uses",[15,254,255],{},"The return on investment of a production tracker only happens when everyone uses it.",[15,257,258],{},"Our goal is simple:",[15,260,261],{},"From artist to producer to supervisor — everyone should feel comfortable on day one.",[15,263,264],{},"Change doesn’t have to be painful.",[15,266,267],{},"With the right structure, it becomes an upgrade.",{"title":269,"searchDepth":270,"depth":270,"links":271},"",2,[272,273,274,275,276,277,278,279,280],{"id":12,"depth":270,"text":13},{"id":45,"depth":270,"text":46},{"id":74,"depth":270,"text":75},{"id":103,"depth":270,"text":104},{"id":132,"depth":270,"text":133},{"id":161,"depth":270,"text":162},{"id":190,"depth":270,"text":191},{"id":222,"depth":270,"text":223},{"id":251,"depth":270,"text":252},"md",{"subtitle":283,"image":284},"How Kitsu Helps You With Training & Adoption","change-management-kitsu.png",true,"/faq/en/change-management",{"title":5,"description":269},"faq/en/change-management","FdCNN_vvbrE2eudZuIR4njDavrNpGESo_wD5TLyKcRM",1774956231290]