Case study visual system

How should
product thinking
look?

Four minimal visual treatments for Signals. Each slide fits a desktop viewport and can be captured as a standalone LinkedIn image.

01Evidence ledger

02Product focus

03Decision trace

04Research notes

01 / 04

Visual direction

Evidence ledger

Treat every visual as proof. Captions make claims and annotations reveal the judgement behind the screen.

Best forRecruiter comprehension and product judgement

“

The platform is easy enough to use. I just don’t always know what I should be looking for.

Illustrative synthesis · replace with verbatim research

The reframeThe real problem wasn’t access to analysis. It was the distance between seeing an idea and feeling confident enough to act.

Signals detail screens showing the progressive information hierarchy
1
Orient firstDirection, market and status before technical terminology.
2
Depth on demandWin rates and levels remain available for scrutiny.
Plain-language context comes first. Technical evidence remains available without dominating the first read.
1
Curate before presenting

Show fewer, higher-quality ideas so the feed feels selected rather than dumped.

2
Borrow a learnt behaviour

Reuse watchlist and filter patterns users already understand.

1 tap

Signal to order ticketInteraction principle, not a claimed outcome

02 / 04

Visual direction

Product focus

Give one product observation enough space to land. The interface is the evidence, not decoration around it.

Best forProduct craft and LinkedIn impact

Signals

More information
wasn’t the answer.

Make ideas easier to understand, then easier to act on.
Signals integrated into the desktop trading platform
1
Native entry pointSignals sits beside tools traders already use.
2
Action stays presentThe insight resolves into an order, not another report.
Third-party intelligence adopts the product’s own interaction grammar, so it feels native rather than embedded.
1
Start with confidence

Every extra idea has to earn its place.

2
Reveal expertise gradually

Plain language first, technical depth one step away.

3
End in the product

Carry intent into a familiar order flow.

03 / 04

Visual direction

Decision trace

Show the causal chain behind the interface, from user tension to product rule and commercial effect.

Best forTechnical fluency and trade-off reasoning

1User tension

I can trade, but I do not know what to trade

2Reframe

The gap is confidence, not information

3Product move

Curate, explain, then shorten the path to action

4Commercial effect

More useful intent reaches the order ticket

Annotated Signals detail screens
1
ExplainStart with a readable idea.
2
SubstantiateExpose performance context when needed.
Each marker identifies the product rule implemented by that part of the interface.
1
Reduce the choice set

Rank quality above catalogue completeness.

Trade-off: A relevant niche idea may be hidden.
2
Preserve expertise

Let beginners stop early and experts continue.

Trade-off: More content states to maintain.
3
Translate the provider

Use familiar states, filters and actions.

Trade-off: Native mapping adds integration work.

Core principleEasy to use does not mean easy to decide.

04 / 04

Visual direction

Research notes

Let one human insight interrupt the product evidence. The system remains editorial, but the work feels observed rather than packaged.

Best forResearch texture and personality

“

I understand how to place a trade. Finding one I actually believe in is the difficult part.

Illustrative synthesis · replace with verbatim research

ObservationInformation volume was being mistaken for usefulness.

KeepWatchlist behaviour was already learnt and trusted.

RemoveProvider-shaped terminology at the top of the experience.

Before

Dense provider language

Signals feed
Ideas compete equally for attention.
→
After

Curated, readable, actionable

Signals detail screen
One idea is explained before asking for action.
1
Edit the feed

Fewer ideas made the product feel more confident, not less capable.

2
Stage the explanation

Start in plain English and reveal technical evidence deliberately.

3
Make it belong

The provider disappears behind familiar product behaviour.

Recommendation

Build around
Evidence ledger.

It communicates judgement fastest and scales across screenshots, research, metrics and diagrams without becoming a portfolio template.

80%

Evidence ledgerCore framing, captions and comparisons

15%

Decision traceCausal diagrams where logic matters

5%

Research notesOne human fragment per case study

  1. 1

    Every annotation states a decision. Never label what the screenshot already shows.

  2. 2

    Every caption makes a claim. Screen names are metadata, not explanation.

  3. 3

    Every metric carries provenance. Show the baseline, period and confidence.

  4. 4

    One visual, one argument. Crop aggressively when context is not the point.