See all works
0→1 Feature Graph UI Real-time Collaboration AI Integration Enterprise UX

Making relationship intelligence native to the platform not a workaround in Miro

I designed Networks from scratch: a visual canvas where teams map how stakeholders connect, find paths and get AI analysis without leaving Genie.

My Role

Lead UX/UI Designer

Company

TSC.ai

Year

2025 2026

Type

0 → 1 feature design

Platform

Web Genie enterprise

Network canvas with the Node Insights panel open on a selected organisation

Canvas with Node Insights: select any node to see its profile, groups, engagement and 1,000+ connections

At a glance

Problem

Relationship knowledge lived in people's heads, spreadsheets and stale Miro boards.

My role

Lead UX/UI designer for the list, creation flows, canvas, node panel and AI integration.

Outcome

A flagship feature whose graph engine now powers two other parts of the platform.

4

Entry points to create a network from existing platform context

12+

Types of entity that can become a node

0→1

No relationship mapping existed in Genie before this feature

Teams knew who influenced whom, but the system didn't

Engagement managers carried deep knowledge of who influences whom, but none of it lived in Genie. Each time they needed an influence map they rebuilt it by hand, and it broke as soon as someone changed roles.

  • Visual map of how stakeholders connect
  • Every node is a live profile: click to see everything Genie knows
  • Path discovery between any two people
  • Start from context (a profile, an AI answer, a project), not only a blank canvas

Every time a team needed to think relationally, they had to rebuild that picture manually from scratch. It was slow, it was fragile, and it broke the moment a stakeholder changed roles.

Three decisions that shaped the entire feature

Decision 01

Separate the information model before designing any screen

Profile data stays with the platform. Canvas state is stored separately, so two people can edit the same map at once.

Decision 02

Separate the canvas engine from the product features

A stable rendering layer with product features on top, which let us reuse the engine elsewhere within six months.

Decision 03

Design the list and creation flows before the canvas

Most journeys start outside the canvas, so I designed the index and four creation entry points first.

User flows

Build a network from context

Goal: see the influence map around a stakeholder

  1. Start anywhere

    From a profile, an Ask Genie answer, a project or an article

  2. Auto-populate

    Genie pre-fills nodes and known relationships

  3. Explore the canvas

    Pan, zoom, group and colour clusters

  4. Inspect a node

    Roles, education and associations; add any of them to the map

  5. AI

    Ask Genie

    AI summarises clusters and suggests who to add

Result: a live map tied to real profiles, not a static diagram that goes stale.

Find a path to a decision-maker

Goal: find a warm introduction

  1. Pick two nodes

    A known contact and the target person

  2. Surface the path

    The shortest relationship path across the whole network

  3. Check each link

    Open every person on the path in the side panel

  4. Act together

    Log a touchpoint, or edit the map live with teammates

Result: "Who do we know who can reach this person?" is answered in seconds.

Screens

Shipped as a flagship feature and a foundation for what came next

"The Networks feature was the thing that made Genie feel like a platform, not just a database. Before, we had all the data but no way to see the shape of it."

  • Shipped end to end: list, 4 entry points, canvas, node panel, path discovery and live collaboration.
  • Reusable foundation: the graph engine now runs in 2 other areas of the platform.
  • Set the patterns for how nodes behave and how context travels between screens.
4 creation entry points Real-time collaboration Force-directed canvas Ask Genie node suggestions Path discovery Reusable graph engine