04 / Connected service

Service design · Cross-channel UX

From offer
to keys.

One home-buying journey that keeps customers, specialists, documents, and decisions in context—even when the service moves between digital and human channels.

Independent concept study
Research-informed wireframes
ONE JOURNEY · MANY ACTORS

No lost context.

The product does not replace every specialist. It makes their shared journey understandable.

Home journey68% complete

Your next step

Review the valuation report

Offer acceptedDocuments verifiedProperty checksFinal approvalClosing day
ADVISOR HANDOFFYour context is ready.

12 decisions · 8 documents · 2 open questions

Meet Derya at 14:30 →
Context

Independent home-buying service concept

Ownership

Research synthesis · Service model · UX

Core channels

Desktop hub · Mobile companion · Human support

Status

Research-informed · Validation-ready

01 / The service problem

The customer has one goal. The system gives them many disconnected processes.

Buying a home involves a lender, property agent, legal professional, surveyor, insurer, seller, and internal operations. Each participant sees one part of the journey. The customer is left to connect the status, documents, deadlines, and consequences.

Design question

How might we make a multi-party service feel like one continuous journey—without hiding who is responsible for the next step?

02 / Research → design decisions

Three signals shaped the service model.

This is desk research for a concept study. Customer and operational interviews are the next validation layer.

01

A home purchase is an ecosystem, not a single application.

SIGNAL

Official guidance names lenders, insurers, legal representatives, surveyors, advisers, agents, and specialist trades as participants in the process.

DESIGN RESPONSE

Show the actor, owner, dependency, and next action at every milestone.

GOV.UK · How to buy a home ↗
02

Information exists, but the journey is not streamlined.

SIGNAL

Fannie Mae research describes homeownership as infrequent and complicated, with consumers gathering information from many sources instead of one streamlined process.

DESIGN RESPONSE

Create one journey record: decisions, documents, questions, and updates stay attached to the same milestone.

Fannie Mae · Consumer education research ↗
03

Closing creates a dense burst of requests and irreversible decisions.

SIGNAL

CFPB guidance asks buyers to submit additional documents, choose service providers, review forms, arrange inspections and insurance, and stay alert for revised information.

DESIGN RESPONSE

Prioritize the next blocking action, explain why it matters, and preserve a review trail before commitment.

CFPB · Closing on your new home ↗

03 / Service ecosystem

One customer journey. Seven operational perspectives.

The interface becomes a shared coordination layer, not a pretend replacement for specialist work.

SHARED JOURNEY RECORDCustomer goalBuy the right home with confidence
CustomerDecisions · documents
LenderEligibility · approval
Property agentOffer · seller updates
LegalSearches · contracts
SurveyorValuation · condition
InsurerCover · evidence
OperationsExceptions · handoffs

04 / Journey architecture

The product organizes work around milestones—not departments.

Every stage answers four questions: Where am I? What is next? Who owns it? What could block progress?

01

Prepare

Affordability, goals, decision in principle

Customer + lender
02

Offer

Property details, offer, accepted terms

Agent + customer
03

Verify

Documents, valuation, survey, searches

Multiple actors
04

Commit

Final approval, review, contracts

Lender + legal
05

Complete

Funds, keys, move, post-close record

Shared closure

Design principles

01

Next, not everything

Prioritize the one action that can move or block the journey now.

02

Ownership is visible

Every wait state names who owns it and when the customer should expect movement.

03

Context travels

Human support receives the decisions, documents, and unresolved questions already captured.

04

Commitment slows down

Irreversible steps receive a clear review state, not a faster button.

05 / Selected wireflows

Three flows prove the connected-service model.

Desktop carries the journey overview and heavy information work. Mobile supports moments, evidence capture, and human handoffs.

FLOW A · START & ORIENT

Turn a fragmented process into a personal route.

The customer sees their full journey, the current milestone, and one prioritized action without reading a project plan.

HOME JOURNEY

Good morning, Buse.

YOUR PURCHASE
12 Willow Street

Offer accepted · £420,000

68%Journey complete
YOUR NEXT STEP · DUE FRIDAY
Review the valuation report

The lender has completed its valuation. Review the result before your mortgage moves to final approval.

1Offer accepted
2Documents verified
3Property checks
4Final approval
5Closing day
WAITING ON
Legal searches

Owned by Mason & Co · Update expected 24 Aug

UPCOMING
Advisor review

Tuesday · 14:30 · 25 minutes

OPEN QUESTION
Is the survey separate?

Answer ready from your guide

A1 · JOURNEY HOME

Senior signal: prioritization, wait-state ownership, and cross-service status are designed as one system.

FLOW B · KEEP MOVING

Resolve document problems without restarting the journey.

A request is attached to the milestone, the reason is visible, and rejected evidence has a clear recovery route.

DOCUMENT HUB

Everything for your purchase

DocumentOwnerStatus
Proof of incomeYouVerified
Bank statement · JulyYouNeeds attention
Property valuationLenderIn review
Legal searchesLegalWaiting
Building insuranceYouNot started
NEEDS ATTENTION
Bank statement · July

The first page is missing, so we cannot verify the account holder and statement period.

What to includeAll pages · name · account number · date
Why we need this
Document request3 of 5
INCOME VERIFICATION

Add your July statement

All pages are required. You can upload a PDF or take clear photos.

Upload a filePDF, JPG, PNG · max 15 MB
What should be visible?

Your name, account number, statement dates, and every transaction page.

Review upload4 of 5
BANK STATEMENT · JULY

One page may be missing

Page 1MissingPage 2ReadyPage 3Ready
Why this matters

We need the opening page to confirm the account holder and date range.

B1–B3 · DOCUMENT RECOVERY

Senior signal: exception handling is part of the primary flow, not an error page after it.

FLOW C · HUMAN HANDOFF

Bring a person in without making the customer repeat the story.

The service prepares both sides: the customer knows what the meeting will solve, and the advisor receives a concise context pack.

Your advisorSecure
CONTEXT HANDOFF

Derya is ready to help.

Your journey summary will be shared before the call. You can review exactly what she sees.

DK
Derya KayaHome journey specialist
Tue · 14:30
12 decisions captured8 documents ready2 questions to resolve
Meeting ready14:30
WHAT WE WILL RESOLVE

A focused 25-minute review

01Valuation result02Survey choice03Final approval timeline
You will not need to repeat

Your property details, income documents, offer terms, or previous decisions.

ADVISOR WORKSPACE · READ-ONLY SUMMARYMeeting in 08:14

Buse’s home journey

12 Willow Street · Offer accepted · Property checks in progress

68%journey complete2open questions1blocking action
CUSTOMER GOAL

Complete the purchase with a clear view of property condition and total ongoing cost.

DECISIONS ALREADY MADE

Fixed-rate option selected · Offer terms confirmed · Legal representative appointed

MEETING OUTCOME

Explain valuation vs. survey, decide survey level, confirm path to final approval.

Context generated from the shared journey record
C1–C3 · CONTEXTUAL SUPPORT

Senior signal: channel transition is designed as a data and expectation handoff—not a calendar link.

06 / Service blueprint

One calm surface requires coordinated work underneath.

The blueprint identifies where a visible status depends on an operational event, document, or specialist decision.

CustomerOffer acceptedUploads evidenceReviews valuationMeets advisorSigns & completes
Front stageJourney startsDocument hubNext actionContext handoffCompletion record
LINE OF VISIBILITY
Service layerMilestone createdQuality checksDependency logicSummary generatedJourney closed
ActorsAgent + lenderCustomer + opsLender + surveyorAdvisorLegal + funds
SystemsCase recordDocument serviceStatus orchestrationScheduling + CRMAudit archive

07 / Validation plan

Test continuity, not only usability.

01

Orientation

Can buyers identify their current milestone, next action, owner, and blocker within 30 seconds?

02

Recovery

Can they fix a rejected document without re-uploading unrelated evidence or contacting support?

03

Handoff trust

Do customers understand what context is shared and feel ready for the advisor conversation?

04

Operational truth

Can internal teams maintain the statuses and promises the interface exposes?

Reflection

A connected service is not one interface. It is one reliable understanding of progress.

The design opportunity was not to automate every specialist. It was to make responsibility, dependencies, and context travel across them—so the customer never has to reconstruct the journey alone.

Selected work complete

Four stories.
Different kinds of complexity. ↗

Back to all workStart again with Safety Shield