<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Generative AI</title>
    <link>https://ux.byu.edu/generative-ai</link>
    <description>Generative AI</description>
    <language>en-US</language>
    <lastBuildDate>Wed, 08 Apr 2026 19:12:25 GMT</lastBuildDate>
    <atom:link href="https://ux.byu.edu/generative-ai.rss" type="application/rss+xml" rel="self" />
    <item>
      <title>Technical Writing and AI Integration</title>
      <link>https://ux.byu.edu/technical-writing-and-ai-integration</link>
      <description>How AI Can Accelerate Drafting and Revision While Remaining a Collaborative Tool</description>
      <pubDate>Wed, 08 Apr 2026 19:12:25 GMT</pubDate>
      <author>Madeline Bryan</author>
      <guid>https://ux.byu.edu/technical-writing-and-ai-integration</guid>
      <content:encoded><![CDATA[<html lang="en">                    <head>                <meta charset="utf-8">                <meta property="op:markup_version" content="v1.0">                                    <link rel="canonical" href="https://ux.byu.edu/technical-writing-and-ai-integration">                                <meta property="fb:article_style" content="default">            </head>                            <body>                <article>                    <header>                                                                            <h1>Technical Writing and AI Integration</h1>                                                                            <h3 class="op-kicker">Technical Writing,Featured Articles,Generative AI</h3>                                                                            <address>    <a rel="author" href="https://ux.byu.edu/madeline-bryan">        Madeline Bryan    </a></address>                                                                            <time class="op-published" dateTime="April 08, 01:12 PM">April 08, 01:12 PM</time>                                                                            <time class="op-modified" dateTime="April 08, 01:42 PM">April 08, 01:42 PM</time>                                            </header>                    <figure> <img src="https://brightspotcdn.byu.edu/46/22/5495b658492e83f1279b37794b9b/technicalwriting-and-ai.png"></figure><p>The integration of AI into technical writing workflows can accelerate the drafting and revision process and serve as a powerful collaborative resource for technical writers. Visit the article <a href="https://ux.byu.edu/this-is-a-test">Technical Writing and UX Writing</a> for additional information.</p>What Can AI Do for Technical Writing?<p>AI is best understood as a drafting and analysis tool, not as an authoritative source. Some of the relevant features of AI include:</p><p><b>Draft generation</b>generating ideas and phrasing</p><p><b>Content adaptation</b>summarizing and rewriting existing information</p><p><b>Revision and clarity</b>refining documentation to improve accuracy and readability for specific audiences</p><p><b>Organization</b>generating outlines and structuring content</p><p>While AI is efficient at supporting content development, it cannot replace human technical writers. Human review remains essential for technical accuracy, context, and effective prompt engineering.</p>What is Prompt Engineering?<p>Prompt engineering is the process of crafting prompts that guide an AI systems output. The quality of an AI-generated response depends heavily on the specificity and clarity of the provided prompt. Technical writers provide relevant context and clear information when instructing the AI model to ensure that the output aligns with the documentation goals.</p><p>Example of poor Prompt Engineering:</p> Can you make this&nbsp;document&nbsp;better?&nbsp;<p>Example of effective Prompt Engineering:</p> Draft an updated version of this&nbsp;article on&nbsp;UX design&nbsp;and technical writing for our university&nbsp;website. Use clear,&nbsp;concise&nbsp;language.&nbsp;Explain how&nbsp;the two fields&nbsp;overlap&nbsp;and&nbsp;provide&nbsp;relevant examples in your explanation.&nbsp;Provide context for readers&nbsp;who&nbsp;are unfamiliar with either discipline.&nbsp;Use active voice and adhere to the Chicago Manual of Style.&nbsp;When Should Technical Writers Avoid Using AI?<p>While AI is a useful resource in technical writing, it should be approached as a conditional tool. Technical writers must assess when AI assistance is appropriate for their specific project. AI outputs can contain inaccurate or misleading information and should not be employed as the primary source for research. AI models often do not guarantee data privacy and should be avoided for projects that contain confidential or sensitive information.</p>Best Practices for Responsible AI Use in Technical Writing<p>Responsible AI use means understanding where human judgement remains essential. By applying clear guidelines, technical writers can leverage AI to improve efficiency and clarity without compromising quality in their writing. Some of the best practices include:</p> Verify all facts, figures, and technical details against authoritative sources&nbsp; Ensure documentation&nbsp;remains&nbsp;user-centered&nbsp; Use only company-approved AI tools and follow internal data-handling policies&nbsp; Evaluate AI outputs for bias, clarity, and inclusiveness&nbsp; Be transparent internally about AI use&nbsp;<p>Through the integration of AI as a collaborative tool in technical writing, technical writers can enhance efficiency and accelerate faster content development while retaining responsibility for accuracy, clarity, and user impact.</p>                                    </article>            <script src="https://brightspotcdn.byu.edu/resource/00000173-da06-d043-a7ff-dece7d790000/_resource/brightspot/analytics/search/SiteSearchAnalytics.5eb1a8a326b06970c71b3a253fbeaa64.gz.js" data-bsp-contentid="0000019d-6e9c-d1a0-a7fd-7f9e55a60000"></script></body>            </html>]]></content:encoded>
    </item>
  </channel>
</rss>
