diff --git a/work/tbx/ask.md b/work/tbx/ask.md
new file mode 100644
index 0000000..071cd18
--- /dev/null
+++ b/work/tbx/ask.md
@@ -0,0 +1,85 @@
+Certainly! I'll provide multiple variations for each section, so you can pick and choose the elements that resonate best. Feel free to mix and match across the variations to create a response that fits your needs.
+
+Priorities and needle movers:
+Variation 1:
+- Leveraging Meraki's robust API to automate network provisioning and management tasks
+- Implementing Fortinet's Security Fabric to provide comprehensive, integrated protection across the entire digital attack surface
+- Deploying a SOAR solution to streamline incident response and optimize security operations
+- Utilizing EDR to proactively hunt for and mitigate advanced threats
+Variation 2: 
+- Integrating Meraki, Fortinet, and other best-of-breed tools to create a unified, automated network and security stack
+- Building custom applications and workflows using the Meraki Dashboard API to drive business value
+- Enhancing infrastructure resilience and scalability through the adoption of cloud-managed networking solutions
+- Improving digital experience by correlating data from network performance monitoring and application performance management tools
+
+Key architectures/technologies:
+Variation 1:
+- Meraki's cloud-based platform for simplified management of wireless, switching, security, and IoT devices
+- Fortinet's FortiGate next-generation firewalls for advanced threat protection and SD-WAN capabilities 
+- Ansible for infrastructure-as-code and network automation at scale
+- Endpoint detection and response (EDR) solutions like CrowdStrike or SentinelOne for advanced threat hunting and remediation
+Variation 2:
+- Software-defined networking (SDN) principles leveraging Meraki and other programmable network solutions
+- Fortinet's Security Fabric architecture to enable broad visibility, integrated protection, and automated operations
+- Cloud-hosted DDI (DNS, DHCP, IPAM) for centralized, software-driven control of core network services
+- Security orchestration, automation and response (SOAR) tools like Splunk Phantom or Palo Alto Networks Cortex XSOAR
+
+Resources assessment:
+Variation 1:  
+- Existing team has strong skills in network engineering and security operations but may need to upskill in areas like Python scripting and API integration
+- Dedicated automation specialists could accelerate our infrastructure-as-code initiatives
+- Cross-training between NetOps and SecOps teams would improve collaboration and break down silos
+Variation 2:
+- Current personnel have deep knowledge of Meraki, Fortinet and Ansible but may require additional training on SOAR and EDR solutions
+- Augmenting the team with data scientists and developers could unlock new use cases leveraging the Meraki Dashboard API 
+- Creating a Cloud Center of Excellence would provide governance and best practices as we transition to cloud-managed networking
+
+Potential barriers:
+Variation 1:
+- Complex, heterogeneous environment with multiple management platforms and limited API support in some areas
+- Organizational resistance to change and preference for manual processes over automation
+- Lack of clear strategy and prioritization from leadership on digital transformation initiatives  
+- Inconsistent adherence to security best practices and policies across the organization
+Variation 2: 
+- Technical debt and legacy systems that are difficult to integrate and automate
+- Skill gaps in areas like data engineering, API development, and cloud native technologies  
+- Procurement and budgeting processes that don't align with the fast pace of technological change
+- Difficulty quantifying the ROI of automation and justifying the upfront investments required
+
+Process issues:  
+Variation 1:
+- Immature incident response processes that rely heavily on manual triage and analysis
+- Inconsistent change management procedures leading to unplanned outages and performance issues
+- Security and compliance controls that impede agility and slow down the pace of innovation
+- Lack of standardized development processes and CI/CD pipelines for network automation code
+Variation 2:
+- Reactive rather than proactive problem management resulting in "firefighting" mode
+- Insufficient monitoring and observability of the end-to-end network and security stack
+- Disconnect between the NetOps and SecOps teams in terms of priorities, tooling, and processes  
+- Over-reliance on tribal knowledge and lack of documentation for key systems and workflows
+
+Resource issues:
+Variation 1:  
+- Difficulty attracting and retaining top talent in a competitive job market
+- Limited training and professional development opportunities for engineers to keep up with the latest technologies
+- Budget constraints forcing tradeoffs between innovation and "keeping the lights on"
+- Lack of diversity in the team leading to blind spots and missed opportunities 
+Variation 2:
+- Workforce spread thin supporting too many different tools and platforms
+- Vendor lock-in and unpredictable pricing models for some of our core systems
+- Shortage of personnel with experience in both networking and security disciplines
+- Inability to scale the team quickly enough to meet the growing demands of the business
+
+Team issues:  
+Variation 1:
+- Communication breakdowns and lack of visibility between different groups working on network and security projects
+- Unclear roles and responsibilities leading to duplication of effort and missed handoffs
+- Cultural divide between the "old guard" and the "new guard" in terms of embracing innovation and automation
+- Lack of a shared vision and roadmap for the future of our network and security architecture 
+Variation 2:  
+- Finger-pointing and blame games that undermine trust and collaboration
+- Unhealthy competition for limited resources and recognition  
+- Fear of failure and risk aversion stifling experimentation and continuous improvement
+- Lack of psychological safety and fear of speaking up about problems and challenges
+
+I hope these variations give you plenty of options to choose from as you put together your response. Let me know if you need any other assistance!
\ No newline at end of file