from [/inteltank/training-creation-toramaki by Sawachin](<a href="https://scrapbox.io/inteltank/training-creation-toramaki">https://scrapbox.io/inteltank/training-creation-toramaki</a> by Sawachin).
<ul>
<li>In <a href="/en/training%20content">training content</a>, it is better to use &quot;number of questions asked&quot; as a KPI rather than &quot;satisfaction at the end of the training&quot;.
 - <a href="/en/(degree%20of)%20satisfaction">(degree of) satisfaction</a> does not correlate with training outcomes
 - Even if participants are satisfied... it doesn&#39;t mean that they are &quot;growing in skills&quot; or &quot;knowledge&quot;.
 - Instead, by using satisfaction as a KPI, only a <a href="/en/sense%20of%20understanding">sense of understanding</a> is generated, and people who &quot;can&#39;t do it at all when they actually try it&quot; are created.
 - [People perceive uncomplicated things as easy to understand, so &quot;<a href="/en/easy-to-understand%20content">easy-to-understand content</a>&quot; often omits many &quot;necessary but difficult-to-understand elements&quot; to create an easy-to-understand story.
 - Too much is left out, and the result is only a sense of understanding.
 - Contents similar to &quot;/nishio/ <a href="/en/understanding">understanding</a>&quot; and others are described from various angles.</li>
</ul>
<a href="/en/number%20of%20questions">number of questions</a>.
<ul>
<li><a href="/en/Incorrect%20KPI%20setting">Incorrect KPI setting</a></li>
</ul>
<hr>
This page is auto-translated from <a href="https://scrapbox.io/nishio/%E3%82%8F%E3%81%8B%E3%81%A3%E3%81%9F%E6%84%9F">/nishio/わかった感</a> using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at <a href="https://twitter.com/nishio_en">@nishio_en</a>. I&#39;m very happy to spread my thought to non-Japanese readers.