Introduction
JCMI produces machines that are complemented with user-manuals dense in jargon. I remember reading through a few hundred pages and finding the need to frequently consult a glossary for contextualizing the concepts.
Some JCMI buyers may be equipped with engineers in their teams who are comfortable with such environments; however, it is not reasonable to generalize this assumption to every client.
I found that the technical debt among certain clients is substantial and seldom alarming. I recall a few instances where my supervisor would be called and asked for clarity in something I did not see the need for; connecting ethernet switches and keeping light-sensitive components in the dark are aspects covered in great detail within the manuals. Given that our clients could benefit from the contents in them, my supervisor would save a great deal of his time at work.
After analyzing our manuals with a lens of undoing the curse of knowledge I seemed to have fallen prey to, I reached out to some clients who built up a rich history in call logs with my supervisor. A simple bridge in semantics between these individuals and manuals seemed to be a trivial solution with lasting impacts; this was my journey with iRAG at JCMI.