õfficevibe

Re-create office vibes, remotely

Could I find a problem the billion-dollar HR industry had somehow missed in less than two weeks? (Spoiler: yes!) This was off-script, off-the-cuff — UX meets Product Management, jazz-improv in one take. Enjoy!

The brief centred on Officevibe: a manager-first employee-engagement platform built on weekly Pulse Surveys, anonymous feedback and smarter 1-on-1s. The ask was a two-week sprint to help remote new starters onboard more easily and feel less alone. The reasoning was the pandemic story everyone knew. Offices shut, and the small human moments went with them: no watercooler chats, no post-work drinks, no bumping into someone by the kettle. New starters had it worst, joining a company they couldn’t see and learning who’s who through a screen. Build towards an MVP, it said, for a launch aimed at January 2022 new joiners.

That date was the first thing I noticed. I was reading the brief long after lockdowns had ended — offices open, hybrid already normal. My immediate thought was that this was a recycled General Assembly UX/UI Design Immersive brief from the previous year, and those students had probably got a great deal from it. Followed by: well, it was bestowed upon me. Challenge accepted! Let’s see what happens when I put my spin on it! I treated the brief as a hypothesis to test, so before I booked a single interview or sketched a single screen, I did the one thing it hadn’t: I asked actual remote new starters whether any of this still held. I put a short survey out from the off.

If not loneliness, then what?

First: was onboarding really solved?

If onboarding were only handled well at slick, well-resourced firms, the brief might still stand for everyone else. It wasn’t. Every company, whether bootstrapped, mid-size or large, treated getting onboarding right as a serious priority:

Small, medium, large — the same answer. Onboarding is a solved, well-funded routine now. Whatever the real gap was, it lived somewhere else. To find it, I listened to both sides properly.

The founders

Their playbooks were much the same: lead with the mission, assign a buddy to shadow, run daily stand-ups and 1-on-1s, and get everyone together in person once or twice a year. Laid side by side they were near-identical:

Stripped to its sequence, that shared play runs mission → buddy → friendships → meeting in person once or twice a year — and then stops. No step for the thing I’d soon realise mattered most.

The remote workers

Both had settled fast and felt genuinely supported — confirming the survey. But plotting their two journeys on one axis showed what the quotes alone didn’t:

One thrived. The other dived.

Same timeline, same mood axis. Sadiqa’s line holds high; Stipica’s climbs through onboarding, then falls away exactly where peer feedback should be.

Stipica’s gem

My very first interview handed me the thing I was hunting for. And it carried real weight, because of where Stipica sat: his company had laid off 10% of its people in seven months. Layoffs in the background, no clear read on his own standing — the exact pressure that’s only become more familiar since. Asked what his company could do better, he didn’t hesitate. He wanted “monthly pulses where each member would judge each member working with them — all anonymous.” That way he could finally see “what my stakeholders think about me.” His reason is the whole problem in a sentence:

Here was a capable person, doing well, watching jobs disappear around him, with no reliable read on how the people he worked with actually rated him. When people fear for their jobs, motivation drops just as the pressure on their numbers climbs. A fair, regular update on where you stand is exactly what breaks that cycle. I crystallised the idea as an index on how you’re doing — your standing with the people you actually work with. Stipica came first, so I raised this exact issue in every interview that followed. I wanted to test whether it was a real, unaddressed problem or just one person’s wish.

So I drilled into it with the others

All three told the same story. Your line manager owns your appraisal, but on cross-team projects they aren’t hands-on, so the people who actually saw your work have no way to weigh in. The need was real and unmet — so the next question was the product one: does anyone already solve this, and where would it even live?

I put my product hat on

Here is where I should say where I come from: before UX, I spent years as a product manager taking ideas to market. So faced with a real, unmet need, I didn’t reach for a sketch pad. The first questions were “does this already exist, and where would it actually live?”

Where would feedback live? Follow the work

Stipica’s peer pulses would only get used if they sat where the work already happened. And the work already had a home: Stipica ran his team out of Guru; Alan and Sadiqa both lived in Confluence — Sadiqa’s team even kept a kudos board there. So my opening hypothesis was simple: whatever I build should plug into the project tool people already open every day. Confluence was the obvious target.

So I got under Officevibe’s hood

Officevibe gave me full access — real login credentials, not a brochure — so I treated it like a product I’d been asked to extend. I set up accounts, clicked through every screen, and went straight to the part most people skip: the integrations list. The verdict was immediate — no Confluence integration. But I noted one that mattered: Slack (hold that thought; it comes back).

An example of an Officevibe Survey in action. A manager-first tool, built around anonymous check-ins.

Then I scanned the competition

Next reflex: was anyone else already doing peer-level feedback, and did any of them plug into Confluence? I worked through the survey market — Culture Amp, Lattice, 15Five, Peakon and the rest. They were strikingly alike: manager-to-employee pulses and engagement dashboards. None offered true peer appraisal, and none integrated with Confluence. One stood apart:

Most interesting competitor

Leapsome did everything Officevibe did plus onboarding — and integrated with Jira, not Confluence. Close, but no peer appraisal tied to the project.

Laid out side by side, the whole market told the same story — and left the same space empty:

Nobody let your peers appraise the cross-functional work your manager never saw. So the space was wide open. Game on!

Then I went to the source

To be certain, I arranged a call with an Account Manager at Officevibe. I asked, indirectly, whether they did anything like peer-and-stakeholder feedback. His answer described the product’s whole philosophy:

Confirmed: manager-first, no peer appraisal. The call paid off twice over — the Account Manager also mentioned a sister product, Softstart, that handles onboarding. That was a useful dead end to close. Chasing onboarding would have been wasted effort, and now I knew Officevibe already had that base covered. I could stay focused on the gap that was genuinely open.

And then — the brick wall

Everything pointed to the same plan: build peer feedback and slot it into Confluence, where the work lived. There was just one problem.

No native integration, no realistic way to bolt one on inside a two-week sprint. The plan I’d reasoned my way to was a non-starter. I sat with it, frustrated — and then, at 3am, the thing flipped.

Having login access made this more than a mock-up. I could build the new flow on Officevibe’s real screens, in its own visual language, so it read as a first-party feature rather than a concept bolted on from outside. And just like that, the integration problem had gone. Phew!

Framing the dip

Stipica’s journey held the whole problem in one shape. Everything his employer did well carried him upward — until the very end, where the line falls off a cliff. That drop wasn’t onboarding. It was the moment he realised there was no transparency about how his work outside his immediate line manager’s remit was being viewed, given the recent job cuts at his company.

That cliff is the design brief I gave myself. Stated as a How Might We:

Meet Amy

Every decision from here was tested against one person — Amy Tan. She’s a London take on Stipica: an experienced Product Manager, but a brand-new starter with everything riding on it.

Amy Tan

Product Manager · just started · Dalston, East London

Experienced PMNew starterCross-department project

Amy spent six months out of work — applying everywhere, slowly losing hope, taking odd jobs to make ends meet. After all those online forms that got ghosted, the break came in person. She met the company at Silicon Milkroundabout, the East London tech job fair, and finally got her foot in the door. She’s good at her job — but after half a year of rejection, the stakes of this fresh start feel enormous.

Needs

An honest, regular read on whether her work is landing — from the peers she actually collaborates with.

Fears

Layoffs are still happening elsewhere in the business. She’s acutely aware her footing isn’t secure.

The catch

Her project sits outside her department, so her best work is invisible to the line manager who decides her future.

Wins when

Feedback is specific, kind, and arrives while she can still act on it.

The problem, stated plainly

Here’s the problem as I framed it. A manager’s 1-on-1s and quarterly targets hang on KPIs and OKRs — but those outcomes are usually the result of a cross-department team effort. So a staff member, especially a new starter, can be a high performer and still have their contribution overlooked if something outside their influence falls over. The people who’d actually know — their peers on the task — have no channel to say so.

The vision

I then took a step back. If the feedback gap was fixed, the same people would go from overlooked to empowered.

Vision

A future where stakeholder feedback is instant, fuelling personal development, better 1-on-1s and people who stay. ♥

Lofty, I know, but every decision that followed pointed back to it.

And because the whole thing is peer-to-peer, it works in the office, hybrid or fully remote, and across any culture. Feedback between the people who did the work: problem solved!

Napkin to high-def Proto

The sprint was tight — so I sketched the concept on paper and went straight to high fidelity.

The concept: bring Projects into Officevibe. A project carries its team, its stakeholders and its objective. From it, you send a lightweight survey to the peers Amy actually worked with and set how long they have to reply. So instead of one manager’s verdict once a quarter, Amy hears regularly from the people she worked alongside.

One task, four fixes

With the concept built natively inside Officevibe, I put it in front of real participants. One task, watched closely — and every screen here is a before/after from those sessions.

Watching people run that task turned up four clear problems. Each became a change driven by what they said — not what I assumed.

Before

After

Before

After

Before

After

Before

After

The clickable prototype

Everything above comes together in a clickable Figma prototype: the native Projects tab, the stakeholder survey and the four test-led fixes.

The walkthrough runs the full loop: create a project, add a new starter, send their stakeholders a survey, then read the results back. Every step happens inside Officevibe.

What the sprint taught me

The first lesson was the biggest: don’t take the brief at its word. The problem it described had been real once, but the world had moved on and the document hadn’t. That 0% was all the reason I needed to change direction.

What I found in its place existed nowhere — peer appraisal of the cross-functional work a manager never sees. There was no pattern to copy, so I defined the problem and designed the first answer to it. That’s the part I’m proudest of.

õfficevibe

Anil Bhima

If I revisited it, I’d push the loop further. I’d spot trends across a whole cohort of new starters, and tie the feedback to the moment it changes a manager’s next 1-on-1.