Navigation überspringen
Workforce Ecosystems
Book

Workforce Ecosystems

Reaching Strategic Goals with People, Partners, and Technologies

MIT Press, 2023 Mehr


Editorial Rating

8

Qualities

  • Comprehensive
  • Well Structured
  • Engaging

Recommendation

The emerging workplace looks very different from the rigid, hierarchical workplace of the past, say writers Elizabeth J. Altman, David Kiron, Jeff Schwartz and Robin Jones. Today’s workforces have more of an ecosystem structure than the traditional silo structure. If you want to lead your workforce to success, you need to know how to orchestrate this structure, while respecting the autonomy of all participants. Learn how embracing a more expansive view of your workforce can help your organization reach its strategic goals. Shift your business mind-set, seeing opportunities for collaboration and growth when others see only the threat of competition.

Take-Aways

  • Today’s workforces are more like dynamic ecosystems than rigid silos. 
  • Leverage interdependencies and complementarities to create more value and reach your goals.
  • Consider three essential ecosystem characteristics when creating your strategy.

About the Authors

Jeff Schwartz is the author of Work Disrupted, as well as an adviser on the future of work for Deloitte Consulting, and the vice president of insights and impact at Gloat. Elizabeth J. Altman is an associate professor of management at the University of Massachusetts Lowell’s Manning School of Business. She’s also a guest editor of the MIT Sloan Management Review Future of the Workforce project. David Kiron is the editorial director of research at MIT Sloan Management Review. He’s also a program lead with MIT’s Big Ideas research initiatives. Robin Jones leads workplace transformation at Deloitte, and she serves on the CEO’s Marketplace Leadership Team with Deloitte Consulting.


Comment on this summary or Diskussion beginnen

  • Avatar
  • Avatar
    P. J. 5 months ago
    Creating interdependent teams is a good idea and has worked in the past. However, it also creates scenarios of over dependency on some members. Any ideas on how to avoid such situations?