Systems Thinking: How to Apply in Product Design [+Tips]

Summary

Systems thinking is a top-down design approach that considers the overarching system before diving into specific interface interactions, preventing premature detail fixation. It is based on Donella H. Meadows’ definition that a system is an interconnected set of elements coherently organized to achieve something, prompting questions about elements, interconnections, and purpose. For Intercom’s Articles product, the team identified the article as the core element and mapped how articles are created, delivered, and interact with other systems, resulting in a complex system diagram. This systems view revealed opportunities like an intelligent suggestion engine that recommends articles during conversations and allowed the team to prioritize the most important parts to build first. The approach also encouraged reusing the Messenger Reactions component for article feedback, sharing design and implementation details like hover effects and clicked states across contexts.

Takeaways

1. 1

   Systems thinking requires defining the system’s elements, interconnections, and purpose before designing specific interactions.

2. 2

   Mapping the system diagram can uncover new product opportunities, such as a suggestion engine that recommends articles based on conversations.

3. 3

   Reusing existing UI components across contexts, for example using Messenger Reactions for article feedback, maintains consistency and reduces design and implementation work.

FAQ