F · People and organization building
Team design
Goals, structure, and capability mix.
Classification boundary
Include: Include team boundaries, structure, responsibilities, collaboration interfaces, and capability mix.
Choose a neighboring leaf when: Use D capacity/dependencies for short-term staffing and F manager-of-managers for leading multiple teams through managers.
This capability may appear in standards across different stages. Explore stage expectations
24 questions
Choose a group based on the evidence you need. Groups follow existing question formats, not difficulty or mandatory prerequisites. Each batch has up to eight questions.
Judgment and options23
Compare goals, constraints, options, and trade-offs.
Questions 1–8
- A team translated its quarterly goal into easy-to-deliver internal improvements, while the business concern about customer churn is absent from the plan. How would you reconnect team goals and work?
- A team shifts from serving one product to supporting six business teams. Technical work has not grown much, but requests, priority conflicts, and feedback channels have multiplied. How would you decide whether to change the organization or first change the operating model?
- The product is organized around a customer journey while engineering teams are split by technical layer, making cross-layer work queue up. How would you assess whether boundaries should change?
- After two teams merge, overlapping roles lack clear ownership and old decision paths remain. How would you redefine responsibilities and check the result?
- A new team owns the full process from discovering user needs through service operations, but its scope is unclear. How would you design its initial capability mix?
- A product passes through five teams from design to launch, with frequent waits and omissions. How would you tell whether the issue is boundaries, process, or capacity?
- A team grows from eight to twenty-five people; decisions slow and members lose context. How would you assess communication, grouping, and management span?
- A platform team owns shared capabilities, while business teams want rapid customization and the backlog grows. How would you design service boundaries and collaboration?
No questions in this section match your target. ·
Questions 9–16
- A business now needs data and automation capabilities that current teams lack, but the long-term structure is uncertain. How would you design a transition arrangement?
- A proposed reorg changes owners of core systems and customer workflows, with knowledge concentrated in a few people. How would you assess risk and transition?
- Cliques have formed on the team. How do you judge whether they help or hurt the team, and how do you deal with their effect on the fairness of information, resources, and decisions?
- How do you build and manage a team with diverse backgrounds, even one using several languages or spread across regions? What problems arise in communication, decisions, evaluation, and belonging?
- Three teams share a senior expert for architecture reviews. Average wait time is over two weeks, and teams hesitate to release without approval. How would you determine whether the issue is staffing, concentrated knowledge, or decision design, and choose an intervention?
- Product organization and technical architecture boundaries differ, cross-team changes keep waiting, and local acquisition targets shift costs to shared technology. How would you compare changes to organization, system interfaces, collaboration, or shared measures and validate their effects?
- As a leader brought in from outside, how do you fit into the existing team? How do you get to know the people and the work, build your own sources of information, and avoid overturning existing practice from day one?
- Research shares insights quarterly, product owns the roadmap, and operations receives training only after launch. User problems surface in operations but rarely affect plans. How would you change team interfaces?
No questions in this section match your target. ·
Questions 17–23
- You inherit a team that has lost continuity. Before assigning anyone work, what would you design first?
- The organization merges a group of new people and new work into your team. How do you make them truly fit in, and how do you handle unease, division of work, and differing standards between existing and new members?
- Critical system knowledge sits with one senior engineer during a peak delivery period. How would you plan knowledge transfer, backup ownership, and short-term capacity?
- How do you judge and shape a team's atmosphere? When it is poor, what signs do you see first, and how do you make people willing to surface problems and disagreement?
- The organization decides to split your team and hand some people and work to other teams. How do you handle the people issues and the work issues, and how do you keep the handover from going wrong?
- The team grows from 12 to 45 people, doubling cross-team meetings while decisions take longer. How would you examine the structure and coordination model?
- Product, legal, and engineering report to different leaders with different priorities, yet jointly own a customer workflow. How would you design collaboration?
No questions in this section match your target. ·
Experience and reflection1
Use past facts to examine contribution, results, and learning.
Questions 1–1
No questions in this section match your target. ·
No questions in this capability match your target. ·