Designing Interconnected Products

Have you ever used an app that just seemed to get you?

You open it up, and everything feels connected, as if it knows what you were doing before, what you might want next, and it helps you get there without breaking your flow. It feels… effortless. Natural. Extremely Intelligent.

Let’s start with something familiar.

You’re using a fitness app with three main features: a workout tracker, a meal planner, and a sleep monitor. You’d expect them to work together, right?

Instead, here’s what happens:

You finish a brutal HIIT session, the kind that leaves you questioning your life choices, and the meal planner proudly suggests a greasy cheeseburger. Later that night, your sleep tracker scolds you for not resting enough… and the next morning, the app cheerfully nudges you to do another HIIT workout.

Each feature works. But together? They’re tone-deaf.

That's what I call a siloed system, a product where the features coexist but don’t communicate with each other.

Now think about the opposite experience.

You wake up after poor sleep, and the workout feature automatically recommends light stretching. Your meal planner self-adjusts your nutrition to match your current recovery needs.

The app adapts to your context.

That’s a seamless, interconnected experience; features share context and support the same user goal together.

The Problem with Siloed Systems

Siloed products are like homes with rooms that don’t have doors. You can live in them, sure, but moving between spaces feels disjointed. Every time a user switches features, they have to reintroduce themselves, start over, set preferences again, and reestablish context.

The result? A product that feels mechanical, repetitive, and unaware.

And yet, users don’t always know the best a product can offer them. If the features perform their functions well, users will say “the features work well”. However, in the quest to design great experiences, the features need to do more than perform their functions well; they need to communicate with each other to add an extra value that a user never anticipates but will be extremely happy to have because it makes their life easier, and they get to experience delight.

What Interconnected Product Experiences Really Mean

An interconnected experience is one where the product behaves like a living system, a team, each feature aware of what the others know, adjusting its behaviour to support a shared goal.

Think of it like this:

In an interconnected system:

• Features share what they know (user goals, preferences, history).
• They adjust behaviour based on what’s happening elsewhere in the product.
• And together, they create new value, insights, recommendations, or actions that no single feature could produce alone.

Example: Google Workspace

You’ve seen this in action.

You schedule a meeting in Google Calendar; it automatically adds a Google Meet link, attaches your agenda from Google Docs and reminds attendees with the correct time zone.

Google could take this further by leveraging its AI note-taking feature from recorded meetings. The system can take note of actions discussed in meetings and automatically create tasks for the user to follow up on after the meeting.

The magic isn’t in any single feature (Calendar, Meet, Docs, or Tasks).

The magic is in how they talk to each other. When features are aware of one another, they can anticipate the next move, reduce friction, and make users feel like the system knows them.

Designing for Interconnection

If the future of UX lies in systems that collaborate, the question becomes:
How do we design products where features work together?

Here’s a three-step framework to start thinking this way.

Step 1: Map Out the Features and Their Relationships

Begin by listing your product’s key features.
Then draw lines between the ones that should talk to each other.

Ask yourself:

• What should Feature A tell Feature B?
• What data or context connects them?
• How can that connection help the user save time or stay consistent?

Here’s a simple example:

When you do this exercise, you start seeing gaps, where the user journey feels fragmented, where the handoff between features is rough, or where the same data is collected multiple times.

That’s your design opportunity.

Step 2: Share data, but most importantly, share context

I always say that it is important for designers to understand the technicalities and logical structure of the system we are designing; only then can we fully utilise the full potential of the system.

Learn the data structure of features, identify shared data between them, understand APIs and their Payloads, and connect them by shared value.

But beyond that (here’s where most teams stumble), they think connecting features just means “sharing data.” But what really matters is sharing context, the story behind that data.

Context answers:

• What is the user trying to do right now?
• What have they already done?
• What’s their current goal or mindset?

Let’s make that concrete.

Imagine you’re using Figma. You add a frame, and it matches the dimensions of a pres slide. A context-aware system would recognise that pattern and ask:

That’s not invasive; it’s helpful.

It saves time, reduces friction, and feels like the app understands your intent.

When features share context like this, they begin to act less like isolated tools and more like teammates collaborating toward a shared outcome.

Step 3: Design for Learning Between Features

Now we move from connected to intelligent.

When one feature learns something, the others should be able to use that insight. This creates a feedback loop, a product that gets smarter, more personal, and more intuitive with every interaction.

Let’s look at two real-world examples.

Example 1: Spotify

Every feature in Spotify is in constant conversation.

• Your listening behaviour (Feature A) influences Discover Weekly (Feature B).
• Your likes (Feature C) shape your playlists (Feature D).
• Your playlists refine your Home feed (Feature E).

Each feature builds upon another.

The more you listen, the more the system learns, and the more the experience feels alive, like a DJ who’s been studying your taste for years.

Example 2: Apple Ecosystem

Start a note on your iPhone and write, “Meeting with James on Saturday, 1st November.” Instantly, your device suggests creating a calendar event.

If you are on a call with James while editing the note, it offers to share the note with him and add him to the schedule.

When Saturday arrives, your reminder pops up with that same note attached, and at the same time keeps James in the loop.

Every feature, Notes, Calendar, Reminders, Calls, and Messages, plays its part.
The continuity is powerful. It doesn’t feel like the user is leaving one feature to go to another; instead, it feels like an all-around journey. A proactive system that makes users feel supported.

That’s the hallmark of great interconnected design: Consistent experience, but context-aware. Continuity as UX.

With the emergence of AI, a lot of designers will feel that this entire process will be carried out by a smart technology like AI…

Even AI implementation requires you to design how it feeds off the connected data in your system to generate meaningful outputs and automation. To top it off, imagine implementing AI functionalities in a product whose connectedness has already been well designed; the result is that you get an extremely intelligent product that the AI can easily learn from to output even better functionalities.

Mini Exercise: Make Features Talk

Here’s a quick thought experiment I use in workshops.

Pick a product you use daily.

Now, choose two features that don’t currently “communicate”

Ask yourself how they could share context to make your experience smoother.

For example:

This exercise can reveal key insights. Often, the most delightful ideas emerge not from new features but from better relationships between existing ones.

Putting It All Together

When you start connecting features, your design process changes.
You no longer just ask, “What can this feature do?”

You start asking,

“What can this feature help another feature do to better serve the users?”

This transforms your product from a collection of tools into a cohesive system.

So remember these principles:

• Don’t design isolated features.
• Design the relationships between them.
• Use shared context to make experiences feel intelligent.
• Don’t be creepy; keep users in control with transparency and clarity.
• Measure success not just by engagement, but by the effort required of users to achieve their goals.

The Future of UX: Systems That Collaborate

The future of product design isn’t just about designing screens; it’s about interactions between features. It’s about creating ecosystems that communicate.

When your product’s features share context, users don’t notice the transitions. They don’t feel the seams. They just flow.

That’s the new benchmark for well-designed products: not just being usable or functional, but self-aware.

Because the best products do more than just help users do things.
They help themselves help the user better.

Final Thought

The next time you sit down to design a new feature, pause for a moment and ask:

“What other part of this product could this feature make smarter?”

That’s where seamless journeys begin.

That’s how disconnected screens turn into unified stories, and that’s where design stops being about tools and starts being about conversation.