|
|
Empowered:
…an empowering team topology is one that minimizes the dependencies.
|
022 |
|
|
Empowered:
…experience teams are most empowered when they are given as much end-to-end responsibility as possible.
|
023 |
|
|
Empowered:
Design is far too important to be run as an internal service. It needs to be a first-class member of the product team, just as the product manager and tech lead are.
|
024 |
|
|
Empowered:
…there is no reason that reporting relationships should dictate team topology.
|
024 |
|
|
Empowered:
Especially for teams that depend on true innovation, team co-location is a significant advantage.
|
025 |
|
|
Empowered:
As much as possible, you should try to keep your existing product teams intact.
|
026 |
|
|
Empowered:
Whatever your goal is, your strategy is how you’re planning to go about accomplishing that goal.
|
27 |
|
|
Empowered:
…product strategy helps us decide what problems to solve, product discovery helps us figure out the tactics that can actually solve the problems, and product delivery builds the solution so we can bring it to market.
|
27 |
|
|
Empowered:
Choices mean focus. Deciding what few things you really need to do, and therefore all the thing you won’t do.
|
027 |
|
|
Empowered:
By not picking your battles and focusing on the few truly critical problems, most of the work going on does not make an impact.
|
028 |
