Use cases
AppsPricingContactBlogSign In
How we use Threads
We use our platform to stay on the same page, collaborate efficiently, and make decisions across different locales and timezones.
Rousseau started a thread
in Announcements
Company, Team, & Individual Flow
Rochelle started a thread
in Design
Admin settings R2 - 77% www
Gabriela started a thread
in Eng Discussions
33% Use Typescript instead of Flow
Rosalee started a thread
in ThreadFam
Women's History Month/ International Women's Day 2020
Click to scroll
Rousseau Kazi
Today
MARKED FOR FOLLOW UP
WE'RE GROWING
We have more customers to support, more members of our #threadfamily, and with that, more projects we're currently tackling. In a couple of weeks, we'll have doubled our number of employees for the year (which is nuts).

GROWTH IS EXCITING
Everyone here has seen us go through the initial struggles of starting a company. This team has been focused, clear, and has executed to get us through some of the scariest questions that every startup faces.

GROWTH IS PAINFUL
Growth is equal parts exciting and exhausting. We're creating a lot of value in a short amount of time. Things weren't meant to grow this fast and with that growth comes pain. This is true from exercising to building a company.

In many ways, we've earned the right to feel growing pains. However, that doesn't make parts of it any less frustrating.
Things were easier when we all fit around one table or when we could all take a single car to an event. Things were easier when I could ask a question and immediately get a response. Things were easier when I was looped into every discussion.

GROWING PAINS COME FASTER THAN WE THINK
I was thinking about how/why this happens for teams specifically. I was able to distill it down to a few points:
  • Most team systems are designed for the current team size.
  • Team communication is an N^2 problem (grows exponentially with the number of people hired).
  • Humans suck at truly internalizing how fast exponential growth can creep up.
  • The kicker for teams is when we hire an additional person, we interpret it as linear growth when it's actually exponential.
  • 
    IT'S ALL ABOUT FLOW
    Q: Why do we create processes for communication & execution? Why do teams implement structure, systems, & shared language?
    A: It's all about flow.
    
    Flow is this magical state where the whole is greater than the sum of the parts. For many startups (especially us), it's the competitive advantage.
    
    You get flow when everyone feels safe, secure, and empowered to do their best work. You get it when people know the company is on the right track, when they know how to navigate/operate/communicate within the team, and when they know they're on the right path to maximize their value/personal growth.
    
    IMPROVING OUR FLOW
    The systems/processes we created to maximize flow for our team last year are starting to crack as we grow. To some of you, the cracks are clear. For others, you haven't really noticed it yet. In either case, if left unattended, the additional stress as we grow will cause the cracks to become breaks.
    
    Over the next few months, I will be focusing on making more intentional investments to maximize our flow. Flow will be broken up into company, team, and individual flow. Even though we will be thinking through all of these in parallel, we will likely implement them serially.
    
    IMPROVING COMPANY FLOW
    Company flow is knowing your go to market, understanding your personas, and having a clear path to the next step of success.
    
  • Value: We know our product is valuable. We have people we've never met before paying top dollar for it, leaving great testimonials, and we would be shocked if they ever churned.
  • Scale: We have seen our product growing on it's own, without our help. We need to double down on our investments here.
  • 
    We have amazing work in the pipeline that will help here. Explorations around Silk, easy to access mobile apps, a re-engagement system, a potential desktop app, templates, and so many other things landing around the same time. Any one of these things can have a significant impact on our ability to precipitate broader product scale fit.
    
    The next 6 weeks will be filled with strong insights. Improving company flow will come from us doing a great job landing these major projects over the next few weeks and efficiently learning from them.
    
    IMPROVING TEAM FLOW
    By team, I mean #threadfam. As our team scales, it's getting harder to know...
  • What am I accountable for?
  • How does my work apply to the larger company strategy/flow?
  • How do things get prioritized?
  • Who can unblock me?
  • Which threads are urgent vs. things I can get to later?
  • Am I working on the most important thing?
  • etc.
  • Ultimately, this is all tied to "What is my identity at the company? Am I doing my best work here?". Team structures, shared language, and well-designed holistic processes help answer these questions and more. When people know who they are, how their role plays into the bigger picture, and how they can self regulate/navigate the system - it's much easier for them to do their best work (which will lead to collective flow).
    
    IMPROVING INDIVUDAL FLOW
    We hire incredible people. Even some of the most selfish desires are for the greater good. The number of people who come to me asking for how they can "grow" so they can help the company and their colleagues is inspiring to say the least.
    
    Individual flow comes from someone understanding their weaknesses, their superpowers, understanding who they want to be, and the path to get there. When someone is excited about who they can be, they end up finding more energy and creativity for the journey. This leads to them getting into a strong positive feedback loop, and ultimately helps them reach flow (which increases team flow, which increases company flow).
    
    As we grow, we're going to need to have individuals who are directly responsible for maximizing another individuals flow/growth (aka managers). This word is very overloaded and I think most companies mess this up, so more on this later.
    Flow Pyramid
    NEXT STEPS
    
  • Share with the team my thinking around maximizing flow & growing pains, and what's on my mind.
  • Make sure the company is on track for landing the major changes that will help us find product scale fit & have a path to full launch.
  • In parallel to [2], start thinking through, getting feedback, and putting together a proposal for a team structure that will (i) maximize flow (ii) support our growth for the next 12months (minimum).
  • Once we have a team structure that we're willing to commit to for a bit, start designing out the best way each individual can get the support they need to maximize their own flow.
  • 
    16
    Tami, Mehdi and 14 others
    See how Threads has worked for a few of our teammates
    Meet
    Gabriela
    From referencing requirements, responding to bug reports to organizing our movies nights, Gabriela uses Threads every day to contribute to the product, learn from and support the team, and build the company culture.
    We use threads to
    Discuss online, in one tool
    Proposal spaces keep your team's work and feedback organized. A thread is designed for discussions, so the conversation stays in one place, and doesn't get scattered across tools. The space stores all the feedback, so it's easy to catch up and contribute later.
    Projects
    Updates
    Proposals
    Our team shares product feedback so everyone can discuss next steps in one thread.
    Rochelle started a thread
    in Design
    Admin settings R2 - 77% www
    Shirley started a thread
    in Launch
    Design Left Pre-Launch
    Click to scroll
    Rochelle Shen
    Today
    MARKED FOR FOLLOW UP
    I'm really excited to have the 2nd main 77% iteration of admin settings after user research. This allowed me to continue the iterative design process, which greatly improves the design each time in the cycle.
    
    I'm going to go over: 1/ People, 2/ Profile & Settings, 3/ Permissions.

    1 — People

    view all people & invitations
    Members & Guests tab
  • Combining members and guests together.
  • Columns to view role, joined date, and invited by.
  • Links to non-compliant members and security section.
  • 
    Invitations tab
    
  • A central place for admins to see how and who can invite members to the org
  • Links to Permissions tab and Whitelisted domains section

  • 2 — Profile & settings

    Org name, image, share link, default spaces
    Share link and default spaces may not live here and be moved to invitations. If you have feedback on a better location for these, please leave it below also!

    3 — Permissions

    Role based access
    One big focus of this iteration was making settings more granular to have more role based options. The settings are now broken down by feature (space, thread, user list) and have permission options for each one.

    Next steps

    I will continue to polish a couple of the items I mentioned above for a final revision and incorporate any feedback from this as well. If there's feedback you want to give, please leave it by next Wednesday 1/29.
    11
    Abdul, Chris and 9 others
    Rousseau Kazi
    MARKED FOR FOLLOW UP
    Thanks for taking the time to write this all up, Rochelle. When someone new to product thinks about "design" they tend to over-fixate on new features. However, the hardest design projects are system projects. It's been cool to see you tackle this and work through our feedback. Keep up the great work.

    OVERALL FEEDBACK

    
    Principles: For these types of projects, it's good to restate the principles you're optimizing for. It makes it easier for people to understand why you made certain decisions.

    PEOPLE

    
    (?) I'm a little confused by the Invitation page. What I'm seeing in this page are all of the people who have currently been invited but has not accepted the invite yet, right? Will admins be able to trace who invited anyone? For example, if you already created your account - could I track which member invited you?

    PROFILE & SETTINGS

    
    This all looks good to me. I imagine the "manual default spaces" ui will look the same as it does today.
    
    Share link and default spaces may not live here and be moved to invitations. If you have feedback on a better location for these, please leave it below also!
    
    (?) I'm not in love with the name Profile & Settings. I just don't think it makes a ton of sense for the Organization since profile feels very individual. Maybe Organization Settings? Logo, Name, Default Spaces feels better for Org Settings I think.
    
    Though, I'm not the content expert here - so would love to hear what Courtney thinks here.
    Today
    Suman Venkataswamy
    MARKED FOR FOLLOW UP
    Great feedback Rousseau!
    
    What I'm seeing in this page are all of the people who have currently been invited but has not accepted the invite yet, right?
    That's correct. Is there anything in specific that you were confused by or is there something that you were expecting instead?
    
    For example, if you already created your account - could I track which member invited you?
    Yup! This is actually in the main members and guests tab, but sounds like we might want to make this more clear?
    image.png
    I'm not in love with the name Profile & Settings
    Rochelle, Courtney- I believe we just decided to make this "Profile", right?
    Today
    Rousseau Kazi
    MARKED FOR FOLLOW UP
    Yup! This is actually in the main members and guests tab, but sounds like we might want to make this more clear?
    
    Thanks for highlighting it in the image! I was going through a lot of them, so easily missed it. Yes, that's for sure clear enough. Thanks!
    
    I believe we just decided to make this "Profile", right?
    
    Profile still feels weird to me since it's so associated with an individual account, but that could just be me. If other products also call it profile, then I think that's fine.
    Today
    Rochelle Shen
    MARKED FOR FOLLOW UP
    However, the hardest design projects are system projects. It's been cool to see you tackle this and work through our feedback. Keep up the great work.
    Thanks Rousseau, it's been such a fun project, can't wait to ship it 🥳!
    
    Principles
    Ah totally. I should've linked the main admin settings product principles that Suman and I worked on here, because I didn't want to flood the beginning of this thread with all of that since we have another post. There is a combination of the principles & insights from these threads:
  • Revamping the Admin View and Org Settings
  • [Summary] Admin settings user research: December 2019
  • 
    Profile still feels weird to me since it's so associated with an individual account, but that could just be me. If other products also call it profile, then I think that's fine.
    Yup, I'll take another pass with Courtney. I think if we are keeping the location of share link & default spaces, we can add be more description than just "Profile".
    Today
    Slack and Threads work better together
    Slack and Threads both help our team distribute our work. Slack is great for urgent or high-speed work, like notifications from integrations, and Threads is great for important & longer-lasting work, like aligning on goals & priorities.

    Linking Channels & Spaces
    We found the best way to pair these technologies is by linking a Threads Space with a Slack Channel. Whenever a thread is posted in a linked space, our integration will cross-post that thread to the slack channel.

    For a full set of features and installation instructions, check out integrations page here
    We use threads to
    Unblock a project, from one space
    A project space provides a layer of hierarchy in discussion, so you can see every discussion, and unblock them, from one place. Coordinate, share proposals, and raise questions — knowing nothing will get lost or forgotten.
    Launch
    GDPR
    Website Redesign
    Hit milestones together—we share blocking tasks so the team can chip-in to help, and then celebrate the wins.
    Jon started a thread
    in Launch
    Deploy schedule for Launch
    Shirley started a thread
    in Launch
    Design Left Pre-Launch
    Click to scroll
    Jon McCord
    2 days ago
    MARKED FOR FOLLOW UP

    Context

    Rousseau had asked
    What's our schedule for launch day?
    See here:
    Dry Run Update 2/23

    Schedule:

    There are two separate deployables: Public Site (the waitlist, survey, help articles, etc), and Web App (the Threads web app and backend).
  • 130 PM: Suman deploys our Web App build to RC for one last QA pass.
  • 6 PM: deploy the RC Web App build to production.
  • 10 PM: all Public Site changes should be in master.
  • Create a minimal "coming soon" landing page for Public Site. This will be used between 12am and 6am, and in theory, won't be seen by anyone. Rosalee is this ok with you?
  • 5am or 530am: Launch the full Public Site again to threads.com. Sanity test one more time. We are now ready for the embargo to end! Sohan thoughts on 5 versus 530?
  • Tomorrow, after QA pass: deploy the RC Web App to production one more time.
  • 
    Thoughts?
    8
    Wei-Wei, Suman and 6 others
    Rosalee MacKinnon
    MARKED FOR FOLLOW UP
    Create a minimal "coming soon" landing page for Public Site. This will be used between 12am and 6am, and in theory, won't be seen by anyone. Rosalee is this ok with you?
    
    Sounds great!
    5
    Chris, Mark and 3 others
    2 days ago
    Sohan Jain
    MARKED FOR FOLLOW UP
    5am or 530am: Launch the full Public Site again to threads.com. Sanity test one more time. We are now ready for the embargo to end! Sohan thoughts on 5 versus 530?
    We should give ourselves at least 30 minutes before we want the site to be completely live to allow time for the deploy itself, dns updates, and any contingencies. My vote is earlier = better
    2
    Gabriela and Jon
    2 days ago
    Hiro Dozono
    MARKED FOR FOLLOW UP
    For the 'coming soon' page, at which level are we handling that? cloudfront behavior? (Sohan do we already have that or is it easy to add in?)
    3
    Jon, Sohan and Wei-Wei
    Today
    Jon McCord
    MARKED FOR FOLLOW UP
    can we not just deploy a gatsby app that says "coming soon?"
    Today
    Hiro Dozono
    MARKED FOR FOLLOW UP
    ok so:
  • make a modified gatsby app that has just 'coming soon'
  • build and deploy
  • when we're ready, revert changes and rebuild and deploy?
  • 
    Today
    Jon McCord
    MARKED FOR FOLLOW UP
    Yup, exactly.
    Today
    Hiro Dozono
    MARKED FOR FOLLOW UP
    Sounds good! We just need a new built index.html. we can replace the contents of the s3 bucket's web/ and mobile/ folders with that index.html.
    Today
    START A THREAD
    Unlock your team's potential
    Resources
    Blog
    Terms & Privacy
    © 2020 Threads Group Inc.