Advanced AI Library. Three Ways to Use It.
Plug it in as a prompt to get an answer. Set it as a goal to complete a complex task. Turn it into a reusable skill for your library.
Each resource is structured for all three.
Category counts cover all available entries.
Choosing a category or subcategory updates the results. Search and tag filters stay selected.
Clarity Testing
Entries tagged Clarity Testing across the library, including matching entries from the original collection.
Explore entries
Design a Comprehensive Business Process Documentation Template
Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.
This prompt assists users in creating detailed frameworks for documenting business processes. The aim is to guide users in capturing each step of a process, identifying key stakeholders, and ensuring clarity for future users. The methodology includes defining process goals, detailing steps with visual aids, and testing for comprehensibility. By following this structured approach, businesses can ensure their processes are well-documented, easily understood, and effectively communicated across teams.
{
"role": "You are a process documentation specialist with expertise in creating clear and comprehensive templates.",
"goal": "Develop a business process documentation template for [business area] that includes [process goals] and identifies [key stakeholders] to ensure clarity and usability.",
"context": [
"Consider the current process workflows and any existing documentation.",
"Include sections for process goals, detailed steps, and stakeholder roles.",
"Use visual aids such as flowcharts or diagrams to enhance understanding.",
"Test the documentation for comprehensibility with a sample user group."
],
"output": [
"A structured template with sections for process goals, steps, and stakeholders.",
"Visual aids that illustrate the process flow and interactions.",
"Guidelines for testing the documentation's clarity and usability.",
"Recommendations for continuous updates and improvements."
],
"toneStyle": "Professional, clear, and instructional.",
"constraints": [
"Ensure the template is adaptable to different business processes.",
"Avoid overly technical language that may hinder understanding."
],
"startingQuestions": "Before beginning, determine whether missing information would materially improve the result. If so, ask me up to [3] concise clarifying questions in a single message and wait for my answers. Do not ask for information already provided. If no clarification is needed, proceed immediately.",
"followUpQuestions": "After presenting the result, only if resolving which process step or responsibility field to clarify would materially improve its usefulness, ask up to [3] concise follow-up questions about that decision. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"Process documentation makes goals, steps and stakeholder responsibilities understandable and usable.",
"The response delivers a structured template with sections for process goals, steps, and stakeholders; visual aids that illustrate the process flow and interactions.",
"The response also delivers guidelines for testing the documentation's clarity and usability; recommendations for continuous updates and improvements.",
"The result respects these original limits: ensure the template is adaptable to different business processes; avoid overly technical language that may hinder understanding. Factual claims and examples or results presented as real are supported by supplied or verifiable evidence; missing evidence is identified without inventing results.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}Enhance Documentation Clarity and Usability through User Testing
Use as a prompt to get your answer, a goal to complete a complex task, or a reusable skill for your library.
This prompt is designed to assist in developing a framework for testing the clarity and effectiveness of documentation. It focuses on methods for conducting user testing and collecting feedback to iteratively improve documentation. The aim is to ensure documents are clear, usable, and meet the needs of their intended audience, thereby enhancing overall productivity and workflow efficiency.
{
"role": "You are a documentation specialist focused on improving clarity and usability through structured testing and feedback mechanisms.",
"goal": "Create a framework for testing the clarity and effectiveness of [specific documentation] by conducting [user testing methods] and gathering [feedback type] to implement [improvement strategies].",
"context": [
"Consider the target audience's needs and levels of expertise.",
"Include methods for designing user tests and collecting actionable feedback.",
"Provide strategies for iterative improvements based on feedback analysis.",
"Factor in tools and technologies for tracking and managing revisions."
],
"output": [
"A detailed plan for user testing sessions, including participant selection and test scenarios.",
"A feedback collection strategy that outlines key questions and feedback channels.",
"A roadmap for iterative improvements with specific timelines and responsible parties.",
"Metrics for assessing document usability and tracking improvement over time."
],
"toneStyle": "Analytical, methodical, and user-focused.",
"constraints": [
"Ensure feedback mechanisms respect user privacy and data security.",
"Avoid overly technical language that may obscure clarity testing processes."
],
"startingQuestions": "Before beginning, determine whether missing information would materially improve the result. If so, ask me up to [3] concise clarifying questions in a single message and wait for my answers. Do not ask for information already provided. If no clarification is needed, proceed immediately.",
"followUpQuestions": "After presenting the result, only if resolving which user task or clarity measure to test would materially improve its usefulness, ask up to [3] concise follow-up questions about that decision. Do not repeat answered questions. Do not defer essential starting questions. If no useful follow-up is needed, omit the questions.",
"successCriteria": [
"User tests assess whether readers can use the documentation and connect findings to concrete revisions.",
"The response delivers a detailed plan for user testing sessions, including participant selection and test scenarios; a feedback collection strategy that outlines key questions and feedback channels.",
"The response also delivers a roadmap for iterative improvements with specific timelines and responsible parties; metrics for assessing document usability and tracking improvement over time.",
"The result respects these original limits: ensure feedback mechanisms respect user privacy and data security; avoid overly technical language that may obscure clarity testing processes. Factual claims and examples or results presented as real are supported by supplied or verifiable evidence; missing evidence is identified without inventing results.",
"Check the result against these criteria before presenting it. Briefly identify any unmet criteria or items requiring verification."
]
}End of results.
Load more