*Genre Quest

(t8n-arrive:"zoom")[''Welcome back to TechGrowth Solutions!''] [Your team in Corporate Communications needs to manage internal communication about an upcoming system update. In "The Mixed Message," you assessed audiences who are potentially affected by the update. Now, you'll explore ways to convey information to those audiences through different genres.] [[Instructions]]

[Throughout this RPG scenario, you'll use dice to complete ability checks. These ability checks give you information and questions to guide your analysis of the scenario.] [Here's how to complete an ability check: 1. Have one member of your team roll a D20. 2. Add their ability modifier to the score. (You can find your ability modifiers in your character sheets!) 3. Enter the combined score to reveal the relevant information and questions.] [Throughout this game, take careful notes! You'll base your Audience Analysis assignment on this in-game scenario. You may choose to play the game together—taking turns to choose audiences and genres—or you may choose to play independently. Even if you choose to play independently, you'll need to refer to your team's notes from "The Mixed Message." I recommend discussing the genre information you acquire with your team to help think through your choices.] [[[[Let's begin!->First Audience + Genre Choice]]]]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Sales uses Teams primarily during business hours and has a general department channel plus regional sub-channels. ''Guiding Questions:'' * "Which channel(s) will reach the right people?" * "What's the most urgent information for sales staff?" * "How will they need to adjust client communications?" ] (else-if:$analysisCheck1 < 15)[Sales teams frequently check Teams during client meetings for system status. They use the 'Important' tag for updates and expect quick replies during business hours. ''Guiding Questions:'' * "How can we format for quick reference during client meetings?" * "What priority level should we assign?" * "What client-facing implications need emphasis?" * "How should we handle time zone differences?" ] (else-if:$analysisCheck1 >= 15)[Sales has a dedicated 'Systems Status' tab in Teams where they pin critical updates. They've created quick-response templates for common client questions about system changes. ''Guiding Questions:'' * "How can we align with their existing system status format?" * "What client communication tools need updating?" * "How should we support their response templates?" * "What follow-up tracking would help?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check ST]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results ST]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy options include posting in main Sales channel and asking regional managers to share in sub-channels. ''Guiding Questions:'' * "When is the best time to post for maximum visibility?" * "How should we sequence regional communications?" * "What immediate follow-up might be needed?" ] (else-if:$strategyCheck1 < 15)[Sales has peak Teams activity before client meetings and end-of-day reporting. They rely on pinned messages for quick reference during client calls. ''Guiding Questions:'' * "How can we time the message for maximum awareness?" * "What should we pin for quick reference?" * "How should we coordinate with sales leadership?" * "What client-facing resources should we prepare?" ] (else-if:$strategyCheck1 >= 15)[Sales uses a multi-channel strategy: initial alert in main channel, detailed info in regional channels, and quick-reference cards in their client support channel. They schedule system updates around major client presentations. ''Guiding Questions:'' * "How can we leverage all available channels?" * "What quick-reference tools would be most useful?" * "How should we coordinate with their client calendar?" * "What follow-up communications might be needed?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check ST]].]

[Have one team member roll for Adaptation. Then, add their Adaptation modifier to the number they rolled, and enter it below!] (input-box:2bind $adaptationInput1,"=XX=") [[Next->Adaptation Results ST]]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Sales team messages typically use bullet points and highlight customer impact in bold. ''Guiding Questions:'' * "What formatting conventions does Sales usually follow?" * "How should we highlight client-facing information?" * "What standard Teams features do they rely on?" ] (else-if:$adaptationCheck1 < 15)[Sales uses a specific message template: 'Impact Level' header, client-facing talking points, internal notes in collapsible sections, and standard response emojis for acknowledgment. ''Guiding Questions:'' * "How can we adapt the update for their template?" * "What talking points need development?" * "How should we organize internal vs. external info?" * "What response options should we include?" ] (else-if:$adaptationCheck1 >= 15)[Sales has developed sophisticated message conventions: color-coded impact badges, expandable FAQ sections, linked client communication templates, and integration with their CRM notification system. ''Guiding Questions:'' * "How can we use their impact badge system?" * "What FAQ sections would be most useful?" * "How should we structure CRM-linked content?" * "What client templates need updating?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check ST]].]

[Have one team member roll for Innovation. Then, add their Innovation modifier to the number they rolled, and enter it below!] (input-box:2bind $innovationInput1,"=XX=") [[Next->Innovation Results ST]]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Teams offers basic features like pinning messages and using the announcement format. ''Guiding Questions:'' * "How could we use announcement features creatively?" * "What pinning strategy might be most effective?" * "Could we use emoji reactions in meaningful ways?" ] (else-if:$innovationCheck1 < 15)[Sales has started experimenting with Teams tabs for quick reference guides and using Planner for update tracking. They're interested in new ways to make information more accessible during client calls. ''Guiding Questions:'' * "How could we create an innovative quick reference system?" * "What new ways could we track message receipt?" * "How might we integrate with their client meeting workflow?" * "What creative uses of Teams tabs could help?" ] (else-if:$innovationCheck1 >= 15)[Sales has access to Power Automate flows, interactive message cards, and a bot that helps find relevant information. They're open to creating new templates for system updates. ''Guiding Questions:'' * "How could we use interactive cards creatively?" * "What innovative bot interactions could help?" * "How might we automate client communication updates?" * "What new template features could we pioneer?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check ST]].]

[Have one team member roll for Implementation. Then, add their Implementation modifier to the number they rolled, and enter it below!] (input-box:2bind $implementationInput1,"=XX=") [[Next->Implementation Results ST]]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires posting in main Sales channel and confirming regional managers received the message. ''Guiding Questions:'' * "What's our posting timeline?" * "How will we track message receipt?" * "What immediate follow-up might be needed?" ] (else-if:$implementationCheck < 15)[Sales has a message testing protocol: draft review by team leads, test post in private channel, scheduled release to main channel, and tracked acknowledgments through reactions. ''Guiding Questions:'' * "How should we sequence the review process?" * "What testing criteria should we use?" * "How can we ensure consistent delivery?" * "What tracking methods work best?" ] (else-if:$implementationCheck >= 15)[Sales uses a sophisticated implementation system: staged message release, automated client communication updates, real-time engagement tracking, and scheduled follow-up prompts. ''Guiding Questions:'' * "How can we optimize the release sequence?" * "What automation tools should we utilize?" * "How should we measure engagement?" * "What follow-up system works best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check ST]].]

[Have one team member roll for Collaboration. Then, add their Collaboration modifier to the number they rolled, and enter it below!] (input-box:2bind $collaborationInput1,"=XX=") [[Next->Collaboration Results]]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires checking with Sales team leads before posting. ''Guiding Questions:'' * "Who needs to review the message?" * "How do we coordinate with regional managers?" * "What feedback loops should we create?" ] (else-if:$collaborationCheck1 < 15)[Sales uses a collaborative review process: draft review by client success team, input from regional leaders, coordination with technical support, and alignment with customer communication plans. ''Guiding Questions:'' * "How should we gather stakeholder input?" * "What cross-team coordination is needed?" * "How can we align customer messaging?" * "What review sequence works best?" ] (else-if:$collaborationCheck1 >= 15)[Sales has a comprehensive collaboration system: shared message development workspace, integrated feedback from client-facing teams, coordinated response planning with support teams, and alignment with marketing communications. ''Guiding Questions:'' * "How can we optimize cross-team coordination?" * "What collaborative tools should we use?" * "How should we manage multiple stakeholder input?" * "What alignment checks are crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

(set: $rounds to 2) [For your second audience, you choose to write to (cycling-link: bind $audience1, "Sales","IT","Production","Vendors","Executives") through (cycling-link: bind $genre1, "a Teams message","an email","an FAQ","a website update","a meeting").] [[Ready?->Ready2]]

#[Genre Quest] [[Start]]

(set: $rounds to 1) [For your first audience, you choose to write to (cycling-link: bind $audience1, "Sales","IT","Production","Vendors","Executives") through (cycling-link: bind $genre1, "a Teams message","an email","an FAQ","a website update","a meeting").] [[Ready?]]

(storylet: when $audience1 is "Sales" and $genre1 is "a Teams message") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results ST]]

[Remember, you'll need access to your team's notes from "The Mixed Message."] (link-storylet: "Let's get started!", where "round1" is in its tags)

(storylet: when $audience1 is "IT" and $genre1 is "a Teams message") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results ITT]]

(storylet: when $audience1 is "Production" and $genre1 is "a Teams message") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results PT]]

(storylet: when $audience1 is "Vendors" and $genre1 is "a Teams message") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results VT]]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[IT Support uses a dedicated channel for system updates and requires specific technical details in a standard format. ''Guiding Questions:'' * "What technical specifications are required?" * "How should we format for their standard template?" * "What immediate actions will they need to take?" ] (else-if:$analysisCheck1 < 15)[IT Support integrates Teams messages with their ticket system and uses specific tags to categorize system changes. They maintain a running changelog in their channel. ''Guiding Questions:'' * "What tags and categories should we use?" * "How does this fit their changelog format?" * "What documentation needs to be linked?" * "How should we handle support ticket routing?" ] (else-if:$analysisCheck1 >= 15)[IT Support has automated alerts set up based on Teams messages and uses Power Automate flows to update their knowledge base and trigger testing protocols. ''Guiding Questions:'' * "How can we ensure automated systems work correctly?" * "What testing protocols need to be triggered?" * "How should knowledge base updates be handled?" * "What emergency procedures need to be addressed?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check ITT]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results ITT]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Standard protocol requires posting in the system updates channel and tagging the on-duty support team. ''Guiding Questions:'' * "What tags will reach the right team members?" * "How should we time the initial notification?" * "What immediate responses should we prepare for?" ] (else-if:$strategyCheck1 < 15)[IT Support uses a three-stage communication approach: advance notice, implementation alert, and completion confirmation. Each stage has specific tagging requirements. ''Guiding Questions:'' * "How should we structure each stage?" * "What technical details belong in each message?" * "How can we ensure proper handoffs between shifts?" * "What confirmation systems should we use?" ] (else-if:$strategyCheck1 >= 15)[IT Support has an automated workflow triggered by specific message formats: initial post generates tickets, second stage initiates testing protocols, final stage updates documentation and closes tickets. ''Guiding Questions:'' * "How can we optimize the automated workflow?" * "What trigger phrases need to be included?" * "How should we handle exceptions?" * "What documentation updates need to be coordinated?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check ITT]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[IT Support requires specific formatting tags: [SYSTEM UPDATE], [PRIORITY LEVEL], and [TIMELINE]. ''Guiding Questions:'' * "What standard tags apply to this update?" * "How should technical specifications be formatted?" * "What reference links need to be included?" ] (else-if:$adaptationCheck1 < 15)[IT Support uses a structured message format: header with tracking number, collapsible technical details, @mentions for key personnel, and status update fields that integrate with their dashboard. ''Guiding Questions:'' * "How should we structure the technical details?" * "Which personnel need @mentions?" * "What status fields are required?" * "How can we optimize for their dashboard?" ] (else-if:$adaptationCheck1 >= 15)[IT Support messages must follow their change management format: coded prefixes for automation, structured JSON-like fields for system integration, standardized markup for knowledge base updates, and linked test protocols. ''Guiding Questions:'' * "How can we meet all formatting requirements?" * "What automation triggers should we include?" * "How should we structure knowledge base content?" * "What testing documentation needs linking?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check ITT]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Teams allows for code snippet sharing and threaded technical discussions. ''Guiding Questions:'' * "How could we use code blocks creatively?" * "What new ways might we organize technical threads?" * "Could we innovate with tagging systems?" ] (else-if:$innovationCheck1 < 15)[IT Support has Power Automate capabilities and can create custom message extensions. They're interested in better ways to link Teams discussions with their knowledge base. ''Guiding Questions:'' * "What innovative automations could we create?" * "How might we reimagine knowledge base integration?" * "What creative ways could we track system changes?" * "How could we make technical details more accessible?" ] (else-if:$innovationCheck1 >= 15)[IT Support can develop custom Teams apps, use adaptive cards for interactive updates, and create Power BI dashboards from Teams data. They're open to building new tools for system update communication. ''Guiding Questions:'' * "What innovative dashboard features could we design?" * "How could adaptive cards improve update tracking?" * "What creative ways could we visualize system changes?" * "How might we automate documentation updates?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check ITT]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Implementation requires posting in the system updates channel and confirming receipt from the current support team. ''Guiding Questions:'' * "What's our verification process?" * "How do we ensure shift coverage?" * "What immediate actions need tracking?" ] (else-if:$implementationCheck < 15)[IT Support follows a structured implementation: test post for automation triggers, verification of ticket generation, confirmation of knowledge base updates, and handoff protocol between shifts. ''Guiding Questions:'' * "How should we test automation systems?" * "What verification steps are crucial?" * "How can we ensure smooth shift handoffs?" * "What documentation needs updating?" ] (else-if:$implementationCheck >= 15)[IT Support uses an advanced implementation framework: automated testing of message triggers, real-time system integration verification, cascading update notifications, and automated documentation updates with version control. ''Guiding Questions:'' * "How can we optimize the testing sequence?" * "What integration checks are needed?" * "How should we manage version control?" * "What automated tracking should we use?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check ITT]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires coordinating with the IT manager and current support team. ''Guiding Questions:'' * "Who needs to be involved in message development?" * "How do we coordinate across support shifts?" * "What technical review is needed?" ] (else-if:$collaborationCheck1 < 15)[IT Support uses a collaborative workflow: technical review team input, coordination with system administrators, alignment with help desk scripts, and integration with ongoing support tickets. ''Guiding Questions:'' * "How should we coordinate technical reviews?" * "What help desk coordination is needed?" * "How can we align with current tickets?" * "What cross-team checks are important?" ] (else-if:$collaborationCheck1 >= 15)[IT Support has an integrated collaboration system: shared documentation workspace, coordinated testing teams, automated workflow notifications, and cross-functional technical review process. ''Guiding Questions:'' * "How can we optimize technical collaboration?" * "What testing coordination is needed?" * "How should we manage documentation updates?" * "What stakeholder sign-offs are required?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Production staff check Teams at shift changes and rely on shift supervisors to relay important updates. ''Guiding Questions:'' * "How can we reach all three shifts?" * "What role should supervisors play?" * "What's the most critical information for their work?" ] (else-if:$analysisCheck1 < 15)[Production uses shared tablets for Teams access and has a system of shift-specific channels. They use a simple thumbs-up reaction to confirm message receipt. ''Guiding Questions:'' * "How should we format for tablet viewing?" * "What confirmation system should we use?" * "How can we ensure between-shift communication?" * "What workflow impacts need highlighting?" ] (else-if:$analysisCheck1 >= 15)[Production has developed a color-coded system for updates and uses Teams' scheduling feature to ensure messages hit at shift changes. Supervisors hold brief huddles around the Teams display board. ''Guiding Questions:'' * "How can we use their color system effectively?" * "What timing will reach all shifts?" * "How can we support supervisor huddles?" * "What visual elements would aid comprehension?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check PT]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results PT]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy involves posting updates at main shift changes: 6am, 2pm, and 10pm. ''Guiding Questions:'' * "How can we ensure consistent message delivery across shifts?" * "What handoff procedures should we include?" * "How should supervisors share this information?" ] (else-if:$strategyCheck1 < 15)[Production uses a 'cascade' communication strategy: supervisor briefing, shift huddle announcement, and posted quick-reference guide on shared tablets. ''Guiding Questions:'' * "How should we structure information for each communication stage?" * "What visual aids would support shift huddles?" * "How can we make tablet reference guides effective?" * "What confirmation system ensures all shifts are informed?" ] (else-if:$strategyCheck1 >= 15)[Production has developed a strategic communication framework: priority alerts with color coding, shift-specific checklists, and digital display board updates. They integrate Teams messages with their production schedule tracking. ''Guiding Questions:'' * "How can we align with their visual alert system?" * "What checklist items are needed for each shift?" * "How should we coordinate with production scheduling?" * "What backup communication methods should we plan?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check PT]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Production messages need large, clear headers and step-by-step instructions with numbers. ''Guiding Questions:'' * "What visual hierarchy works best?" * "How should we break down instructions?" * "What formatting makes tablet viewing easier?" ] (else-if:$adaptationCheck1 < 15)[Production uses a standardized format: shift-specific headers in different colors, checkboxes for action items, visual indicators for system status, and simplified technical terms. ''Guiding Questions:'' * "How should we adapt technical language?" * "What visual indicators work best?" * "How can we make action items clear?" * "What shift-specific elements need attention?" ] (else-if:$adaptationCheck1 >= 15)[Production has developed a visual communication system: status icons, process flow diagrams, interactive checklists, and QR codes linking to training materials. Messages must be optimized for their digital display boards. ''Guiding Questions:'' * "How can we incorporate their visual system?" * "What process flows need updating?" * "How should we structure interactive elements?" * "What training links should we include?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check PT]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Teams can display on shared screens and support basic image sharing. ''Guiding Questions:'' * "How could we use visual elements creatively?" * "What new ways might we make updates noticeable?" * "Could we innovate shift handoff communication?" ] (else-if:$innovationCheck1 < 15)[Production has access to Teams display mode features and QR code integration. They're interested in better ways to make updates visible across all shifts. ''Guiding Questions:'' * "What creative display layouts could we design?" * "How might we use QR codes innovatively?" * "What new ways could we confirm message receipt?" * "How could we make updates more interactive?" ] (else-if:$innovationCheck1 >= 15)[Production can use Teams live tiles, create custom status indicators, and integrate with their digital signage system. They're open to developing new visual communication tools. ''Guiding Questions:'' * "How could we use live tiles creatively?" * "What innovative status indicators could we design?" * "How might we reimagine shift communication?" * "What new visual tools could improve comprehension?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check PT]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Implementation involves posting at shift changes and confirming supervisor acknowledgment. ''Guiding Questions:'' * "How do we time shift change posts?" * "What supervisor confirmation is needed?" * "How do we track shift handoffs?" ] (else-if:$implementationCheck < 15)[Production uses a coordinated implementation: supervisor preview, shift huddle preparation, digital display updates, and tracked acknowledgments from each shift. ''Guiding Questions:'' * "How should we sequence shift communications?" * "What display updates are needed?" * "How can we verify all shifts received info?" * "What backup systems should we have ready?" ] (else-if:$implementationCheck >= 15)[Production has developed a comprehensive implementation system: synchronized digital displays, automated shift alerts, interactive checklist tracking, and integration with production schedule updates. ''Guiding Questions:'' * "How can we optimize display synchronization?" * "What alert systems should we utilize?" * "How should we track completion?" * "What schedule integration is needed?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check PT]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires working with shift supervisors and production manager. ''Guiding Questions:'' * "How do we coordinate with all shifts?" * "What supervisor input do we need?" * "How should we gather floor feedback?" ] (else-if:$collaborationCheck1 < 15)[Production uses a collaborative approach: supervisor review team, input from each shift, coordination with maintenance staff, and alignment with safety protocols. ''Guiding Questions:'' * "How should we gather multi-shift input?" * "What maintenance coordination is needed?" * "How can we ensure safety alignment?" * "What review process works best?" ] (else-if:$collaborationCheck1 >= 15)[Production has developed a comprehensive collaboration system: cross-shift review teams, integrated feedback from floor leads, coordinated equipment checks, and alignment with quality control processes. ''Guiding Questions:'' * "How can we optimize shift coordination?" * "What quality control alignment is needed?" * "How should we manage equipment impacts?" * "What safety checks are crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[External vendors access a limited Teams channel and require advance notice of system changes per their service agreements. ''Guiding Questions:'' * "What contractual notification requirements apply?" * "How technical should the language be?" * "What access limitations should we consider?" ] (else-if:$analysisCheck1 < 15)[Vendors use Teams primarily for scheduled check-ins and have varying technical expertise. They need to coordinate their own system updates with ours. ''Guiding Questions:'' * "How can we accommodate different technical levels?" * "What timeline information is crucial?" * "How should we handle vendor questions?" * "What coordination tools would help?" ] (else-if:$analysisCheck1 >= 15)[Vendors have set up Teams notifications to their own ticketing systems and need specific formatting to trigger their change management protocols. Some vendors require formal acknowledgment of critical updates. ''Guiding Questions:'' * "How can we meet various vendor notification requirements?" * "What acknowledgment system should we use?" * "How can we track vendor preparations?" * "What security considerations apply?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check VT]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results VT]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Standard strategy requires 48-hour advance notice and confirmation of receipt. ''Guiding Questions:'' * "How should we sequence vendor notifications?" * "What confirmation process should we use?" * "How should we handle vendor questions?" ] (else-if:$strategyCheck1 < 15)[Vendors require a three-part communication strategy: preliminary notice, detailed specifications, and implementation confirmation. Each vendor has specific technical contacts. ''Guiding Questions:'' * "How should we structure each communication phase?" * "What technical details belong in each message?" * "How can we track vendor readiness?" * "What coordination tools would be most effective?" ] (else-if:$strategyCheck1 >= 15)[Vendors operate on a sophisticated notification system with automated integration to their systems. They require specific formatting to trigger their change management protocols and have established testing windows. ''Guiding Questions:'' * "How can we optimize message formatting for their systems?" * "What testing coordination is needed?" * "How should we handle different vendor timelines?" * "What contingency plans should we develop?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check VT]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Vendor communications require formal headers with contract reference numbers and clear action items. ''Guiding Questions:'' * "What contract details need inclusion?" * "How should we format required actions?" * "What acknowledgment format is expected?" ] (else-if:$adaptationCheck1 < 15)[Vendor messages follow a structured template: legal notification header, technical specifications in standardized fields, timeline table, and formal acknowledgment buttons integrated with their systems. ''Guiding Questions:'' * "How should we adapt our update to their template?" * "What technical fields are required?" * "How can we present timeline clearly?" * "What system integration elements need attention?" ] (else-if:$adaptationCheck1 >= 15)[Vendor communication requires specific formatting for cross-system compatibility: XML-style tags for automated processing, standardized security clearance markers, compatibility check fields, and integrated testing schedules. ''Guiding Questions:'' * "How can we meet all technical requirements?" * "What security markers apply?" * "How should we structure testing coordination?" * "What documentation needs to be linked?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check VT]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Teams offers secure external sharing and basic notification settings. ''Guiding Questions:'' * "How could we use sharing permissions creatively?" * "What new ways might we track message receipt?" * "Could we innovate the notification process?" ] (else-if:$innovationCheck1 < 15)[Vendors can access secure shared channels and use Teams' translation features. They're interested in better ways to coordinate system changes across organizations. ''Guiding Questions:'' * "What creative uses of shared channels could we develop?" * "How might we use translation features innovatively?" * "What new coordination tools could we create?" * "How could we make technical coordination more efficient?" ] (else-if:$innovationCheck1 >= 15)[Teams supports cross-organization automation, secure file sharing with version control, and custom approval flows. Vendors are open to creating new coordination tools. ''Guiding Questions:'' * "What innovative approval processes could we design?" * "How could we reimagine cross-organization updates?" * "What creative security features could we implement?" * "How might we automate coordination?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check VT]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Implementation requires posting in vendor channel and collecting formal acknowledgments within 24 hours. ''Guiding Questions:'' * "How do we track acknowledgments?" * "What's our follow-up timeline?" * "How do we document vendor responses?" ] (else-if:$implementationCheck < 15)[Vendor implementation follows contractual requirements: preliminary notice period, formal distribution list, tracked receipt confirmations, and scheduled coordination checkpoints. ''Guiding Questions:'' * "How should we sequence notifications?" * "What tracking system works best?" * "How can we manage multiple vendor timelines?" * "What coordination checkpoints are crucial?" ] (else-if:$implementationCheck >= 15)[Vendors require sophisticated implementation: automated distribution with security protocols, cross-system verification, coordinated testing windows, and documented compliance tracking. ''Guiding Questions:'' * "How can we optimize security protocols?" * "What verification systems need attention?" * "How should we coordinate testing?" * "What compliance documentation is required?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check VT]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires coordinating with vendor account managers and our procurement team. ''Guiding Questions:'' * "Who are our key vendor contacts?" * "How do we coordinate internal approvals?" * "What legal review is needed?" ] (else-if:$collaborationCheck1 < 15)[Vendor collaboration involves: technical team coordination, legal compliance review, procurement team alignment, and cross-organization security checks. ''Guiding Questions:'' * "How should we coordinate technical teams?" * "What compliance reviews are needed?" * "How can we align multiple vendors?" * "What security coordination is crucial?" ] (else-if:$collaborationCheck1 >= 15)[Vendor collaboration uses an integrated system: cross-organization technical workgroups, coordinated compliance teams, shared testing environments, and aligned change management processes. ''Guiding Questions:'' * "How can we optimize cross-org collaboration?" * "What testing coordination is needed?" * "How should we manage compliance alignment?" * "What change management processes apply?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

(storylet: when $audience1 is "Sales" and $genre1 is "an email") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results SE]]

(storylet: when $audience1 is "Executives" and $genre1 is "a Teams message") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results ET]]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Executives check Teams during morning meetings and expect critical updates to be flagged as 'Important.' ''Guiding Questions:'' * "What's the most crucial information for this audience?" * "How formal should the message be?" * "What priority level is appropriate?" ] (else-if:$analysisCheck1 < 15)[Executives use Teams' priority notifications for urgent updates and expect clear escalation paths. They prefer updates that include both business impact and technical details. ''Guiding Questions:'' * "How can we balance technical and business information?" * "What priority settings are appropriate?" * "How should we structure for quick decisions?" * "What escalation paths need to be clear?" ] (else-if:$analysisCheck1 >= 15)[Executives have a private channel with IT leadership for system discussions and use Teams' briefing emails for morning updates. Their assistants monitor and flag critical responses needed. ''Guiding Questions:'' * "How can we coordinate with IT leadership's communication?" * "What briefing tools should we use?" * "How can we support assistant monitoring?" * "What business metrics should we highlight?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check ET]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results ET]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Executive communications are typically scheduled around their 8:30am meeting schedule. ''Guiding Questions:'' * "What preview information might be needed?" * "How should we structure for quick review?" * "What follow-up should we prepare?" ] (else-if:$strategyCheck1 < 15)[Executives use a tiered communication strategy: brief alert, detailed briefing document, and impact summary. Their assistants manage message prioritization. ''Guiding Questions:'' * "How should we structure each tier of information?" * "What business impacts need highlighting?" * "How can we support assistant prioritization?" * "What decision points need emphasis?" ] (else-if:$strategyCheck1 >= 15)[Executive communication strategy includes integration with their daily briefing system, automated scheduling of follow-up discussions, and coordination with department head updates. They expect clear decision pathways and risk assessments. ''Guiding Questions:'' * "How can we leverage their briefing system?" * "What decision framework should we provide?" * "How should we coordinate with department updates?" * "What risk assessment format would be most effective?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check ET]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Executive messages require brief, scannable format with clear business impact highlighted. ''Guiding Questions:'' * "How can we make this most scannable?" * "What business metrics need emphasis?" * "How should we highlight action items?" ] (else-if:$adaptationCheck1 < 15)[Executive format includes standard elements: priority indicator, executive summary box, collapsible technical details, and clear decision points with response options. ''Guiding Questions:'' * "How should we structure the summary?" * "What decision points need highlighting?" * "How can we present technical details accessibly?" * "What response options should we include?" ] (else-if:$adaptationCheck1 >= 15)[Executive communication follows their briefing system format: KPI impact indicators, risk assessment matrix, resource allocation summary, and integration with their strategic dashboard. Messages must support their morning briefing workflow. ''Guiding Questions:'' * "How can we align with briefing formats?" * "What KPIs need highlighting?" * "How should we present risk assessment?" * "What strategic elements need emphasis?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check ET]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Teams supports priority notifications and meeting scheduling integration. ''Guiding Questions:'' * "How could we use priority features creatively?" * "What new ways might we integrate with calendars?" * "Could we innovate briefing formats?" ] (else-if:$innovationCheck1 < 15)[Executives use Teams' briefing emails and Power BI dashboard integration. They're interested in better ways to track system changes' business impact. ''Guiding Questions:'' * "What creative briefing formats could we develop?" * "How might we visualize business impact innovatively?" * "What new ways could we present decision points?" * "How could we make technical updates more strategic?" ] (else-if:$innovationCheck1 >= 15)[Executives have access to custom Teams apps, adaptive cards for quick decisions, and integration with their strategic planning tools. They're open to new ways of tracking system changes' strategic impact. ''Guiding Questions:'' * "What innovative decision-making tools could we create?" * "How could we reimagine strategic impact tracking?" * "What creative ways could we present risk assessment?" * "How might we automate strategic updates?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check ET]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Implementation requires posting before morning meeting and confirming executive assistant receipt. ''Guiding Questions:'' * "What's our optimal timing?" * "How do we verify message delivery?" * "What immediate follow-up might be needed?" ] (else-if:$implementationCheck < 15)[Executive implementation includes: pre-brief to assistants, scheduled release to executive channel, briefing material updates, and tracked decision points. ''Guiding Questions:'' * "How should we sequence the communication?" * "What briefing updates are needed?" * "How can we track decisions effectively?" * "What follow-up system works best?" ] (else-if:$implementationCheck >= 15)[Executive implementation uses an integrated system: automated briefing updates, strategic dashboard integration, decision tracking workflow, and scheduled follow-up prompts with escalation paths. ''Guiding Questions:'' * "How can we optimize briefing integration?" * "What dashboard updates are needed?" * "How should we track decisions?" * "What escalation protocols apply?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check ET]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires coordinating with executive assistants and department heads. ''Guiding Questions:'' * "Who needs to provide input?" * "How do we coordinate with assistants?" * "What departmental alignment is needed?" ] (else-if:$collaborationCheck1 < 15)[Executive collaboration includes: department head review council, coordination with strategic planning team, alignment with corporate communications, and input from technical leaders. ''Guiding Questions:'' * "How should we gather leadership input?" * "What strategic alignment is needed?" * "How can we coordinate messaging?" * "What review sequence works best?" ] (else-if:$collaborationCheck1 >= 15)[Executive collaboration uses a strategic system: integrated leadership review process, coordinated impact assessment teams, aligned strategic communications, and cross-functional decision support. ''Guiding Questions:'' * "How can we optimize leadership coordination?" * "What impact assessments are needed?" * "How should we align strategic messaging?" * "What decision support is crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

(link-storylet: "Let's get started!", where "round2" is in its tags)

(storylet: when $audience1 is "IT" and $genre1 is "an email") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results ITE]]

(storylet: when $audience1 is "Production" and $genre1 is "an email") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results PE]]

(storylet: when $audience1 is "Vendors" and $genre1 is "an email") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results VE]]

(storylet: when $audience1 is "Executives" and $genre1 is "an email") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results EE]]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Sales team members check email during client meetings and rely on mobile-friendly formats. ''Guiding Questions:'' * "What information needs to be visible in preview pane?" * "How should we format for mobile reading?" * "What subject line will ensure attention?" ] (else-if:$analysisCheck1 < 15)[Sales uses a tiered email system: urgent alerts, daily digests, and weekly summaries. They flag system updates for client communication impact and save important emails in shared folders. ''Guiding Questions:'' * "Which tier is appropriate for this update?" * "How should we highlight client impact?" * "What filing tags should we include?" * "How can we support mobile reference needs?" ] (else-if:$analysisCheck1 >= 15)[Sales has developed sophisticated email protocols: impact-coded subject lines, client-ready forwarding sections, mobile-optimized quick reference cards, and integration with their CRM email templates. ''Guiding Questions:'' * "How can we optimize for their email workflow?" * "What forwarding sections are needed?" * "How should we structure quick reference elements?" * "What CRM integration points matter?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check SE]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[IT Support requires specific subject line tags [SYS-UPDATE] and expects technical details in a structured format. ''Guiding Questions:'' * "What email tags are required?" * "How should technical content be structured?" * "What attachments might be needed?" ] (else-if:$analysisCheck1 < 15)[IT Support uses an email classification system: priority headers, categorized technical specifications, linked documentation, and automated ticket generation from specific email formats. ''Guiding Questions:'' * "How should we format for ticket generation?" * "What documentation links are crucial?" * "How can we ensure proper categorization?" * "What technical details need highlighting?" ] (else-if:$analysisCheck1 >= 15)[IT Support has implemented advanced email protocols: JSON-formatted technical blocks for automation, embedded troubleshooting guides, version control tracking, and integration with their knowledge base email updates. ''Guiding Questions:'' * "How can we optimize for their automation?" * "What troubleshooting elements need inclusion?" * "How should we handle version tracking?" * "What knowledge base updates need linking?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check ITE]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Production staff primarily access email at workstations during shift changes and prefer clear, concise updates. ''Guiding Questions:'' * "How can we ensure shift-change visibility?" * "What format is most readable at workstations?" * "What subject line will be most effective?" ] (else-if:$analysisCheck1 < 15)[Production uses a standardized email system: shift-specific distribution lists, color-coded priority indicators, printable quick-reference attachments, and required acknowledgment tracking. ''Guiding Questions:'' * "How should we handle shift-specific details?" * "What priority indicators apply?" * "What quick-reference formats work best?" * "How can we track acknowledgments?" ] (else-if:$analysisCheck1 >= 15)[Production has developed comprehensive email protocols: shift-synchronized delivery timing, interactive PDF attachments, digital signage email integration, and automated reminder systems for unacknowledged updates. ''Guiding Questions:'' * "How can we optimize delivery timing?" * "What interactive elements are needed?" * "How should we integrate with signage?" * "What follow-up systems apply?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check PE]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Vendor emails require formal business format and must reference contract numbers in subject lines. ''Guiding Questions:'' * "What contract details need inclusion?" * "How should we format for formality?" * "What receipt confirmation is needed?" ] (else-if:$analysisCheck1 < 15)[Vendor email communication follows strict protocols: security classification headers, encrypted technical attachments, standardized response requirements, and compliance tracking markers. ''Guiding Questions:'' * "What security markers are required?" * "How should we handle attachments?" * "What response format should we request?" * "How can we ensure compliance tracking?" ] (else-if:$analysisCheck1 >= 15)[Vendors use sophisticated email systems: automated security scanning, cross-platform compatibility checking, digital signature requirements, and integration with their change management email workflows. ''Guiding Questions:'' * "How can we meet security requirements?" * "What compatibility issues need attention?" * "How should we handle signatures?" * "What change management elements apply?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check VE]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Executives rely on email preview panes and expect clear subject lines indicating priority level. ''Guiding Questions:'' * "What preview content is most crucial?" * "How should we indicate priority?" * "What executive summary format works best?" ] (else-if:$analysisCheck1 < 15)[Executive email protocol includes: priority flagging system, executive summary bullets, business impact highlights, and integration with their morning briefing email digest. ''Guiding Questions:'' * "How should we structure the summary?" * "What business impacts need emphasis?" * "How can we support briefing integration?" * "What follow-up flags are appropriate?" ] (else-if:$analysisCheck1 >= 15)[Executives use an advanced email system: AI-powered priority sorting, interactive dashboard links, automated briefing integration, and strategic impact tracking through their email analytics. ''Guiding Questions:'' * "How can we optimize for AI sorting?" * "What dashboard elements need linking?" * "How should we structure for analytics?" * "What strategic elements need emphasis?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check EE]].]

(set: $rounds to 3) [For your final audience, you choose to write to (cycling-link: bind $audience1, "Sales","IT","Production","Vendors","Executives") through (cycling-link: bind $genre1, "a Teams message","an email","an FAQ","a website update","a meeting").] [[Ready?->Ready3]]

(link-storylet: "Let's get started!", where "round3" is in its tags)

(storylet: when $audience1 is "Sales" and $genre1 is "an FAQ") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results SF]]

(storylet: when $audience1 is "IT" and $genre1 is "an FAQ") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results ITF]]

(storylet: when $audience1 is "Production" and $genre1 is "an FAQ") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results PF]]

(storylet: when $audience1 is "Vendors" and $genre1 is "an FAQ") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results VF]]

(storylet: when $audience1 is "Executives" and $genre1 is "an FAQ") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results EF]]

(storylet: when $audience1 is "Sales" and $genre1 is "a meeting") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results SM]]

(storylet: when $audience1 is "IT" and $genre1 is "a meeting") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results ITM]]

(storylet: when $audience1 is "Production" and $genre1 is "a meeting") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results PM]]

(storylet: when $audience1 is "Vendors" and $genre1 is "a meeting") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results VM]]

(storylet: when $audience1 is "Executives" and $genre1 is "a meeting") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results EM]]

(storylet: when $audience1 is "Sales" and $genre1 is "a website update") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results SW]]

(storylet: when $audience1 is "IT" and $genre1 is "a website update") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results ITW]]

(storylet: when $audience1 is "Production" and $genre1 is "a website update") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results PW]]

(storylet: when $audience1 is "Vendors" and $genre1 is "a website update") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results VW]]

(storylet: when $audience1 is "Executives" and $genre1 is "a website update") [Have one team member roll for Analysis. Then, add their Analysis modifier to the number they rolled, and enter it below!] (input-box:2bind $analysisInput1,"=XX=") [[Next->Analysis Results EW]]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Sales needs FAQ sheets that address both internal process changes and client concerns. ''Guiding Questions:'' * "What questions will clients ask?" * "What internal processes are changing?" * "How should we organize different question types?" ] (else-if:$analysisCheck1 < 15)[Sales uses a two-tier FAQ system: client-facing questions with approved responses, and internal questions with detailed technical context. They rely heavily on searchable formats. ''Guiding Questions:'' * "How should we separate internal/external content?" * "What search terms matter most?" * "How can we structure for quick reference?" * "What response scripts are needed?" ] (else-if:$analysisCheck1 >= 15)[Sales has developed a sophisticated FAQ framework: scenario-based questions, integrated CRM responses, customizable client scripts, and dynamic updating based on common support tickets. ''Guiding Questions:'' * "How can we optimize for different scenarios?" * "What CRM integration points matter?" * "How should we structure response scripts?" * "What updating system works best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check SF]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Sales meetings need to balance system update information with client impact discussion. ''Guiding Questions:'' * "What's the optimal meeting length?" * "How should we prioritize topics?" * "What preparation materials are needed?" ] (else-if:$analysisCheck1 < 15)[Sales uses a structured meeting format: client impact overview, technical update briefing, response strategy planning, and action item assignment. ''Guiding Questions:'' * "How should we sequence topics?" * "What discussion points need emphasis?" * "How can we support strategy planning?" * "What follow-up items matter most?" ] (else-if:$analysisCheck1 >= 15)[Sales has developed comprehensive meeting frameworks: pre-meeting briefing materials, scenario-based discussion guides, CRM-integrated action items, and client communication planning tools. ''Guiding Questions:'' * "How can we optimize pre-meeting prep?" * "What scenarios need coverage?" * "How should we structure action items?" * "What planning tools matter most?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check SM]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Sales needs both internal portal updates and client-facing system status pages. ''Guiding Questions:'' * "What content needs internal restriction?" * "How should we structure client access?" * "What navigation paths are crucial?" ] (else-if:$analysisCheck1 < 15)[Sales uses dual-layer website structure: internal knowledge base with detailed system impacts, and client portal with simplified status updates and response templates. ''Guiding Questions:'' * "How should we organize different access levels?" * "What search functionality matters most?" * "How can we support quick reference?" * "What client resources need updating?" ] (else-if:$analysisCheck1 >= 15)[Sales has developed sophisticated web architecture: role-based content delivery, integrated CRM portal access, dynamic response generator, and personalized client communication center. ''Guiding Questions:'' * "How can we optimize role-based access?" * "What CRM integration points matter?" * "How should we structure updates?" * "What personalization features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check SW]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[IT Support requires technical FAQs with troubleshooting steps and error code references. ''Guiding Questions:'' * "What technical details need inclusion?" * "How should we organize error codes?" * "What troubleshooting sequences matter?" ] (else-if:$analysisCheck1 < 15)[IT Support uses a structured FAQ system: tiered technical complexity, linked documentation references, common error resolution paths, and integration with their ticket categorization system. ''Guiding Questions:'' * "How should we organize complexity levels?" * "What documentation links matter most?" * "How can we align with ticket categories?" * "What resolution paths need mapping?" ] (else-if:$analysisCheck1 >= 15)[IT Support has implemented an advanced FAQ framework: decision-tree troubleshooting, automated solution suggestions, integrated testing protocols, and real-time update capabilities based on resolution data. ''Guiding Questions:'' * "How can we optimize troubleshooting paths?" * "What automation points matter?" * "How should we structure testing steps?" * "What update triggers are crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check ITF]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Production needs clear, step-by-step FAQs focused on workflow changes and equipment access. ''Guiding Questions:'' * "What workflow changes need explanation?" * "How should we format instructions?" * "What visual aids are needed?" ] (else-if:$analysisCheck1 < 15)[Production uses shift-specific FAQ formats: visual process guides, equipment access instructions, safety protocol reminders, and common issue resolution steps. ''Guiding Questions:'' * "How should we organize by shift?" * "What visual elements work best?" * "How can we emphasize safety?" * "What common issues need coverage?" ] (else-if:$analysisCheck1 >= 15)[Production has developed a comprehensive FAQ system: interactive process flows, QR-coded equipment guides, integrated safety checks, and shift-specific troubleshooting procedures. ''Guiding Questions:'' * "How can we optimize process visualization?" * "What equipment guidance matters most?" * "How should we integrate safety protocols?" * "What troubleshooting paths work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check PF]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Vendors need FAQs addressing system access changes and compliance requirements. ''Guiding Questions:'' * "What access changes need explanation?" * "How should we address compliance?" * "What technical details are crucial?" ] (else-if:$analysisCheck1 < 15)[Vendors use a structured FAQ format: security protocol updates, integration requirements, testing procedures, and compliance verification steps. ''Guiding Questions:'' * "How should we organize security information?" * "What integration details matter most?" * "How can we clarify testing requirements?" * "What compliance steps need emphasis?" ] (else-if:$analysisCheck1 >= 15)[Vendors require sophisticated FAQ organization: role-based access matrices, cross-system integration guides, automated compliance checklists, and coordinated testing protocols. ''Guiding Questions:'' * "How can we optimize access explanations?" * "What integration guidance matters most?" * "How should we structure compliance info?" * "What testing details are crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check VF]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Executives need FAQs focused on business impact and strategic implications. ''Guiding Questions:'' * "What business impacts need addressing?" * "How should we present strategic elements?" * "What decision points matter?" ] (else-if:$analysisCheck1 < 15)[Executive FAQs use a strategic framework: business impact summaries, risk assessment guides, resource allocation explanations, and decision-making protocols. ''Guiding Questions:'' * "How should we organize impact information?" * "What risk details matter most?" * "How can we clarify decisions needed?" * "What resource questions need addressing?" ] (else-if:$analysisCheck1 >= 15)[Executives use an advanced FAQ system: KPI impact matrices, strategic decision frameworks, resource optimization guides, and stakeholder management protocols. ''Guiding Questions:'' * "How can we optimize KPI presentation?" * "What decision guidance matters most?" * "How should we structure strategic info?" * "What stakeholder concerns need addressing?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check EF]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[IT Support meetings need technical briefing structure and clear task assignments. ''Guiding Questions:'' * "What technical details need coverage?" * "How should we organize testing steps?" * "What documentation needs reviewing?" ] (else-if:$analysisCheck1 < 15)[IT Support uses tiered meeting structure: system impact overview, technical implementation details, testing protocol review, and support strategy planning. ''Guiding Questions:'' * "How should we sequence technical content?" * "What testing details need discussion?" * "How can we plan support coverage?" * "What documentation needs updating?" ] (else-if:$analysisCheck1 >= 15)[IT Support has developed advanced meeting frameworks: pre-meeting technical documentation, interactive testing demonstrations, automated task tracking, and knowledge base update planning. ''Guiding Questions:'' * "How can we optimize technical review?" * "What demonstrations matter most?" * "How should we structure support plans?" * "What automation needs discussion?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check ITM]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Production meetings need shift handover focus and clear process changes. ''Guiding Questions:'' * "What shift coverage is needed?" * "How should we explain changes?" * "What safety items need review?" ] (else-if:$analysisCheck1 < 15)[Production uses visual meeting structure: process change demonstrations, equipment access updates, safety protocol review, and shift coordination planning. ''Guiding Questions:'' * "How should we sequence demonstrations?" * "What visual aids need preparation?" * "How can we ensure shift coverage?" * "What coordination points matter most?" ] (else-if:$analysisCheck1 >= 15)[Production has developed comprehensive meeting frameworks: interactive process walkthroughs, digital demonstration tools, cross-shift coordination plans, and real-time feedback collection. ''Guiding Questions:'' * "How can we optimize demonstrations?" * "What digital tools matter most?" * "How should we structure shift handoffs?" * "What feedback methods work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check PM]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Vendor meetings need compliance focus and clear integration timelines. ''Guiding Questions:'' * "What contract requirements need review?" * "How should we structure timelines?" * "What technical coordination is needed?" ] (else-if:$analysisCheck1 < 15)[Vendor meetings use structured format: security protocol review, integration planning, compliance verification, and coordinated testing schedule. ''Guiding Questions:'' * "How should we sequence requirements?" * "What integration details need discussion?" * "How can we verify compliance?" * "What testing coordination matters most?" ] (else-if:$analysisCheck1 >= 15)[Vendors require sophisticated meeting frameworks: secure documentation review, cross-system testing plans, automated compliance tracking, and coordinated implementation scheduling. ''Guiding Questions:'' * "How can we optimize security review?" * "What testing plans matter most?" * "How should we structure coordination?" * "What implementation details need focus?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check VM]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Executive meetings need strategic focus and clear decision points. ''Guiding Questions:'' * "What business impacts need review?" * "How should we present decisions?" * "What resource discussions are needed? ] (else-if:$analysisCheck1 < 15)[Executive meetings use strategic format: business impact analysis, risk assessment review, resource allocation planning, and strategic decision-making. ''Guiding Questions:'' * "How should we sequence strategic topics?" * "What risk details need discussion?" * "How can we facilitate decisions?" * "What resource planning matters most?" ] (else-if:$analysisCheck1 >= 15)[Executives use advanced meeting frameworks: KPI impact analysis, strategic planning integration, automated dashboard reviews, and stakeholder management planning. ''Guiding Questions:'' * "How can we optimize impact analysis?" * "What strategic elements matter most?" * "How should we structure decisions?" * "What stakeholder concerns need focus?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check EM]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[IT Support needs technical documentation updates and system status tracking. ''Guiding Questions:'' * "What technical details need documenting?" * "How should we display status?" * "What search capabilities are needed?" ] (else-if:$analysisCheck1 < 15)[IT Support uses structured web architecture: technical knowledge base, real-time system monitoring dashboard, ticket tracking integration, and documentation version control. ''Guiding Questions:'' * "How should we organize technical content?" * "What monitoring displays matter most?" * "How can we integrate with tickets?" * "What version control needs attention?" ] (else-if:$analysisCheck1 >= 15)[IT Support has implemented advanced web features: AI-powered troubleshooting guides, automated documentation updates, integrated testing environments, and real-time collaboration spaces. ''Guiding Questions:'' * "How can we optimize troubleshooting flows?" * "What automation tools matter?" * "How should we structure testing areas?" * "What collaboration features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check ITW]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Production needs simplified system status pages and clear process documentation. ''Guiding Questions:'' * "What status indicators are crucial?" * "How should we display instructions?" * "What mobile access is needed?" ] (else-if:$analysisCheck1 < 15)[Production uses visual web structure: interactive process guides, shift-specific portals, equipment status tracking, and mobile-optimized documentation. ''Guiding Questions:'' * "How should we organize visual content?" * "What shift information matters most?" * "How can we support mobile users?" * "What status updates need emphasis?" ] (else-if:$analysisCheck1 >= 15)[Production has developed comprehensive web tools: QR-linked documentation, interactive training modules, real-time equipment status, and shift-specific communication portals. ''Guiding Questions:'' * "How can we optimize mobile access?" * "What training features matter?" * "How should we display status?" * "What communication tools work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check PW]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Vendors need secure portal access and compliance documentation. ''Guiding Questions:'' * "What security levels are required?" * "How should we organize documentation?" * "What access tracking is needed?" ] (else-if:$analysisCheck1 < 15)[Vendors use structured portal design: role-based security access, integration documentation library, compliance tracking dashboard, and secure communication channels. ''Guiding Questions:'' * "How should we manage access levels?" * "What documentation matters most?" * "How can we track compliance?" * "What communication tools are crucial?" ] (else-if:$analysisCheck1 >= 15)[Vendors require sophisticated web architecture: multi-factor authentication portals, automated compliance verification, cross-system integration guides, and secure collaboration spaces. ''Guiding Questions:'' * "How can we optimize security?" * "What verification tools matter?" * "How should we structure guides?" * "What collaboration features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check VW]].]

(set: $analysisInput1 to (num: $analysisInput1)) (set: $analysisCheck1 to $analysisInput1) (if:$analysisCheck1 < 11)[Executives need strategic dashboard access and simplified status overview. ''Guiding Questions:'' * "What metrics need highlighting?" * "How should we display progress?" * "What decision support is needed?" ] (else-if:$analysisCheck1 < 15)[Executive portal uses strategic design: KPI dashboard integration, resource impact tracking, strategic planning tools, and stakeholder communication center. ''Guiding Questions:'' * "How should we present KPIs?" * "What tracking features matter most?" * "How can we support decisions?" * "What communication tools are crucial?" ] (else-if:$analysisCheck1 >= 15)[Executives use advanced web features: AI-powered analytics dashboard, predictive impact modeling, strategic resource visualization, and integrated stakeholder management tools. ''Guiding Questions:'' * "How can we optimize analytics?" * "What prediction tools matter?" * "How should we visualize data?" * "What management features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Strategy Check ->Strategy Check EW]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results SE]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic email strategy involves morning distribution to catch pre-client meeting review time. ''Guiding Questions:'' * "When is the optimal sending time?" * "Should we send reminders?" * "What immediate follow-up might be needed?" ] (else-if:$strategyCheck1 < 15)[Sales uses a strategic email approach: preview alert, detailed update, and follow-up digest. They coordinate email timing with their client meeting calendar and CRM notifications. ''Guiding Questions:'' * "How should we sequence these messages?" * "What client meeting impacts need planning?" * "How can we align with CRM updates?" * "What follow-up strategy works best?" ] (else-if:$strategyCheck1 >= 15)[Sales has developed a comprehensive email strategy: time-zone adjusted distribution, automated client-facing update generation, mobile-first design approach, and integration with their sales enablement platform. ''Guiding Questions:'' * "How can we optimize for different time zones?" * "What client communication tools need updating?" * "How should we support mobile access?" * "What platform integration is crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check SE]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Sales emails typically use bullet points and highlight customer-facing information in bold. ''Guiding Questions:'' * "How should we structure key points?" * "What client impact needs highlighting?" * "What preview text is most important?" ] (else-if:$adaptationCheck1 < 15)[Sales uses specific email conventions: impact-level subject tags, client-ready talking points in blue boxes, internal notes in gray boxes, and mobile-optimized quick facts. ''Guiding Questions:'' * "How should we format different information types?" * "What talking points need development?" * "How can we optimize for mobile?" * "What quick facts are essential?" ] (else-if:$adaptationCheck1 >= 15)[Sales has sophisticated email templates: collapsible technical details, client-ready forwarding sections, integrated CRM snippets, and role-specific viewing options. ''Guiding Questions:'' * "How can we structure layered information?" * "What forwarding elements need attention?" * "How should we integrate CRM content?" * "What role-specific adaptations matter?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check SE]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic email features include attachment options and read receipt tracking. ''Guiding Questions:'' * "How could we use tracking creatively?" * "What innovative attachment formats might help?" * "Could we use email rules in new ways?" ] (else-if:$innovationCheck1 < 15)[Sales has access to dynamic email content, mobile preview tools, and CRM email integration features. They're interested in better ways to manage client-facing information. ''Guiding Questions:'' * "How could we use dynamic content creatively?" * "What new mobile solutions might work?" * "How might we innovate CRM integration?" * "What creative preview options exist?" ] (else-if:$innovationCheck1 >= 15)[Sales can use interactive email elements, automated response templates, AI-powered content suggestions, and cross-platform notification systems. ''Guiding Questions:'' * "How could we use interactive elements innovatively?" * "What creative automation might help?" * "How might we leverage AI features?" * "What new cross-platform approaches could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check SE]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires sending during prime sales hours and confirming regional manager receipt. ''Guiding Questions:'' * "What's our optimal sending schedule?" * "How do we verify receipt?" * "What immediate follow-up is needed?" ] (else-if:$implementationCheck < 15)[Sales follows a staged email implementation: test send to team leads, client impact review, scheduled distribution with tracking, and automated reminder sequence. ''Guiding Questions:'' * "How should we sequence the rollout?" * "What testing criteria matter most?" * "How can we track engagement?" * "What reminder system works best?" ] (else-if:$implementationCheck >= 15)[Sales uses advanced implementation tools: time-zone optimized distribution, CRM-integrated tracking, automated client communication updates, and engagement analytics monitoring. ''Guiding Questions:'' * "How can we optimize timing across zones?" * "What tracking metrics matter most?" * "How should we manage client updates?" * "What analytics need monitoring?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check SE]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires review from sales manager and client success team. ''Guiding Questions:'' * "Who needs to review content?" * "How do we gather team input?" * "What sign-offs are needed?" ] (else-if:$collaborationCheck1 < 15)[Sales uses collaborative email development: client success team input, regional manager review, technical support consultation, and marketing message alignment. ''Guiding Questions:'' * "How should we coordinate multiple reviewers?" * "What technical input is needed?" * "How can we align with marketing?" * "What review sequence works best?" ] (else-if:$collaborationCheck1 >= 15)[Sales has integrated collaboration tools: shared email drafting workspace, automated stakeholder review routing, client communication alignment system, and cross-functional approval tracking. ''Guiding Questions:'' * "How can we optimize review workflow?" * "What stakeholder input matters most?" * "How should we coordinate messaging?" * "What approval tracking works best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results ITE]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires sending during primary shift hours and copying backup distribution lists. ''Guiding Questions:'' * "What distribution lists are essential?" * "How should we time the release?" * "What backup communications are needed?" ] (else-if:$strategyCheck1 < 15)[IT Support uses a staged email strategy: technical preview to leads, full documentation distribution, automated ticket creation, and scheduled follow-up notifications. ''Guiding Questions:'' * "How should we sequence technical details?" * "What documentation needs coordination?" * "How can we optimize ticket creation?" * "What follow-up schedule makes sense?" ] (else-if:$strategyCheck1 >= 15)[IT Support implements a multi-phase email strategy: automated system notifications, coordinated documentation updates, integrated knowledge base synchronization, and automated testing schedule coordination. ''Guiding Questions:'' * "How can we align automated notifications?" * "What documentation syncing is needed?" * "How should we coordinate testing?" * "What escalation paths need defining?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check ITE]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[IT Support emails require technical specifications in monospace font and standardized headers. ''Guiding Questions:'' * "What technical formatting is required?" * "How should we structure headers?" * "What code elements need special formatting? ] (else-if:$adaptationCheck1 < 15)[IT Support uses structured email formats: collapsible technical blocks, color-coded severity indicators, linked documentation sections, and formatted command snippets. ''Guiding Questions:'' * "How should we organize technical content?" * "What severity indicators apply?" * "How can we format documentation links?" * "What command formatting is needed?" ] (else-if:$adaptationCheck1 >= 15)[IT Support has developed advanced email templates: JSON-formatted data blocks, integrated troubleshooting trees, version comparison tables, and automated testing instruction formatting. ''Guiding Questions:'' * "How can we structure data blocks?" * "What troubleshooting formats work best?" * "How should we present version changes?" * "What testing instructions need emphasis?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check ITE]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Email system supports code block formatting and automated categorization. ''Guiding Questions:'' * "How could we use code blocks creatively?" * "What new categorization approaches might help?" * "Could we innovate tracking methods?" ] (else-if:$innovationCheck1 < 15)[IT Support has access to email-to-ticket conversion tools, documentation linking features, and automated testing notifications. They're interested in streamlining technical communication. ''Guiding Questions:'' * "How could we enhance ticket integration?" * "What new documentation approaches might work?" * "How might we innovate testing notifications?" * "What creative troubleshooting tools could we add?" ] (else-if:$innovationCheck1 >= 15)[IT Support can implement interactive troubleshooting flows, AI-powered solution suggestions, automated version control tracking, and integrated testing environments through email. ''Guiding Questions:'' * "How could we use interactive elements innovatively?" * "What new AI applications might help?" * "How might we revolutionize version tracking?" * "What creative testing integrations could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check ITE]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires sending to support distribution list and confirming ticket creation. ''Guiding Questions:'' * "What distribution lists are crucial?" * "How do we verify ticket creation?" * "What immediate actions need tracking?" ] (else-if:$implementationCheck < 15)[IT Support uses structured implementation: technical review phase, automated system notifications, knowledge base updates, and shift handover protocols. ''Guiding Questions:'' * "How should we sequence technical reviews?" * "What system notifications matter?" * "How can we ensure knowledge transfer?" * "What handover protocols apply?" ] (else-if:$implementationCheck >= 15)[IT Support implements with automated tools: system integration verification, cascading notification protocols, automated documentation updates, and real-time testing coordination. ''Guiding Questions:'' * "How can we optimize system integration?" * "What notification sequence works best?" * "How should we handle documentation?" * "What testing coordination is crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check ITE]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires technical review and help desk input. ''Guiding Questions:'' * "Who provides technical review?" * "How do we incorporate help desk perspective?" * "What coordination is needed?" ] (else-if:$collaborationCheck1 < 15)[IT Support uses structured collaboration: system administrator input, support team review, documentation team consultation, and cross-shift coordination. ''Guiding Questions:'' * "How should we gather technical feedback?" * "What documentation input matters?" * "How can we coordinate across shifts?" * "What review sequence works best?" ] (else-if:$collaborationCheck1 >= 15)[IT Support has developed integrated collaboration tools: shared technical documentation workspace, automated cross-team review routing, knowledge base coordination system, and real-time feedback integration. ''Guiding Questions:'' * "How can we optimize technical input?" * "What cross-team coordination matters?" * "How should we manage documentation updates?" * "What feedback systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results PE]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy involves sending updates before each shift change with supervisor CCs. ''Guiding Questions:'' * "What shift change timing works best?" * "How should we involve supervisors?" * "What acknowledgment strategy is needed?" ] (else-if:$strategyCheck1 < 15)[Production uses coordinated email timing: shift handover alerts, detailed shift-specific instructions, supervisor briefing materials, and scheduled reminder sequences. ''Guiding Questions:'' * "How should we time shift communications?" * "What supervisor support is needed?" * "How can we ensure consistent handoffs?" * "What reminder system works best?" ] (else-if:$strategyCheck1 >= 15)[Production has developed an integrated email strategy: synchronized shift notifications, automated workstation alerts, digital signage email integration, and coordinated maintenance schedule updates. ''Guiding Questions:'' * "How can we optimize notification timing?" * "What workstation alerts need coordination?" * "How should we integrate with other systems?" * "What maintenance coordination is crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check PE]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Production emails need large headers and numbered action items. ''Guiding Questions:'' * "What visual hierarchy works best?" * "How should we format instructions?" * "What essential information needs emphasis?" ] (else-if:$adaptationCheck1 < 15)[Production uses specialized email formatting: shift-specific color coding, checkable action boxes, simplified technical terms, and printer-friendly layouts. ''Guiding Questions:'' * "How should we adapt technical language?" * "What visual cues work best?" * "How can we ensure print clarity?" * "What action items need highlighting?" ] (else-if:$adaptationCheck1 >= 15)[Production has developed comprehensive email templates: visual process flows, interactive checklists, shift-specific appendices, and workstation-optimized viewing formats. ''Guiding Questions:'' * "How can we incorporate visual elements?" * "What checklist format works best?" * "How should we structure shift-specific content?" * "What workstation display needs matter?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check PE]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Email system supports basic HTML formatting and scheduled delivery. ''Guiding Questions:'' * "How could we use formatting creatively?" * "What new scheduling approaches might help?" * "Could we innovate shift communication?" ] (else-if:$innovationCheck1 < 15)[Production has access to visual instruction builders, shift-specific templates, and digital signage integration. They're interested in improving information accessibility. ''Guiding Questions:'' * "How could we enhance visual instructions?" * "What new template features might help?" * "How might we innovate shift handoffs?" * "What creative display options could work?" ] (else-if:$innovationCheck1 >= 15)[Production can implement QR-coded instructions, augmented reality links, interactive checklists, and automated shift report generation through email. ''Guiding Questions:'' * "How could we use QR codes innovatively?" * "What new AR applications might help?" * "How might we enhance checklist interaction?" * "What creative reporting tools could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check PE]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires coordinated sending before shift changes. ''Guiding Questions:'' * "What's our shift change timing?" * "How do we verify supervisor receipt?" * "What backup methods are needed?" ] (else-if:$implementationCheck < 15)[Production uses synchronized implementation: supervisor preview period, shift-specific distributions, workstation notification checks, and acknowledgment tracking. ''Guiding Questions:'' * "How should we coordinate with shifts?" * "What notification checks matter?" * "How can we track understanding?" * "What backup systems need testing?" ] (else-if:$implementationCheck >= 15)[Production implements with integrated systems: automated shift notifications, digital signage synchronization, interactive checklist tracking, and cross-shift verification protocols. ''Guiding Questions:'' * "How can we optimize notifications?" * "What display systems need updating?" * "How should we track completion?" * "What verification methods work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check PE]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires supervisor input and safety team review. ''Guiding Questions:'' * "How do we gather supervisor feedback?" * "What safety considerations matter?" * "Who else needs to be involved?" ] (else-if:$collaborationCheck1 < 15)[Production uses collaborative review: shift supervisor input, safety team consultation, maintenance coordination, and operator feedback integration. ''Guiding Questions:'' * "How should we coordinate across teams?" * "What operator input matters?" * "How can we integrate safety protocols?" * "What review sequence works best?" ] (else-if:$collaborationCheck1 >= 15)[Production has comprehensive collaboration systems: cross-shift review coordination, integrated safety protocol alignment, equipment team consultation, and operator feedback channels. ''Guiding Questions:'' * "How can we optimize shift coordination?" * "What safety alignment matters most?" * "How should we integrate equipment concerns?" * "What feedback channels work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results VE]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires sending during business hours with 48-hour response window. ''Guiding Questions:'' * "What timing meets contract requirements?" * "How should we track responses?" * "What follow-up timeline is appropriate?" ] (else-if:$strategyCheck1 < 15)[Vendor email strategy includes: preliminary notification, detailed technical bulletin, compliance confirmation request, and coordinated testing schedule announcements. ''Guiding Questions:'' * "How should we sequence notifications?" * "What technical details need staging?" * "How can we streamline confirmations?" * "What testing coordination is needed?" ] (else-if:$strategyCheck1 >= 15)[Vendors require a sophisticated email strategy: security-cleared distribution lists, automated compliance tracking, cross-organization calendar integration, and coordinated change management notifications. ''Guiding Questions:'' * "How can we optimize security protocols?" * "What compliance tracking is crucial?" * "How should we coordinate schedules?" * "What change management elements need attention?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check VE]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Vendor emails require formal letterhead formatting and specific legal disclaimers. ''Guiding Questions:'' * "What letterhead elements are required?" * "How should we format disclaimers?" * "What contract references need inclusion?" ] (else-if:$adaptationCheck1 < 15)[Vendor emails use standardized templates: security classification headers, technical specification tables, compliance checklist sections, and formal acknowledgment blocks. ''Guiding Questions:'' * "How should we format security markers?" * "What specification format works best?" * "How can we structure compliance items?" * "What acknowledgment format is required?" ] (else-if:$adaptationCheck1 >= 15)[Vendors require sophisticated email formatting: encrypted technical addendums, cross-reference linking systems, automated compliance tracking markers, and multi-party approval blocks. ''Guiding Questions:'' * "How can we structure sensitive information?" * "What linking systems need attention?" * "How should we format tracking elements?" * "What approval workflows need support?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check VE]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Email system supports encryption and automated receipt confirmation. ''Guiding Questions:'' * "How could we use security features creatively?" * "What new confirmation approaches might help?" * "Could we innovate tracking methods?" ] (else-if:$innovationCheck1 < 15)[Vendors have access to secure collaboration tools, cross-platform notification systems, and automated compliance checking. They're interested in improving coordination efficiency. ''Guiding Questions:'' * "How could we enhance secure collaboration?" * "What new compliance tools might help?" * "How might we innovate coordination?" * "What creative tracking solutions could work?" ] (else-if:$innovationCheck1 >= 15)[Vendors can implement blockchain-verified communications, smart contract integration, automated testing coordination, and cross-organization workflow automation through email. ''Guiding Questions:'' * "How could we use verification innovatively?" * "What new automation approaches might help?" * "How might we enhance coordination?" * "What creative compliance tools could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check VE]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires sending during business hours with receipt confirmation tracking. ''Guiding Questions:'' * "What timing meets contract requirements?" * "How do we track confirmations?" * "What follow-up protocol is needed?" ] (else-if:$implementationCheck < 15)[Vendors require structured implementation: security clearance verification, staged distribution sequence, compliance tracking protocols, and coordinated response monitoring. ''Guiding Questions:'' * "How should we verify security clearance?" * "What distribution stages matter?" * "How can we track compliance?" * "What response monitoring is crucial?" ] (else-if:$implementationCheck >= 15)[Vendors use sophisticated implementation tools: automated security protocols, cross-organization verification systems, integrated compliance tracking, and coordinated testing schedules. ''Guiding Questions:'' * "How can we optimize security measures?" * "What verification steps are crucial?" * "How should we coordinate testing?" * "What compliance tracking matters most?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check VE]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires legal review and procurement team input. ''Guiding Questions:'' * "Who handles legal review?" * "How do we coordinate with procurement?" * "What contract checks are needed?" ] (else-if:$collaborationCheck1 < 15)[Vendor collaboration includes: legal compliance review, technical team coordination, security team consultation, and cross-organization alignment. ''Guiding Questions:'' * "How should we sequence reviews?" * "What technical coordination matters?" * "How can we ensure security alignment?" * "What cross-org protocols apply?" ] (else-if:$collaborationCheck1 >= 15)[Vendors require sophisticated collaboration: integrated compliance review system, cross-organization technical workgroups, automated security clearance coordination, and multi-stakeholder approval tracking. ''Guiding Questions:'' * "How can we optimize compliance review?" * "What technical collaboration matters most?" * "How should we coordinate approvals?" * "What tracking systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results EE]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy involves early morning distribution before leadership meetings. ''Guiding Questions:'' * "What timing aligns with executive schedule?" * "How should we coordinate with assistants?" * "What follow-up planning is needed?" ] (else-if:$strategyCheck1 < 15)[Executive email strategy includes: preview to assistants, coordinated briefing materials, impact summary distribution, and scheduled decision-point reminders. ''Guiding Questions:'' * "How should we sequence information?" * "What briefing coordination is needed?" * "How can we streamline decisions?" * "What reminder system works best?" ] (else-if:$strategyCheck1 >= 15)[Executives use an integrated email strategy: AI-prioritized distribution, automated briefing integration, strategic dashboard updates, and coordinated leadership communication cascade. ''Guiding Questions:'' * "How can we optimize for AI prioritization?" * "What dashboard elements need coordination?" * "How should we support leadership cascade?" * "What strategic timing is crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check EE]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Executive emails require clear subject lines and executive summaries in the first paragraph. ''Guiding Questions:'' * "What subject line format works best?" * "How should we structure the summary?" * "What preview text is most important?" ] (else-if:$adaptationCheck1 < 15)[Executive email format includes: priority indicators, business impact highlights, collapsible technical details, and decision-required markers. ''Guiding Questions:'' * "How should we highlight impacts?" * "What technical details need adaptation?" * "How can we clarify decision points?" * "What priority markers matter most?" ] (else-if:$adaptationCheck1 >= 15)[Executives use advanced email templates: KPI-linked summaries, strategic impact visualizations, interactive decision matrices, and automated briefing integration formats. ''Guiding Questions:'' * "How can we integrate KPI data?" * "What visualizations work best?" * "How should we structure decisions?" * "What briefing elements need attention?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check EE]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Email system supports priority flagging and calendar integration. ''Guiding Questions:'' * "How could we use priority features creatively?" * "What new calendar approaches might help?" * "Could we innovate briefing methods?" ] (else-if:$innovationCheck1 < 15)[Executives have access to AI-powered email sorting, dashboard integration features, and automated briefing tools. They're interested in streamlining decision-making. ''Guiding Questions:'' * "How could we enhance AI sorting?" * "What new dashboard features might help?" * "How might we innovate briefing formats?" * "What creative decision tools could work?" ] (else-if:$innovationCheck1 >= 15)[Executives can implement predictive analytics integration, interactive decision matrices, strategic impact visualization, and automated follow-up coordination through email. ''Guiding Questions:'' * "How could we use analytics innovatively?" * "What new visualization approaches might help?" * "How might we enhance decision support?" * "What creative follow-up tools could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check EE]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires early morning delivery and assistant confirmation. ''Guiding Questions:'' * "What's our optimal timing?" * "How do we verify receipt?" * "What follow-up is needed?" ] (else-if:$implementationCheck < 15)[Executive implementation includes: assistant preview period, briefing material coordination, priority flagging verification, and response tracking system. ''Guiding Questions:'' * "How should we coordinate with assistants?" * "What briefing materials matter?" * "How can we ensure proper flagging?" * "What tracking methods work best?" ] (else-if:$implementationCheck >= 15)[Executives use advanced implementation tools: AI-powered priority routing, automated briefing integration, strategic dashboard updates, and decision tracking protocols. ''Guiding Questions:'' * "How can we optimize AI routing?" * "What briefing integration matters?" * "How should we update dashboards?" * "What decision tracking is crucial?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check EE]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires department head input and assistant coordination. ''Guiding Questions:'' * "Who needs to provide input?" * "How do we coordinate with assistants?" * "What leadership alignment is needed?" ] (else-if:$collaborationCheck1 < 15)[Executive collaboration includes: department head review council, strategic planning team input, corporate communications alignment, and assistant coordination network. ''Guiding Questions:'' * "How should we gather leadership input?" * "What strategic alignment matters?" * "How can we coordinate messaging?" * "What assistant protocols work best?" ] (else-if:$collaborationCheck1 >= 15)[Executive team uses integrated collaboration tools: leadership review dashboard, strategic impact assessment system, cross-functional alignment tools, and automated briefing coordination. ''Guiding Questions:'' * "How can we optimize leadership review?" * "What strategic assessment matters most?" * "How should we align messaging?" * "What coordination tools work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results SF]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy involves categorizing questions by internal process and client impact. ''Guiding Questions:'' * "How should we organize categories?" * "What access points are needed?" * "How do we prioritize questions?" ] (else-if:$strategyCheck1 < 15)[Sales uses a strategic FAQ approach: searchable digital format, scenario-based organization, quick-reference summaries, and mobile-optimized layouts for client meetings. ''Guiding Questions:'' * "How should we structure for quick access?" * "What scenarios need coverage?" * "How can we support mobile use?" * "What reference tools matter most?" ] (else-if:$strategyCheck1 >= 15)[Sales implements advanced FAQ strategy: AI-powered search functionality, dynamic response generation, CRM-integrated examples, and client-specific customization options. ''Guiding Questions:'' * "How can we optimize search features?" * "What customization options matter?" * "How should we integrate with CRM?" * "What response tools work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check SF]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Sales FAQs need both technical and client-friendly language versions. ''Guiding Questions:'' * "How should we adapt technical terms?" * "What client-friendly language works best?" * "How do we maintain consistency?" ] (else-if:$adaptationCheck1 < 15)[Sales uses dual-purpose FAQ formatting: client-ready responses in blue boxes, internal notes in gray boxes, scenario-based examples, and customizable talking points. ''Guiding Questions:'' * "How should we format different response types?" * "What scenarios need examples?" * "How can we structure talking points?" * "What customization options matter?" ] (else-if:$adaptationCheck1 >= 15)[Sales has developed adaptive FAQ templates: role-specific viewing modes, dynamic response generation, industry-specific terminology options, and CRM-integrated example libraries. ''Guiding Questions:'' * "How can we optimize different views?" * "What response options matter most?" * "How should we handle terminology?" * "What examples need inclusion?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check SF]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic FAQ features include search function and printable formats. ''Guiding Questions:'' * "How could we enhance searchability?" * "What new format options might help?" * "Could we innovate organization methods?" ] (else-if:$innovationCheck1 < 15)[Sales has access to dynamic FAQ tools: customizable response generators, mobile quick-reference features, and scenario-based filtering options. ''Guiding Questions:'' * "How could we use response generators creatively?" * "What new mobile solutions might work?" * "How might we innovate scenario planning?" * "What filtering options could we add?" ] (else-if:$innovationCheck1 >= 15)[Sales can implement advanced FAQ features: AI-powered response suggestions, interactive client scenarios, voice-activated search, and augmented reality product demonstrations. ''Guiding Questions:'' * "How could we use AI creatively?" * "What interactive elements might help?" * "How might we leverage voice search?" * "What AR features could enhance understanding?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check SF]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires publishing in shared drive and notifying sales teams. ''Guiding Questions:'' * "How do we ensure access?" * "What notification system works best?" * "How do we track usage?" ] (else-if:$implementationCheck < 15)[Sales uses staged FAQ implementation: test group review, client scenario testing, regional team validation, and CRM knowledge base integration. ''Guiding Questions:'' * "How should we sequence testing?" * "What validation steps matter most?" * "How can we ensure CRM alignment?" * "What usage metrics need tracking?" ] (else-if:$implementationCheck >= 15)[Sales implements advanced FAQ systems: AI-powered content verification, automated update notifications, usage analytics tracking, and dynamic content optimization. ''Guiding Questions:'' * "How can we optimize verification?" * "What update systems matter?" * "How should we track effectiveness?" * "What optimization metrics work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check SF]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires input from sales managers and client success team. ''Guiding Questions:'' * "Who needs to review content?" * "How do we gather field feedback?" * "What approval process works best?" ] (else-if:$collaborationCheck1 < 15)[Sales uses collaborative FAQ development: client success team input, regional manager review, technical team validation, and marketing message alignment. ''Guiding Questions:'' * "How should we coordinate reviews?" * "What technical input matters most?" * "How can we align messaging?" * "What feedback loops work best?" ] (else-if:$collaborationCheck1 >= 15)[Sales has integrated FAQ collaboration: shared content development workspace, cross-functional review system, automated feedback collection, and dynamic update coordination. ''Guiding Questions:'' * "How can we optimize review processes?" * "What collaboration tools matter?" * "How should we manage updates?" * "What feedback systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results ITF]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires organizing questions by system component and error type. ''Guiding Questions:'' * "How should we categorize issues?" * "What technical hierarchy works best?" * "How do we prioritize solutions?" ] (else-if:$strategyCheck1 < 15)[IT Support uses structured FAQ strategy: troubleshooting decision trees, severity-based organization, linked knowledge base articles, and ticket resolution pathways. ''Guiding Questions:'' * "How should we map decision trees?" * "What severity levels matter most?" * "How can we integrate knowledge base?" * "What resolution paths need emphasis?" ] (else-if:$strategyCheck1 >= 15)[IT Support implements advanced FAQ strategy: automated solution suggestions, integrated testing protocols, real-time update mechanisms, and machine learning-enhanced search functionality. ''Guiding Questions:'' * "How can we optimize automation?" * "What testing integration matters?" * "How should we handle updates?" * "What search features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check ITF]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[IT Support FAQs require technical specifications and step-by-step troubleshooting formats. ''Guiding Questions:'' * "How should we format technical details?" * "What troubleshooting structure works best?" * "How do we organize different complexity levels?" ] (else-if:$adaptationCheck1 < 15)[IT Support uses tiered FAQ adaptation: severity-coded sections, collapsible technical details, linked command references, and role-based access levels. ''Guiding Questions:'' * "How should we structure severity tiers?" * "What technical details need layers?" * "How can we organize commands?" * "What access levels matter most?" ] (else-if:$adaptationCheck1 >= 15)[IT Support has developed sophisticated FAQ formatting: interactive troubleshooting flows, code snippet integration, automated testing sequences, and dynamic documentation links. ''Guiding Questions:'' * "How can we optimize troubleshooting paths?" * "What code formatting matters?" * "How should we integrate testing?" * "What documentation links work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check ITF]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic FAQ features include code block formatting and issue categorization. ''Guiding Questions:'' * "How could we enhance code presentation?" * "What new categorization methods might help?" * "Could we innovate troubleshooting flows?" ] (else-if:$innovationCheck1 < 15)[IT Support has access to interactive FAQ tools: decision tree builders, live code testing environments, and automated solution suggestions. ''Guiding Questions:'' * "How could we make decision trees more dynamic?" * "What new testing features might work?" * "How might we innovate solution finding?" * "What automation could we add?" ] (else-if:$innovationCheck1 >= 15)[IT Support can implement advanced FAQ features: AI-powered troubleshooting, virtual environment testing, chatbot integration, and predictive issue resolution. ''Guiding Questions:'' * "How could we use AI for troubleshooting?" * "What virtual testing might help?" * "How might we enhance chatbot support?" * "What predictive features could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check ITF]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires knowledge base upload and help desk notification. ''Guiding Questions:'' * "How do we integrate with existing systems?" * "What testing is needed?" * "How do we track effectiveness?" ] (else-if:$implementationCheck < 15)[IT Support uses structured FAQ implementation: technical accuracy verification, ticket system integration, automated link checking, and version control tracking. ''Guiding Questions:'' * "How should we verify accuracy?" * "What integration steps matter most?" * "How can we maintain links?" * "What version control needs attention?" ] (else-if:$implementationCheck >= 15)[IT Support implements sophisticated FAQ systems: automated testing protocols, real-time update verification, usage pattern analysis, and AI-powered content optimization. ''Guiding Questions:'' * "How can we optimize testing?" * "What update checks matter?" * "How should we analyze usage?" * "What optimization metrics work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check ITF]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires technical review team and help desk input. ''Guiding Questions:'' * "Who provides technical validation?" * "How do we incorporate help desk experience?" * "What review sequence works best?" ] (else-if:$collaborationCheck1 < 15)[IT Support uses structured FAQ collaboration: system administrator review, support team validation, documentation team coordination, and cross-shift feedback integration. ''Guiding Questions:'' * "How should we coordinate technical reviews?" * "What support insights matter most?" * "How can we align documentation?" * "What feedback methods work best?" ] (else-if:$collaborationCheck1 >= 15)[IT Support has developed comprehensive FAQ collaboration: integrated technical review platform, automated knowledge base synchronization, real-time feedback analysis, and cross-team update coordination. ''Guiding Questions:'' * "How can we optimize technical input?" * "What synchronization tools matter?" * "How should we analyze feedback?" * "What coordination systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results PF]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy involves organizing questions by shift and workstation type. ''Guiding Questions:'' * "How should we organize by location?" * "What shift-specific info matters?" * "How do we ensure accessibility?" ] (else-if:$strategyCheck1 < 15)[Production uses visual FAQ strategy: process-based organization, step-by-step guides, equipment-specific sections, and shift handover protocols. ''Guiding Questions:'' * "How should we structure visual guides?" * "What processes need coverage?" * "How can we support handovers?" * "What equipment details matter most?" ] (else-if:$strategyCheck1 >= 15)[Production implements comprehensive FAQ strategy: interactive digital displays, QR-linked resources, real-time update capabilities, and shift-specific troubleshooting workflows. ''Guiding Questions:'' * "How can we optimize digital access?" * "What QR resources matter?" * "How should we manage updates?" * "What workflows need mapping?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check PF]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Production FAQs need clear visual formats and simple, direct language. ''Guiding Questions:'' * "How should we simplify language?" * "What visual elements work best?" * "How do we ensure clarity?" ] (else-if:$adaptationCheck1 < 15)[Production uses specialized FAQ formatting: color-coded sections, numbered steps, equipment diagrams, and shift-specific annotations. ''Guiding Questions:'' * "How should we use color coding?" * "What step-by-step formats work best?" * "How can we integrate diagrams?" * "What shift notes matter most?" ] (else-if:$adaptationCheck1 >= 15)[Production has developed visual FAQ systems: interactive process flows, QR-linked video guides, touchscreen-friendly layouts, and multi-language toggle options. ''Guiding Questions:'' * "How can we optimize visual flows?" * "What interactive elements matter?" * "How should we handle languages?" * "What accessibility features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check PF]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic FAQ features include visual guides and printable checklists. ''Guiding Questions:'' * "How could we enhance visual elements?" * "What new checklist formats might help?" * "Could we innovate shift handoffs?" ] (else-if:$innovationCheck1 < 15)[Production has access to interactive FAQ tools: digital process flows, QR-linked video guides, and touchscreen-friendly interfaces. ''Guiding Questions:'' * "How could we make processes more interactive?" * "What new video features might work?" * "How might we innovate touch interfaces?" * "What digital tools could help?" ] (else-if:$innovationCheck1 >= 15)[Production can implement advanced FAQ features: augmented reality work instructions, voice-controlled displays, real-time translation, and IoT sensor integration. ''Guiding Questions:'' * "How could we use AR effectively?" * "What voice features might help?" * "How might we enhance translations?" * "What sensor data could we integrate?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check PF]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires posting at workstations and shift supervisor review. ''Guiding Questions:'' * "How do we ensure visibility?" * "What supervisor support is needed?" * "How do we track understanding?" ] (else-if:$implementationCheck < 15)[Production uses phased FAQ implementation: shift leader testing, visual guide validation, workstation placement optimization, and accessibility verification. ''Guiding Questions:'' * "How should we sequence rollout?" * "What placement strategies work best?" * "How can we verify understanding?" * "What accessibility checks matter?" ] (else-if:$implementationCheck >= 15)[Production implements integrated FAQ systems: digital display synchronization, QR code verification, usage tracking analytics, and real-time update distribution. ''Guiding Questions:'' * "How can we optimize display systems?" * "What verification tools matter?" * "How should we track engagement?" * "What update methods work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check PF]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires shift supervisor input and safety team review. ''Guiding Questions:'' * "How do we gather shift feedback?" * "What safety input is crucial?" * "How do we coordinate across shifts?" ] (else-if:$collaborationCheck1 < 15)[Production uses collaborative FAQ development: shift leader input, operator feedback sessions, equipment team consultation, and safety protocol alignment. ''Guiding Questions:'' * "How should we gather operator input?" * "What equipment details matter most?" * "How can we verify safety alignment?" * "What feedback formats work best?" ] (else-if:$collaborationCheck1 >= 15)[Production has integrated FAQ collaboration: cross-shift review system, interactive feedback collection, equipment specialist consultation, and real-time update coordination. ''Guiding Questions:'' * "How can we optimize shift coordination?" * "What feedback tools matter?" * "How should we integrate specialist input?" * "What update systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

(text-style:"bold","sway")[You've completed "Genre Quest!"] [In this game, you used questions derived from rhetorical theory (Grant-Davies) and activity theory (Wardle & Kain) to understand how particular genres, or patterns of writing, help adapt the same basic information in order to convey that information to multiple audiences.] [Use the reasoning and information you gathered through this scenario to inform your first major assignment, the Audience Analysis Report. We'll workshop ''complete first drafts'' in class on Thursday, February 12!]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results VF]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires organizing questions by compliance requirements and technical integration needs. ''Guiding Questions:'' * "How should we organize requirements?" * "What integration details need priority?" * "How do we track understanding?" ] (else-if:$strategyCheck1 < 15)[Vendors use structured FAQ strategy: security protocol sections, integration checklists, compliance verification guides, and coordinated testing procedures. ''Guiding Questions:'' * "How should we sequence information?" * "What checklist format works best?" * "How can we verify compliance?" * "What testing guides matter most?" ] (else-if:$strategyCheck1 >= 15)[Vendors require advanced FAQ strategy: role-based access controls, automated compliance tracking, cross-system integration guides, and secure update distribution protocols. ''Guiding Questions:'' * "How can we optimize access control?" * "What tracking systems matter?" * "How should we manage updates?" * "What security features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check VF]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Vendor FAQs need formal technical language and clear compliance markers. ''Guiding Questions:'' * "How should we format requirements?" * "What technical terms need definition?" * "How do we highlight compliance?" ] (else-if:$adaptationCheck1 < 15)[Vendors use structured FAQ adaptation: security classification headers, technical specification tables, compliance checklist formats, and role-specific access markers. ''Guiding Questions:'' * "How should we organize classifications?" * "What specification formats work best?" * "How can we structure checklists?" * "What access markers matter most?" ] (else-if:$adaptationCheck1 >= 15)[Vendors require sophisticated FAQ formatting: secure documentation standards, cross-reference linking systems, automated compliance tracking markers, and multi-organization terminology alignment. ''Guiding Questions:'' * "How can we optimize security formats?" * "What linking systems matter?" * "How should we track compliance?" * "What terminology needs alignment?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check VF]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic FAQ features include secure access and compliance tracking. ''Guiding Questions:'' * "How could we enhance security features?" * "What new tracking methods might help?" * "Could we innovate verification systems?" ] (else-if:$innovationCheck1 < 15)[Vendors have access to secure FAQ tools: automated compliance checkers, cross-platform integration guides, and real-time status tracking. ''Guiding Questions:'' * "How could we make compliance checking dynamic?" * "What new integration features might work?" * "How might we innovate status updates?" * "What automation could improve security?" ] (else-if:$innovationCheck1 >= 15)[Vendors can implement advanced FAQ features: blockchain verification, smart contract integration, automated testing environments, and cross-organization collaboration tools. ''Guiding Questions:'' * "How could we use blockchain creatively?" * "What smart contract features might help?" * "How might we enhance testing?" * "What collaboration tools could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check VF]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires secure distribution and compliance verification. ''Guiding Questions:'' * "How do we ensure secure access?" * "What verification steps are needed?" * "How do we track receipt?" ] (else-if:$implementationCheck < 15)[Vendors use structured FAQ implementation: security protocol verification, compliance tracking setup, cross-platform testing, and access control configuration. ''Guiding Questions:'' * "How should we verify security?" * "What tracking systems matter most?" * "How can we test accessibility?" * "What access controls need setup?" ] (else-if:$implementationCheck >= 15)[Vendors require sophisticated FAQ implementation: automated security verification, cross-organization access management, compliance monitoring systems, and real-time update tracking. ''Guiding Questions:'' * "How can we optimize security checks?" * "What access tools matter?" * "How should we monitor compliance?" * "What update tracking works best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check VF]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires legal review and vendor coordinator input. ''Guiding Questions:'' * "Who needs to approve content?" * "How do we gather vendor feedback?" * "What compliance checks are needed?" ] (else-if:$collaborationCheck1 < 15)[Vendors use structured FAQ collaboration: legal compliance review, technical team coordination, security protocol validation, and cross-organization alignment. ''Guiding Questions:'' * "How should we sequence reviews?" * "What technical input matters most?" * "How can we verify security compliance?" * "What alignment checks work best?" ] (else-if:$collaborationCheck1 >= 15)[Vendors require sophisticated FAQ collaboration: integrated compliance review system, cross-organization technical workgroups, secure feedback channels, and automated update coordination. ''Guiding Questions:'' * "How can we optimize compliance review?" * "What workgroup tools matter?" * "How should we manage feedback?" * "What coordination systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results EF]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy involves organizing questions by business impact and resource requirements. ''Guiding Questions:'' * "How should we prioritize impacts?" * "What resource details matter?" * "How do we highlight decisions?" ] (else-if:$strategyCheck1 < 15)[Executive FAQ strategy includes: strategic impact sections, risk assessment summaries, resource allocation guides, and decision-making frameworks. ''Guiding Questions:'' * "How should we present impacts?" * "What risk details need emphasis?" * "How can we clarify decisions?" * "What resource guides matter most?" ] (else-if:$strategyCheck1 >= 15)[Executives use sophisticated FAQ strategy: KPI-linked sections, strategic planning integration, automated dashboard updates, and stakeholder management protocols. ''Guiding Questions:'' * "How can we optimize KPI presentation?" * "What strategic links matter?" * "How should we support decisions?" * "What stakeholder concerns need emphasis?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check EF]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Executive FAQs need concise business language and clear strategic implications. ''Guiding Questions:'' * "How should we present business impacts?" * "What strategic elements need emphasis?" * "How do we highlight key decisions?" ] (else-if:$adaptationCheck1 < 15)[Executive FAQ adaptation includes: strategic impact summaries, risk assessment matrices, resource requirement tables, and decision-point highlighting. ''Guiding Questions:'' * "How should we format summaries?" * "What matrix designs work best?" * "How can we present resources?" * "What decision formats matter most?" ] (else-if:$adaptationCheck1 >= 15)[Executives use advanced FAQ formatting: KPI dashboard integration, strategic planning alignment, interactive decision frameworks, and stakeholder impact visualization. ''Guiding Questions:'' * "How can we optimize KPI presentation?" * "What visualization tools matter?" * "How should we structure decisions?" * "What impact measures work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check EF]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic FAQ features include priority flagging and decision tracking. ''Guiding Questions:'' * "How could we enhance priority systems?" * "What new tracking methods might help?" * "Could we innovate decision support?" ] (else-if:$innovationCheck1 < 15)[Executives have access to smart FAQ tools: strategic impact visualizations, interactive decision matrices, and automated briefing generators. ''Guiding Questions:'' * "How could we make visualizations dynamic?" * "What new decision tools might work?" * "How might we innovate briefings?" * "What automation could aid decisions?" ] (else-if:$innovationCheck1 >= 15)[Executives can implement advanced FAQ features: AI-powered strategic analysis, predictive impact modeling, real-time KPI integration, and stakeholder sentiment tracking. ''Guiding Questions:'' * "How could we use AI for strategy?" * "What predictive features might help?" * "How might we enhance KPI tracking?" * "What sentiment tools could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check EF]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires briefing integration and assistant coordination. ''Guiding Questions:'' * "How do we align with briefings?" * "What assistant support is needed?" * "How do we track usage?" ] (else-if:$implementationCheck < 15)[Executive FAQ implementation includes: strategic alignment verification, dashboard integration setup, decision support configuration, and priority tracking system. ''Guiding Questions:'' * "How should we verify alignment?" * "What dashboard elements matter?" * "How can we support decisions?" * "What tracking methods work best?" ] (else-if:$implementationCheck >= 15)[Executives use advanced FAQ implementation: AI-powered priority management, strategic dashboard synchronization, automated briefing integration, and impact tracking analytics. ''Guiding Questions:'' * "How can we optimize AI features?" * "What synchronization tools matter?" * "How should we track impact?" * "What analytics work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check EF]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires department head input and assistant coordination. ''Guiding Questions:'' * "Who needs to provide strategic input?" * "How do we coordinate with assistants?" * "What approval process works best?" ] (else-if:$collaborationCheck1 < 15)[Executive FAQ collaboration includes: strategic planning team input, department head review, corporate communications alignment, and leadership feedback integration. ''Guiding Questions:'' * "How should we gather leadership input?" * "What strategic alignment matters most?" * "How can we coordinate messaging?" * "What feedback methods work best?" ] (else-if:$collaborationCheck1 >= 15)[Executives use integrated FAQ collaboration: leadership review dashboard, strategic impact assessment team, cross-functional alignment tools, and automated update coordination. ''Guiding Questions:'' * "How can we optimize leadership review?" * "What assessment tools matter?" * "How should we manage alignment?" * "What coordination systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results SM]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires morning timing and client meeting consideration. ''Guiding Questions:'' * "What's the optimal meeting time?" * "How long should each section be?" * "What pre-meeting materials are needed?" ] (else-if:$strategyCheck1 < 15)[Sales uses strategic meeting planning: pre-meeting briefing distribution, regional team coordination, client impact scenario planning, and action item tracking system. ''Guiding Questions:'' * "How should we sequence information?" * "What scenarios need preparation?" * "How can we ensure regional coverage?" * "What follow-up system works best?" ] (else-if:$strategyCheck1 >= 15)[Sales implements advanced meeting strategy: hybrid meeting optimization, real-time CRM integration, interactive scenario planning tools, and automated follow-up coordination. ''Guiding Questions:'' * "How can we optimize hybrid participation?" * "What CRM elements matter most?" * "How should we structure interactions?" * "What automation tools work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check SM]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Sales meetings need both technical update and client-facing sections. ''Guiding Questions:'' * "How should we separate internal/external info?" * "What format works for hybrid meetings?" * "How do we balance discussion time?" ] (else-if:$adaptationCheck1 < 15)[Sales uses dual-purpose agenda format: technical briefing sections in gray, client impact sections in blue, scenario discussion blocks, and action planning segments. ''Guiding Questions:'' * "How should we format different sections?" * "What discussion prompts work best?" * "How can we structure role-playing?" * "What planning templates matter most?" ] (else-if:$adaptationCheck1 >= 15)[Sales has developed adaptive meeting templates: role-specific viewing modes, interactive scenario planning sections, CRM-integrated discussion points, and customizable follow-up frameworks. ''Guiding Questions:'' * "How can we optimize different views?" * "What interaction tools matter?" * "How should we integrate CRM data?" * "What follow-up formats work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check SM]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic meeting features include virtual attendance options and slide sharing. ''Guiding Questions:'' * "How could we enhance virtual engagement?" * "What new presentation tools might help?" * "Could we innovate role-playing methods?" ] (else-if:$innovationCheck1 < 15)[Sales has access to interactive meeting tools: scenario simulation features, real-time CRM data integration, and collaborative note-taking platforms. ''Guiding Questions:'' * "How could we make scenarios more dynamic?" * "What new collaboration features might work?" * "How might we innovate client response planning?" * "What engagement tools could we add?" ] (else-if:$innovationCheck1 >= 15)[Sales can implement advanced meeting features: AI-powered scenario generation, virtual reality client simulations, predictive response modeling, and gamified training elements. ''Guiding Questions:'' * "How could we use AI creatively?" * "What VR elements might help?" * "How might we enhance training?" * "What gamification features could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check SM]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires calendar invites and pre-meeting material distribution. ''Guiding Questions:'' * "How do we ensure material review?" * "What preparation is needed?" * "How should we track attendance?" ] (else-if:$implementationCheck < 15)[Sales uses staged meeting implementation: pre-meeting brief distribution, technology check scheduling, regional coordinator alignment, and follow-up task tracking. ''Guiding Questions:'' * "How should we sequence preparation?" * "What tech checks matter most?" * "How can we coordinate regions?" * "What follow-up system works best?" ] (else-if:$implementationCheck >= 15)[Sales implements advanced meeting management: automated preparation reminders, hybrid meeting optimization tools, real-time engagement tracking, and integrated action item monitoring. ''Guiding Questions:'' * "How can we optimize preparation?" * "What engagement tools matter?" * "How should we track participation?" * "What action item systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check SM]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires input from sales managers and technical team. ''Guiding Questions:'' * "Who needs to help plan?" * "How do we gather agenda items?" * "What coordination is needed?" ] (else-if:$collaborationCheck1 < 15)[Sales uses collaborative meeting planning: regional team input, client success consultation, technical support coordination, and marketing message alignment. ''Guiding Questions:'' * "How should we coordinate teams?" * "What input matters most?" * "How can we align messages?" * "What review process works best?" ] (else-if:$collaborationCheck1 >= 15)[Sales has developed integrated meeting collaboration: shared agenda development platform, cross-functional planning tools, automated stakeholder input collection, and dynamic content coordination. ''Guiding Questions:'' * "How can we optimize planning?" * "What collaboration tools matter?" * "How should we manage input?" * "What coordination systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results ITM]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires shift coverage consideration and technical review time. ''Guiding Questions:'' * "How do we accommodate shifts?" * "What technical prep is needed?" * "How should we structure testing discussion?" ] (else-if:$strategyCheck1 < 15)[IT Support uses phased meeting strategy: technical preview distribution, testing environment preparation, knowledge base review planning, and support coverage coordination. ''Guiding Questions:'' * "How should we sequence technical review?" * "What testing prep matters most?" * "How can we ensure coverage?" * "What documentation needs attention?" ] (else-if:$strategyCheck1 >= 15)[IT Support implements sophisticated meeting strategy: virtual testing environment integration, automated documentation updates, cross-team coordination tools, and real-time issue tracking. ''Guiding Questions:'' * "How can we optimize testing review?" * "What automation tools matter?" * "How should we coordinate teams?" * "What tracking systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check ITM]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[IT Support meetings need technical detail sections and clear testing protocols. ''Guiding Questions:'' * "How should we format technical content?" * "What testing sequence needs outlining?" * "How do we structure task assignments?" ] (else-if:$adaptationCheck1 < 15)[IT Support uses structured agenda format: severity-coded sections, technical specification blocks, testing procedure outlines, and support coverage matrices. ''Guiding Questions:'' * "How should we organize severity levels?" * "What specification formats work best?" * "How can we clarify procedures?" * "What coverage planning tools matter?" ] (else-if:$adaptationCheck1 >= 15)[IT Support has developed advanced agenda templates: interactive troubleshooting flows, live testing demonstration segments, automated task assignment blocks, and knowledge base integration points. ''Guiding Questions:'' * "How can we optimize technical review?" * "What demonstration formats matter?" * "How should we structure assignments?" * "What integration points work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check ITM]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic meeting features include screen sharing and code review tools. ''Guiding Questions:'' * "How could we enhance technical demos?" * "What new testing approaches might help?" * "Could we innovate documentation review?" ] (else-if:$innovationCheck1 < 15)[IT Support has access to interactive testing environments, virtual troubleshooting simulations, and collaborative documentation platforms. ''Guiding Questions:'' * "How could we make testing more dynamic?" * "What simulation features might work?" * "How might we innovate knowledge sharing?" * "What collaboration tools could we add?" ] (else-if:$innovationCheck1 >= 15)[IT Support can implement advanced meeting features: virtual sandbox environments, AI-powered issue prediction, augmented reality troubleshooting guides, and automated documentation generation. ''Guiding Questions:'' * "How could we use sandboxes creatively?" * "What AI features might help?" * "How might we leverage AR?" * "What automation tools could enhance learning?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check ITM]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires technical documentation sharing and shift coverage planning. ''Guiding Questions:'' * "How do we distribute documentation?" * "What shift coordination is needed?" * "How should we track testing plans?" ] (else-if:$implementationCheck < 15)[IT Support uses structured meeting implementation: testing environment preparation, knowledge base access verification, cross-shift handoff planning, and task assignment tracking. ''Guiding Questions:'' * "How should we prepare testing?" * "What documentation needs ready?" * "How can we ensure shift coverage?" * "What tracking systems matter most?" ] (else-if:$implementationCheck >= 15)[IT Support implements sophisticated meeting management: automated environment setup, real-time documentation updates, integrated task assignment system, and cross-team coordination tools. ''Guiding Questions:'' * "How can we optimize environment prep?" * "What automation tools matter?" * "How should we manage assignments?" * "What coordination features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check ITM]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires technical team input and help desk coordination. ''Guiding Questions:'' * "Who provides technical input?" * "How do we coordinate shifts?" * "What review process is needed?" ] (else-if:$collaborationCheck1 < 15)[IT Support uses structured meeting collaboration: system administrator input, support team coordination, documentation team review, and cross-shift planning. ''Guiding Questions:'' * "How should we gather technical feedback?" * "What coordination matters most?" * "How can we align documentation?" * "What planning tools work best?" ] (else-if:$collaborationCheck1 >= 15)[IT Support has integrated meeting collaboration: shared technical planning platform, automated cross-team coordination, real-time documentation updates, and dynamic task assignment system. ''Guiding Questions:'' * "How can we optimize technical planning?" * "What coordination tools matter?" * "How should we manage updates?" * "What assignment systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results PM]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires shift change timing and visual aid preparation. ''Guiding Questions:'' * "What timing works for all shifts?" * "What visuals need preparation?" * "How do we ensure consistent messaging?" ] (else-if:$strategyCheck1 < 15)[Production uses coordinated meeting strategy: shift overlap planning, visual demonstration preparation, safety review integration, and cross-shift communication tools. ''Guiding Questions:'' * "How should we manage shift transitions?" * "What demonstrations matter most?" * "How can we verify understanding?" * "What communication tools work best?" ] (else-if:$strategyCheck1 >= 15)[Production implements comprehensive meeting strategy: digital demonstration integration, real-time feedback collection, interactive training tools, and automated shift handoff coordination. ''Guiding Questions:'' * "How can we optimize demonstrations?" * "What feedback tools matter?" * "How should we structure training?" * "What handoff systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check PM]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Production meetings need visual guides and clear action steps. ''Guiding Questions:'' * "How should we format instructions?" * "What visual aids need inclusion?" * "How do we highlight key changes?" ] (else-if:$adaptationCheck1 < 15)[Production uses specialized agenda format: color-coded process changes, step-by-step demonstration blocks, safety review sections, and shift handover checklists. ''Guiding Questions:'' * "How should we organize visual elements?" * "What demonstration sequence works best?" * "How can we emphasize safety?" * "What handover tools matter most?" ] (else-if:$adaptationCheck1 >= 15)[Production has developed comprehensive agenda templates: interactive process maps, digital demonstration segments, multi-shift coordination blocks, and real-time feedback sections. ''Guiding Questions:'' * "How can we optimize visual guides?" * "What interaction tools matter?" * "How should we structure shift coordination?" * "What feedback methods work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check PM]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic meeting features include visual aids and process demonstrations. ''Guiding Questions:'' * "How could we enhance visual elements?" * "What new demonstration methods might help?" * "Could we innovate shift handoffs?" ] (else-if:$innovationCheck1 < 15)[Production has access to digital process mapping tools, interactive training modules, and cross-shift communication platforms. ''Guiding Questions:'' * "How could we make processes more interactive?" * "What training features might work?" * "How might we innovate shift coordination?" * "What communication tools could we add?" ] (else-if:$innovationCheck1 >= 15)[Production can implement advanced meeting features: augmented reality work instructions, virtual equipment demonstrations, real-time process simulation, and gamified safety training. ''Guiding Questions:'' * "How could we use AR effectively?" * "What simulation features might help?" * "How might we enhance training?" * "What gamification elements could work?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check PM]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires shift timing coordination and visual aid preparation. ''Guiding Questions:'' * "How do we coordinate shift timing?" * "What materials need ready?" * "How should we track attendance?" ] (else-if:$implementationCheck < 15)[Production uses coordinated meeting implementation: visual demonstration setup, safety review preparation, shift handover planning, and attendance verification system. ''Guiding Questions:'' * "How should we prepare demos?" * "What safety materials matter?" * "How can we verify attendance?" * "What handover tools work best?" ] (else-if:$implementationCheck >= 15)[Production implements comprehensive meeting management: digital display synchronization, interactive demonstration tools, automated attendance tracking, and cross-shift communication system. ''Guiding Questions:'' * "How can we optimize demonstrations?" * "What tracking tools matter?" * "How should we manage communication?" * "What verification systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check PM]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires supervisor input and safety team review. ''Guiding Questions:'' * "Who needs to provide input?" * "How do we coordinate shifts?" * "What safety review is needed?" ] (else-if:$collaborationCheck1 < 15)[Production uses collaborative planning: shift leader input, equipment team consultation, safety coordinator review, and operator feedback integration. ''Guiding Questions:'' * "How should we gather shift input?" * "What consultation matters most?" * "How can we integrate feedback?" * "What review process works best?" ] (else-if:$collaborationCheck1 >= 15)[Production has developed comprehensive meeting collaboration: cross-shift planning platform, integrated safety review tools, real-time operator feedback system, and dynamic demonstration coordination. ''Guiding Questions:'' * "How can we optimize shift planning?" * "What safety tools matter?" * "How should we manage feedback?" * "What coordination systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results VM]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires secure meeting platform and timeline coordination. ''Guiding Questions:'' * "What security measures are needed?" * "How do we coordinate time zones?" * "What documentation should be ready?" ] (else-if:$strategyCheck1 < 15)[Vendors use structured meeting strategy: secure document distribution, compliance review preparation, integration timeline coordination, and multi-organization scheduling. ''Guiding Questions:'' * "How should we handle sensitive info?" * "What compliance prep matters most?" * "How can we align schedules?" * "What coordination tools work best?" ] (else-if:$strategyCheck1 >= 15)[Vendors implement advanced meeting strategy: secure virtual collaboration environments, automated compliance tracking, cross-organization calendar integration, and real-time translation services. ''Guiding Questions:'' * "How can we optimize secure collaboration?" * "What tracking tools matter?" * "How should we manage schedules?" * "What translation needs attention?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check VM]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Vendor meetings need formal structure and clear compliance sections. ''Guiding Questions:'' * "How should we format requirements?" * "What security protocols need emphasis?" * "How do we structure approvals?" ] (else-if:$adaptationCheck1 < 15)[Vendors use standardized agenda format: security protocol review blocks, technical integration sections, compliance verification checklists, and coordinated timeline matrices. ''Guiding Questions:'' * "How should we present security items?" * "What integration details need structure?" * "How can we organize compliance checks?" * "What timeline formats work best?" ] (else-if:$adaptationCheck1 >= 15)[Vendors require sophisticated agenda templates: secure documentation review sections, cross-system integration planning blocks, automated compliance tracking segments, and multi-organization coordination frameworks. ''Guiding Questions:'' * "How can we optimize security review?" * "What integration planning tools matter?" * "How should we structure compliance?" * "What coordination formats work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check VM]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic meeting features include secure file sharing and compliance checklists. ''Guiding Questions:'' * "How could we enhance secure collaboration?" * "What new verification methods might help?" * "Could we innovate coordination tools?" ] (else-if:$innovationCheck1 < 15)[Vendors have access to secure virtual workspaces, automated compliance tracking, and cross-platform integration tools. ''Guiding Questions:'' * "How could we make collaboration more dynamic?" * "What tracking features might work?" * "How might we innovate integration testing?" * "What security tools could we add?" ] (else-if:$innovationCheck1 >= 15)[Vendors can implement advanced meeting features: blockchain-verified documentation sharing, AI-powered compliance monitoring, virtual integration testing environments, and real-time translation services. ''Guiding Questions:'' "How could we use blockchain creatively?" "What AI features might help?" "How might we enhance testing?" "What translation tools could improve coordination?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check VM]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires secure platform setup and compliance documentation preparation. ''Guiding Questions:'' * "How do we ensure secure access?" * "What documentation is needed?" * "How should we track participation?" ] (else-if:$implementationCheck < 15)[Vendors use structured meeting implementation: security protocol verification, compliance document distribution, multi-organization scheduling, and action item tracking. ''Guiding Questions:'' * "How should we verify security?" * "What compliance prep matters?" * "How can we coordinate schedules?" * "What tracking methods work best?" ] (else-if:$implementationCheck >= 15)[Vendors implement sophisticated meeting management: automated security clearance verification, cross-organization calendar integration, real-time translation services, and integrated compliance tracking. ''Guiding Questions:'' * "How can we optimize security checks?" * "What integration tools matter?" * "How should we manage translation?" * "What compliance systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check VM]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires legal team input and vendor coordinator review. ''Guiding Questions:'' * "Who needs to approve content?" * "How do we coordinate organizations?" * "What security review is needed?" ] (else-if:$collaborationCheck1 < 15)[Vendors use structured collaboration: compliance team input, technical coordinator review, security protocol verification, and multi-organization scheduling coordination. ''Guiding Questions:'' * "How should we gather compliance input?" * "What coordination matters most?" * "How can we verify security?" * "What scheduling tools work best?" ] (else-if:$collaborationCheck1 >= 15)[Vendors require sophisticated meeting collaboration: integrated compliance review platform, cross-organization planning tools, secure document sharing system, and automated coordination tracking. ''Guiding Questions:'' * "How can we optimize compliance review?" * "What planning tools matter?" * "How should we manage security?" * "What tracking systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results EM]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires early morning timing and briefing material preparation. ''Guiding Questions:'' * "What timing fits executive schedules?" * "What briefing materials are needed?" * "How do we structure decisions?" ] (else-if:$strategyCheck1 < 15)[Executive team uses strategic meeting planning: pre-meeting dashboard updates, strategic impact review preparation, decision point structuring, and stakeholder communication planning. ''Guiding Questions:'' * "How should we present impacts?" * "What decisions need preparation?" * "How can we streamline review?" * "What stakeholder concerns matter most?" ] (else-if:$strategyCheck1 >= 15)[Executives implement sophisticated meeting strategy: AI-powered briefing integration, real-time KPI dashboard access, strategic planning tools, and automated follow-up coordination. ''Guiding Questions:'' * "How can we optimize data presentation?" * "What strategic tools matter?" * "How should we structure decisions?" * "What automation supports leadership best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check EM]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Executive meetings need strategic focus and clear decision points. ''Guiding Questions:'' * "How should we highlight decisions?" * "What strategic elements need emphasis?" * "How do we structure updates?" ] (else-if:$adaptationCheck1 < 15)[Executive agenda uses strategic format: business impact summaries, risk assessment matrices, resource allocation tables, and decision-point frameworks. ''Guiding Questions:'' * "How should we present impacts?" * "What risk formats work best?" * "How can we clarify decisions?" * "What resource planning tools matter?" ] (else-if:$adaptationCheck1 >= 15)[Executives use advanced agenda templates: KPI dashboard integration points, strategic planning frameworks, interactive decision matrices, and stakeholder impact visualization blocks. ''Guiding Questions:'' * "How can we optimize data presentation?" * "What strategic tools matter most?" * "How should we structure decisions?" * "What visualization formats work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check EM]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic meeting features include dashboard sharing and decision tracking. ''Guiding Questions:'' * "How could we enhance data presentation?" * "What new decision tools might help?" * "Could we innovate strategic planning?" ] (else-if:$innovationCheck1 < 15)[Executives have access to interactive dashboard tools, strategic planning platforms, and automated briefing generators. ''Guiding Questions:'' * "How could we make data more interactive?" * "What planning features might work?" * "How might we innovate decision-making?" * "What automation tools could we add?" ] (else-if:$innovationCheck1 >= 15)[Executives can implement advanced meeting features: AI-powered strategic analysis, predictive impact modeling, interactive decision matrices, and real-time stakeholder sentiment tracking. ''Guiding Questions:'' * "How could we use AI strategically?" * "What prediction tools might help?" * "How might we enhance decision support?" * "What sentiment tracking could improve outcomes?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check EM]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires briefing material preparation and assistant coordination. ''Guiding Questions:'' * "How do we prepare briefings?" * "What coordination is needed?" * "How should we track decisions?" ] (else-if:$implementationCheck < 15)[Executive meetings use strategic implementation: dashboard update scheduling, briefing material distribution, decision point preparation, and follow-up task coordination. ''Guiding Questions:'' * "How should we prepare dashboards?" * "What briefing elements matter?" * "How can we structure decisions?" * "What follow-up systems work best?" ] (else-if:$implementationCheck >= 15)[Executives implement advanced meeting management: AI-powered briefing generation, real-time dashboard integration, automated decision tracking, and strategic follow-up coordination. ''Guiding Questions:'' * "How can we optimize briefings?" * "What integration tools matter?" * "How should we track decisions?" * "What automation systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check EM]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires department head input and assistant coordination. ''Guiding Questions:'' * "Who needs to provide input?" * "How do we coordinate briefings?" * "What review process is needed?" ] (else-if:$collaborationCheck1 < 15)[Executive meetings use strategic collaboration: leadership team input, strategic planning coordination, department head review, and assistant network coordination. ''Guiding Questions:'' * "How should we gather leadership input?" * "What coordination matters most?" * "How can we align departments?" * "What review process works best?" ] (else-if:$collaborationCheck1 >= 15)[Executives use integrated meeting collaboration: leadership planning platform, cross-functional coordination tools, automated briefing preparation, and strategic alignment tracking. ''Guiding Questions:'' * "How can we optimize leadership planning?" * "What coordination tools matter?" * "How should we manage briefings?" * "What alignment systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results SW]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires separating internal and client-facing content. ''Guiding Questions:'' * "How do we structure navigation?" * "What access controls are needed?" * "How should we phase updates?" ] (else-if:$strategyCheck1 < 15)[Sales uses strategic web planning: layered access implementation, CRM integration staging, response template development, and user testing coordination. ''Guiding Questions:'' * "How should we sequence updates?" * "What integration points matter most?" * "How can we ensure usability?" * "What testing approaches work best?" ] (else-if:$strategyCheck1 >= 15)[Sales implements advanced web strategy: personalized content delivery, automated CRM synchronization, AI-powered response suggestions, and multi-platform accessibility optimization. ''Guiding Questions:'' * "How can we optimize personalization?" * "What automation tools matter?" * "How should we structure content?" * "What platform features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check SW]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Sales needs both technical and client-friendly content versions. ''Guiding Questions:'' * "How should we adapt technical language?" * "What client view needs simplifying?" * "How do we maintain consistency?" ] (else-if:$adaptationCheck1 < 15)[Sales uses dual-purpose web design: internal portal with detailed system information, client portal with simplified updates, and role-specific content filtering. ''Guiding Questions:'' * "How should we structure different views?" * "What content needs translation?" * "How can we support quick access?" * "What customization options matter?" ] (else-if:$adaptationCheck1 >= 15)[Sales has developed adaptive web architecture: dynamic content generation, persona-based viewing modes, automated language adaptation, and context-aware navigation. ''Guiding Questions:'' * "How can we optimize dynamic content?" * "What persona features matter?" * "How should we handle adaptation?" * "What context tools work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check SW]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic web features include search function and document sharing. ''Guiding Questions:'' * "How could we enhance search?" * "What new sharing features might help?" * "Could we innovate navigation?" ] (else-if:$innovationCheck1 < 15)[Sales has access to dynamic web tools: interactive response builders, client portal customization, and real-time CRM integration features. ''Guiding Questions:'' * "How could we make responses more dynamic?" * "What new portal features might work?" * "How might we innovate CRM integration?" * "What customization tools could we add?" ] (else-if:$innovationCheck1 >= 15)[Sales can implement advanced web features: AI-powered content personalization, virtual client consultation spaces, predictive response generation, and augmented reality product demonstrations. ''Guiding Questions:'' * "How could we use AI creatively?" * "What virtual spaces might help?" * "How might we enhance predictions?" * "What AR features could improve understanding?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check SW]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires content migration and user notification. ''Guiding Questions:'' * "How do we manage content transfer?" * "What testing is needed?" * "How should we notify users?" ] (else-if:$implementationCheck < 15)[Sales uses staged web implementation: beta testing with select teams, CRM integration verification, content migration scheduling, and user training coordination. ''Guiding Questions:'' * "How should we sequence rollout?" * "What integration checks matter most?" * "How can we ensure data integrity?" * "What training approach works best?" ] (else-if:$implementationCheck >= 15)[Sales implements advanced web deployment: automated content migration, phased feature rollout, AI-powered testing suite, and personalized user onboarding system. ''Guiding Questions:'' * "How can we optimize migration?" * "What testing tools matter?" * "How should we manage features?" * "What onboarding methods work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check SW]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires input from sales managers and IT team. ''Guiding Questions:'' * "Who needs to review content?" * "How do we gather feedback?" * "What approvals are needed?" ] (else-if:$collaborationCheck1 < 15)[Sales uses collaborative web development: regional team input, client success consultation, technical team coordination, and user experience testing groups. ''Guiding Questions:'' * "How should we coordinate reviews?" * "What user testing matters most?" * "How can we align messaging?" * "What feedback methods work best?" ] (else-if:$collaborationCheck1 >= 15)[Sales has integrated web collaboration: shared content development platform, cross-functional review system, automated feedback collection, and dynamic user testing coordination. ''Guiding Questions:'' * "How can we optimize review process?" * "What testing tools matter?" * "How should we manage feedback?" * "What coordination systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results ITW]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires organizing technical documentation and status updates. ''Guiding Questions:'' * "How do we structure documentation?" * "What status displays are needed?" * "How should we manage versions?" ] (else-if:$strategyCheck1 < 15)[IT Support uses structured web strategy: knowledge base architecture planning, monitoring dashboard integration, ticket system synchronization, and documentation workflow design. ''Guiding Questions:'' * "How should we organize knowledge?" * "What monitoring tools matter most?" * "How can we integrate tickets?" * "What workflow systems work best? ] (else-if:$strategyCheck1 >= 15)[IT Support implements sophisticated web strategy: automated documentation updates, real-time system monitoring, AI-powered search optimization, and integrated testing environment deployment. ''Guiding Questions:'' * "How can we optimize automation?" * "What monitoring features matter?" * "How should we enhance search?" * "What testing tools work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check ITW]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[IT Support needs technical documentation layers and status display options. ''Guiding Questions:'' * "How should we layer technical detail?" * "What status views are needed?" * "How do we organize complexity levels?" ] (else-if:$adaptationCheck1 < 15)[IT Support uses tiered web adaptation: complexity-level toggle options, role-based documentation access, customizable dashboard views, and searchable knowledge base formats. ''Guiding Questions:'' * "How should we structure tiers?" * "What viewing options matter most?" * "How can we customize dashboards?" * "What search features need adapting?" ] (else-if:$adaptationCheck1 >= 15)[IT Support has developed sophisticated web customization: AI-powered content recommendation, user-specific documentation paths, adaptive troubleshooting flows, and personalized workspace configuration. ''Guiding Questions:'' * "How can we optimize recommendations?" * "What path options matter?" * "How should we adapt workflows?" * "What workspace features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check ITW]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic web features include documentation search and status updates. ''Guiding Questions:'' * "How could we enhance documentation?" * "What new status features might help?" * "Could we innovate troubleshooting?" ] (else-if:$innovationCheck1 < 15)[IT Support has access to interactive tools: virtual testing environments, automated documentation generators, and real-time monitoring dashboards. ''Guiding Questions:'' * "How could we make testing more dynamic?" * "What new documentation tools might work?" * "How might we innovate monitoring?" * "What automation features could we add?" ] (else-if:$innovationCheck1 >= 15)[IT Support can implement advanced features: AI-powered problem prediction, virtual reality training environments, automated knowledge base evolution, and augmented reality troubleshooting guides. ''Guiding Questions:'' * "How could we use AI for prediction?" * "What VR features might help?" * "How might we enhance knowledge base?" * "What AR tools could improve support?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check ITW]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires documentation transfer and system testing. ''Guiding Questions:'' * "How do we verify documentation?" * "What testing sequence is needed?" * "How should we track updates?" ] (else-if:$implementationCheck < 15)[IT Support uses structured implementation: knowledge base migration, monitoring system integration, ticket system synchronization, and staged feature deployment. ''Guiding Questions:'' * "How should we sequence migration?" * "What integration steps matter most?" * "How can we maintain service?" * "What deployment checks work best?" ] (else-if:$implementationCheck >= 15)[IT Support implements sophisticated deployment: automated documentation verification, real-time system monitoring setup, AI-powered testing automation, and zero-downtime migration. Guiding Questions: * "How can we optimize verification?" * "What monitoring tools matter?" * "How should we automate testing?" * "What migration methods work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check ITW]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires technical review team and documentation team input. ''Guiding Questions:'' * "Who provides technical review?" * "How do we coordinate documentation?" * "What testing collaboration is needed?" ] (else-if:$collaborationCheck1 < 15)[IT Support uses structured collaboration: system administrator input, knowledge base team coordination, user interface testing groups, and cross-shift feedback collection. ''Guiding Questions:'' * "How should we gather technical input?" * "What testing groups matter most?" * "How can we coordinate shifts?" * "What feedback systems work best?" ] (else-if:$collaborationCheck1 >= 15)[IT Support has developed comprehensive collaboration: integrated technical review platform, automated documentation workflow, cross-team testing coordination, and real-time feedback analysis. ''Guiding Questions:'' * "How can we optimize review process?" * "What workflow tools matter?" * "How should we coordinate testing?" * "What analysis methods work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results PW]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires mobile-friendly design and clear status indicators. ''Guiding Questions:'' * "How do we ensure mobile access?" * "What status displays work best?" * "How should we organize instructions?" ] (else-if:$strategyCheck1 < 15)[Production uses visual web strategy: shift-specific portal development, equipment status integration, mobile-first design implementation, and QR code system planning. ''Guiding Questions:'' * "How should we structure shift access?" * "What status tools matter most?" * "How can we optimize mobile use?" * "What QR systems work best?" ] (else-if:$strategyCheck1 >= 15)[Production implements comprehensive web strategy: interactive training module deployment, real-time status synchronization, cross-device optimization, and augmented reality integration planning. ''Guiding Questions:'' * "How can we optimize training?" * "What synchronization tools matter?" * "How should we handle devices?" * "What AR features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check PW]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Production needs shift-specific views and simplified navigation. ''Guiding Questions:'' * "How should we adapt for shifts?" * "What navigation needs simplifying?" * "How do we ensure accessibility?" ] (else-if:$adaptationCheck1 < 15)[Production uses specialized web adaptation: shift-optimized layouts, role-based content filtering, mobile-responsive design, and visual instruction formatting. ''Guiding Questions:'' * "How should we customize layouts?" * "What content filters matter most?" * "How can we optimize mobile view?" * "What visual formats work best?" ] (else-if:$adaptationCheck1 >= 15)[Production has developed comprehensive web customization: shift-aware content delivery, device-specific optimization, interactive training adaptation, and accessibility-enhanced interfaces. ''Guiding Questions:'' * "How can we optimize shift content?" * "What device features matter?" * "How should we adapt training?" * "What accessibility tools work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check PW]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic web features include mobile access and visual guides. ''Guiding Questions:'' * "How could we enhance mobile features?" * "What new visual tools might help?" * "Could we innovate shift communication?" ] (else-if:$innovationCheck1 < 15)[Production has access to interactive tools: digital process mapping, QR-linked documentation, and real-time status tracking. ''Guiding Questions:'' * "How could we make processes more interactive?" * "What new QR features might work?" * "How might we innovate tracking?" * "What visualization tools could we add?" ] (else-if:$innovationCheck1 >= 15)[Production can implement advanced features: augmented reality work instructions, IoT sensor integration, voice-controlled interfaces, and gamified training modules. ''Guiding Questions:'' * "How could we use AR effectively?" * "What IoT features might help?" * "How might we enhance voice control?" * "What gamification could improve learning?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check PW]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires shift-by-shift rollout and device testing. ''Guiding Questions:'' * "How do we manage shift transitions?" * "What device checks are needed?" * "How should we verify access?" ] (else-if:$implementationCheck < 15)[Production uses phased implementation: workstation compatibility testing, shift-specific training coordination, mobile access verification, and QR system deployment. ''Guiding Questions:'' * "How should we sequence training?" * "What compatibility checks matter most?" * "How can we ensure access?" * "What verification methods work best?" ] (else-if:$implementationCheck >= 15)[Production implements comprehensive deployment: cross-device optimization, interactive training module rollout, real-time status system integration, and automated accessibility verification. ''Guiding Questions:'' * "How can we optimize deployment?" * "What training tools matter?" * "How should we manage integration?" * "What verification systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check PW]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires shift supervisor input and safety team review. ''Guiding Questions:'' * "Who needs to provide input?" * "How do we gather shift feedback?" * "What safety review is needed?" ] (else-if:$collaborationCheck1 < 15)[Production uses collaborative development: shift leader input, equipment team consultation, safety coordinator review, and operator testing groups. ''Guiding Questions:'' * "How should we coordinate shifts?" * "What testing groups matter most?" * "How can we verify safety?" * "What feedback methods work best?" ] (else-if:$collaborationCheck1 >= 15)[Production has integrated collaboration: cross-shift review system, interactive feedback collection, safety verification workflow, and real-time user testing coordination. ''Guiding Questions:'' * "How can we optimize shift input?" * "What testing tools matter?" * "How should we verify safety?" * "What coordination systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results VW]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires secure portal design and compliance documentation structure. ''Guiding Questions:'' * "How do we ensure security?" * "What documentation paths are needed?" * "How should we track access?" ] (else-if:$strategyCheck1 < 15)[Vendors use structured portal strategy: security protocol implementation, documentation library organization, compliance tracking integration, and multi-organization access planning. ''Guiding Questions:'' * "How should we layer security?" * "What documentation tools matter most?" * "How can we verify compliance?" * "What access systems work best?" ] (else-if:$strategyCheck1 >= 15)[Vendors implement advanced web strategy: blockchain-verified access control, automated compliance monitoring, cross-system integration management, and secure collaboration platform deployment. ''Guiding Questions:'' * "How can we optimize security?" * "What verification tools matter?" * "How should we manage integration?" * "What collaboration features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check VW]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Vendors need role-based access and compliance-focused layouts. ''Guiding Questions:'' * "How should we adapt security levels?" * "What compliance views are needed?" * "How do we customize access?" ] (else-if:$adaptationCheck1 < 15)[Vendors use structured web adaptation: organization-specific portals, customized compliance dashboards, role-filtered documentation, and secure communication interfaces. ''Guiding Questions:'' * "How should we customize portals?" * "What dashboard views matter most?" * "How can we filter documentation?" * "What communication tools need adapting?" ] (else-if:$adaptationCheck1 >= 15)[Vendors require sophisticated web customization: organization-aware content delivery, automated compliance reporting views, integration-specific documentation paths, and personalized collaboration spaces. ''Guiding Questions:'' * "How can we optimize organization views?" * "What reporting features matter?" * "How should we adapt documentation?" * "What collaboration tools work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check VW]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic web features include secure login and document repository. ''Guiding Questions:'' * "How could we enhance security?" * "What new document features might help?" * "Could we innovate access control?" ] (else-if:$innovationCheck1 < 15)[Vendors have access to secure collaboration tools: automated compliance checking, cross-platform integration testing, and real-time status monitoring. ''Guiding Questions:'' * "How could we make compliance more dynamic?" * "What new testing tools might work?" * "How might we innovate monitoring?" * "What security features could we add?" ] (else-if:$innovationCheck1 >= 15)[Vendors can implement advanced features: blockchain-verified documentation, AI-powered integration verification, virtual testing environments, and cross-organization collaboration spaces. ''Guiding Questions:'' * "How could we use blockchain creatively?" * "What AI features might help?" * "How might we enhance testing?" * "What collaboration tools could improve coordination?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check VW]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires security verification and access testing. ''Guiding Questions:'' * "How do we verify security?" * "What access tests are needed?" * "How should we track deployment?" ] (else-if:$implementationCheck < 15)[Vendors use structured implementation: security protocol verification, phased access rollout, compliance system integration, and cross-organization testing coordination. ''Guiding Questions:'' * "How should we sequence security checks?" * "What rollout steps matter most?" * "How can we verify compliance?" * "What coordination methods work best?" ] (else-if:$implementationCheck >= 15)[Vendors implement sophisticated deployment: automated security verification, staged integration testing, cross-platform compatibility checking, and real-time compliance monitoring setup. ''Guiding Questions:'' * "How can we optimize security?" * "What testing tools matter?" * "How should we manage integration?" * "What monitoring systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check VW]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires legal team review and vendor coordinator input. ''Guiding Questions:'' * "Who needs to approve changes?" * "How do we coordinate vendors?" * "What security review is needed?" ] (else-if:$collaborationCheck1 < 15)[Vendors use structured collaboration: compliance team input, security review coordination, cross-organization testing groups, and user acceptance verification. ''Guiding Questions:'' * "How should we gather compliance input?" * "What testing groups matter most?" * "How can we coordinate organizations?" * "What verification methods work best?" ] (else-if:$collaborationCheck1 >= 15)[Vendors require sophisticated collaboration: integrated compliance review platform, cross-organization testing coordination, automated security verification workflow, and real-time feedback analysis. ''Guiding Questions:'' * "How can we optimize compliance review?" * "What coordination tools matter?" * "How should we verify security?" * "What analysis systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]

[Have one team member roll for Strategy. Then, add their Strategy modifier to the number they rolled, and enter it below!] (input-box:2bind $strategyInput1,"=XX=") [[Next->Strategy Results EW]]

(set: $strategyInput1 to (num: $strategyInput1)) (set: $strategyCheck1 to $strategyInput1) (if:$strategyCheck1 < 11)[Basic strategy requires dashboard integration and strategic overview design. ''Guiding Questions:'' * "How do we present metrics?" * "What overview formats work best?" * "How should we structure updates?" ] (else-if:$strategyCheck1 < 15)[Executive portal uses strategic implementation: KPI dashboard development, impact visualization planning, decision support tool integration, and stakeholder communication platform design. ''Guiding Questions:'' * "How should we organize metrics?" * "What visualization tools matter most?" * "How can we support decisions?" * "What communication systems work best?" ] (else-if:$strategyCheck1 >= 15)[Executives implement sophisticated web strategy: AI-powered analytics integration, predictive modeling deployment, strategic resource tracking optimization, and automated briefing system development. ''Guiding Questions:'' * "How can we optimize analytics?" * "What prediction tools matter?" * "How should we track resources?" * "What automation features work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Adaptation Check->Adaptation Check EW]].]

(set: $adaptationInput1 to (num: $adaptationInput1)) (set: $adaptationCheck1 to $adaptationInput1) (if:$adaptationCheck1 < 11)[Executives need customized dashboards and strategic view options. ''Guiding Questions:'' * "How should we adapt metrics?" * "What view options are needed?" * "How do we customize reports?" ] (else-if:$adaptationCheck1 < 15)[Executive portal uses strategic adaptation: role-specific dashboard views, customizable KPI displays, personalized briefing formats, and stakeholder communication interfaces. ''Guiding Questions:'' * "How should we customize dashboards?" * "What KPI views matter most?" * "How can we adapt briefings?" * "What communication tools need customizing?" ] (else-if:$adaptationCheck1 >= 15)[Executives use advanced web customization: AI-powered insight adaptation, personalized analytics views, strategic planning interfaces, and customizable decision support tools. ''Guiding Questions:'' * "How can we optimize insights?" * "What analytics features matter?" * "How should we adapt planning tools?" * "What decision support needs customizing?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Innovation Check->Innovation Check EW]].]

(set: $innovationInput1 to (num: $innovationInput1)) (set: $innovationCheck1 to $innovationInput1) (if:$innovationCheck1 < 11)[Basic web features include dashboard access and report generation. ''Guiding Questions:'' * "How could we enhance dashboards?" * "What new reporting features might help?" * "Could we innovate data presentation?" ] (else-if:$innovationCheck1 < 15)[Executives have access to interactive tools: strategic planning interfaces, real-time KPI tracking, and automated briefing generators. ''Guiding Questions:'' * "How could we make planning more dynamic?" * "What new tracking tools might work?" * "How might we innovate briefings?" * "What automation features could we add?" ] (else-if:$innovationCheck1 >= 15)[Executives can implement advanced features: AI-powered strategic analysis, predictive modeling interfaces, virtual strategic planning spaces, and real-time stakeholder sentiment tracking. ''Guiding Questions:'' * "How could we use AI strategically?" * "What prediction tools might help?" * "How might we enhance planning?" * "What sentiment tracking could improve decisions?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Implementation Check->Implementation Check EW]].]

(set: $implementationInput1 to (num: $implementationInput1)) (set: $implementationCheck1 to $implementationInput1) (if:$implementationCheck1 < 11)[Basic implementation requires dashboard migration and access verification. ''Guiding Questions:'' * "How do we transfer dashboards?" * "What testing is needed?" * "How should we verify functionality?" ] (else-if:$implementationCheck < 15)[Executive portal uses strategic implementation: KPI dashboard migration, phased feature rollout, decision support tool integration, and user acceptance testing. ''Guiding Questions:'' * "How should we sequence migration?" * "What features matter most?" * "How can we ensure continuity?" * "What testing approaches work best?" ] (else-if:$implementationCheck >= 15)[Executives implement advanced deployment: AI-powered analytics migration, strategic tool integration, automated dashboard verification, and personalized feature activation. ''Guiding Questions:'' * "How can we optimize migration?" * "What integration tools matter?" * "How should we verify features?" * "What activation methods work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] [When you're ready, move on to the [[Collaboration Check->Collaboration Check EW]].]

(set: $collaborationInput1 to (num: $collaborationInput1)) (set: $collaborationCheck1 to $collaborationInput1) (if:$collaborationCheck1 < 11)[Basic collaboration requires department head input and assistant coordination. ''Guiding Questions:'' * "Who needs to review changes?" * "How do we gather leadership feedback?" * "What strategic input is needed?" ] (else-if:$collaborationCheck1 < 15)[Executive portal uses strategic collaboration: leadership team input, strategic planning coordination, department head review groups, and user acceptance testing. ''Guiding Questions:'' * "How should we gather leadership input?" * "What testing groups matter most?" * "How can we align departments?" * "What feedback methods work best?" ] (else-if:$collaborationCheck1 >= 15)[Executives use integrated collaboration: leadership review platform, cross-functional testing coordination, strategic alignment verification, and automated feedback analysis. ''Guiding Questions:'' * "How can we optimize leadership review?" * "What coordination tools matter?" * "How should we verify alignment?" * "What analysis systems work best?" ] [Talk with your team and take notes on your responses! These notes will form the basis of your Audience Analysis paper.] (if: $rounds is 1)[When you're ready, move on to your [[second audience->Second Audience]].] (else-if: $rounds is 2)[When you're ready, move on to your [[third audience->Third Audience]].] (else-if: $rounds is 3)[When you're ready, move on to the [[Conclusion]].]