AgenticFor DevelopersTech Communication & Leadership

Team Topology Designer.

When team structure is creating bottlenecks, unclear ownership, or slow delivery.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1750 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
team-topology-designer-4.md Β· 1750 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Tech Communication & Leadership
- Use case: Team Topology Designer
- Source task:
  - Design the optimal team structure for an engineering organisation of {{number}} engineers building {{describe_the_product}}. Current pain points: {{describe_slow_delivery_too_many_dependencies_unclear_ownership}}.
  - Step 1: map the sociotechnical system (identify the main streams of work, platform needs, and complex subsystems).
  - Step 2: recommend team types (stream-aligned, enabling, platform, complicated-subsystem) and their boundaries.
  - Step 3: design interaction modes between teams (collaboration, X-as-a-Service, facilitating).
  - Step 4: define a 6-month transition plan from current to target structure.

# Goal
Sociotechnical system map, team type recommendations, interaction mode design, and 6-month transition plan.

# Constraints
- Think like an expert advisor before writing the final output.
- Ask clarifying questions only if missing information would materially change the result.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Sociotechnical system map, team type recommendations, interaction mode design, and 6-month transition plan.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roleteam structure advisor (Team Topologies framework)
{{use_case}}Your specific valueteam topology designer
{{number}}Number5
{{describe_the_product}}Describe the productExample describe the product
{{describe_slow_delivery_too_many_dependencies_unclear_ownership}}Describe slow delivery too many dependencies unclear ownershipslow delivery

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When team structure is creating bottlenecks, unclear ownership, or slow delivery.

PRO TIP

Conway's Law always wins β€” your software architecture will mirror your communication structure. Design teams first, then let the architecture follow.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’