Akvelon Power BI Startup Org Chart Infographic

Tech architecture infographic titled "Akvelon Power BI" using HOW-IT-WORKS archetype adapted as a squad / pod-based org structure for a 5-10 startup team. Create a hierarchical org-chart style diagram with visually grouped departments and clear reporting lines, rendered as labeled boxes connected by arrows showing responsibility and collaboration direction. Use generic placeholder role titles only, no real-person names, no photos.

Layout: central top leadership box, branching into 2-3 pods / squads, each pod containing 2-3 role boxes. Suggested structure: top box "Product Lead" — role description "Sets vision and prioritizes analytics roadmap"; second level boxes "Engineering Lead" — "Owns delivery and technical direction", "BI Lead" — "Defines reporting standards and data modeling", "Client Success" — "Collects requirements and communicates outcomes". Pod boxes below may include: "Power BI Developer" — "Builds dashboards and semantic models", "Data Engineer" — "Prepares pipelines and source integrations", "QA Analyst" — "Validates reports and data accuracy", "Business Analyst" — "Translates business needs into metrics", "Support Analyst" — "Monitors refreshes and user issues". If needed for size balance, add "Scrum Coordinator" — "Keeps sprint flow and team alignment".

Render every role as a box with an icon, a sharp role title, and a one-line role description in English. Show color-coded role pills or avatar-like circular markers inside or above each node to distinguish role types while keeping the overall palette minimal monochrome. Departments / pods should be visually grouped with soft outlines or hand-drawn containers labeled in English, such as "Leadership", "Delivery Pod A", "Delivery Pod B", "Enablement".

Arrows: leadership downward arrows labeled "strategy", "priorities", or "reporting line"; cross-functional arrows between BI and engineering roles labeled "data model", "dashboard spec", "bug fix", "refresh status", "user feedback", "release sign-off". Keep flow technically believable for a Power BI delivery organization: requirements move from business analysis to dashboard design, datasets move from data engineering to semantic modeling, reports move to QA and stakeholder review.

Add a numbered legend (1-7) in English walking through the team workflow lifecycle: 1. Requirements intake, 2. Metric definition, 3. Data preparation, 4. Model and dashboard build, 5. Validation, 6. Release to users, 7. Ongoing support and iteration.

Visual style: hand-drawn whiteboard look, minimal monochrome palette with subtle grayscale linework and selective muted accent colors only for role pills, tasteful framing, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Mood: lightweight, startup, structured but informal, sharp readable labels, clear hierarchy, sketched marker outlines, clean spacing, no 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.