Threads Case Study ✨ Basewell

For Engineers

For Designers

For Product Managers

For Customer Experience

Made with 💜 in SF, LA, SAN, SEA, DEN, TOR, BOS, NYC, NJ, PHL, NC

👋

A bit of context

Hi! We're Brittany (COO) and Evan (CEO) of Basewell. Basewell is a better training platform for startups. In a post-covid world, companies are using virtual tools more than ever to replace IRL connection, so it's really important to have training materials that aren't fragmented.

"Honestly, it felt like we were babysitting our tools before we introduced Threads."

🦕

Life before Threads

We're millennials, so we mainly just used Slack. And honestly, it was awful. It was just so messy. There was no way to know if anyone was actually reading the messages shared, so there was a lot of "did you see it? did you respond? did you do this?" And god forbid if it was in a private message — you can't even search for that!

Information was everywhere. It was very hard to define one central source of truth.

Information was everywhere. It was very hard to define one central source of truth.
We were wasting a lot of time with our team going back and forth.
The search functionality was terrible which made finding older discussions nearly impossible.

We were wasting a lot of time with our team going back and forth.

The search functionality was terrible which made finding older discussions nearly impossible.

🧠

The secret to success

It's eliminated fragmentation in our tool stack. Threads presentation mode has replaced Loom, the video presentation and narration has replaced Zoom, and obviously Threads in and of itself fundamentally replaced Slack. It's even replaced some information housed in Notion because it's just so easy to find.

We're on a hybrid schedule, so even though we work in person we still prefer using Threads over talking — this way we can actually document information, it can be followed up on, and we don't feel like we're interrupting our workflows even if we're in the same room.

We can write out Threads ahead of a meeting and it's truly a love language for us — it's amazing.

An example of presentation mode with video narration

☀️

A day in the life

Integrations on Threads are key for us, since eliminating fragmentation is the goal of what we're doing with our software. Linear and GitHub are really core to our process — we can keep a running track record of what's happening in a thread, and build the conversation around that while keeping tasks in the other tools.
- For example, if we have a support ticket, and then a PR related to the ticket, we pull both of those items into Threads and continue a specific dialogue through threads with the presentation tools, code embed, etc.
- We also use Zapier <> Threads and it has been the best thing ever. It's really, really streamlined.

Integrations on Threads are key for us, since eliminating fragmentation is the goal of what we're doing with our software. Linear and GitHub are really core to our process — we can keep a running track record of what's happening in a thread, and build the conversation around that while keeping tasks in the other tools.
- For example, if we have a support ticket, and then a PR related to the ticket, we pull both of those items into Threads and continue a specific dialogue through threads with the presentation tools, code embed, etc.
- We also use Zapier <> Threads and it has been the best thing ever. It's really, really streamlined.

Integrations on Threads are key for us, since eliminating fragmentation is the goal of what we're doing with our software. Linear and GitHub are really core to our process — we can keep a running track record of what's happening in a thread, and build the conversation around that while keeping tasks in the other tools.
- For example, if we have a support ticket, and then a PR related to the ticket, we pull both of those items into Threads and continue a specific dialogue through threads with the presentation tools, code embed, etc.
- We also use Zapier <> Threads and it has been the best thing ever. It's really, really streamlined.

Integrations on Threads are key for us, since eliminating fragmentation is the goal of what we're doing with our software. Linear and GitHub are really core to our process — we can keep a running track record of what's happening in a thread, and build the conversation around that while keeping tasks in the other tools.
- For example, if we have a support ticket, and then a PR related to the ticket, we pull both of those items into Threads and continue a specific dialogue through threads with the presentation tools, code embed, etc.
- We also use Zapier <> Threads and it has been the best thing ever. It's really, really streamlined.

We will start a running thread of what we accomplished, what we had issues with, thoughts we had, whatever else would come up and schedule the thread to be sent out to the team as a recap. That means people can easily take 10 minutes, if even that, to cross-examine each thread, make comments, create follow-ups...it's awesome.

💥

The moment it clicked

"I didn't realize how much we were missing until we had Threads."

Literally every simple feature — you don't realize how important they are until you use it.

Mark as unread
Image highlights
Follow ups
Writing in blocks
…all of it

Mark as unread
Image highlights
Follow ups
Writing in blocks
…all of it

👍

A recommendation

You should use Threads if you prioritize productivity and happy people. If you actually care about remaining productive and care about the quality of life for your workforce, the quality of information being shared, and communicating in a delightful way, then Threads is for you. It's what the future of communication actually looks like.

"If you care about productivity and happy people, you need Threads."

How Threads replaced all other tools for Basewell

company

insights from

Brittany Stewart · COO

Evan Stewart · CEO

Published

December 21, 2022