GUIDE Framework: Goal-Oriented User-Intent Driven Execution

A user-centric framework for creating detailed prompts that maintain focus on end objectives while adapting to user needs

Task ExecutionIntermediate

GUIDE

Framework Structure

The key components of the GUIDE Framework framework

Goal: What is the ultimate objective or purpose?
User: Who is the target audience and what are their needs?
Information: What context, data, or background is needed?
Directions: What specific steps or actions are required?
Evaluation: How will success be measured or feedback incorporated?

Core Example Prompt

A practical template following the GUIDE Framework structure

Example Prompt

Create a tutorial for our app. The goal is to increase new user activation by 40%. Our users are mostly seniors with limited tech experience who need accessibility features. For context, our onboarding surveys show navigation is the biggest pain point. Provide step-by-step instructions with large, high-contrast screenshots for each action. Success will be measured by reduced support tickets and increased feature adoption rates.

Usage Tips

Best practices for applying the GUIDE Framework framework

✓Start with a clear, measurable goal that defines what success looks like
✓Be specific about user characteristics, pain points, and preferences
✓Include only relevant contextual information that impacts the output
✓Break down directions into sequential, actionable steps
✓Define concrete evaluation criteria to judge effectiveness

Detailed Breakdown

In-depth explanation of the framework components

## TASK 1: SETTING UP YOUR PROFILE (5 simple steps)

### Step 1: Enter Your Basic Information

!Profile screen with Name, Date of Birth, and Phone fields highlighted with

bright yellow circles

Type your name and phone number in the highlighted boxes. Your date of birth

helps us provide age-appropriate health information.

TIP: Fields marked with a red asterisk () must be completed. All other

fields are optional.*

### Step 2: Set Your Text Size

!Accessibility button highlighted at top right of

screen

Tap the "Text Size" button in the top corner. Choose "Large" or "Extra Large"

if you prefer bigger text.

TIP: You can say "Make text larger" for hands-free adjustment.

### Step 3: Add Emergency Contact (Optional)

!Emergency contact section with "Add Contact" button

highlighted

This step is optional but recommended. Tap "Add Contact" to select someone

from your phone contacts who should be notified in emergencies.

*NOTE: Your emergency contact will never have access to your medication

information unless you specifically grant permission.*

### Step 4: Set Reminder Preferences

!Notification preferences with sound and vibration options

highlighted

Choose how you want to receive medication reminders. We recommend enabling

both sound and vibration for important alerts.

### Step 5: Save Your Profile

!Large "Save Profile" button at bottom of screen highlighted in

green

Tap the large green "Save Profile" button at the bottom of your screen. Your

information is now securely stored.

*PRIVACY NOTE: All your personal information is encrypted and never shared

with third parties.*

[PROGRESS: Profile Complete - 50%]

## TASK 2: TRACKING YOUR FIRST MEDICATION (5 simple steps)

### Step 1: Open the Medications Screen

!Home screen with "My Medications" button

highlighted

Tap the "My Medications" button on your home screen. This is where you'll

manage all your prescriptions.

### Step 2: Add a New Medication

!Large "+" button highlighted in medication screen

Tap the large "+" button to add your first medication.

*TIP: You can also say "Add a new medication" if you prefer using voice

commands.*

### Step 3: Enter Medication Details

!Medication name and dosage fields highlighted

Type the name of your medication and the dosage. If you're unsure about

spelling, use the search icon to find your medication in our database.

*TIP: You can tap the camera icon to scan your prescription bottle instead of

typing.*

### Step 4: Set Your Schedule

!Schedule section with time selector and frequency options

highlighted

Choose how often you take this medication and at what times. Tap "Add Time" if

you take this medication multiple times per day.

### Step 5: Save Your Medication

!Large "Save Medication" button highlighted at bottom of

screen

Tap the large "Save Medication" button. Your first medication is now set up

with reminders!

SUCCESS! You've completed the essential setup of MediRemind.

[PROGRESS: Setup Complete - 100%]

## QUICK REFERENCE GUIDE

• To add more medications: Tap "My Medications" then the "+" button

• To edit a medication: Tap on its name, then "Edit"

• To mark a dose as taken: Tap "Taken" when you receive a reminder

• To view reports: Tap "Reports" on the bottom menu

• To change text size: Tap the "Aa" icon in the top corner

• To use voice commands: Tap the microphone icon or say "Hey MediRemind"

## NEED HELP?

• Tap "Help" on any screen

• Call our Senior Support Line: 1-800-MED-HELP (toll-free)

• Email: support@mediremind.com

We'd love to know if this tutorial was helpful! Please tap a star below to

rate your experience:

[1] [2] [3] [4] [5]

Thank you for choosing MediRemind to help manage your health!

lastUpdated: '2025-11-05'

G.U.I.D.E. Framework

The G.U.I.D.E. framework (Goal, User, Information, Directions, Evaluation) provides a comprehensive structure for crafting effective prompts by focusing on end objectives, understanding audience needs, providing relevant context, outlining clear instructions, and establishing success metrics. The evaluation component reflects testing practices recommended in Anthropic's prompt design documentation.

Introduction

The G.U.I.D.E. Framework (Goal, User, Information, Directions, Evaluation) is a comprehensive approach to prompt engineering that maintains unwavering focus on outcomes while adapting to user needs. This framework excels at creating detailed, actionable prompts that drive successful execution of complex tasks with specific objectives.

Unlike frameworks that focus primarily on the content structure or creation process, G.U.I.D.E. takes a holistic, user-centric approach to prompt engineering. It ensures that every aspect of the prompt, from the overarching objective to success measurement, aligns with both the desired outcome and the needs of those who will engage with the content.

The G.U.I.D.E. framework produces outputs that are:

Purpose-Driven – Aligned with specific, measurable objectives
User-Centered – Tailored to audience needs, preferences, and pain points
Context-Informed – Grounded in relevant background information and data
Action-Oriented – Built around clear, executable instructions
Results-Focused – Designed with concrete success criteria

This framework is particularly valuable when:

Tasks have specific performance targets or measurable outcomes
Outputs need to serve well-defined audience segments
Background information significantly impacts execution approach
Detailed, sequential instructions are required
Success measurement is critical for evaluation or iteration

The G.U.I.D.E. framework can be applied to virtually any content creation task but is especially powerful for:

User tutorials and educational content
Process documentation and standard operating procedures
Task-oriented marketing materials
User experience design
Project requirements and specifications

By systematically addressing all five components, the G.U.I.D.E. framework transforms general requests into comprehensive, outcome-focused prompts that drive successful execution.

G.U.I.D.E. Framework Structure

1. Goal

What is the ultimate objective or purpose?

The Goal component establishes the specific, measurable objective the output should achieve. This goes beyond simply describing what type of content to create. It articulates the concrete purpose or outcome the content should accomplish.

Good examples:

"Create a step-by-step onboarding guide that reduces new user abandonment rate from 45% to under 20% and increases feature discovery by helping users complete their first project within 10 minutes of signing up."
"Develop an implementation plan that will enable our team to migrate 5,000 customer accounts to our new platform with zero data loss and less than 2 hours of total downtime, all within a 6-week timeframe."
"Design a customer feedback survey that achieves a 30%+ completion rate and provides actionable data on our three key product challenges: usability, performance, and integration capabilities."

Bad examples:

"Create a user guide" (lacks specific objective and measurable outcome)
"Make a migration plan" (doesn't specify what success looks like)
"Design a customer survey" (missing the purpose and intended outcome)
"Increase sales" (too broad without specific targets or mechanisms)

2. User

Who is the target audience and what are their needs?

The User component defines the specific audience for the output, including their characteristics, needs, pain points, preferences, and context of use. This ensures the content is appropriately tailored to those who will engage with it.

Good examples:

"Our target users are financial advisors (average age 45-60) who are technically proficient with desktop software but struggle with mobile applications. They operate under strict compliance requirements, have limited time for learning new systems (15 minutes max per session), and primarily value efficiency and accuracy over aesthetic design. Their key frustration with our current system is the complexity of client data entry."
"This documentation is for junior developers (0-2 years experience) who are new to our codebase and tech stack. Most have CS degrees but limited professional experience with microservices architecture. They report feeling overwhelmed by our current documentation and struggle to find contextual connections between different services. They prefer learning through examples and interactive elements over abstract explanations."
"The audience for this campaign consists of urban parents (80% mothers, ages 28-42) of children under 5, who prioritize organic food options but are price-sensitive. They're primarily smartphone users who shop online at least weekly and engage with social media daily (primarily Instagram and Facebook). Their key barriers to purchase are concerns about freshness and delivery reliability."

Bad examples:

"For our users" (too vague to guide content creation)
"For beginners" (lacks specific characteristics and needs)
"For everyone" (fails to prioritize specific audience segments)
"For tech-savvy people" (insufficient detail about specific needs and context)

3. Information

What context, data, or background is needed?

The Information component provides the essential context, background data, constraints, and relevant facts needed to properly execute the task. This ensures the output is built on accurate information and appropriate context.

Good examples:

"Our current checkout process has a 67% abandonment rate, with analytics showing that 80% of abandonments occur at the shipping cost screen. User testing reveals confusion about delivery options and unexpected costs are the primary friction points. Our competitors offer free shipping with a $35 minimum order, while our threshold is $50. We've recently upgraded our logistics system to support more flexible delivery options, but haven't updated the UI to reflect these capabilities."
"Your task requires understanding of our recent reorganization which merged the product and engineering teams under one leadership structure. Previous documentation was created when teams operated independently, which has led to communication gaps. Current approval workflows require sign-off from both product managers and engineering leads, which wasn't necessary before. Team surveys indicate frustration with redundant approvals and unclear decision authority."
"The market research for this task includes three key insights: 1) 72% of our target audience has switched to competitors in the past 18 months due to perceived technological advantages; 2) Price sensitivity is low when features clearly address productivity pain points; 3) Integration with existing tools ranks as the #1 purchase consideration. Our current positioning overemphasizes cost savings rather than productivity benefits and innovation."

Bad examples:

"It's for our website" (lacks specific contextual information)
"We need this ASAP" (only provides urgency without relevant background)
"Make it better than what we have now" (subjective without specific improvement areas)
"Similar to the last one we did" (assumes knowledge without providing context)

4. Directions

What specific steps or actions are required?

The Directions component outlines the specific steps, instructions, requirements, and specifications needed to execute the task successfully. This ensures clarity about exactly what should be done and how it should be structured or formatted.

Good examples:

"Create an email sequence with 5 messages to be sent over 14 days. Each email should be 250-350 words with a single clear CTA. Follow this structure for each: 1) Personalized greeting using first name; 2) Problem statement with emotional hook; 3) Solution introduction with one key benefit; 4) Social proof element (customer quote or statistic); 5) Clear next step with button CTA; 6) Simple signature with name and title. The sequence should progressively introduce our three core features while addressing key objections of cost, implementation time, and team adoption."
"Develop a 10-page technical whitepaper with these specifications: Executive summary (1 page), problem overview (2 pages), solution approach (3 pages), implementation requirements (2 pages), case study (1 page), and next steps (1 page). Include at least 5 original diagrams illustrating key concepts. All technical claims must be supported by either our internal data or cited industry research. Use our approved technical terminology throughout (terminology guide attached). Format for both digital (interactive PDF with navigation) and print (high-resolution export with appropriate margins)."
"Create an onboarding workflow that guides new users through 4 key actions: account setup, team invitation, first project creation, and feature tour. Each step should offer both a quick path (essential fields only) and detailed option (full customization). Include progress indicators, clear next/back navigation, and allow users to skip steps with a reminder system to complete later. Incorporate micro-animations for completion success and contextual help tooltips for complex fields. Design for both desktop and mobile interfaces with appropriate interaction patterns for each."

Bad examples:

"Just make it good" (subjective without specific requirements)
"Follow best practices" (vague without specifying which practices apply)
"Keep it simple" (lacks clear direction about actual content and structure)
"Do whatever you think is best" (abdicates specification responsibility)

5. Evaluation

How will success be measured or feedback incorporated?

The Evaluation component establishes clear success criteria, feedback mechanisms, and measurement approaches to determine if the output achieves its intended goal. This ensures accountability and enables continuous improvement.

Good examples:

"Success will be measured through these key metrics: 1) Increase in trial conversion rate from current 12% to target 20% within 60 days; 2) Reduction in support tickets related to setup questions by 35%; 3) Improvement in first-time user task completion rate from 60% to 85%; 4) User satisfaction scores of 4.5/5 or higher from post-onboarding surveys. We'll conduct A/B testing with a 25% sample of new users before full implementation and iterate based on quantitative performance and qualitative feedback from exit surveys of users who don't complete the process."
"The documentation will be evaluated through a combination of: 1) Usability testing with 12 developers across experience levels with specific tasks to complete using only the documentation; 2) Completion time comparison against our benchmark tasks; 3) Accuracy of implementation based on predefined correctness criteria; 4) Developer confidence ratings before and after using the documentation; 5) A 30-day and 90-day follow-up assessment to measure knowledge retention and continued reference value. Success requires meeting our threshold scores in all five dimensions."
"Campaign effectiveness will be judged on these KPIs: 1) Email open rate exceeding industry benchmark by 10 percentage points; 2) CTR of 4.5%+ on primary campaign CTAs; 3) Conversion rate to product demo requests of at least 2.5%; 4) Attribution of $250K+ in pipeline within 90 days; 5) Reduction in average sales cycle for engaged prospects by 20% compared to control group. We'll implement tracking parameters for all digital touchpoints and conduct in-depth analysis of the customer journey to identify high-performing elements for future optimization."

Bad examples:

"We'll know it when we see it" (subjective without defined criteria)
"If people like it" (lacks measurable success metrics)
"If it looks good" (aesthetic focus without functional success criteria)
"If it's better than what we have now" (comparative without specific benchmarks)

Example Prompts Using the G.U.I.D.E. Framework

Example 1: User Documentation

Prompt:

markdown

Goal: Create a comprehensive user manual for our project management software that reduces onboarding time from 2 weeks to 5 days, decreases support ticket volume by 30%, and enables users to successfully complete their first project within 48 hours of installation.

User: Our primary users are small business owners and project managers in companies with 5-50 employees. They have moderate technical proficiency but limited time for learning new systems (averaging 20-30 minutes per day for training). They're typically juggling multiple responsibilities, value efficiency over comprehensive feature knowledge, and prefer visual learning with practical examples. Their top pain points with previous solutions include complexity of initial setup, difficulty assigning and tracking team tasks, and challenges with reporting capabilities.

Information:
- Our software includes 5 core modules: Dashboard, Projects, Tasks, Team Management, and Reports
- Data shows 72% of new users fail to properly configure project templates, leading to inefficient workflows later
- User testing indicates confusion about the difference between project-level and task-level permissions
- Key competitive advantage is our automated workflow system, but it's the least-discovered feature (only 14% of users implement within first month)
- Most frequent support tickets involve: report generation (32%), user permission settings (27%), and integration with third-party tools (19%)
- Software was recently updated with AI-assisted features that significantly reduce manual work, but require initial setup
- Most users access via desktop (78%) with occasional mobile use (22%)

Directions:
- Create a modular manual with clear section dividers and a comprehensive table of contents
- Begin with a "Quick Start Guide" limited to 5 pages that covers only essential functions to create and manage a basic project
- For each feature, include: purpose, step-by-step instructions, at least one screenshot with annotated UI elements, common use cases, and troubleshooting tips
- Organize information hierarchically: core functions first, followed by advanced features
- Include a "Best Practices" section showing real-world examples from different industries
- Create a glossary of terms that clarifies technical language and unique system terminology
- Add "Pro Tips" callout boxes highlighting efficiency shortcuts and power-user features
- Include step-by-step tutorials for the 10 most common workflows (identified from user data)
- Ensure all instructions follow the format: action, location, result (e.g., "Click the '+' button [action] in the top right corner of the Projects tab [location] to create a new project [result]")

Evaluation:
- Test documentation with 3 user groups: complete novices, those familiar with competing products, and existing users upgrading from our previous version
- Measure task completion rates and time-to-completion for 15 essential workflows using only the documentation as a guide
- Success requires: 90%+ task completion rate, 40%+ reduction in time-to-first-project, and user satisfaction ratings of at least 8/10
- Collect feedback through embedded survey links in digital version with specific questions about clarity, completeness, and usefulness
- Track which manual sections correlate with reduced support tickets to verify effectiveness
- Implement quarterly reviews and updates based on usage data, support trends, and user feedback

G.U.I.D.E. Breakdown:

Goal: Create user manual that reduces onboarding time, decreases support tickets, and enables quick project completion
User: Small business owners and project managers with moderate technical skills but limited time, specific pain points
Information: Software modules, user behavior data, pain points, competitive advantages, support ticket patterns
Directions: Modular manual structure, formatting requirements, content organization, specific elements to include
Evaluation: Testing methodology, success metrics, feedback mechanisms, ongoing improvement process

Example 2: Marketing Campaign

Prompt:

markdown

Goal: Create a multi-channel marketing campaign for our premium coffee subscription service that increases new subscribers by 40% (approx. 2,000 new customers) over 60 days, improves conversion rate from 2.3% to 3.5%+, and raises average subscription value from $32 to $40+ per month through successful upselling of our specialty bean offerings.

User: Our target customers are urban professionals, ages 28-45, with household incomes above $85,000, who consider themselves coffee enthusiasts rather than casual drinkers. They value quality, sustainability, and convenience, and are willing to pay premium prices for superior products. They're digitally savvy, primarily use mobile devices for browsing (72%) and purchasing (68%), and research shows they typically consume content in short sessions throughout the day rather than long dedicated periods. They're motivated by discovering unique flavors, the story behind their products, and membership in exclusive communities. Their key barriers to purchase include concerns about freshness, uncertainty about receiving varieties they won't enjoy, and reluctance to commit to recurring payments.

Information:
- Our subscription offers 3 tiers: Starter ($25/mo), Enthusiast ($38/mo), and Connoisseur ($58/mo)
- Customer data shows highest satisfaction and retention (92%) among Enthusiast tier subscribers
- We've recently secured exclusive arrangements with 3 award-winning small-batch roasters
- Market research shows our target audience follows similar subscription models for wine, meal kits, and fashion
- Competitor analysis reveals most competing services focus on convenience rather than education and discovery
- Our Net Promoter Score is 72, with customers specifically praising our variety, freshness, and education materials
- Previous campaigns that emphasized storytelling and producer connections outperformed discount-focused marketing by 3.5x
- We offer a satisfaction guarantee with free replacement of any beans customers don't enjoy

Directions:
- Develop campaign creative around the theme "Beyond the Bean: A Journey of Discovery"
- Create assets for these channels: email (drip sequence), Instagram (feed and stories), Facebook (including targeted ads), YouTube (30-second spots), and podcast spots (60-second reads)
- Design a campaign landing page with: tiered subscription comparison, flavor profile quiz, success stories, and FAQ addressing main purchase barriers
- Email sequence should include 5 touchpoints: introduction, educational content, social proof, special offer, and final reminder
- All visuals should follow our updated brand guidelines with emphasis on rich browns, earthy greens, and our new hand-drawn illustration style
- Messaging hierarchy: 1) Exclusive varieties not available elsewhere, 2) Educational journey and flavor discovery, 3) Convenience and flexibility, 4) Sustainability and producer relationships
- Include at least 3 customer testimonials focusing on discovery of new favorites
- Use "first bag free" offer with 3-month minimum subscription as primary CTA
- Create segmented approaches for: complete coffee novices, those dissatisfied with grocery store options, and serious enthusiasts seeking unique varieties
- Implement retargeting strategy for cart abandoners with secondary offer of free brewing guide

Evaluation:
- Primary KPIs: new subscriber acquisition, conversion rate, average subscription value, and 90-day retention rate
- Secondary metrics: site visit duration, quiz completion rate, social engagement rate, and email open/click rates
- A/B test at least 3 variations of key campaign elements: headlines, primary imagery, and CTA language
- Implement attribution tracking across all channels to identify highest-performing touchpoints
- Set up conversion tracking by entry point to optimize channel investment mid-campaign
- Conduct post-purchase surveys to identify most compelling aspects of messaging
- Analyze tier selection and upsell acceptance rates to refine value proposition
- Measure long-term retention cohort analysis comparing campaign-acquired customers vs. previous acquisition methods

G.U.I.D.E. Breakdown:

Goal: Increase new subscribers, improve conversion rate, raise average subscription value through upselling
User: Urban professionals with specific demographics, values, behaviors, motivations, and purchase barriers
Information: Subscription tiers, customer data, market research, competitive analysis, previous campaign performance
Directions: Campaign theme, channel specifications, messaging hierarchy, visual guidelines, CTA strategy
Evaluation: Primary and secondary KPIs, testing methodology, attribution tracking, post-purchase analysis

Example 3: Product Development

Prompt:

markdown

Goal: Design a new feature for our project management application that increases team collaboration by enabling real-time document co-editing. Success metrics include: 50%+ of teams actively using co-editing within 90 days of release, 30% reduction in time spent switching between our app and external editing tools, and 25%+ improvement in user satisfaction scores related to team collaboration.

User: Our application is used by cross-functional teams of 5-25 people across marketing, product, design, and development departments. Team members have varying levels of technical proficiency, with approximately 30% considering themselves "power users" and 25% describing themselves as "technically challenged." They primarily work on desktop devices (92%) during standard business hours, though 40% report some evening/weekend usage. Their primary pain points include: having to switch between multiple tools to collaborate on documents, lack of context when reviewing others' work, version control issues when multiple people contribute to documents, and difficulty tracking feedback and approvals across communication channels.

Information:
- 78% of our users currently use Google Docs, Microsoft Office Online, or Notion alongside our platform for document collaboration
- Teams using our platform manage an average of 65 documents per project
- User research shows document handoffs and feedback cycles consume an average of 5.2 hours per team member weekly
- Our system currently supports basic document viewing but no native editing functionality
- Key competitors have recently added similar capabilities, cited as a reason for churn in 22% of exit interviews
- We've secured API partnerships with Google Workspace and Microsoft 365 for potential integration
- Internal technical assessment confirms our infrastructure can handle real-time synchronization requirements
- Legal review requires specific data handling protocols for document storage and access control
- User interviews indicate strong preference for familiar editing interfaces rather than learning new conventions

Directions:
- Design feature with three core components: document creator/editor, commenting/feedback system, and version history/management
- Editor must support these essential functions: text formatting, image insertion, tables, headings/structure, and tracked changes
- Create a permissions system with granular controls: view-only, comment-only, edit specific sections, and full editing rights
- Implement real-time presence indicators showing who is currently viewing or editing the document
- Design intuitive commenting that allows threading discussions, tagging team members, and marking resolutions
- Include version history with clear visual differentiation between versions and ability to restore previous states
- Create seamless transitions between document editing and other project elements (tasks, timelines, resources)
- Design mobile view focused on reviewing, commenting, and minor edits rather than full creation
- Provide import/export compatibility with .docx, .gdoc, and .pdf formats
- Develop an onboarding tutorial sequence for both document creators and collaborators

Evaluation:
- Conduct usability testing with 3 distinct user groups: technical power users, non-technical users, and mixed teams
- Measure time-to-competency for basic operations (document creation, editing, commenting, version management)
- Success requires: <15 minute learning curve for basic functions, 90%+ task completion rate for essential operations
- Beta test with 20 client teams across different industries and team compositions
- Implement analytics tracking: feature adoption rate, time spent in document editor vs. external tools, frequency of collaboration
- Establish baseline satisfaction metrics before launch and measure improvement at 30, 60, and 90 days post-release
- Track support ticket volume related to document collaboration features
- Conduct comparative testing against similar features in competitor products

G.U.I.D.E. Breakdown:

Goal: Design co-editing feature with specific usage, time-saving, and satisfaction metrics
User: Cross-functional teams with varying technical proficiency, usage patterns, and specific pain points
Information: Current behaviors, competitor analysis, technical capabilities, legal requirements, user preferences
Directions: Feature components, essential functions, permissions system, compatibility requirements
Evaluation: Testing methodology with specific user groups, adoption metrics, satisfaction measurement

Best Use Cases for the G.U.I.D.E. Framework

The G.U.I.D.E. framework excels in situations where prompts need to be comprehensive, user-focused, and outcome-oriented. It's particularly effective in the following scenarios:

Educational Content Development

When creating educational materials that need to achieve specific learning outcomes for well-defined audiences, the G.U.I.D.E. framework ensures all pedagogical elements are properly addressed.

Example Prompt:

markdown

Goal: Create an interactive online course on cybersecurity fundamentals that achieves an 85%+ completion rate, results in a measurable 40% improvement in security practices (as assessed through pre/post-testing), and prepares non-technical employees to identify and appropriately respond to the 5 most common security threats facing our organization.

User: Our learners are non-technical employees across all departments (marketing, sales, HR, operations) with varying levels of digital literacy. 65% use only basic computer functions in their daily work, while 35% have more advanced skills. The age range is broad (22-65), with a median age of 42. Most have encountered some form of security training before but report it was unmemorable and they struggle to apply the concepts in real-world situations. They primarily access learning materials during work hours on desktop computers, have approximately 15-20 minutes available per session, and strongly prefer interactive content over passive reading. Their main objections to previous training include: too technical/jargon-heavy, not relevant to their daily work, boring delivery, and unclear expectations.

Information:
- Our security incident data shows the most common threats are: phishing (62%), weak/reused passwords (23%), unpatched software (8%), physical security lapses (4%), and social engineering (3%)
- Previous training had a 37% completion rate and showed only a 12% improvement in security behaviors
- We experienced 14 security incidents last year that could have been prevented with better employee awareness
- Regulatory compliance requires annual security training with documented completion
- Our IT department reports that employees frequently bypass security measures when they perceive them as inconvenient
- Employee surveys indicate a desire for real-world examples and clear, actionable guidance
- We have access to our LMS platform which supports SCORM content, video embedding, quizzes, and simulations
- Training must be accessible on both desktop and mobile devices, though desktop is primary

Directions:
- Create a modular course divided into 5 core sections (one for each primary threat), plus introduction and conclusion
- Each section should follow this structure:
  * Brief overview video (max 2 minutes) explaining the threat in simple terms
  * Interactive scenario simulation allowing users to identify and respond to the threat
  * Key indicators/warning signs presented as an illustrated checklist
  * Step-by-step response protocol with decision tree
  * Knowledge check quiz with immediate feedback
- Include real-world examples relevant to our industry and company size
- Use everyday language with any necessary technical terms clearly defined
- Incorporate gamification elements including: progress tracking, achievement badges, and leaderboard
- Create a downloadable quick-reference guide summarizing key points from each module
- Design mobile-friendly interactions that work without requiring precise mouse movements
- Include periodic knowledge reinforcement through microlearning modules (30-60 seconds) delivered weekly after course completion
- Create pre-test and post-test assessments that measure both knowledge and anticipated behaviors

Evaluation:
- Success metrics include:
  * Completion rate of 85%+ within assigned timeframe
  * Knowledge improvement of 50%+ from pre-test to post-test
  * Behavior change demonstrated through scenario-based assessments (40%+ improvement)
  * Reduction in preventable security incidents by 60% over 12 months
  * User satisfaction rating of 4.2/5 or higher
- Implement tracking of engagement metrics including time spent per module, replay rate of interactive elements, and help resources accessed
- Conduct follow-up pulse surveys at 30, 60, and 90 days to assess knowledge retention
- Run simulated phishing tests before and after training to measure real-world behavior change
- Gather qualitative feedback through focus groups with representative sample of employees
- Track correlation between training performance and actual security incident involvement

Technical Documentation

G.U.I.D.E. enables the creation of technical documentation that achieves specific outcomes for users while providing clear evaluation metrics.

Example Prompt:

markdown

Goal: Create API documentation for our payment processing system that reduces integration time from current average of 3 weeks to under 1 week, decreases integration support tickets by 65%, and enables developers to successfully implement core payment flows without errors on the first attempt.

User: Our API users are primarily web and mobile developers with intermediate to advanced experience (2+ years) working at small to medium-sized e-commerce and SaaS companies. They're comfortable with RESTful APIs but have varying levels of experience with payment processing systems. They value thorough examples, accurate information, and quick reference materials over conceptual explanations. Their primary frustrations with API documentation in general include: outdated information, missing edge cases, inadequate error handling guidance, and difficulty understanding authentication flows. They typically consult documentation in two modes: initial implementation (reading comprehensively) and debugging (searching for specific information).

Information:
- Our payment API handles these core functions: payment authorization, capture, refunds, subscriptions, and payment method storage
- Most common integration errors relate to: authentication (32%), handling declined transactions (28%), and webhook implementation (21%)
- Recent survey of developer experience shows 83% of developers prefer interactive examples they can test directly in documentation
- Our API underwent a major security update that introduced a new authentication system and response format
- We offer client libraries in JavaScript, Python, Ruby, PHP, and Java, but 35% of developers use direct REST integration
- Competitors with highly-rated documentation feature interactive request builders, detailed error catalogs, and implementation checklists
- Support team reports that 40% of tickets could be avoided with better documentation of common pitfalls
- Our system has unique handling requirements for international transactions that frequently cause confusion

Directions:
- Structure documentation with clear navigation separating conceptual information, reference materials, and tutorials
- Begin with a "Quick Start" guide that enables a simple test transaction within 5 minutes
- For each endpoint, include:
  * Clear description of purpose and use cases
  * Complete request parameters with type, format, requirements, and defaults
  * Example requests and responses in all supported languages
  * Common errors and troubleshooting guidance
  * Rate limits, timeouts, and performance considerations
- Create an interactive request builder that allows testing endpoints directly from documentation
- Include a comprehensive error catalog with each error code, cause, and resolution steps
- Develop step-by-step tutorials for the 5 most common integration scenarios
- Provide implementation checklists for development, testing, and production environments
- Create visual diagrams for authentication flows, payment lifecycles, and webhook implementations
- Include a detailed security implementation guide with best practices for storing sensitive data
- Develop a migration guide for users of previous API versions
- Add a search function optimized for finding specific parameters and error codes quickly

Evaluation:
- Measure documentation effectiveness through:
  * Integration time tracking for new vs. previous customers
  * Support ticket volume and categories related to integration
  * Documentation-specific satisfaction surveys
  * Usage analytics including most-visited sections and search terms
- Conduct usability testing with developers of varying experience levels attempting key integration tasks
- Success requires: 90%+ task completion rate using only documentation, average integration time under 7 days, and satisfaction rating of 8/10 or higher
- Implement feedback collection on each documentation page with thumbs up/down and specific improvement suggestions
- Track correlation between documentation sections and related support tickets
- Conduct quarterly audits for accuracy and completeness based on new features and common questions

User Experience Optimization

The G.U.I.D.E. framework helps create prompts for UX improvements that focus on specific user needs and measurable outcomes.

Example Prompt:

markdown

Goal: Redesign our e-commerce checkout process to increase conversion rate from current 43% to target 68%, reduce cart abandonment by 40%, and decrease average checkout time from 4.2 minutes to under 2 minutes while maintaining or improving error rates.

User: Our customers are primarily women (65%) aged 25-45 shopping for home goods and decor. They have moderate digital literacy but limited patience for complicated processes. 58% shop on mobile devices, with highest traffic during evening hours and weekends. Their primary pain points in the current checkout process include: uncertainty about shipping costs until final step, confusion about promo code application, account creation requirements interrupting flow, and difficulty editing cart items. Accessibility is crucial as approximately 15% of users have some form of visual impairment, and 8% report motor control challenges when using mobile devices.

Information:
- Analytics data shows 72% of cart abandonments occur at the shipping information stage
- User testing identified 5 major friction points: unexpected shipping costs, required account creation, too many form fields, unclear error messages, and lack of preferred payment methods
- Heatmap analysis shows users frequently attempt to click back to review cart but often lose entered information
- Session recordings reveal average users make 2.7 attempts to apply promo codes correctly
- Mobile users spend 1.5x longer on checkout than desktop users for the same purchase
- Competitors with higher conversion rates offer: guest checkout, simplified forms with smart defaults, real-time validation, and transparent shipping calculation earlier in process
- Customer support reports frequent calls about promo code application and shipping cost calculation
- Security requirements mandate PCI compliance while maintaining a smooth user experience

Directions:
- Create a streamlined checkout flow with these key improvements:
  * Reduce required form fields from 14 to maximum 8 by eliminating redundant information and making appropriate fields optional
  * Implement real-time field validation with clear, inline error messages
  * Add shipping cost calculator on cart page before checkout begins
  * Create a single-page checkout option with accordion sections rather than multiple pages
  * Implement guest checkout with optional account creation after purchase completion
  * Design mobile-first interfaces with appropriately sized touch targets (minimum 44x44px)
  * Add progress indicator showing checkout stages and completion percentage
  * Implement smart defaults based on location detection and purchase history
  * Create persistent cart summary visible throughout process
  * Redesign promo code entry with clear validation and confirmation
- Ensure WCAG 2.1 AA compliance for all checkout elements
- Maintain consistent design language with main site while optimizing for conversion
- Include clear microcopy explaining each step and requirement
- Design error states that clearly explain issues and how to resolve them
- Create skeleton loading states to reduce perceived wait time during processing

Evaluation:
- Primary success metrics:
  * Checkout conversion rate increase (target: 68%+)
  * Cart abandonment rate decrease (target: 40%+ reduction)
  * Average checkout time decrease (target: under 2 minutes)
  * Error rate maintenance or improvement (current: 7% of attempts)
- Secondary metrics:
  * Promo code usage success rate
  * Guest checkout adoption rate
  * Account creation rate post-purchase
  * Support ticket volume related to checkout
- Implement A/B testing methodology with control group before full deployment
- Conduct usability testing with 15 participants representing core user segments on both mobile and desktop
- Add user feedback mechanism for 30 days post-launch to catch unforeseen issues
- Analyze checkout funnel metrics at each step to identify any remaining friction points
- Set up heat mapping and session recording for the new checkout flow to verify behavior improvements

Process Documentation

G.U.I.D.E. is ideal for creating process documentation that needs to achieve specific efficiency or quality improvements with clear success metrics.

Example Prompt:

markdown

Goal: Create a comprehensive standard operating procedure (SOP) for our customer support team that reduces average ticket resolution time from 4.3 hours to under 2 hours, improves first-contact resolution rate from 62% to 85%+, and increases customer satisfaction scores from 3.7/5 to 4.5/5 while maintaining compliance with our service level agreements.

User: Our support team consists of 35 agents across three global offices with varying levels of experience (40% junior with <1 year, 40% mid-level with 1-3 years, 20% senior with 3+ years). They handle approximately 3,000 tickets weekly across email, chat, and phone channels. They frequently need to coordinate with product, engineering, and billing teams to resolve complex issues. Their primary challenges include: inconsistent processes between team members, difficulty locating relevant information quickly, uncertainty about escalation paths, and lack of clarity on authorization levels for different solutions (refunds, credits, exceptions).

Information:
- Ticket data shows these top categories: account access (22%), billing issues (18%), product confusion (15%), technical errors (25%), feature requests (8%), and cancellations (12%)
- Current knowledge base has over 500 articles but agent surveys show difficulty finding relevant information
- Average ticket touch count is 3.8, with 40% of tickets requiring escalation to senior agents or other departments
- Customer feedback indicates frustration with inconsistent information between agents and having to repeat information multiple times
- New product features are released bi-weekly, often without updated support documentation
- Company policy dictates various authorization levels for monetary adjustments (junior: up to $50, mid-level: up to $200, senior: up to $500)
- We recently implemented a new ticketing system with automation capabilities not yet fully utilized
- Support team experiences 35% seasonal volume fluctuations with holiday peaks
- Compliance requirements mandate specific handling protocols for payment data and personal information

Directions:
- Create a modular SOP document organized by:
  * Ticket categories with decision trees for each major issue type
  * Triage protocols with clear prioritization guidelines
  * Detailed resolution workflows with step-by-step processes
  * Escalation matrices showing when and to whom issues should be routed
  * Authorization guidelines for different compensation and exception scenarios
  * Quality assurance standards and review processes
- Include these specific components:
  * Quick-reference troubleshooting guides for top 20 issues
  * Templates for common responses that can be personalized
  * Screenshots and visual aids for complex processes
  * Clear definitions of severity levels with response time requirements
  * Checklists for verification steps before closing tickets
  * Process maps for cross-department coordination
  * Guidelines for appropriate tone and language in different scenarios
- Design for both comprehensive training and daily reference with clear indexing and search functionality
- Create a change management protocol for updating procedures when new features launch
- Include special handling procedures for VIP customers and urgent escalations
- Develop dashboard reference showing current SLAs and team performance

Evaluation:
- Success metrics include:
  * Average resolution time reduction (target: under 2 hours)
  * First-contact resolution improvement (target: 85%+)
  * Customer satisfaction increase (target: 4.5/5)
  * Escalation rate reduction (target: under 20%)
  * Quality audit pass rate (target: 95%+)
- Implement baseline measurement period before launch followed by 30, 60, and 90-day reviews
- Conduct agent feedback sessions to identify areas for improvement and clarification
- Monitor ticket tag data to identify remaining problem categories
- Track knowledge base article usage to determine most valuable resources
- Measure consistency of resolutions across agents and offices
- Analyze correlation between SOP adherence and customer satisfaction scores
- Conduct quarterly reviews to incorporate new scenarios and optimize existing processes

Project Planning

The G.U.I.D.E. framework helps create thorough project plans with clear goals, user considerations, contextual information, and evaluation criteria.

Example Prompt:

markdown

Goal: Create a detailed implementation plan for migrating our on-premise CRM system to a cloud-based solution that minimizes business disruption (target <2% decrease in sales activities during transition), ensures 100% data integrity, completes within a 90-day timeframe, and achieves 90%+ user adoption within 30 days post-launch.

User: This plan will be executed by our cross-functional implementation team consisting of IT staff (3 administrators, 2 developers), sales operations managers (2), department heads (4), and executive stakeholders (2). The team has varying levels of technical expertise, from highly technical IT personnel to non-technical sales managers. They have differing priorities: IT focuses on security and integration, sales ops prioritizes functionality and data accessibility, department heads care about minimal disruption and training requirements, and executives are concerned with ROI and strategic alignment. The plan needs to be comprehensive enough for technical implementation but also clear enough for non-technical stakeholders to understand progress and impacts.

Information:
- Current on-premise system contains 7+ years of customer data (approximately 50,000 accounts, 250,000 contacts, 180,000 opportunities)
- Integration points include: marketing automation platform, ERP system, support ticketing system, and email client
- 215 active users across sales, customer success, and management will need access
- Team uses 12 custom objects and 35 custom fields not standard in the new system
- 28 automated workflows and 15 custom reports need to be recreated
- Historical data includes closed-won opportunities that are critical for reference and forecasting
- Compliance requirements mandate specific data handling, retention, and access controls
- New system offers enhanced mobile capabilities and AI-powered insights not available in current system
- Previous technology migrations have faced resistance from sales team if they impacted daily workflows

Directions:
- Create a comprehensive implementation plan with these components:
  * Executive summary with goals, timeline, and key milestones
  * Detailed phase breakdown with specific tasks, owners, and deadlines
  * Risk assessment matrix with mitigation strategies for high-impact scenarios
  * Data migration strategy including mapping, cleansing, validation, and verification
  * Integration architecture plan for all connected systems
  * Training and change management approach tailored to different user groups
  * Communication timeline specifying messages, audiences, channels, and frequency
  * Testing strategy including UAT protocols with acceptance criteria
  * Cutover plan detailing the actual transition weekend activities by hour
  * Post-implementation support structure and issue resolution process
- Include a RACI matrix clarifying responsibilities across all team members
- Create contingency plans for critical risks including data corruption, integration failures, and timeline delays
- Develop detailed data backup and rollback procedures in case of critical failure
- Design a phased implementation approach that allows for adjustments based on early feedback
- Include specific approaches for managing custom objects, fields, reports, and workflows
- Create a resource allocation plan accounting for team members' existing responsibilities

Evaluation:
- Define specific success criteria including:
  * Zero data loss or corruption during migration (100% integrity)
  * System availability during business hours (target: 99.9%)
  * User adoption rate 30 days post-launch (target: 90%+)
  * Data accessibility for critical functions (target: 100% within 24 hours)
  * Sales activity metrics during transition (target: <2% decrease)
  * Time to resolve critical issues (target: <2 hours)
- Establish measurement methodology for each criterion
- Create a baseline measurement protocol for pre-migration benchmarking
- Design a post-implementation review process at 7, 30, and 90 days
- Develop executive dashboard for tracking progress against key metrics
- Implement feedback collection system for continuous improvement
- Design comparison protocol for old vs. new system performance
- Create ROI calculation methodology to validate project success against initial business case

Conclusion

The G.U.I.D.E. framework transforms general requests into comprehensive, outcome-focused prompts by systematically addressing the ultimate goal, the needs of target users, relevant contextual information, specific execution directions, and clear evaluation criteria.

What sets G.U.I.D.E. apart is its holistic, user-centric approach that maintains unwavering focus on achieving measurable outcomes. By forcing prompt creators to articulate not just what should be created, but for whom, in what context, with what specific directions, and how success will be measured, the framework eliminates ambiguity and ensures all critical aspects are addressed up front.

When to use the G.U.I.D.E. framework:

When outcomes need to be clearly defined and measured
When addressing specific user needs is critical to success
When relevant background information significantly impacts approach
When detailed execution directions are necessary
When establishing clear success criteria is important

The G.U.I.D.E. framework is particularly valuable for complex projects where success depends on thorough understanding of goals, users, context, and evaluation metrics. By providing a comprehensive structure for prompt creation, it ensures that AI-generated content is precisely aligned with intended outcomes, user needs, and contextual requirements.

Framework in Action: Examples

See how GUIDE Framework transforms basic prompts into powerful instructions

Before & After Examples

See how this framework transforms basic prompts into powerful instructions for AI

Transformation

Basic PromptBefore

Lacks structure and specificity

Create a tutorial for our app.

Effectiveness Score

Low

Goal-User-Information-Directions-Evaluation Enhanced PromptAfter

Clear structure and intent

Goal: Create a beginner-friendly tutorial for our healthcare management app that increases new user activation rate from current 35% to target 75% and reduces day-one abandonment by helping users complete their profile setup and first medication tracking entry. User: Our primary users are adults 65+ with chronic conditions managing multiple medications. They have limited technology experience (40% report using smartphones less than 2 years), may have visual impairments (30% report difficulty reading small text), and express anxiety about making mistakes in health-related apps (85% fear "breaking something" or entering incorrect medical information). Information: - Our onboarding data shows that only 23% of users successfully navigate from account creation to medication entry without abandoning - Heat map analysis reveals users get stuck primarily on the profile setup screen (35% drop-off) and medication entry form (42% drop-off) - User testing indicates confusion about required vs. optional fields and uncertainty about where information is stored - App was recently updated with larger text options and voice input capabilities that most new users aren't discovering - Support call logs show 70% of first-day questions relate to basic navigation and concerns about data privacy Directions: - Create a sequential, visually-oriented tutorial with no more than 5 steps per task - For each step, include: * A large, clearly labeled screenshot with key action areas highlighted * Brief instructional text (maximum 2 sentences per step) at 16pt font minimum * Alternative approaches where relevant (e.g., touch option and voice command option) * A single focused action for the user to take - Include progress indicators showing completion percentage - Incorporate reassurance about data privacy at relevant points - Explicitly label optional vs. required fields - End with a "quick reference" summary users can save or print - Include clear paths to human support options Evaluation: - Success will be measured by: * Completion rate of full profile setup (target: 85%+) * Successful first medication entry (target: 80%+) * Reduction in first-day support calls (target: 40% decrease) * User confidence ratings via post-tutorial survey (target: 4.5/5) - Tutorial will be tested with a focus group of 12 representative users before full release - Incorporate a feedback mechanism directly in the tutorial to collect improvement suggestions - Track which steps have highest drop-off rates for continuous improvement

Effectiveness Score

High

Basic PromptBefore

Create a tutorial for our app.

Effectiveness

Low

Goal-User-Information-Directions-Evaluation EnhancedAfter

Effectiveness

High

Response Comparison

Basic AI ResponseBefore

Quality:

# How to Use Our App

Welcome to our app! This tutorial will help you get started.

## Creating Your Account
1. Download the app from the App Store or Google Play
2. Open the app and tap "Sign Up"
3. Enter your email and create a password
4. Verify your email

## Setting Up Your Profile
1. Tap on the Profile tab
2. Enter your personal information
3. Add your photo if desired
4. Save your changes

## Using the Main Features
1. Navigate the dashboard to see different options
2. Tap on features to explore them
3. Use the menu to return to the main screen

If you need help, contact our support team at support@ourapp.com

Generic information

Lacks structure

Limited detail

Goal-User-Information-Directions-Evaluation Enhanced ResponseAfter

Quality:

# MediRemind Tutorial: Getting Started the Easy Way

## Welcome to MediRemind!
This step-by-step guide will help you set up your account and track your first medication in just a few minutes. Every piece of information you share is private and securely protected.

[PROGRESS: Getting Started - 0%]

Professional format

Expert insights

Actionable content

Key Improvements with the Framework

Professional Structure

Clear organization with logical sections

Targeted Focus

Precisely aligned with specific outcomes

Enhanced Clarity

Clear intent and specific requirements

Actionable Output

Concrete recommendations and detailed analysis

Framework Component Breakdown

Goal

What is the ultimate objective or purpose?

User

Who is the target audience and what are their needs?

Information

What context, data, or background is needed?

Directions

What specific steps or actions are required?

Evaluation

How will success be measured or feedback incorporated?