Connected Communication

Bringing conversations, decisions and collaboration into the flow of work.

Role
Lead Product Designer
Platform
B2B SaaS Platform
Focus
Task Management, Collaboration, Communication
Contribution
Research, UX, Product Strategy, UI Design, Prototyping
Challenge

Communication wasn’t the problem.

Everyone was already talking.

Residents, operators, contractors and suppliers exchanged information constantly through emails, phone calls, messaging apps and internal systems.

The problem was that every conversation lived somewhere different.

As communication volumes increased, teams spent more time searching for information, reconstructing decisions and chasing updates than actually resolving issues.

A simple repair could involve dozens of conversations spread across multiple channels, with no reliable way to understand the full story behind a task.

The challenge wasn’t helping people send messages.

It was helping them maintain context.

Approach
Keeping Communication Connected To The Work

During discovery, I noticed that most communication tools treated conversations as a destination.

Users would leave their task, switch applications, search for information, then return to continue working.

Every context switch introduced friction.

Every disconnected conversation increased the risk of lost information, duplicated effort and delayed decisions.

Rather than creating another communication platform, I wanted communication to become part of the operational workflow itself.

Conversations, files, updates and decisions needed to remain connected to the work they supported.

Several principles guided the approach:

  • Reduce context switching
  • Improve visibility across teams
  • Preserve decision history
  • Support different communication styles
  • Make information easier to discover
  • Maintain traceability throughout the lifecycle of work

The goal wasn’t better messaging.

It was better operational understanding.

Key Decisions
Designing For Context, Not Conversation

Embedding Communication Directly Into Tasks

One of the earliest decisions was avoiding a standalone messaging experience.

When conversations become detached from the work itself, users are forced to manually reconstruct context.

By embedding communication directly within tasks, conversations remained connected to the actions, decisions and updates that created them.

Supporting Multiple Communication Formats

Different situations require different ways of communicating.

Rather than forcing teams into a single format, the platform supported messaging, file sharing, updates, voice notes and AI-assisted interactions while maintaining a single source of truth.

Making Information Discoverable

As communication volumes grow, finding information becomes more valuable than creating it.

Search, filtering and participant visibility helped users quickly locate conversations, decisions and supporting information without relying on individual memory.

Preserving Operational History

One frustration surfaced repeatedly during research: teams struggled to understand why previous decisions had been made.

Maintaining a complete communication timeline created an auditable history that helped teams understand what happened, who was involved and how decisions evolved over time.

Solution
A Communication Layer For Operations

The final solution introduced a unified communication framework embedded directly within operational workflows.

Conversations, files, updates, voice notes and AI-assisted interactions were brought together into a single experience connected to tasks, assets and operational activities.

Users could:

  • Communicate within the context of a task
  • Share files and supporting information
  • Access complete activity history
  • Collaborate across teams and suppliers
  • Search conversations and decisions
  • Use AI-assisted interactions to accelerate communication
  • Access information across multiple devices

Operational teams no longer needed to piece together information from disconnected channels.

Context travelled with the work.

My goal wasn’t to create another messaging platform.

It was to ensure communication remained connected to the work it supported.

Outcome
Where Communication And Work Meet

Looking back, the most valuable outcome wasn’t faster communication.

It was reducing the effort required to understand what was happening.

By keeping communication attached to operational activity, teams gained greater visibility into conversations, decisions and progress without relying on disconnected tools.

The solution delivered:

  • Improved operational visibility
  • Reduced context switching
  • Better collaboration across teams
  • Faster access to information
  • Stronger auditability and traceability
  • Greater continuity throughout the lifecycle of work

This project reinforced something I’ve observed throughout my career.

People rarely struggle because information doesn’t exist.

They struggle because the information they need is disconnected from the moment they need it.

The best communication systems don’t simply help people talk.

They help people understand.