Personal information:
├── Full name and display name
├── Professional title and role
├── Contact information (email, phone)
├── Profile photo (optional)
├── Timezone and location
├── Preferred language
├── Communication preferences
└── Accessibility needs

Role definition:
├── Primary role: Project Manager, Scrum Master, Engineering Manager
├── Secondary roles: Product Owner, Team Lead, Consultant
├── Reporting structure: Individual contributor vs manager
├── Decision authority: Full authority vs consultative
├── Scope of responsibility: Single team vs multi-team vs portfolio
├── Geographic scope: Local vs regional vs global
├── Industry focus: Software, Healthcare, Finance, etc.
└── Specialization areas: Agile, DevOps, Digital Transformation

Role-based customization:
├── Project Manager → Focus on delivery metrics, stakeholder communication
├── Scrum Master → Emphasize team velocity, impediment tracking
├── Engineering Manager → Balance technical debt with feature delivery
├── Product Owner → Prioritize customer value, market feedback
├── Team Lead → Individual performance, skill development
├── Consultant → Client satisfaction, knowledge transfer
├── Executive → Portfolio health, strategic alignment
└── Specialist → Domain-specific metrics, best practices

Experience-based adaptation:
├── Junior (0-2 years) → More guidance, detailed explanations
├── Mid-level (2-5 years) → Balanced insights, skill development focus
├── Senior (5-10 years) → Strategic insights, leadership opportunities
├── Executive (10+ years) → High-level summaries, business impact
├── Expert (15+ years) → Industry trends, innovation opportunities
└── Consultant → Client-focused, transferable insights

Company information:
├── Company size: Startup (<50), SMB (50-500), Enterprise (500+)
├── Industry: Software, Healthcare, Finance, Manufacturing, etc.
├── Business model: B2B, B2C, B2B2C, Platform, Marketplace
├── Stage: Early startup, Growth, Mature, Transformation
├── Culture: Fast-paced, Methodical, Innovation-focused, Process-driven
├── Geographic presence: Local, National, International, Global
├── Regulatory environment: Highly regulated vs flexible
└── Competitive landscape: Established vs emerging market

Team context:
├── Team size: Individual contributor, Small team (2-8), Large team (8+)
├── Team distribution: Co-located, Hybrid, Fully remote
├── Team composition: Developers, Designers, QA, DevOps, Product
├── Seniority mix: Junior-heavy, Balanced, Senior-heavy
├── Skill diversity: Specialized vs full-stack vs cross-functional
├── Team stability: High turnover vs stable vs growing
├── Collaboration style: Autonomous vs collaborative vs directed
└── Performance culture: Individual vs team vs collective focus

Project characteristics:
├── Project types: Feature development, Infrastructure, Research, Maintenance
├── Project duration: Short sprints vs long initiatives vs ongoing operations
├── Project complexity: Simple features vs complex systems vs transformations
├── Stakeholder complexity: Internal team vs cross-department vs external clients
├── Risk tolerance: Conservative vs balanced vs aggressive
├── Innovation level: Incremental vs breakthrough vs experimental
├── Budget constraints: Tight vs flexible vs unconstrained
└── Timeline pressure: Relaxed vs moderate vs aggressive deadlines

Success metrics:
├── Primary KPIs: Delivery speed, Quality, Customer satisfaction, Revenue
├── Quality standards: Minimum viable vs high quality vs perfection
├── Performance expectations: Meet targets vs exceed vs innovate
├── Risk management: Risk-averse vs balanced vs risk-taking
├── Stakeholder satisfaction: Internal focus vs customer focus vs balanced
├── Innovation emphasis: Stability vs incremental vs breakthrough
├── Efficiency focus: Cost optimización vs speed vs quality
└── Strategic alignment: Tactical execution vs strategic contribution

Experience assessment:
├── Years in current role: 0-1, 1-3, 3-5, 5-10, 10+ years
├── Years in project management: Total PM experience across roles
├── Industry experience: Years in current industry vs cross-industry
├── Team leadership experience: Individual contributor vs team lead vs manager
├── Methodology experience: Waterfall, Agile, Scrum, Kanban, SAFe, Custom
├── Tool proficiency: Jira, Azure DevOps, Monday, Asana, Custom tools
├── Domain expertise: Technical, Business, Process, People, Strategy
└── Certification level: None, Basic (PMP, CSM), Advanced (PMI-ACP, SAFe), Expert

Skill assessment:
├── Technical skills: Understanding of development process, architecture
├── Business skills: Market understanding, financial acumen, strategy
├── People skills: Leadership, communication, conflict resolution, coaching
├── Process skills: Methodology expertise, optimización, change management
├── Analytical skills: Data analysis, metrics interpretation, forecasting
├── Strategic skills: Vision setting, roadmap planning, stakeholder management
├── Innovation skills: Creative problem solving, experimentation, transformation
└── Cross-functional skills: Marketing, Sales, Operations, Finance understanding

Learning style:
├── Information processing: Visual, Auditory, Kinesthetic, Reading/Writing
├── Detail preference: High-level summaries vs detailed analysis
├── Learning pace: Quick overview vs deep dive vs progressive disclosure
├── Feedback style: Direct vs diplomatic vs coaching-oriented
├── Example preference: Abstract concepts vs concrete examples vs case studies
├── Complexity tolerance: Simple explanations vs nuanced analysis
├── Context preference: Immediate actionable vs strategic understanding
└── Validation style: Data-driven vs experience-based vs consensus-seeking

Professional development:
├── Career goals: Individual contributor vs management vs executive track
├── Skill development priorities: Technical vs business vs leadership
├── Learning time availability: Limited vs moderate vs extensive
├── Preferred learning methods: Reading, Videos, Hands-on, Mentoring, Courses
├── Certification interests: Industry certifications vs internal training
├── Knowledge sharing: Consumer vs contributor vs thought leader
├── Innovation involvement: Follower vs adopter vs pioneer
└── Career timeline: Short-term tactical vs long-term strategic focus

Primary methodology:
├── Agile/Scrum: Sprint-based development with ceremonies
├── Kanban: Continuous flow with WIP limits
├── Waterfall: Sequential phases with gates
├── SAFe: Scaled Agile for large organizations
├── Lean: Value stream optimización
├── Hybrid: Combination of methodologies
├── Custom: Organization-specific approach
└── Flexible: Adapt methodology to project needs

Methodology preferences:
├── Planning horizon: Short sprints vs longer cycles vs continuous
├── Change tolerance: Embrace change vs controlled change vs minimal change
├── Documentation level: Minimal vs balanced vs comprehensive
├── Process rigor: Lightweight vs structured vs formal
├── Team autonomy: High autonomy vs guided vs directed
├── Stakeholder involvement: Minimal vs regular vs continuous
├── Risk management: Reactive vs proactive vs predictive
└── Quality approach: Continuous vs milestone-based vs final validation

Communication preferences:
├── Meeting frequency: Daily vs weekly vs as-needed
├── Meeting style: Structured vs informal vs hybrid
├── Decision making: Consensus vs consultative vs directive
├── Conflict resolution: Direct vs diplomatic vs facilitatested
├── Feedback delivery: Immediate vs scheduled vs continuous
├── Status reporting: Formal vs informal vs automated
├── Stakeholder engagement: Regular vs milestone vs exception-based
└── Team interaction: High-touch vs balanced vs autonomous

Collaboration approach:
├── Team structure: Hierarchical vs flat vs matrix
├── Work distribution: Centralized vs distributed vs self-organizing
├── Knowledge sharing: Formal vs informal vs continuous
├── Innovation approach: Top-down vs bottom-up vs collaborative
├── Problem solving: Individual vs team vs cross-functional
├── Resource sharing: Dedicated vs shared vs flexible
├── Performance management: Individual vs team vs collective
└── Culture building: Formal vs organic vs intentional

Technology comfort:
├── Technical proficiency: Non-technical vs technical vs expert
├── Tool adoption: Conservative vs early adopter vs bleeding edge
├── Integration complexity: Simple vs moderate vs complex
├── Automation preference: Manual vs semi-automated vs fully automated
├── Data comfort: Basic metrics vs advanced analytics vs data science
├── Mobile usage: Desktop-only vs mobile-friendly vs mobile-first
├── Collaboration tools: Basic vs integrated vs advanced
└── Security consciousness: Basic vs security-aware vs security-expert

Workflow preferences:
├── Information density: Minimal vs balanced vs comprehensive
├── Visual style: Text-based vs visual vs interactive
├── Navigation style: Linear vs exploratory vs search-driven
├── Customization level: Standard vs personalized vs highly customized
├── Notification style: Minimal vs balanced vs comprehensive
├── Response time: Immediate vs scheduled vs batch
├── Integration depth: Surface-level vs deep vs comprehensive
└── Backup preferences: Manual vs automated vs redundant

Primary schedule:
├── Work days: Monday-Friday, Monday-Saturday, Custom
├── Start time: 7:00 AM, 8:00 AM, 9:00 AM, 10:00 AM, Flexible
├── End time: 4:00 PM, 5:00 PM, 6:00 PM, 7:00 PM, Flexible
├── Lunch break: 30 min, 1 hour, Flexible, None
├── Time zone: Auto-detect, Manual override, Multiple zones
├── Daylight saving: Auto-adjust, Manual, Ignore
├── Holiday calendar: Country/region specific, Company calendar
└── Vacation tracking: Manual entry, Calendar integration, HR system sync

Flexible arrangements:
├── Remote work days: Specific days, Hybrid schedule, Fully remote
├── Compressed schedule: 4x10 hours, 9x80 hours, Custom
├── Flexible start/end: Core hours with flexible boundaries
├── Seasonal adjustments: Summer hours, Holiday schedules
├── Travel accommodations: Different time zones, irregular schedules
├── Part-time arrangements: Reduced hours, Specific days
├── Sabbatical periods: Extended leave, Reduced availability
└── Emergency availability: After-hours contact, Weekend coverage

Status communication:
├── Available: Actively working, responsive to messages
├── Busy: Working but may have delayed responses
├── In meeting: Unavailable for immediate communication
├── Focus time: Deep work, minimal interruptions only
├── Away: Temporarily unavailable, back soon
├── Lunch: On break, back at specific time
├── Off work: Outside work hours, emergency only
└── Vacation: Extended absence, delegate contact provided

Automatic status:
├── Calendar integration: Meeting status from calendar
├── Activity detection: Active vs idle status
├── Location awareness: Office vs remote vs mobile
├── Project context: Which project currently working on
├── Urgency escalation: When to override availability status
├── Team coordination: Shared team availability view
├── Stakeholder visibility: What external stakeholders see
└── Historical patterns: Typical availability trends

Deep work blocks:
├── Morning focus: 2-4 hour blocks for complex work
├── Afternoon focus: Post-lunch productivity optimización
├── Full-day focus: Minimal meetings, maximum productivity
├── Weekly patterns: Consistent focus time scheduling
├── Project-specific: Dedicated time for specific initiatives
├── Creative time: Innovation, planning, strategic thinking
├── Administrative time: Email, reports, routine tasks
└── Learning time: Skill development, training, research

Focus protection:
├── Meeting-free zones: Protected time blocks
├── Notification management: Reduced interruptions during focus
├── Communication delays: Batch processing of non-urgent items
├── Escalation thresholds: What interruptions are allowed
├── Team coordination: Shared understanding of focus time
├── Stakeholder education: Setting expectations about availability
├── Emergency protocols: How to reach during focus time
└── Recovery time: Buffer time after intense focus sessions

Energy management:
├── Peak performance hours: When you do your best work
├── Low-energy periods: Routine tasks, administrative work
├── Meeting fatigue: Optimal meeting density and spacing
├── Context switching: Minimizing task switching overhead
├── Cognitive load: Managing complexity and decision fatigue
├── Break optimización: Rest periods for sustained performance
├── Weekly rhythm: Balancing intense and lighter work periods
└── Seasonal adjustments: Adapting to energy level changes

Work-life integration:
├── Boundary management: Clear work/personal time separation
├── Flexibility needs: Accommodating personal commitments
├── Stress management: Preventing burnout and overwork
├── Family considerations: School schedules, family events
├── Health optimización: Exercise, medical appointments
├── Commute planning: Travel time, traffic patterns
├── Social commitments: Team events, networking, conferences
└── Personal development: Learning, hobbies, side projects

Meeting preferences:
├── Meeting frequency: Daily standups, Weekly reviews, Monthly planning
├── Meeting duration: 15-min check-ins, 30-min discussions, 1-hour deep dives
├── Meeting size: 1-on-1s, Small groups (3-5), Large groups (6+)
├── Meeting format: In-person, Video call, Phone call, Async
├── Preparation time: Buffer before meetings for preparation
├── Follow-up style: Immediate notes, Scheduled summaries, Action items
├── Decision making: Consensus building, Consultative, Directive
└── Facilitation style: Structured agenda, Open discussion, Hybrid

Meeting scheduling:
├── Preferred times: Morning energy, Post-lunch focus, End-of-day wrap-up
├── Back-to-back tolerance: Continuous meetings vs buffer time
├── Day-of-week preferences: Monday planning, Friday reviews, Mid-week execution
├── Advance notice: Same-day, 24-hour, 48-hour, Weekly planning
├── Cancellation policy: How much notice needed, rescheduling preferences
├── Recurring patterns: Weekly 1-on-1s, Bi-weekly team meetings
├── Seasonal adjustments: Holiday schedules, Summer patterns
└── Emergency meetings: Criteria for urgent scheduling

Regular touchpoints:
├── Daily standups: Team sync, blocker identification, priority alignment
├── Weekly reviews: Progress assessment, upcoming planning, risk review
├── Bi-weekly retrospectives: Process improvement, team health, lessons learned
├── Monthly planning: Strategic alignment, resource planning, goal setting
├── Quarterly reviews: Performance assessment, strategic pivots, team development
├── Annual planning: Vision setting, major initiative planning, team evolution
├── Ad-hoc check-ins: Project-specific, crisis response, opportunity discussions
└── Stakeholder updates: Regular communication with key stakeholders

Communication channels:
├── Face-to-face: High-stakes discussions, relationship building, complex topics
├── Video calls: Regular meetings, team collaboration, remote connection
├── Phone calls: Quick decisions, urgent matters, personal conversations
├── Instant messaging: Quick questions, status updates, informal coordination
├── Email: Formal communication, documentation, external stakeholders
├── Project tools: Work-related updates, task coordination, progress tracking
├── Shared documents: Collaborative planning, knowledge sharing, documentation
└── Async communication: Time zone differences, deep thinking, documentation

Communication urgency levels:
├── Emergency (immediate): Production outages, critical blockers, safety issues
├── Urgent (within 1 hour): Project delays, team conflicts, stakeholder escalations
├── Important (within 4 hours): Planning decisions, resource requests, status updates
├── Normal (within 24 hours): Regular questions, routine updates, non-critical issues
├── Low priority (within 48 hours): Information sharing, future planning, nice-to-have
├── Scheduled (next meeting): Discussion topics, complex decisions, strategic planning
├── Async (when convenient): Documentation, learning materials, reference information
└── Batched (weekly): Reports, summaries, administrative tasks

Channel-specific expectations:
├── Phone/SMS: Emergency only, immediate response expected
├── Instant messaging: Quick questions, 15-minute response during work hours
├── Email: Formal communication, 24-hour response standard
├── Project tools: Work updates, response within context of project timeline
├── Video calls: Scheduled communication, preparation time expected
├── In-person: High-priority discussions, immediate attention
├── Shared documents: Collaborative work, response when reviewing
└── Async tools: Thoughtful responses, no immediate pressure

Escalation pathways:
├── Level 1: Direct team member, immediate supervisor, project stakeholder
├── Level 2: Department manager, project sponsor, cross-functional lead
├── Level 3: Senior management, executive sponsor, external stakeholder
├── Emergency: Skip levels for critical issues, multiple contact methods
├── After-hours: Specific criteria for off-hours contact
├── Vacation coverage: Designated backup, clear handoff procedures
├── Extended absence: Temporary delegation, decision-making authority
└── Crisis management: Special protocols for major incidents

Availability communication:
├── Status updates: Regular communication of availability changes
├── Calendar sharing: Appropriate visibility into schedule and availability
├── Out-of-office: Clear messages with return date and emergency contact
├── Delegation: Who to contact for different types of issues
├── Response delays: Proactive communication about delayed responses
├── Priority filtering: How to indicate urgency and importance
├── Context sharing: Enough information for others to make decisions
└── Feedback loops: Regular check-ins on communication effectiveness

Detail level:
├── Executive summary: High-level insights, key decisions, strategic implications
├── Manager briefing: Balanced detail, actionable insights, team implications
├── Practitioner depth: Technical details, implementation guidance, best practices
├── Expert analysis: Comprehensive analysis, nuanced considerations, advanced concepts
├── Beginner friendly: Step-by-step guidance, explanations, learning opportunities
├── Context-aware: Adjust detail based on question complexity and urgency
├── Progressive disclosure: Start simple, offer deeper detail on request
└── Custom depth: User-defined preference for specific topic areas

Tone and style:
├── Professional formal: Business language, structured responses, official tone
├── Professional casual: Friendly but professional, conversational style
├── Technical precise: Accurate terminology, detailed specifications, minimal ambiguity
├── Coaching supportive: Encouraging tone, learning-focused, growth-oriented
├── Direct efficient: Concise responses, action-oriented, minimal fluff
├── Collaborative inclusive: Team-focused language, shared responsibility, collective success
├── Strategic visionary: Future-focused, big-picture thinking, transformational language
└── Adaptive contextual: Adjust tone based on situation urgency and stakeholder audience

Information structure:
├── Bullet points: Quick scanning, action-oriented, easy to digest
├── Narrative format: Story-telling, context-rich, relationship-building
├── Structured analysis: Problem-solution-impact, cause-effect, pros-cons
├── Visual descriptions: Charts, graphs, diagrams explained in text
├── Step-by-step: Process-oriented, implementation-focused, sequential
├── Priority-ordered: Most important first, urgency-based sequencing
├── Category-grouped: Organized by theme, department, or functional area
└── Timeline-based: Chronological order, project phases, milestone-oriented

Length and complexity:
├── Tweet-length: Ultra-concise, key points only, immediate action focus
├── Email-length: Standard business communication, balanced detail
├── Report-length: Comprehensive coverage, supporting details, full context
├── Presentation-ready: Structured for sharing, stakeholder-appropriate
├── Documentation-style: Reference material, comprehensive, searchable
├── Conversation-starter: Discussion prompts, open-ended, collaborative
├── Decision-support: Options analysis, recommendations, risk assessment
└── Learning-oriented: Educational content, skill development, knowledge building

Language preferences:
├── Spanish (Latin America): Mexican, Colombian, Argentinian variants
├── Spanish (Spain): Peninsular Spanish, formal business language
├── English (US): American business English, US terminology and conventions
├── English (UK): British English, UK business terminology and spelling
├── Portuguese (Brazil): Brazilian Portuguese, local business customs
├── Portuguese (Portugal): European Portuguese, formal business language
├── French (Canada): Canadian French, bilingual business environment
├── French (France): Metropolitan French, European business conventions
└── Multi-language: Code-switching based on context and audience

Technical terminology:
├── Native language: Translate all technical terms to local language
├── English technical: Keep technical terms in English, explain in local language
├── Mixed approach: Common terms translated, specialized terms in English
├── Industry standard: Use established industry terminology regardless of language
├── Audience-adaptive: Adjust based on team's language preferences
├── Glossary-supported: Provide definitions for technical terms
├── Context-sensitive: Formal vs informal terminology based on situation
└── Learning-oriented: Introduce English terms with local explanations

Business culture:
├── Hierarchy awareness: Formal vs informal address, respect for seniority
├── Decision-making style: Consensus-building vs directive vs consultative
├── Time orientation: Punctuality expectations, deadline flexibility, planning horizons
├── Communication directness: Direct feedback vs diplomatic approach vs indirect
├── Relationship building: Task-focused vs relationship-first vs balanced
├── Risk tolerance: Conservative vs moderate vs aggressive approach
├── Innovation culture: Stability-focused vs change-embracing vs disruption-seeking
└── Work-life integration: Boundary respect, family considerations, cultural holidays

Regional business practices:
├── Meeting etiquette: Punctuality, preparation, participation styles
├── Email conventions: Formality level, greeting styles, closing conventions
├── Reporting structures: Hierarchical vs flat vs matrix organization preferences
├── Performance feedback: Direct vs coaching vs developmental approach
├── Conflict resolution: Direct confrontation vs mediation vs avoidance
├── Celebration and recognition: Individual vs team vs collective achievement focus
├── Learning and development: Formal training vs mentoring vs experiential learning
└── Technology adoption: Conservative vs progressive vs cutting-edge preferences

Audience-specific adaptation:
├── C-level executives: Strategic focus, business impact, high-level metrics
├── Senior management: Departmental implications, resource needs, risk management
├── Peer managers: Collaborative tone, shared challenges, mutual support
├── Direct reports: Coaching style, development focus, clear direction
├── Cross-functional teams: Inclusive language, shared goals, coordination focus
├── External stakeholders: Professional formal, value proposition, relationship building
├── Customers/clients: Service-oriented, value-focused, satisfaction-driven
└── Vendors/partners: Collaborative professional, mutual benefit, clear expectations

Communication adjustment:
├── Technical depth: Adjust complexity based on audience technical background
├── Business context: Include relevant business implications for each audience
├── Urgency indicators: Appropriate escalation language for different stakeholders
├── Action orientation: Clear next steps appropriate to audience authority level
├── Risk communication: Appropriate level of concern and mitigation focus
├── Success metrics: Relevant KPIs and success measures for each audience
├── Timeline communication: Appropriate planning horizons and milestone focus
└── Resource implications: Budget, people, and time considerations by audience

Situational adaptation:
├── Crisis communication: Clear, calm, action-oriented, solution-focused
├── Planning sessions: Collaborative, exploratory, option-generating, future-focused
├── Performance reviews: Balanced, developmental, achievement-recognizing, growth-oriented
├── Stakeholder updates: Professional, progress-focused, transparent, confidence-building
├── Team meetings: Inclusive, participatory, energy-building, alignment-creating
├── One-on-one conversations: Personal, supportive, development-focused, trust-building
├── Presentation preparation: Structured, audience-aware, compelling, clear
└── Documentation: Comprehensive, searchable, reference-oriented, knowledge-preserving

Emotional intelligence:
├── Stress recognition: Adjust communication when team or individual stress is high
├── Celebration moments: Recognize achievements, build momentum, share success
├── Conflict situations: Neutral language, fact-focused, solution-oriented
├── Change management: Empathetic, supportive, clear about benefits and challenges
├── Learning opportunities: Encouraging, growth-focused, mistake-tolerant
├── Innovation discussions: Open-minded, possibility-focused, experimentation-friendly
├── Performance challenges: Constructive, specific, improvement-oriented
└── Team building: Inclusive, relationship-focused, shared-value-emphasizing

Communication style matching:
├── Analytical: Data-driven, logical structure, evidence-based conclusions
├── Driver: Results-focused, efficient communication, action-oriented
├── Expressive: Enthusiastic tone, relationship-focused, collaborative language
├── Amiable: Supportive approach, consensus-building, harmony-preserving
├── Introvert-friendly: Written communication preference, preparation time, depth over breadth
├── Extrovert-engaging: Interactive discussions, brainstorming, energy-building
├── Detail-oriented: Comprehensive information, thorough analysis, complete context
└── Big-picture: Strategic focus, vision-oriented, pattern-recognition, trend-analysis

Decision-making style:
├── Data-driven: Metrics-focused, evidence-based, analytical approach
├── Intuition-based: Pattern recognition, experience-leveraging, gut-check validation
├── Consensus-building: Collaborative decision-making, stakeholder input, shared ownership
├── Consultative: Input-gathering, expert consultation, informed decision-making
├── Directive: Clear decision authority, efficient process, accountability-focused
├── Experimental: Hypothesis-testing, iterative approach, learning-oriented
├── Risk-aware: Thorough risk assessment, mitigation planning, conservative approach
└── Opportunity-focused: Growth-oriented, innovation-embracing, calculated risk-taking

Cross-cultural awareness:
├── Power distance: Hierarchy respect, authority recognition, formal vs informal address
├── Individualism vs collectivism: Personal achievement vs team success emphasis
├── Uncertainty avoidance: Structure preference, risk tolerance, planning detail
├── Long-term orientation: Future focus vs immediate results, tradition respect
├── Masculinity vs femininity: Competition vs cooperation, achievement vs relationship focus
├── Indulgence vs restraint: Work-life balance, celebration culture, flexibility
├── Context sensitivity: High-context (implicit) vs low-context (explicit) communication
└── Time orientation: Monochronic (linear) vs polychronic (flexible) time management

Inclusive communication:
├── Gender-neutral language: Inclusive pronouns, role-neutral descriptions
├── Accessibility awareness: Clear language, alternative formats, accommodation consideration
├── Generational sensitivity: Technology comfort, communication preferences, value alignment
├── Neurodiversity support: Communication style flexibility, processing time consideration
├── Cultural holiday awareness: Scheduling sensitivity, celebration recognition
├── Language proficiency: Adjust complexity for non-native speakers, provide context
├── Socioeconomic sensitivity: Resource awareness, opportunity accessibility
└── Geographic considerations: Time zone awareness, regional business practice respect