A small group in conversation around a table in a bright workroom

Batu Caves · Selangor

Which features in a productivity app actually stay in daily use.

Socket Vertex Hub sits with people while they plan the day, file a note, or skip a reminder. We write down what they keep, what they bury, and what they already do on paper. The work is for teams who ship task lists, calendars, notes, and document editors — and who are tired of guessing from a chart.

Request a feature adoption study

The work

A study, not a score.

We do not sell a rank or a dashboard. We recruit people who already use the app for real jobs in Malaysian offices, watch a named set of features, and return a brief the product lead can read before the next planning sitting.

Colleagues with printed pages spread across a meeting table

Flagship

Feature Adoption Study

Four to six weeks. Four to eight named features. Eight to twelve people who already live in the app. Observed sessions, conversations with those who stopped, and a written brief plus a sitting with the product group.

Read the study outline

First-Week Walkthrough Review

New users during their first seven days: what they reach, skip, and never notice while the getting-started path is still on the screen.

Walkthrough details

Abandoned-Feature Interviews

People who tried a capability and went back to the method they already trusted. The substitute is the finding.

Interview details

How a week looks

We watch the work, not the empty state.

A typical Tuesday in this office starts with a coordinator in Shah Alam who never opened “My Day,” a teacher in Cheras who muted reminders after they fired in class, and a clerk in Gombak who still tags nothing because search already finds last month’s note. Those are the hours we try to sit in.

The method is written out in full — recruitment, consent, observed sittings, and the briefing we refuse to turn into a town hall.

See how a study is run

Desk with papers, a notebook, and a person reviewing written notes

From recent sittings

What people told us after the brief landed.

They sat with two of our coordinators in the operations room in Shah Alam and watched them ignore the repeating-task field for an entire morning. I had assumed the field was hard to find. It was not. The coordinators already kept repeats in a wall calendar they trusted in front of the whole shift. The brief named that, which annoyed me at first, and then saved us from another round of tutorial screens.
Hafiz Rahman, Product lead, a task list used by warehouse teams
The first-week write-up was shorter than I wanted. I said so in the briefing. Farid pointed at the day-three notes: nobody had opened the shared-tag screen because the shared folder in the old notes app still held the month’s work. Length was not the problem. We had asked the wrong people to switch too early.
Siti Nur Aisyah, Research manager, a notes app sold to small offices

More client notes

Field notes

From the journal