Takt Time and Transactional Processes

Six Sigma – iSixSigma Forums General Forums Methodology Takt Time and Transactional Processes

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #54716

    Samantha Waytowich

    A question related to using takt time in transactional value stream maps….

    What is the best approach for calculating the takt time? Since most transactional processes do not take up a entire persons work day, do you simply take a percentage of a total work day (i.e. I work 25% on reviewing resumes each day)? What if there are multiple contributors in the value stream working different percentages of their total work day on the process?

    I am interested in hearing how others handle this.



    Don Strayer

    Before I look at Takt time I do a Time Value Map. This is simply a time line that shows how long each step takes and the intervening wait times. Value added steps are above the line and non value added beneath. A TVM illustrates where, and how much, time is wasted. This is useful in itself. Creating one requires the data needed to put a number on Takt. In cases such as yours where time spent on each step is highly variable I do typical, best case, and worst case TVMs for comparison and then do a PERT calculation.




    Takt time is nothing but customer requirement time, its no way related to how many type of job you need to do in a day. Suppose you take 25% of each day i.e. 25% of 8Hrs you take to reviewing resumes and in that time suppose you can review maximum 4 resumes that TAKT time is not = 2hrs / 4 = 30minute, But this is the cycle time of your reviewing the job.
    But if your management can spare you maximum one working day for review and on average you have 8 resume / day to review than TAKT time for this job is 8hrs/8 = 1Hrs, but as your cycle time for this job is less than the TAKT time then you need not do anything, but if you can review only 2 resumes in 25% of your day then you cycle time = 1 hr then you may get problem due to some other delays. So you need to plan some kaizen to reduce the cycle time.



    Takt is available work time divided by average demand, so if someone works in multiple value streams (which in common in transactional work), simply determine what time is available (ie 25% of an 8 hr day is 2 hrs) to get your AWT for that value stream. Note: you want to isolate variability before you minimize it by segmenting the work into product families…one takt per value stream and one value stream per product family…good luck.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.