A single view of contributors, followers and any connected channels from apps - so that project owners can check their updates are reaching the right audience and manage access if they need to.
We released the Share dialog exclusively to private projects to gain confidence. Feedback from customers was positive, but when we began to dogfood the redesign on open projects, I found some rough edges.
I streamlined the details about who is following and connecting to channels. The interface optimises for copying a link and adding new people as the main task.
We knew from research that some of the use cases for private projects were highly sensitive, like company acquisitions and HR policy work.
I opted to provide consistent reassurance about whether a project is open or private - in the dialog, with a lock lozenge on avatars, and an icon on the Share button.
Compared to Slack, Microsoft Teams requires users to go through a few extra steps to install an app.
I added guidance to help people get setup when discovering the option to connect a channel to their Atlas project.
The redesigned experience supports privacy and sharing tasks, and is an important surface for inviting new users.
What I learned
When I brought up pausing the customer rollout because of my concerns that the flow felt clunky for open projects, the team were receptive.
It cost us additional development effort to make changes to the experience, but the appetite is to get the experience right.
