OneLink

Teams today have so many links stored in so many places.

Role

Co-Founder, Head of Product Design

Timeline

Apr - May, 2023

Skills

User research, Product design, Interaction design

More than just a dashboard

Shared dashboard for teams to store all their links in one place. But it OneLink is also built to be accessible from anywhere:

1.

Save and auto-categorize links on your browser via a Chrome Extension

2.

Auto-save links mid-conversation via a Slack/Discord bot

3.

Generate onboarding briefs via a Slack/Discord bot

User Research
Finding the right customer segment

Our team interviewed 40+ people in various industries and company sizes. Here are the most notable insights:

The Problem
Too many links across too many places

User Problem

Finding important links across separate platforms is irritating and results in lost time and, sometimes, lost work.

User Research Takeaways

1.

Problem is consistently felt in teams with 10-50 people

2.

On average, links are scattered across 4+ platforms

3.

Most projects have 8+ links from at least 2 tools

The Process
Time constraints = Speed + Rapid iterations

* Doing user research in parallel with designs meant iterations could be implemented swiftly

Constraints

As a side-project, my friends and I wanted to launch in 15 days. This means the designs needed to be quick to develop, while catering to user behavior!

Scope & Initial Feature Sets

With our 15 day timeline, we had to be picky with our initial features, relying on user feedback to prioritize the next features to add:

* For our MVP, users didn't get an 'invite and accept' email. They just had to log in lol.

Iterating from our Beta-Tests

Beta-testing helped when designing something filled with many assumptions like our "Sharing Permissions."

I gave 8 beta-testers a goal: "Share this dashboard." Below is the original design (A) and the iteration (B).

[A]

This was the original permissions design, inspired by Figma. But, our users didn't know how to send out invites nor did they understand how the link sharing permissions worked.

[B]

This is the new and updated permissions design. Using user feedback, we added an invite button. We also made a more intuitive way to set the link sharing permissions.

The Solution
Save, access, and share your links in one place

Feature #1 / Dashboard

[1]

This is your team's dashboard. Click the large "+" icon to add a link

[2]

Paste your link and continue

[3]

We'll autofill the details for you (site icon and title)

[4]

This is what a filled dashboard would look like

* To watch a demo for features 1 and 2, scroll to the top or bottom

Feature #2 / Sharing Permissions

[5]

Add your teammates' emails to give them view/edit access or send them a link to your dashboard!

[6]

If a user isn't logged in but they try to access a dashboard, this is what they see

[7]

If a user is logged in but doesn't have access to a dashboard they opened, a "request access" container appears

* To watch a demo for features 1 and 2, scroll to the top or bottom

Feature #3 / Alternate Points of Access

We built ways to access OneLink without going into the dashboard.

[8]

Click on the extension and we’ll automatically parse the link and title. We'll also auto-sort it into the right dashboard

[9]

Add optional tags before the bar reaches the end

[10]

Some users store and share links on Discord/Slack. So we made a bot where users can store and request links

Reflection
Beta-Testers to Users to Nothing

Lessons

It's obvious that talking to your users can open many doors. But listening without products can only take you so far. Never waste time on indecision: just launch and iterate as it opens new directions.

Reflection

‍OneLink started as a side-project to solve our own pains, but we thought it would be fun to launch it.

Nobel

Case Study: Personal AI research assistant