tag:blogger.com,1999:blog-7108456.post7009154658071150489..comments2007-07-03T22:01:46.661-05:00Mark Grabanhttp://www.blogger.com/profile/07953086531083611251noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7108456.post-71385924959122625742007-06-01T10:52:00.000-05:002007-06-01T10:52:00.000-05:002007-06-01T10:52:00.000-05:00I looked over the book expecting to find more details about the process structure like the famous DNA aritcal outlines.<BR/>Gerrygerry.gateshttp://www.blogger.com/profile/13332009730684161589noreply@blogger.comtag:blogger.com,1999:blog-7108456.post-79074444973197322682007-05-30T08:42:00.000-05:002007-05-30T08:42:00.000-05:002007-05-30T08:42:00.000-05:00Mark,<BR/><BR/>Thanks for this thoughtful post. Being a TWI Zealot, I viewed my copy (got mine before Amazon!) as the biggest gift to the TWI community in decades. <BR/><BR/>Being a "heavy user" of TWI, particluarily Job Instruction, one question that often comes up is documentation. We are an ISO shop, and have developed many forms of documentation over the years. Many people rightfully view JI as "good tool, but yet another document".<BR/><BR/>We have been using the Job Breakdown Sheet as a standard work document (our work is not yet synchronized enough to do a combination table format). We use an 11x17 format that looks much like a Toyota Standardized Work Chart (work elements/key points on the left, work diagram on right).<BR/><BR/>The question that arises is that this format does not provide a complete description of the job. It only includes the steps and key points, which by definition are only the 10-20% of the job that really makes a difference for a quality, safe outcome.<BR/><BR/>People have suggested that we should also have a document that attempts to spell out the whole job. The idea being "someone can read it and do the job". My take is that we never really do that, and most people learn a job throught 1-on-1 training, which the JBS is designed to improve.<BR/><BR/>Either way, I'm interested in David's thoughts on this. How many documents would a typical Toyota job of moderate complexity, perhaps an internal engine assembly operation or die changeover task, have and what kind of information is contained in each? Some of this is included in the book, but I still lack the whole picture...<BR/><BR/>Thanks, JeffAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-7108456.post-53360271175816263152007-05-30T08:30:00.000-05:002007-05-30T08:30:00.000-05:002007-05-30T08:30:00.000-05:00Thanks for the synopsis on the book. Sounds really good. <BR/><BR/>As far as a question for the Podcast or a general question for Mr Meier, do they have a timeline for the Toyota Process and Toyota Problem Solving books?joe wnoreply@blogger.com