Pathmaker

TemplatesThe Designer as Systems Thinker
intermediate
Creative Practice
analytical

The Designer as Systems Thinker

A class on interfaces, workflows, brand systems, content systems, product ecosystems, and organizational context — design as connected thinking.

5 weeks
4 hrs/week
20 total hours
4 learners

About This Course

This class introduces systems thinking for designers. Rather than focusing only on isolated visual artifacts, students learn to understand workflows, environments, organizational structures, information systems, and operational relationships.

The class helps learners see design as connected to larger ecosystems — and positions the designer not as a maker of individual objects, but as a thinker who works across the entire relational context in which those objects operate.

From 'Toward a More Expansive Design Education': 'The future designer will still study typography, image-making, materials, interfaces, environments, and visual culture.

But they may increasingly understand those practices within a larger framework connected to products, systems, organizations, experiences, communication, and economic life.'

What You'll Learn

  • 1
    Understand relationships between systems, components, and contexts
  • 2
    Map workflows, information flows, and organizational structures
  • 3
    Identify how design decisions affect operational coherence
  • 4
    Move between artifact-level and system-level thinking
  • 5
    Design for interconnected ecosystems rather than isolated objects

Week by Week

1

What Is a System?

Systems thinking is not a technique — it is a way of seeing. This week introduces the core vocabulary and practice: understanding how components relate, how feedback loops function, how changing one element affects the whole.

We look at systems in design, nature, cities, and organizations — building the mental models that will inform the rest of the course.

Explore this week's curriculum

Key concepts

System: A set of connected elements organized around a function — where the relationships between parts matter as much as the parts themselves

Feedback loop: A cycle in which a system's output influences its own future inputs — creating either amplification or stabilization

Emergence: Properties that appear at the system level but don't exist in any individual component — the behavior that arises from relationships

Studio activities

System Identification Exercise

Choose a designed artifact you use daily. Map the system it belongs to — what inputs feed into it, what outputs it produces, what other elements it connects to, and what breaks if it's removed.

  1. Select a designed artifact (app, piece of furniture, wayfinding sign, product packaging)
  2. Draw a diagram showing all connected elements
  3. Identify the inputs (what feeds it), outputs (what it produces), and relationships
  4. Ask: what would break elsewhere if this element changed or disappeared?
Success criteria

Your diagram shows relationships, not just components — and reveals something non-obvious about how the artifact functions within its context.

Reflection

  • What's the difference between designing an object and designing a system?
  • What systems are invisible to most users of the products you've studied?
  • When does systems thinking become an obstacle to making things?

Study guidance

  • Look at a familiar object — a chair, a menu, a signup flow — and ask: what system is this part of?
  • Practice drawing simple diagrams of relationships rather than just listing features

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

Can you describe something you design as part of a system rather than a standalone object?

What systems do you participate in daily without consciously thinking of them as systems?

What breaks when a system loses coherence?

What's the difference between designing an object and designing a system?

What systems are invisible to most users of the products you've studied?

When does systems thinking become an obstacle to making things?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

4 hrs
2

Mapping Workflows and Relationships

Designers frequently encounter workflow problems — processes that are fragmented, confusing, or inefficient. This week teaches practical tools for mapping how work, information, and people move through systems.

We look at user journeys, service blueprints, organizational flows, and process diagrams as design instruments.

Explore this week's curriculum

Key concepts

User journey: A map of the sequence of steps, decisions, and experiences a person moves through in relation to a product or service

Service blueprint: A detailed map of a service showing both the customer-facing experience and the backstage operations that support it

Touchpoint: Any moment of contact between a user and a product, service, or organization — each a designed opportunity

Studio activities

Journey Map + Blueprint

Select a service or product experience (a booking system, a return process, a healthcare visit, a checkout flow). Map the user journey and the service blueprint — including both the visible experience and the operational layer supporting it.

  1. Choose a multi-step service experience
  2. Map every step the user takes from start to finish
  3. For each step, identify the backstage operations that enable it
  4. Mark friction points, gaps, and disconnects
  5. Propose one systemic change — not a surface fix — that would improve coherence
Success criteria

Your map reveals the gap between the designed experience and the operational reality — and your proposed improvement addresses a systemic issue, not a cosmetic one.

Reflection

  • What parts of a user journey are invisible to the user but essential to the experience?
  • How do workflow maps change what you notice about designed environments?
  • When is a fragmented user journey a design failure vs. a business decision?

Study guidance

  • Use sticky notes or a whiteboard rather than jumping to polished diagrams — mapping is thinking, not presentation
  • Look for gaps: the moments in a journey where the system provides nothing, and users are left to figure things out alone

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

Walk me through the most frustrating workflow you've experienced recently. What was broken at the system level?

What does a workflow diagram reveal that a description alone misses?

Where do the most consequential design decisions happen in a service blueprint — at the customer-facing layer, or backstage?

What parts of a user journey are invisible to the user but essential to the experience?

How do workflow maps change what you notice about designed environments?

When is a fragmented user journey a design failure vs. a business decision?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

4 hrs
3

Organizational Thinking for Creatives

Design doesn't happen outside organizations — it happens inside them. This week examines how organizational structures, decision-making systems, and team dynamics shape what gets designed, how, and why.

Understanding the organization is part of understanding the design brief.

Explore this week's curriculum

Key concepts

Conway's Law: The observation that systems often mirror the communication structures of the organizations that created them — a designer's organizational context shapes their output

Design operations (DesignOps): The systems, processes, and infrastructure that enable design teams to function coherently at scale

Stakeholder landscape: The full map of people, teams, and interests that influence a design project — often determining what's possible more than aesthetic judgment does

Studio activities

Organizational Design Audit

Study a company's products and then research its organizational structure. Look for evidence of Conway's Law — places where the organizational structure is visible in the design output. Write a brief analysis.

  1. Choose a company with public information about its structure
  2. Examine 3–4 of its products or designed touchpoints
  3. Research its team structure and decision-making model
  4. Identify connections between organizational structure and design output
  5. Reflect: what would change in the design if the organization were structured differently?
Success criteria

You can identify at least two specific connections between organizational structure and design outcome — moving beyond aesthetics into systemic explanation.

Reflection

  • What organizational structures produce the most coherent design?
  • How do you design well inside an organization whose systems work against coherence?
  • Should designers understand business strategy, or does that compromise creative independence?

Study guidance

  • Think of organizational constraints not as obstacles but as design materials — they shape what's possible and often produce interesting solutions
  • Ask who has to approve, implement, or maintain any design you create — their needs are part of your brief

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

How has an organizational constraint ever improved a design you worked on?

What does it mean that organizations often produce systems that look like themselves?

How should designers think about their role inside institutions they may disagree with?

What organizational structures produce the most coherent design?

How do you design well inside an organization whose systems work against coherence?

Should designers understand business strategy, or does that compromise creative independence?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

4 hrs
4

Designing Systems Instead of Objects

The shift from designing objects to designing systems is one of the most significant changes in contemporary practice.

This week examines design systems, content systems, and information architectures — structured approaches that define rules, relationships, and constraints so that coherence emerges at scale, not through individual decisions.

Explore this week's curriculum

Key concepts

Design system: A documented set of standards, components, and principles that enables consistent, scalable design across a product or organization

Information architecture: The structural design of shared information environments — how content is organized, labeled, and made navigable

Atomic design: A methodology that structures design from the smallest components (atoms) up through molecules, organisms, templates, and pages — emphasizing systemic thinking over page-level design

Studio activities

Build a Micro Design System

Create a minimal design system for a simple product — a mobile app, a newsletter, or a small website. Define tokens (color, type, spacing), core components, and usage principles. Document it as if handing it to a collaborator.

  1. Define the scope: what product or context is this system for?
  2. Establish design tokens: 2–3 colors, 2 type styles, spacing scale
  3. Create 3–5 reusable components that use the tokens
  4. Write brief usage principles for each component
  5. Present the system as documentation — not as a design spec for a single screen
Success criteria

Your system enables consistent decision-making without specifying every outcome — someone else could use it to create new screens that feel coherent with yours.

Reflection

  • What does it mean to design rules rather than outcomes?
  • How do design systems change the relationship between individual designers and collective output?
  • Where do design systems break down — and what happens when they do?

Study guidance

  • Think of a design system as a language — it defines vocabulary, grammar, and usage rules so that many people can speak coherently
  • Look at design systems that are publicly documented (like Google Material, IBM Carbon, or Apple HIG) to understand how decisions are articulated at scale

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

What's the difference between a style guide and a design system?

How does a design system enable speed and coherence at scale — and what does it sacrifice?

When does a design system become a creative constraint rather than a creative tool?

What does it mean to design rules rather than outcomes?

How do design systems change the relationship between individual designers and collective output?

Where do design systems break down — and what happens when they do?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

4 hrs
5

Building Coherent Ecosystems

The most sophisticated design challenge is building coherence across an entire ecosystem — multiple products, platforms, touchpoints, and audiences that must feel connected while serving different needs.

This final week applies systems thinking to the whole: examining how coherent ecosystems are built, maintained, and sometimes deliberately broken apart.

Explore this week's curriculum

Key concepts

Product ecosystem: A family of related products, services, and experiences that share identity, interaction patterns, and values — creating network effects and loyalty

Ecosystem coherence: The quality of feeling connected and intentional across all elements of a product family — difficult to achieve, easy to erode

Platform thinking: Designing not just for immediate user needs but for the infrastructure that enables others to build within the system

Studio activities

Ecosystem Audit and Proposal

Select a product or brand ecosystem (Apple, Google, Airbnb, a design studio's portfolio). Audit its coherence across 5+ touchpoints. Identify where it succeeds and where it breaks down. Propose one systemic improvement.

  1. Select an ecosystem with multiple distinct touchpoints
  2. Evaluate coherence across at least 5 touchpoints: does each feel part of the same family?
  3. Identify the connective elements — what creates coherence?
  4. Find the weakest link — where does coherence break down and why?
  5. Propose a systemic solution — addressing the underlying cause, not the surface symptom
Success criteria

You can explain coherence and its breakdown in systemic terms — and your proposed improvement addresses relationships between elements, not just individual touchpoints.

Reflection

  • What does it mean to be responsible for an ecosystem rather than a product?
  • How do ecosystems age? What causes them to become incoherent over time?
  • What is the relationship between ecosystem design and organizational design?

Study guidance

  • Study companies that have successfully maintained ecosystem coherence over time — and ones that have lost it
  • Consider how ecosystems create switching costs: the design is not just functional, it is relational

Discuss with Professor Reed

Choose a question to discuss with Professor Reed. Copy it and paste it into your conversation with him. The copied text includes this week's lesson and assignment; add your own questions or explain where you are stuck.

What ecosystems do you feel genuinely locked into — and how much of that lock-in is designed?

Where does ecosystem coherence become control rather than quality?

How should independent designers think about their work's relationship to larger platforms and ecosystems?

What does it mean to be responsible for an ecosystem rather than a product?

How do ecosystems age? What causes them to become incoherent over time?

What is the relationship between ecosystem design and organizational design?

Ask me one question at a time to check my understanding, then explain any gaps.

Help me plan this assignment without doing the work for me.

4 hrs

Topics Covered

systems thinking
design systems
workflows
organizational design
product ecosystems
information architecture
toward a more expansive design education

More in This Track

Ready to begin?

Start your personalized curriculum today — free to try, no credit card needed.