Informa helps businesses and professionals in hundreds of ways.

Our international portfolio of live events, world-leading research publications, and innovative digital services provide specialists with the knowledge and connections they need to thrive.

HDI Service & Support World
April 25-29, 2027
Caesars PalaceLas Vegas, NV
Your KB Articles Have Too Many Notes

Want to make your knowledge base articles easier to read and your instructions easier to follow? Stop writing stuff like this:

  • Note: This is the default when this field is left empty.
  • Note: Do not start this process until you are sure you have enough time to do it in one sitting. Exiting out of the Duo Mobile setup without completing the other steps below may require you to call the Help Desk to unlock the account.
  • Note: If you do not have a Company Name or DBA, reenter your Business Legal Name in this field.

Enough! Take it easy on the Notes, please.


How Notes hurt KB articles

To make them predictable and easy to scan, KB articles have structure: clearly named sections, first-level and second-level headings, bulleted and numbered lists, etc. But when KB writers drop in a Note, these asides disrupt the article’s structure. For example, a Note on the second step in a four-step procedure probably could have been a fifth step. Or a Note in the article’s Resolution section is actually a workaround, which belongs in the Workaround section, of course.

“Note” is a nearly meaningless label for any piece of information. Unlike more specific labels, such as “Warning” or “Preparation,” the word “Note” doesn’t hint at the content of what will follow. All the label “Note” can convey is that the writer has the urge to tell the reader something. “Note” is a little like saying to the reader, “Look over here.” A Note can grab the reader’s attention, but it can’t do much to help the reader synthesize the info in the Note with the other info nearby.


4 kinds of damage done by Notes

  • Notes obscure action items. NC State University’s OIT Public Knowledge Base contains a short, five-step, 140-word KB article, “Connect to the NC State VPN.” But a Note in Step 5 is confusing: “Note: This is the default when this field is left empty.” Which is the default? And do I need to do anything? Do you mean, “This is the default when you leave the field empty?” or “Decide whether to keep or change the default?”
  • Notes obscure context. At 313,214 views to date, this “Initial Password Change” article is the most frequently viewed in OIT Public Knowledge Base. With that much attention, it had better be written well, and generally, it is. The article helps readers understand the process for setting up an NC State account, overall, and then provides specific sets of steps to complete each task. It has only one Note, which begins “Do not start this process until you are sure you have enough time to do it in one sitting…” That advice is context, and the “Set Up Duo Two-Factor Authentication” heading above the Note is clear enough that the word “Note” just isn’t necessary.
  • Notes allow sloppy thinking. The Institute for Public Procurement’s knowledge base contains an article titled “What is the most efficient way to pay for my membership?” I know the organization wants people to find this payment article easy to read! The article explains that paying online is easiest, but members can also pay by check or credit card. The very last sentence is a Note: “Only the Agency Representative may add or remove individuals from the organization's membership online during renewal.”This Note raises questions instead of answering them. Why are you telling me about removing members in an article about paying for membership? Is paying for an individual membership different from paying for an organization’s membership? Do I need to ask an Agency Representative to add me to my organization’s membership? I can’t tell whether this Note contains essential information or unrelated information. It’s the very definition of sloppy.
  • Notes make difficult content more difficult. Maryland has a knowledge base for eMaryland Marketplace Advantage (eMMA), the state’s official online procurement system. As you might imagine, the KB article “Start Your Vendor Registration, Part I (Vendor)” is complex. With this much info about vendor registration, they needed a Part 2! In fact, the Part 1 KB article is 1,900 words, has 21 screen shots and offers detailed instructions for the 15 steps required to start your vendor registration. That’s a lot. It also contains 16 Notes. The Overview section itself contains three Notes. When there are more Notes than steps, we know the KB has a problem. These writers are making readers work too hard.


3 better ways to handle Notes

  • Present the Note as an overview statement before the steps begin. Remove the label “Note” and just present the content. For example, the “Initial Password Change” article includes the H2, H3 and Note content (see screenshot, below). The label “Note” isn’t necessary. The two headings provide the logical structure to hold the information in the Note, which reminds the user to complete the process in one sitting.

Initial Account Setup Process

Set Up Duo Two-Factor Authentication

Note: Do not start this process until you are sure you have enough time to do it in one sitting. Exiting out of the Duo Mobile setup without completing the other steps below may require you to call the Help Desk to unlock the account.

  • Present the Note as one of the numbered steps. Duke University’s OIT knowledge base includes the article, “Dukeblue: Getting connected to Linux,” which presents more than eleven steps to getting connected. This Note appears before Step 1: “Make sure the machine is within range of an 802.11 AP that’s broadcasting the Dukeblue SSID.” That Note should be Step 1. Making sure the machine is within range is the first step of the task, not something to merely note before completing the task in earnest.
  • Replace the label “Note” with a more informative word. The audio technology manufacturer Shure has this article in its knowledge base: “MOTIV Mobile Apps: Best Practices for Recording and Livestreaming.” Near the end, the KB article includes a bit of specific advice for iOS 26 users. Instead of using the label “Note,” the writers chose a better label: “iOS 26 users.” This user-specific label helps more than “Note” partly because it frees non-iOS 26 users from having to read the content.

Try one of these labels instead of “Note”:

    • For Contractors
    • For Employees
    • Limitations
    • Options
    • Reminder
    • Version
    • Warning

Just like a fever that keeps your kid home from school, Notes are a symptom that your KB article is too ill to do its job. Notes allow logical clutter and distracting asides. Want healthy KB content? Find a home for each Note within the structure of the article.

Related news

Bridging the Gap: 5 Tips for Cross-Functional Collaboration That Enables AI Transformation

Ask ten executives who owns AI at their company, and you’ll get ten different answers. IT says it’s not their call. Legal gets blamed for slowing everything down. HR figures it’s someone else’s department. Meanwhile, teams are buying tools nobody signed off on, duplicating work and hoping it all sorts itself out. Sound familiar?

Lisa Duerre spent the last year studying why that happens. As part of an applied research project for her leadership consulting collective, RLD Group, she studied where AI adoption breaks down inside organizations, and where it works. The findings from RLD Group’s research helped inform a collaboration on the CONVERSATIONS WORTH HAVING®: The Human Accelerator for Artificial Intelligence Quick Start Guide, which is available as a digital download.

Duerre views organizations through what she calls an I–WE–US leadership framework, defined like this:

  • I: individual judgment and accountability

  • WE: workflows and cross-functional coordination

  • US: governance, decision rights and organizational measures

“All three levels are contributing to the breakdown or the alignment, whether people realize it or not,” Duerre says. “AI is amplifying whatever’s already true in your system. The teams that were disconnected before AI showed up are more disconnected now. The ones that talked to each other are moving faster, together.”

If your company is ready to collaborate better with AI tools, Duerre shared the following tips. Take a look.

Form a cross-functional AI committee

Duerre’s background is in HR, and she says most HR leaders assume AI ownership belongs to IT. It doesn’t, at least not exclusively.

“Ownership needs to sit at the system level,” Duerre says. “Each function carries a piece of it, based on what they do, how well they understand that part of the business and how their work depends on everyone else’s. AI is flattening how we work. You can’t just keep it in your own business unit anymore. You have to look all around you.”

For starters, she suggests building a cross-functional AI committee instead of having one department make all the AI decisions. Legal, IT, cybersecurity and HR should be on the committee, Duerre says.

“If you have a C in front of your title, you should be on that committee,” Duerre says. “That’s how I look at it, because it’s a system-level solution.”

During these meetings, Duerre says you’ll find out that some departments are racing ahead with AI and others are holding back.

“Both sides need to name the trade-offs aloud,” Duerre says. “With teams moving too cautiously, you have to talk about the opportunity cost of falling behind. With teams sprinting ahead, you have to ask them what happens if they don’t bring everyone else along with them.”

Figure out how to use AI strategically

Most companies spent the past two years telling employees to use AI with anything, without much strategy behind it. Duerre says that’s starting to catch up with organizations as finance teams scrutinize the cost.

Her rule of thumb: if you can’t articulate the goal and how you’ll measure success, don’t roll it out yet.

“Teams that use AI well have a strategy behind it,” Duerre says. “They’ve kicked the tires on what they’re trying to solve it for. You need to ask yourself, ‘Which business outcome are we trying to improve, and what must be aligned for AI to create measurable value?’”

Here are a few examples of how to use AI strategically:

  • A company could select a workflow that regularly creates delays, redesign it with AI and test the new approach. Then, measure whether it improves time, cost, quality or capacity.

  • Use AI to support early sales outreach and qualification across markets and languages. AI can help a business reach and assess more potential opportunities, while people remain responsible for understanding the customer and building trust.

  • Flag patterns in customer complaints across multiple channels with AI, so leadership can see recurring problems before it shows up in satisfaction scores.

Check-in regularly during an AI rollout

Duerre recommends a minimum weekly check-in during any AI rollout, sometimes daily depending on complexity. But the format matters more than the frequency. Status updates don’t cut it.

“Ask, ‘What are we learning and what are we surprised by?’ That’s a question that helps you with your check-ins, versus, ‘It’s in three products now and we’ve tested six,’” Duerre says. “That doesn't help, because you’re having these meetings to figure out what’s working and why. If you ask more strategic questions, you can move even faster.”

Publish AI guardrails

Employees who don’t know what’s allowed with AI will either freeze or go around the system entirely, Duerre says. She recommends publishing clear, specific guardrails on what’s okay and what’s not. Come up with some real examples, and pair them with an intake process that doesn’t require writing a thesis to get an approval for using it.

"The approval path should be lightweight, not bureaucratic,” Duerre says. “Something like, ‘If you’re going to use AI, here’s the path. And if it needs approval, here’s three or four quick questions for you to answer.’”

Take employee anxiety about AI seriously

“AI is just a tool” is a phrase Duerre hears at nearly every conference she attends, but she doesn’t buy it.

“Saying it’s a tool is underselling what’s happening at companies right now,” Duerre says. “AI is changing how we work. It’s changing how we lead teams.”

Duerre wants leaders to remember that a lot of employees are fearful of AI. Pew Research Center found 52% of U.S. workers are worried about the future impact of AI in the workplace.

Employees who feel AI is being “done to them,” instead of built alongside them are especially anxious, she says.

“Leaders need to recognize that anxiety is contagious,” Duerre says. “As a leader, this is your opportunity to show up as the safe, steady person who is showing what you’re learning with AI. And don’t be afraid to show how you’ve failed using AI, too.”

Duerre asks every executive she works with: “Who am I with AI?” and encourages them to pass this mindset question along to their employees, too.

“AI is now your teammate,” Duerre says. “Phrasing it as, ‘who am I with AI?’ is different than, ‘what’s going to happen to me with AI?’ You really want your team to feel empowered with AI and show them how it can help accelerate their career.”

Put these ideas into action

Rewiring your organization for AI requires more than the right tools. It takes shared language, practical frameworks, and a willingness to keep learning. Here are a few resources to help you take the next step.

  • Enterprise AI Playbook: Practical frameworks and executive discussion questions to help IT, HR, and business leaders align around AI that delivers measurable value.

  • Work-First AI Use Case Assessment: Identify the workflows where AI can have the greatest impact before you invest in new tools.

  • The REWIRED Brief: Get weekly insights, real-world case studies, and practical advice on leading AI transformation.