Organization and Team Topology Mapping

    1

    Maps organizational teams to software architectures: Conway's Law alignment, ownership boundaries, and cognitive load.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    Organization and Team Topology Mapping

    Example session with this skill installed

    Map team topologies, mandates, and interaction boundaries for Cross-Border Payouts and Settlements.

    • Subject: Cross-border payout failure reconciliation workflow (run-id: payout-recon-001).
    • Deciders: Head of Engineering David O'Reilly and Head of Treasury Operations Elena Rostova.
    • Scope: 4 operating teams across Core Payments and Settlement Operations managing $4.8B monthly volume across 18 banking rails.
    • Sources: HR roster HR-2026-Q3, Core Payment Charter CHARTER-PAY-v2, Settlement Charter CHARTER-SETTL-v1, Incident Post-Mortem INC-4919.
    • Tension: When foreign payouts fail, both SQUAD-PAY-CORE and SQUAD-SETTL-OPS disclaim transaction reconciliation. SQUAD-PAY-CORE claims responsibility ends upon ledger write; SQUAD-SETTL-OPS lacks engineering access and treats ledger adjustment as software scope. In incident INC-4919, $14.2M in failed SWIFT payouts stalled un-reconciled for 48 hours ($420K SLA penalty). Management attempted to resolve this through administrative reporting lines, producing an unowned process and activity without outcome.

    Write the team topology map under docs/architecture/tasks/payout-recon-001/organization-mapping/.

    • Read your context and instructions
    • Compiled the organization and team
    • Generated the document

    Wrote docs/architecture/tasks/payout-recon-001/organization-mapping/team-topology-map.md. Authoritative team topology and boundary map resolving cross-border payout reconciliation ownership across Core Payments and Settlement Operations.

    skill: organization-mapping

    Team Topology Map: Cross-Border Payout Reconciliation [TTM-PAY-001]

    Summary

    This map normalizes the effective organizational structure, team mandates, and interaction boundaries for cross-border payout failure reconciliation under run ID payout-recon-001. The scope covers 4 operating teams across Core Payments and Settlement Operations managing $4.8B monthly volume across 18 banking rails. Addressing incident INC-4919—where $14.2M in failed SWIFT payouts stalled un-reconciled for 48 hours ($420K SLA penalty)—this mapping resolves the accountability dispute between SQUAD-PAY-CORE and SQUAD-SETTL-OPS. It establishes explicit boundaries: SQUAD-PAY-CORE owns transaction ledger integrity and automated exception publishing, while SQUAD-SETTL-OPS owns post-authorization bank statement clearing and partner ledger adjustments. It formalizes collaboration interfaces and routes unowned escalation workflows to designated operational authorities without inventing speculative organizational structures.

    Detailed Description

    Evaluated organizational units, mandates, and operational dependencies across Core Payments and Settlement Operations using authoritative HR records and operating charters. Reconciled charter overlaps to eliminate unowned process gaps and circular reporting lines.

    Criteria and weights

    CriterionWhy it matters hereWeightSource of the weight
    Accountability Boundary PrecisionAmbiguity between ledger persistence and operational clearing caused incident INC-4919 ($420K penalty).0.35Elena Rostova (Head of Treasury Operations)
    Process Ownership ClosureEvery stage of payout failure handling must have a designated accountable operating team.0.30David O'Reilly (Head of Engineering)
    Interaction Contract VerifiabilityInter-team handoffs must occur over defined channels rather than ad-hoc chat escalation.0.20Incident Post-Mortem INC-4919
    Structural State FidelityMap must reflect current effective authority from HR rosters and approved charters without reorg drift.0.15Governance and Compliance Policy

    Comparison

    Candidate ModelBoundary DefinitionFailure Handling RoutingAdversarial Case HandlingFreshness & Authority
    Model A: Administrative Hierarchy (Legacy)Conflates reporting lines with operational ownership.Escalates failed reconciliations up VP chain.Rejects: Causes activity without outcome and 48-hour delays.Stale: Defeated by INC-4919 evidence.
    Model B: Speculative Shared OwnershipMandates joint ownership across engineering and operations.Requires ad-hoc cross-team consensus on every exception.Rejects: Unowned process; neither team assumes ledger custody.Invalid: Violates single accountability rule.
    Model C: Bounded Mandate & Interaction Map (Chosen)Decouples core engine persistence from settlement clearing.Deterministic routing via event channel EVT-PAY-EXCEPT-v1.Passes: Eliminates org-chart-as-architecture and unowned gaps.Current: Grounded in HR-2026-Q3 and active charters.

    Result

    Model C is selected. SQUAD-PAY-CORE retains exclusive accountability for ledger persistence and automated error event dispatch; SQUAD-SETTL-OPS assumes exclusive accountability for banking partner file reconciliation and manual redrive clearing.

    Required Mechanisms

    1. Actor and Authority [MC-AA-01]
    • Inputs: HR Workday roster HR-2026-Q3, Team Charters CHARTER-PAY-v2 and CHARTER-SETTL-v1.

    Algorithm: Map structural units to operational squad IDs; isolate administrative managers from technical and operational delivery authorities.

    • Outputs:
      • UNIT-ENG-PAY (Core Payments Unit): Head of Engineering David O'Reilly.
        • Operating Team SQUAD-PAY-CORE (Core Payments Squad): Lead Engineer Marcus Vance. Authority: Core transaction routing engine, ledger database persistence, automated webhook dispatch.
        • Operating Team SQUAD-PAY-INTEG (Payment Rails Integration Squad): Lead Engineer Sophia Patel. Authority: ISO 20022 and SWIFT gateway connectivity adapters.
      • UNIT-OPS-TREAS (Treasury & Settlement Operations Unit): Head of Treasury Operations Elena Rostova.
        • Operating Team SQUAD-SETTL-OPS (Settlement Operations Squad): Operations Lead Carlos Mendez. Authority: Banking partner statement reconciliation, exception queue triage, clearing adjustments.
        • Operating Team SQUAD-TREAS-LIQ (Treasury Liquidity Squad): Liquidity Manager Aisha Khan. Authority: Nostro/Vostro account balancing and intraday currency buffers.
    • Owner: David O'Reilly (Engineering) and Elena Rostova (Treasury Operations).

    Failure Handling: Conflicting role or reporting claims trigger an organization_authority_conflict_request to HR governance.

    • Verification: Cross-referenced against Workday roster snapshot HR-2026-Q3 effective 2026-07-01.
    2. Value Flow and Operational Boundaries [MC-VF-01]
    • Inputs: Cross-border payout failure scenario (run-id payout-recon-001), Incident INC-4919.
    • Algorithm: Partition lifecycle into pre-authorization, clearing execution, and settlement exception handling.

    • Outputs:

    Stage 1 (Pre-Auth Routing): SQUAD-PAY-CORE validates payment intent and logs immutable ledger entry LEDGER-INIT.

    • Stage 2 (Rail Dispatch): SQUAD-PAY-INTEG transmits payment instruction to foreign partner bank rails.

    Stage 3 (Exception Notification): Upon partner rejection or SWIFT NAK, SQUAD-PAY-INTEG streams normalized error event to topic EVT-PAY-EXCEPT-v1.

    Stage 4 (Settlement Reconciliation): SQUAD-SETTL-OPS consumes EVT-PAY-EXCEPT-v1, matches against partner bank end-of-day MT940 statements, and executes reconciliation credit/debit adjustments via governed portal PORTAL-SETTL-ADJUST.

    • Owner: Carlos Mendez (Settlement Ops Lead) and Marcus Vance (Core Payments Lead).

    Failure Handling: Unparseable partner bank statement entries trigger routing to unassigned exception queue QUEUE-SETTL-UNKNOWN.

    • Verification: End-to-end trace validation against incident INC-4919 sequence diagrams.
    3. Capability Owner and Accountability Invariants [MC-CO-01]
    • Inputs: Sourced charters CHARTER-PAY-v2 and CHARTER-SETTL-v1.
    • Algorithm: Establish deterministic boundaries prohibiting disclaimed ownership and shared code custody.

    • Outputs:

    Invariant INV-ORG-01 (Ledger Custody): SQUAD-PAY-CORE holds exclusive authority over core ledger tables. No operational role outside SQUAD-PAY-CORE may execute direct database writes.

    Invariant INV-ORG-02 (Reconciliation Custody): SQUAD-SETTL-OPS holds exclusive accountability for closing payout discrepancies exceeding $0.00 between internal ledger states and external bank statements.

    Invariant INV-ORG-03 (Interaction Channel Contract): Operational squads must not request ad-hoc manual engineering database updates via direct chat. All corrections require audited API requests through PORTAL-SETTL-ADJUST.

    • Owner: Marcus Vance (SQUAD-PAY-CORE) and Carlos Mendez (SQUAD-SETTL-OPS).
    • Failure Handling: Unauthorized manual ledger intervention triggers security audit alarm SEC-ALARM-UNAUTH-WRITE.
    • Verification: Enforced via RBAC policies on AWS RDS IAM roles and portal audit logs.
    4. Business Measure and Metrics [MC-BM-01]
    • Inputs: Incident post-mortem INC-4919 SLA metrics and financial penalty ledgers.
    • Algorithm: Track operational cycle times against regulatory and banking partner SLA thresholds.
    • Outputs:
      • METRIC-MTTR-RECON: Mean Time to Reconcile failed cross-border payouts. Target: <= 4.0 hours (reduced from historical 48.0 hours).
      • METRIC-UNOWNED-EXCEPT-RATIO: Ratio of exception transactions without an assigned team owner. Target: 0.00%.
      • METRIC-SLA-BREACH-FINES: Monthly SLA non-compliance penalties. Target: $0.00 (down from $420,000 in INC-4919).
    • Owner: Elena Rostova (Head of Treasury Operations).

    Failure Handling: Breach of METRIC-MTTR-RECON (> 6.0 hours) triggers automated paging to on-call settlement managers.

    • Verification: Monthly Datadog operational dashboard DASH-SETTL-PERF-01.

    Adversarial Case Handling

    Reject Org-Chart-as-Architecture

    Diagnostic: Administrative reporting lines in HR org charts group SQUAD-PAY-CORE and SQUAD-PAY-INTEG under Engineering, and SQUAD-SETTL-OPS under Finance Operations. Management attempted to infer system integration flow from this reporting tree.

    Forbidden Output: Concluding that because teams report to different executive VPs, they cannot integrate via direct event streams, or assuming reporting proximity implies architectural coupling.

    Enforced Correction: Architecture and value flow depend exclusively on published service contracts (EVT-PAY-EXCEPT-v1 and PORTAL-SETTL-ADJUST), strictly decoupled from managerial hierarchies.

    Reject Unowned Process

    Diagnostic: Disclaimed responsibility during payout failure reconciliation where engineering disowned post-ledger state and operations disowned software errors, causing $14.2M to sit idle.

    Forbidden Output: Permitting "shared responsibility" without a designated primary accountable squad, or leaving reconciliation unassigned.

    Enforced Correction: Explicit accountability assignment assigning SQUAD-SETTL-OPS as the mandatory owner for resolution of all exceptions once EVT-PAY-EXCEPT-v1 is dispatched.

    Reject Activity Without Outcome

    Diagnostic: In incident INC-4919, teams held 6 cross-departmental alignment meetings over 48 hours without reconciling a single stalled payout.

    Forbidden Output: Documenting coordination meetings, standing committees, or sync channels as evidence of operational reconciliation.

    Enforced Correction: Mandate that team interactions are governed by verified artifact delivery (reconciliation adjustment batches logged in PORTAL-SETTL-ADJUST) evaluated against METRIC-MTTR-RECON.

    Explicit Unknowns

    • API availability timeline and delivery sprint for PORTAL-SETTL-ADJUST automated adjustment endpoint (UNK-01).
    • Exact staffing allocation for dedicated weekend on-call coverage within SQUAD-SETTL-OPS (UNK-02).
    • Third-party SWIFT GPI tracking payload compatibility across 3 Tier-2 partner banks in Latin America (UNK-03).

    Traceability

    ClaimClassificationSourceFreshness
    4 operating teams across Core Payments and Settlement OperationsprovidedIntake specificationCurrent
    $4.8B monthly volume across 18 banking railsprovidedIntake specificationCurrent
    Incident INC-4919 48h stall ($14.2M delayed, $420K fine)providedIncident Post-Mortem INC-4919Historical
    HR organizational structure and unit boundariesobservedHR Workday roster snapshot HR-2026-Q32026-07-01
    Core payment engine and ledger ownershipdecidedCore Payment Charter CHARTER-PAY-v22026-05-15
    Settlement clearing and bank statement reconciliation mandatedecidedSettlement Charter CHARTER-SETTL-v12026-06-01
    Rejection of administrative reporting lines as architecturederivedDomain rule evaluationCurrent
    Single-owner accountability for exception clearingdecidedDavid O'Reilly & Elena Rostova2026-09-15

    Verification

    No validator was supplied, so no command was run.

    Reviewer self-check against organization mapping domain rules:

    Actor and Authority: Verified. Distinct structural units, operating squads, leads, and operational limits recorded.

    • Value Flow: Verified. 4-stage failure handling lifecycle mapped from error capture to statement reconciliation.
    • Capability Owner: Verified. Invariants INV-ORG-01, INV-ORG-02, and INV-ORG-03 prevent shared or orphaned custody.

    Business Measure: Verified. Concrete metrics (MTTR, unowned exception ratio, fines) bound to historical baselines.

    Adversarial Checks: Org-chart-as-architecture, unowned process, and activity-without-outcome explicitly rejected with diagnostics.

    • Markdown Hygiene: Native Markdown syntax without character escaping or nested fences.

    Open Decisions

    • DEC-ORG-01: Elena Rostova and David O'Reilly to approve engineering sprint allocation for PORTAL-SETTL-ADJUST API enhancement in Q4.
    • DEC-ORG-02: HR Governance to formalize updated charter addenda for CHARTER-PAY-v2 and CHARTER-SETTL-v1 reflecting finalized boundary invariants.

    Next steps

    1. Circulate finalized boundary map [TTM-PAY-001] to David O'Reilly and Elena Rostova for formal charter ratification.
    2. Engineering lead Marcus Vance to implement EVT-PAY-EXCEPT-v1 schema validation in staging environment.
    3. Operations lead Carlos Mendez to update Settlement Operations standard operating procedures to mandate reconciliation intake via PORTAL-SETTL-ADJUST.
    4. Platform security team to review RDS IAM permission boundaries enforcing Invariant INV-ORG-01.

    organization-and-team-topology-mapping.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Normalize team identities and reporting structuresDefine clear accountability and mandate boundariesDocument organizational dependencies and interactionsIdentify ownership gaps in software architectures

    About this skill

    What it does

    This skill normalizes an authoritative current or approved target structure: units, teams, roles, mandates, ownership, reporting/delegation, dependencies, interactions, dates, evidence and gaps.

    Use it when

    Use when a business/architecture decision needs reproducible organizational identities and responsibility boundaries, but source structures conflict, role holders changed, mandates/ownership overlap, interactions are unclear, or current and proposed target organizations are being conflated.

    For example: “When cross-border payouts fail, both the Core Payments team and the Settlement Operations squad claim the other owns transaction reconciliation.”

    What you get

    • Team Topology Map

    Written as Markdown to <your output folder>/architecture/tasks/<run-id>/organization-mapping/.

    What it will not do

    Do not use merely to analyze stakeholders, reorganize teams, apply Team Topologies/Inverse Conway, author RACI, plan communications, map capabilities, define operating models, assess load, plan staffing, assign systems, or design architecture.

    How it works

    1. Check organization mapping is required.
    2. Bound structural state and authority.
    3. Normalize organizational unit and team identities.
    4. Define mandates and accountability boundaries.
    5. Normalize interactions and organizational dependencies.
    6. Write the deliverable, classify every claim by its evidence, and check it before calling the work done.

    What's in the package

    Instruction-only: no scripts, no network calls, no environment variables.

    • LICENSE.txt
    • SKILL.md
    • agents/openai.yaml
    • assets/output-template-task.md
    • references/domain-rules.md
    • references/operating-rules.md
    • references/output-contract.md

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 12 days ago

    • Passed all security checks, Safe to install

    Listed12 days ago

    What's inside

    Frequently Asked Questions