The Best Systems Let You Choose Your Light, Then Dress the Same Core Differently

Hatched by Warish

Jun 14, 2026

9 min read

3 views

68%

The strange power of a single core with multiple skins

What do a theme toggle and a bowl of pho have in common? More than it first appears. Both are about a deceptively simple design problem: how do you keep the core stable while allowing the surface to change?

At first glance, these sound like unrelated concerns. One is a tiny interface detail, a switch between light and dark mode. The other is a steaming bowl of noodles, herbs, broth, sauces, and personal taste. But both point to a deeper truth about modern systems, whether they are websites, products, teams, or content strategies: people do not experience the core directly, they experience the choices wrapped around it.

That is why some products feel personal and some feel rigid. Some brands seem to understand context, while others ignore it. Some content feels instantly useful because it meets you where you are. The difference is not that the core changed. The difference is that the system allowed the user to shape the presentation without breaking the underlying structure.

This is not just a design principle. It is a strategy for building things that survive contact with reality.

The tension: one truth, many contexts

The reason theme toggles exist is obvious once you notice the environment. In bright daylight, light mode is often more readable. In a dark room, dark mode can feel gentler and less straining. The content is the same, but the context changes the right form. A system that ignores context forces users to adapt to it. A system that adapts to context becomes easier to live with.

Pho works the same way. The broth is shared. The bowl is personal.

Everyone starts from the same base, but the final experience depends on garnish, herbs, chili, lime, hoisin, and personal restraint or indulgence. One person wants brightness, another wants heat, another wants balance. Nobody asks for a completely different dish. They want the same foundation, tuned to taste.

That is the first lesson: the strongest systems separate what must remain common from what should be locally adjustable.

The goal is not to eliminate variation. The goal is to make variation possible without losing coherence.

This is where many teams get confused. They think standardization and customization are opposites. In reality, the best systems are built from both. Standardization gives you reliability. Customization gives you relevance. If you remove standardization, you get chaos. If you remove customization, you get rigidity.

The challenge is not choosing one. The challenge is deciding where the boundary belongs.

Why context is not an afterthought, but part of the design

A theme toggle can look like a trivial feature, but it encodes a serious philosophy: the user should not have to fight the environment. Light and dark mode are not aesthetic preferences alone. They are responses to conditions. The interface acknowledges that reading in daylight is not the same as reading at night.

That same logic applies to content, product strategy, and even communication inside organizations. A message that works for a first time visitor may be useless for a returning power user. A homepage that helps someone understand your offer may frustrate someone ready to buy. A document written for leadership may not help the team executing the work.

The mistake is to think of the core message as the whole product. In practice, the message is always filtered through context. The audience, timing, medium, and intent all shape meaning. This is why effective systems are rarely built as one fixed artifact. They are built as a core plus adaptations.

Think of a restaurant menu. The kitchen does not prepare a completely different universe for each person, but the best restaurants still leave room for choices. Spice level, toppings, portion size, dietary substitutions, presentation. These are not decorative details. They are the difference between a meal that merely exists and a meal that feels right.

A digital product behaves the same way. The underlying logic should be stable. The interface should flex where the user needs it most. That may mean theme choices, font scaling, layout density, notification preferences, or workflow shortcuts. These are not cosmetic extras. They are signals that the system respects human variation.

The deeper point is that context is not noise around the experience. Context is part of the experience.

Strategy is choice, but choice only matters when the base is strong

There is a beautiful line hiding underneath the pho metaphor: strategy is an act of choosing. Not choosing in the abstract, but choosing now, between two or more options, in order to influence the future.

That definition is powerful because it cuts through a common strategic illusion. Many people treat strategy like an inspirational statement. In practice, strategy is a sequence of exclusions. If you choose one path, you are declining another. If you optimize for one audience, you may be making a tradeoff against another. If you decide to support dark mode, you are acknowledging that not every context is the same.

This is exactly why the theme toggle matters as a strategic metaphor. It is a visible commitment to choice. The system says: the future is not one fixed state. The user participates in shaping it.

But choice alone is not enough. A bowl of pho only works because there is a broth worthy of customization. A toggle only works because the underlying CSS, HTML structure, and JavaScript state management are sound. If the base is weak, flexibility becomes a disguise for inconsistency. If the broth is thin, no amount of chili or lime will save it. If the interface is fragile, theme switching only reveals the cracks faster.

This leads to a useful framework:

Layer 1: The invariant core

This is the thing that must remain true regardless of context. In pho, it is the broth and the essential assembly. In a product, it might be the service promise, the data model, or the actual value delivered.

Layer 2: The contextual surface

This is what adapts. Theme, garnish, layout, language, tone, notifications, and presets all belong here.

Layer 3: The user choice mechanism

This is the control that lets people shape the experience. The toggle, the seasoning station, the filter settings, the account preferences.

Layer 4: The transition

This is the part most people forget. A good system does not just change, it changes smoothly. Abrupt transitions create confusion. Smooth transitions create confidence.

That last layer matters more than people think. A product that flips too harshly between states feels broken even if the underlying logic is correct. A bowl that arrives without the chance to adjust feels less inviting, even if it tastes good. Transition is where usability becomes trust.

The hidden design principle: make the difference visible, not the foundation

There is an elegant design instinct at work in both examples. The system does not hide sameness, and it does not dramatize difference. It makes the shared foundation dependable, then lets the user notice and shape the difference that matters.

This is a useful antidote to two bad habits.

The first bad habit is overcustomization. Some products try to personalize everything, which makes the experience feel fragmented and exhausting. If every choice must be rebuilt from scratch, the user spends more time configuring than using. The same problem exists in organizations that reinvent every process for every team. The result is inconsistency disguised as flexibility.

The second bad habit is fake uniformity. This is when a system pretends everyone wants the same thing and treats adaptation as unnecessary complexity. It creates brittle experiences because it ignores context in the name of efficiency. Light mode at midnight. Dark mode in bright sun. The same onboarding message for every persona. The same content tone for every stage of intent.

The better path is a disciplined modularity.

That means:

Make the core strong enough to stand on its own.
Expose only the choices that actually matter.
Let people customize at the edge, not at the foundation.
Preserve a coherent identity across variants.
Make transitions clear and graceful.

This is why good systems feel both stable and personal. They are not static. They are structured.

The best design is not the one that changes the most. It is the one that changes in the right place.

What this means for content, products, and teams

This principle travels surprisingly far.

In content, the broth is your core idea, and the garnish is your framing. One audience may need a short, direct headline. Another may need a story, a metaphor, or a tactical checklist. The value is not in saying different things for the sake of variety. The value is in expressing the same strategic truth in the form that best fits the reader’s context.

In product design, the broth is the underlying utility. The garnish is the theme, layout density, shortcut preferences, and personalization. A product that allows users to switch themes is really saying something deeper: your comfort matters, your environment matters, and we will not force one experience onto every moment.

In team leadership, the broth is the shared mission. The garnish is the local autonomy given to different people and groups. A strong team does not require everyone to work the same way. It requires everyone to understand what is non negotiable and what can flex. When that boundary is clear, autonomy becomes a source of speed rather than confusion.

In brand strategy, the broth is the promise. The garnish is the channel specific tone, format, and surface expression. The same company may speak differently in a help article, a social post, a sales demo, and a product UI. If the core promise is intact, variation becomes a strength rather than a dilution.

This is the synthesis: the future belongs to systems that are stable in substance and adaptable in presentation.

That sounds obvious until you try to build one. Then you discover how often people confuse polish with substance, or consistency with uniformity, or flexibility with messiness. The real work is drawing the boundary cleanly.

Key Takeaways

Separate the core from the surface. Decide what must stay fixed, and what should adapt to context.
Treat context as part of the experience. Daylight, nighttime, expertise level, intent, and medium all shape what feels right.
Use choice to create relevance, not complexity. Offer only the options that materially improve the experience.
Design transitions, not just states. A smooth change builds trust. Abrupt change creates friction.
Test your system with real variations. Ask whether your product, content, or process still works when the context changes.

The real lesson: flexibility is a form of respect

The easiest way to misunderstand both theme toggles and pho is to think they are about preference. They are, but only at the surface. At a deeper level, they are about respect. Respect for the user’s environment. Respect for the eater’s taste. Respect for the fact that one size rarely fits every moment.

A system that lets people choose their light is not trivial. It is acknowledging that human experience changes across time and place. A bowl of pho that becomes yours through small adjustments is not unfinished. It is complete in a way that makes room for you.

That may be the most useful strategic idea here: the best systems do not force identity through rigidity. They protect identity through a stable core, then let people meet it in the form they need.

So the next time you design a product, write a piece of content, or define a team process, ask a better question than whether it should be standardized or customized. Ask instead: what is the broth, and what is the garnish?

Because once you can answer that, you stop building static things. You start building systems that can live in the real world.