TMS vs ZBT Examples

Quantify based on TMS

This is your best way to quantify the productivity impacts of your decisions.

The TMS shows the differences between two ICs working on the same role, on similar tickets and highlights best practices, tools, tricks by your top performer (and sometimes by your bottom performer).

When you identify the root cause of why the TP outperforms the BP on a given step or set of steps, then you calculate the impact in seconds, then divide it by the bottom performer’s total execution time to get your impact.

Example:

See the following TMS:

Step	Top performer (sec)	Bottom performer (sec)
Step 1	8	13
Step 2	13	24
Step 3	6	6
Step 4	7	12
Total	34	55

If I realize the exact action why my top performer performs Step 2 so much faster, then I can quantify its impact:

Insight	Action	Impact
TP does Step2 faster, because he’s using pivot tables, while my Bottom performer writes a Query every time	Distribute demo of the TP creating the pivot tables to ICs and enforce the usage in Gemba Walks	20% = (24-13)/55

Frequency

When you create your impact analysis you have to think about whether your action is issue-specific, product-specific, task-type specific, or it can fix issues for every IC.

For example, in a coding team, where you can have a team of java, C#, python, C++ developers all in one group, you can’t just provide a tool for C# and claim that the full team’s productivity will increase because of it.

You either have to multiply your impact with the frequency (in this case 10%*0.25 = 2.5%) or provide a tool for every language if the issue exists for everyone.

Quantify based on ZBT

Once you’re done with your ZBT you should have the knowledge and experience to calculate the impact your decisions will have on the team room, by comparing the top performer's numbers to your own numbers.

A good practice is to do the same ticket in your ZBT as your top performer did in his TMS - this way you can have a clean comparison between the most ideal scenario and their work.

Example:

See the following TP TMS vs ZBT:

Step	Top performer (sec)	ZBT (sec)
Step 1	8	0
Step 2	13	13
Step 3	6	6
Step 4	7	3
Total	34	24

Let’s say Step 1 and Step 4 are administrative tasks that we’re eliminating / optimizing during ZBT.

We can calculate the impact by subtracting the new ZBT values from the TMS values (8-0+7-3) then dividing it by the top performer’s total TMS number (34), like:

Insight	Action	Impact
ICs waste 29% of their time with administrative tasks	Auto allocate tasks to ICs and move ticket automatically when they are done (3 seconds remain to create a subtask for review)	35% = (8-0+7-3)/34