I like this framework of strong vs. weak team concepts. I’ve talked before about the importance of domain expertise and relationships for DSes, and domain expertise is precisely why many DS teams are automatically weak concept.https://lethain.com/weak-and-strong-team-concepts/ …
-
-
You can also use a conversation like this to give the IC context from another part of the org. Done well, this can be a good opportunity to raise their awareness of how their work connects to the rest of the company and facilitate organizational alignment across disparate teams.
Show this thread -
Remember to frame these comments in terms of how they’ll benefit the IC, and allow them to evaluate how much additional work they’ll need to share or adapt their work for a broader audience. Find ways to help them share with less friction, if it’s possible for you to do so
Show this thread -
In addition to helping the IC learn about other areas of the company, this can be a way for them to organically explore new types of responsibility. It helps them grow, and managers investing in their ICs' growth builds trust.
Show this thread -
Strong concept teams are unified by a shared mission. Without that, weak concept teams are held together with the glue of trust. If you’re managing this kind of team, cultivating trust is one of the most important things you can do
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

