Tomasz Manugiewicz: Hybrid Heroes: Crafting Teams for Tomorrow's Challenges
summary
Argues that hybrid, product-oriented, cross‑functional teams beat component or ad‑hoc project allocations for ownership and quality, showing specific tradeoffs: 98% want remote, but 69% report burnout from communication and only 35% feel more productive at home. Recommends clear expectations, two‑day in‑person onboarding, quarterly company gatherings and tooling (Jira, Confluence, GitLab/GitHub, Selenium) to stitch relationships and knowledge; a real company example with 19 nationalities, 120 teams, 7 locations and 20% office time 80% home reports that this model works.
AI-written summary · about
chapters (12)
- 0:00Hybrid team challenges
- 1:53Why we build teams
- 4:42Cross-functional vs component teams
- 9:00Product vs project teams benefits
- 15:41Cross-functionality promises and realities
- 16:46Remote work promises
- 22:19Face-to-face communication matters
- 28:04Remote work risks
- 31:45Hybrid model dilemma and solution
- 33:33Our hybrid team structure
- 37:07Harvard study on relationships
- 39:35Q&A
related talks
51mHow to build cross-functional, hybrid teams that Get Stuff Done
32mThe Future Is Hybrid: How To Do Hybrid Teams Right
14mThe uncanny valley of hybrid working
52mRemote Working Approaches That Worked (And Some That Didn’t)
47mPanel: The Culture of Hybrid Work
46mThe UX of Work: Creating excellent experiences across hybrid workplaces
13mManaging Remote Teams
57mLessons from {distributed,remote,virtual} communities and companies