Move Between Concrete and Abstract: Like a Doctor Connecting Symptoms to the Larger System

How product designers connect interface details, user behavior, business goals, and wider ecosystems.

Putra once accompanied his father to a clinic after several evenings of headaches.

The doctor did not begin with a grand theory. She asked where the pain appeared, when it started, how long it lasted, and what his father had eaten. She checked blood pressure, looked at a medication list, and asked about sleep.

Then the conversation widened. Had work become more stressful? Was he drinking enough water during fasting? Had his daily routine changed? Did the headaches appear only after long hours looking at a screen?

The doctor moved between a precise symptom and a larger pattern. She did not ignore the pain because “the system” was more strategic. She also did not treat the pain as an isolated object with no history, behavior, or environment around it.

That movement reminded Putra of a design ability that becomes essential when products grow complex: Move Between Concrete and Abstract.

It is the ability to shift levels, from a specific interface detail to the experience it creates, from an individual moment to a system, from a broad intention back to something people can actually use.

🔴 The Problem Looked Like a Red Button

Putra’s team managed a logistics platform used by small online sellers. One afternoon, support reported that users frequently clicked a red “Cancel shipment” button by mistake.

The concrete problem seemed obvious. Move the button. Change the color. Add a confirmation dialog.

Putra opened recent support conversations. Several sellers had not clicked by accident. They had deliberately canceled shipments because pickup dates were uncertain. Some recreated orders with different couriers. Others canceled after buyers changed their address through chat.

The red button was a visible symptom. The surrounding system included courier availability, buyer communication, pickup promises, seller anxiety, and platform rules.

If the team stayed only at the concrete level, it might improve the confirmation dialog while leaving the larger experience untouched. If it stayed only at the abstract level, discussing “trust in logistics ecosystems,” it might produce elegant strategy language without helping a seller facing a pickup deadline at four o’clock.

The work required movement in both directions.

🔎 Zoom In Until the Experience Becomes Tangible

Abstract statements can align a team, but they can also hide disagreement.

“We want a seamless shipping experience” sounds reasonable. What does seamless mean when a courier misses pickup? What should a seller see? Which action is available? What happens to the buyer notification? Who carries the cost?

Putra brought the strategy down to a specific scenario:

A home-based seller in Surabaya has packed twelve parcels. The courier pickup window ends in forty minutes. Three buyers are asking for tracking numbers. The app still shows “waiting for courier” and provides no estimate.

Suddenly, abstract values such as reliability, control, and transparency had concrete consequences.

The team sketched the status screen, notification timing, recovery options, and language. By making the situation tangible, they could see where their broad ambition failed to guide actual behavior.

Moving toward the concrete helps a team test whether its principles survive contact with reality.

🌐 Zoom Out Until the Detail Makes Sense

The reverse movement is equally important.

Why did sellers cancel shipments? Because they lacked confidence in pickup timing. Why did timing feel uncertain? Because the platform showed a system status but not a meaningful promise. Why could the platform not provide a reliable promise? Because courier partners updated events differently, and internal teams had never agreed on what the customer-facing state should represent.

The button was connected to data contracts, operations, partner incentives, notification rules, and the product’s promise to sellers.

Putra mapped the experience across layers:

• The concrete interface action.
• The seller’s immediate goal and emotion.
• The end-to-end shipping journey.
• The operational and technical systems producing the status.
• The platform’s broader value proposition of dependable selling.

Each layer changed how the others were understood.

Moving toward the abstract helps a team see relationships, principles, and consequences that are invisible inside a single screen.

🩺 Do Not Confuse the Symptom With the Diagnosis

The doctor at the clinic did not dismiss Putra’s father’s headache. She treated the symptom seriously while asking what might produce it.

Designers need the same discipline. A usability issue can be real and still be part of a larger problem. A business objective can be important and still require translation into small interaction decisions.

Putra’s team kept the confirmation step because accidental cancellation did happen. But they also redesigned the status model, added clearer pickup expectations, created recovery paths, and worked with operations on event consistency.

This was not a choice between “pixel work” and “strategy work.” Both were design work at different levels of resolution.

The ability lies in knowing when to move.

When a discussion becomes too philosophical, bring it down to a person, moment, object, or behavior. When a team argues endlessly about a component, move upward and ask what experience, system, or principle the component is meant to serve.

🪜 Use the Ladder in Both Directions

One practical way to move between levels is to ask “why” and “how” as two directions on a ladder.

“We need a clearer shipment status.”

Why? So sellers know whether the pickup is progressing.

Why does that matter? Because they must communicate with buyers and decide whether to wait or intervene.

Why does that matter to the product? Because the platform promises sellers dependable control over fulfillment.

Then move downward with “how.”

How might the platform make progress dependable? By expressing a meaningful pickup promise.

How might the interface express that promise? Through a status, time range, confidence level, and recovery action.

How might the team test it? By showing realistic delayed-pickup scenarios to sellers and observing what they understand and choose.

The ladder prevents broad purpose from floating away and concrete execution from becoming arbitrary.

🗺️ Change the Representation to Change the Conversation

Different levels often need different representations.

A screen helps the team discuss wording, hierarchy, and action. A journey map helps reveal what happens before and after the screen. A system map exposes actors, data, and dependencies. A storyboard makes an abstract service idea visible in time. A principle captures a reusable intention.

Putra changed artifacts as the question changed. He did not force every conversation into Figma.

When operations and engineering debated courier events, a system map helped. When sellers struggled to interpret the new states, a prototype helped. When leadership asked why the work mattered, a simple story connected the status problem to seller trust and repeat usage.

Moving between concrete and abstract is also moving between ways of seeing.

🩻 The Doctor’s Final Question

Before Putra and his father left the clinic, the doctor explained what they knew, what remained uncertain, and what signs would require another visit. She connected a broad hypothesis to concrete next actions.

That balance is what strong design work creates.

A designer should be able to discuss how a product supports a business and social system, then return to the exact sentence a person reads when something goes wrong. One level does not make the other less important.

When teams remain too abstract, they create promises nobody knows how to deliver. When they remain too concrete, they polish symptoms while the system keeps producing them.

The craft is in the movement.

Zoom in until the idea becomes real enough to examine. Zoom out until the detail becomes meaningful enough to guide. Then keep moving as new evidence changes what you see.

🧺 Takeaways to Bring Into Your Next Project

• Move between specific details and larger patterns instead of treating either level as the whole problem.
• Use concrete scenarios to test whether abstract strategies and principles have practical meaning.
• Zoom out from interface symptoms to goals, journeys, operations, technologies, relationships, and incentives.
• Ask “why” to move toward purpose and “how” to move toward implementation.
• Change the representation when the level of the question changes.
• Treat strategy and craft as connected resolutions of the same design work.

P.S. Next up:

“Build and Craft Intentionally: Like a Watchmaker Engineering Every Gear” 👀

🔗 About This Series

This is article 5 of Designerly Thinking: Eight Core Design Abilities, followed by a reflection epilogue. The abilities come from the Stanford d.school and are not intended as a rigid sequence.

1. Design Your Design Work: Like Setting Up Your Kitchen Before You Cook
2. Learn from Others: Like Watching a Barista Who Knows Your Order and Your Mood
3. Synthesize Information: Like Sifting Gold from Sand to Find Meaning in Messy Research
4. Rapidly Experiment: Like a Chef Testing Small Portions Before Serving the Full Menu
5. Move Between Concrete and Abstract: Like a Doctor Connecting Symptoms to the Larger System
6. Build and Craft Intentionally: Like a Watchmaker Engineering Every Gear
7. Communicate Deliberately: Like a Diplomat Aligning Allies in a High-Stakes Room
8. Navigate Ambiguity: Like a Captain Forging the Route Through the Fog
9. Reflection: Like a Warung After Closing, Turning a Busy Day into Better Judgment

#ProductDesign #SystemsThinking #DesignStrategy #UXDesign #ProductStrategy #DesignAbility #UserExperienceDesign #DigitalProductDesign #StanfordDschool

Move Between Concrete and Abstract: Like a Doctor Connecting Symptoms to the Larger System 🩻 was originally published in Bootcamp on Medium, where people are continuing the conversation by highlighting and responding to this story.