Organisation Chart Office 365 Radial Team Infographic

Tech architecture infographic titled "Organisation Chart Office 365" using HOW-IT-WORKS adapted to a radial / sunburst org-chart layout. Create a central hub box labeled "Office 365 Organization" with a brief role line "Central company structure and reporting overview", surrounded by 11-20 text-only role boxes arranged in concentric grouped department clusters with clear hierarchical reporting arrows radiating outward. Use sharp readable role-title typography only, no avatars, no photos, no real-person names, placeholder generic titles only.

Render labeled BOXES for each component with a small generic icon, a canonical English role/department name, and a one-line English role description. Suggested structure: center "Office 365 Organization"; first ring leadership boxes: "Executive Director - Sets strategic direction", "Operations Manager - Oversees daily operations", "IT Manager - Leads technology services", "HR Manager - Manages people operations", "Finance Manager - Controls budgeting and reporting", "Sales Manager - Drives revenue and accounts". Second ring departmental report boxes grouped visually by department: under Operations: "Project Coordinator - Tracks delivery timelines", "Administrative Assistant - Supports office workflows"; under IT: "Microsoft 365 Administrator - Manages tenant and licenses", "Support Specialist - Resolves user issues", "Security Analyst - Monitors identity and access"; under HR: "HR Specialist - Handles recruitment and policy", "Training Coordinator - Supports staff enablement"; under Finance: "Accountant - Maintains ledgers and payments", "Procurement Officer - Manages purchasing"; under Sales: "Account Executive - Manages customer accounts", "Marketing Coordinator - Supports campaigns", "Customer Success Specialist - Guides client adoption".

Connect all boxes with ARROWS showing reporting direction from manager to report and coordination direction between key departments. Each arrow must have a short English label such as "reports to", "service request", "budget approval", "policy guidance", "user support", "project update", "license request", "customer feedback". Keep flows technically clear as organizational reporting lines and collaboration links.

Add a numbered legend (1-7) in English explaining the organizational lifecycle: 1. "Executive leadership defines strategy" 2. "Department managers own functional goals" 3. "Team leads coordinate daily operations" 4. "Specialists execute role-specific tasks" 5. "Cross-team requests move between departments" 6. "Managers consolidate updates and approvals" 7. "Organization status rolls up to leadership".

Departments must be visually grouped with subtle blue cluster boundaries or shaded rings: Leadership, Operations, IT / Microsoft 365, HR, Finance, Sales / Marketing. Emphasize hierarchical reporting lines, tasteful framing, balanced radial symmetry, compact small-team scale, and text-only nodes rendered crisp and readable.

Visual style: sketchnote editorial developer-blog illustration with hand-drawn annotation feel, isometric or flat tech-diagram style, vector-clean infographic layout. Use a tech blue palette with white background, navy and cyan linework, light blue fills, subtle gray secondary notes, polished but informal mood, neat sunburst composition, high contrast labels, minimal clutter.

All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real-person names or photos. Generic role titles. Tasteful framing throughout.