[{"data":1,"prerenderedAt":321},["ShallowReactive",2],{"template:workflow-case-study:en":3},{"title":4,"description":5,"readTime":6,"slug":7,"language":8,"kind":9,"coverUrl":10,"document":11},"How a Team Improved Its Workflow","A case study: the problem, the diagnosis, the changes and the result after three months","10 min","workflow-case-study","en","case-study","\u002Ftemplate-media\u002Fworkflow-case-study\u002Fcover.jpg",{"v":12,"kind":13,"design":14,"blocks":25},2,"longread",{"fontPairing":15,"baseTheme":16,"lineHeight":17,"blockGap":18,"showProgressBar":19,"accentColor":20,"viewPassThreshold":21,"quizPassThreshold":22,"quizShowCorrectness":19,"quizAllowRetry":19,"outlineSource":23,"tocPlacement":24,"language":8},"editorial","classic","relaxed","normal",true,"#10b981",80,70,"chapters","document",[26,35,42,47,52,59,76,80,83,111,118,143,147,174,188,199,205,212,216,222,225,238,253,258,262,276,292,297,306,318],{"id":27,"type":28,"title":4,"subtitle":5,"author":29,"date":30,"readTime":6,"imageUrl":10,"style":31,"overlayOpacity":32,"titleColor":33,"subtitleColor":34},"cs-cover","cover","Operations team","","split",30,"#ffffff","#e2e8f0",{"id":36,"type":37,"text":38,"dropCap":19,"alignment":39,"columns":40,"fontSize":41},"cs-lead","paragraph","\u003Cp>A seven-person marketing team was busy from morning till night and still missed deadlines. Three months later, they delivered more with less overtime — without hiring anyone. This case study walks through what they changed and why it worked. Replace the team and the numbers with your own story.\u003C\u002Fp>","left",1,"lg",{"id":43,"type":44,"title":45,"description":46,"chapterNumber":30,"level":40,"style":16},"cs-problem","chapter","The team and the problem","Busy all the time, finishing too little",{"id":48,"type":37,"text":49,"dropCap":50,"alignment":39,"columns":40,"fontSize":51},"cs-problem-text","\u003Cp>The team handled campaigns, social media and requests from sales. Work arrived through email, chat and hallway conversations. Everyone had a dozen tasks “in progress”, and nobody could say what would be finished this week.\u003C\u002Fp>",false,"base",{"id":53,"type":54,"text":55,"author":56,"role":57,"style":58},"cs-quote","quote","We were busy all day, every day — and still the most important campaign slipped by two weeks.","Team lead","Marketing team","highlight",{"id":60,"type":61,"columnsCount":62,"items":63},"cs-symptoms","grid",3,[64,68,72],{"title":65,"text":66,"icon":67},"Too much in progress","Each person juggled 10–15 tasks at once and switched between them all day.","Activity",{"title":69,"text":70,"icon":71},"Invisible requests","Requests came from five channels, and some were simply lost.","BookOpen",{"title":73,"text":74,"icon":75},"Late surprises","Problems surfaced on the deadline day, when it was too late to react.","Sparkles",{"id":77,"type":44,"title":78,"description":79,"chapterNumber":30,"level":40,"style":16},"cs-diagnosis","Diagnosis","Looking at the work, not at the people",{"id":81,"type":37,"text":82,"dropCap":50,"alignment":39,"columns":40,"fontSize":51},"cs-diagnosis-text","\u003Cp>Instead of asking people to work harder, the team mapped how work actually flowed. Click the markers to follow the case from problem to result.\u003C\u002Fp>",{"id":84,"type":85,"url":86,"caption":87,"aspectRatio":88,"markerStyle":89,"trigger":90,"markers":91},"cs-map","hotspots","\u002Ftemplate-media\u002Fworkflow-case-study\u002Fmap.png","Click a marker to follow the case","auto","number","click",[92,98,102,107],{"id":93,"x":94,"y":95,"title":96,"text":97},"cs-map-1",12.5,12,"Problem","Deadlines missed on 4 out of 10 campaigns; overtime every week.",{"id":99,"x":100,"y":95,"title":78,"text":101},"cs-map-2",53.8,"Work in progress was three times higher than the team could finish; requests had no single entry point.",{"id":103,"x":94,"y":104,"title":105,"text":106},"cs-map-3",57,"Solution","One visual board, a limit on work in progress and a 15-minute daily stand-up.",{"id":108,"x":100,"y":104,"title":109,"text":110},"cs-map-4","Result","Lead time halved, missed deadlines dropped to one in twenty, overtime almost disappeared.",{"id":112,"type":113,"url":114,"alt":115,"caption":116,"credits":30,"layout":117,"aspectRatio":88},"cs-figure","image","\u002Ftemplate-media\u002Fworkflow-case-study\u002Ffigure.png","Chaotic overlapping cards on the left, neat columns of cards on the right, an arrow between them","Before and after: scattered tasks on the left, a board with clear columns on the right","contained",{"id":119,"type":120,"headers":121,"rows":125,"caption":142,"hasHeaderRow":19,"hasHeaderColumn":19,"striped":19,"bordered":19},"cs-metrics","table",[122,123,124],"Metric","Before","After 3 months",[126,130,134,138],[127,128,129],"Average lead time","18 days","9 days",[131,132,133],"Tasks in progress per person","12","3",[135,136,137],"Missed deadlines","4 of 10","1 of 20",[139,140,141],"Overtime per week","6 hours","1 hour","Team metrics before and after the changes",{"id":144,"type":44,"title":145,"description":146,"chapterNumber":30,"level":40,"style":16},"cs-changes","What the team changed","Three simple practices, introduced one by one",{"id":148,"type":149,"items":150,"orientation":171,"numbering":172,"style":173},"cs-weeks","timeline",[151,155,159,163,167],{"value":152,"title":153,"text":154},"Week 1","One board for all work","Every request became a card on a shared board. Nothing outside the board counted as work.",{"value":156,"title":157,"text":158},"Week 2","Single entry point","Sales and other teams submitted requests through one form instead of chats and emails.",{"value":160,"title":161,"text":162},"Week 3","Limit work in progress","No more than three tasks per person in progress. New work started only when something was finished.",{"value":164,"title":165,"text":166},"Week 4","Daily stand-up","Fifteen minutes at the board every morning: what is blocked, what finishes today.",{"value":168,"title":169,"text":170},"Month 3","Monthly retrospective","One hour to review the numbers and choose one improvement for the next month.","vertical","manual","card",{"id":175,"type":176,"items":177,"style":186,"defaultIndex":187},"cs-practices","tabs",[178,181,184],{"title":179,"text":180,"imageUrl":30,"videoUrl":30},"Visual board","\u003Cp>Columns “Requested”, “In progress”, “Review”, “Done”. Everyone sees the state of every task — no status meetings needed.\u003C\u002Fp>",{"title":182,"text":183,"imageUrl":30,"videoUrl":30},"WIP limits","\u003Cp>Limiting work in progress feels slower at first. In practice, tasks stop waiting and start finishing.\u003C\u002Fp>",{"title":165,"text":185,"imageUrl":30,"videoUrl":30},"\u003Cp>Not a report to the manager, but a quick check of what is blocked. Problems surface days earlier.\u003C\u002Fp>","underline",0,{"id":189,"type":190,"question":191,"options":192,"selectionType":193,"pairs":194,"correctIndex":195,"correctIndexes":196,"explanation":197,"feedbackIncorrect":30,"variant":198},"cs-quiz-order","quiz","Put the changes in the order the team introduced them.",[153,157,161,165,169],"sequence",[],null,[],"You first need to see all the work before you can limit it and manage it daily.","interactive",{"id":200,"type":201,"title":202,"text":203,"variant":204},"cs-tip","callout","Change one thing at a time","Introducing all practices at once overwhelms people and makes it impossible to see what worked. One change per week or two keeps the team on board.","idea",{"id":206,"type":207,"label":208,"scope":209,"style":210,"align":211},"cs-continue","continue","Continue to the results","next-step","primary","center",{"id":213,"type":44,"title":214,"description":215,"chapterNumber":30,"level":40,"style":16},"cs-results","The results","What changed after three months",{"id":217,"type":218,"url":219,"caption":220,"credits":30,"layout":117,"aspectRatio":221,"autoplay":50,"loop":19,"muted":19},"cs-video","video","\u002Ftemplate-media\u002Fworkflow-case-study\u002Fclip.mp4","Lead time and missed deadlines went down month by month","16:9",{"id":223,"type":37,"text":224,"dropCap":50,"alignment":39,"columns":40,"fontSize":51},"cs-results-text","\u003Cp>The team did not work longer hours — they finished what they started. With fewer tasks in progress, each task spent less time waiting, and the board made problems visible early enough to act.\u003C\u002Fp>",{"id":226,"type":190,"question":227,"options":228,"selectionType":233,"pairs":234,"correctIndex":195,"correctIndexes":235,"explanation":236,"feedbackIncorrect":237,"variant":198},"cs-quiz-lead-time","Which changes reduced the team’s lead time?",[229,230,231,232],"Limiting work in progress","Making all work visible on one board","Daily checks of blocked tasks","Working longer hours","multiple",[],[187,40,12],"Lead time dropped because work stopped waiting, not because people worked more.","The team actually reduced overtime — longer hours were not the solution.",{"id":239,"type":190,"question":240,"options":241,"selectionType":242,"pairs":243,"correctIndex":195,"correctIndexes":251,"explanation":252,"feedbackIncorrect":30,"variant":198},"cs-quiz-fixes","Match each problem with the change that solved it.",[],"matching",[244,246,248,249],{"left":245,"right":157},"Requests got lost",{"left":247,"right":161},"Constant switching between tasks",{"left":73,"right":165},{"left":250,"right":153},"Nobody knew the status",[],"Each practice targeted a specific cause found during the diagnosis.",{"id":254,"type":255,"style":256,"spacing":257},"cs-separator","separator","diamonds","md",{"id":259,"type":44,"title":260,"description":261,"chapterNumber":30,"level":40,"style":16},"cs-lessons","Lessons learned","What other teams can take from this case",{"id":263,"type":264,"items":265,"multiple":50,"icon":275,"style":173,"firstOpen":19},"cs-faq","accordion",[266,269,272],{"title":267,"text":268},"What would the team do differently?","\u003Cp>Start measuring lead time before the changes. The first month of data was reconstructed from memory and email.\u003C\u002Fp>",{"title":270,"text":271},"Was there resistance?","\u003Cp>Yes — WIP limits felt like “doing less”. Showing the lead-time numbers after two weeks convinced the skeptics.\u003C\u002Fp>",{"title":273,"text":274},"Does this work for other teams?","\u003Cp>The principles — visible work, limited work in progress, frequent check-ins — work for any team with a flow of requests.\u003C\u002Fp>","chevron",{"id":277,"type":278,"columnsCount":12,"flip":90,"items":279,"frontBg":30,"frontColor":30,"backBg":30,"backColor":30},"cs-terms","flashcards",[280,283,286,289],{"frontTitle":281,"frontText":30,"frontImageUrl":30,"backTitle":30,"backText":282,"backImageUrl":30},"Lead time","Time from a request to its completion.",{"frontTitle":284,"frontText":30,"frontImageUrl":30,"backTitle":30,"backText":285,"backImageUrl":30},"WIP limit","The maximum number of tasks in progress at once.",{"frontTitle":287,"frontText":30,"frontImageUrl":30,"backTitle":30,"backText":288,"backImageUrl":30},"Bottleneck","The stage where work piles up and waits.",{"frontTitle":290,"frontText":30,"frontImageUrl":30,"backTitle":30,"backText":291,"backImageUrl":30},"Retrospective","A regular meeting to review how the team works and improve it.",{"id":293,"type":294,"text":295,"level":296,"alignment":39,"withAccent":19},"cs-takeaways","heading","Takeaways for your team","h3",{"id":298,"type":299,"style":300,"items":301},"cs-takeaways-list","list","ordered",[302,303,304,305],"Diagnose the flow of work before changing it","Make all work visible in one place","Limit work in progress to finish faster","Measure, then improve one thing at a time",{"id":307,"type":190,"question":308,"options":309,"selectionType":313,"pairs":314,"correctIndex":40,"correctIndexes":315,"explanation":316,"feedbackIncorrect":317,"variant":198},"cs-quiz-first-step","Your team is overloaded and misses deadlines. What is the best first step based on this case?",[310,311,312],"Hire two more people","Map how work flows and make it visible","Ask everyone to work faster","single",[],[],"Seeing the work comes first: it reveals where tasks wait and what to change.","More people or more pressure rarely help when the flow itself is broken.",{"id":319,"type":37,"text":320,"dropCap":50,"alignment":39,"columns":40,"fontSize":51},"cs-closing","\u003Cp>Every team has its own version of this story. Use this template to tell yours: describe the problem honestly, show the numbers and explain what you changed.\u003C\u002Fp>",1792666404466]