Postman Enterprise

Managing world class API development teams at scale

Managing world class API development teams at scale

Overview

Project Description

My Role

Designing the feature end-to-end, working closely with engineering to craft X experiences in detail.

The Team

Design lead, mentoring 1 junior designer, 1 content designer, 1 product manager and 5 engineers.

Timeline

Jan 2021 - Jun 2021; Phased roll out over 2 quarters.

Common enterprise needs

Common enterprise needs

  1. Manage permissions of team members

  2. Ensure ownership of accounts created with the team’s domain.

  3. Bulk permission management and sharing of resources.

  4. Control all team member resources.

Role based access

By default, team members are invited as developers, who have access to all team workspaces.

After mapping pain points in the user's collaboration journey, I identified the jobs to be done at each step.

Manage roles

Admins can assign additional permissions on the team with Admin, Biller and Community Manager roles.

Akshayn

akshay.nkr@gmail.com

Dark-knight-Dev

apps@akshayn.com

Sign in with a different account

Existing accounts?

Existing accounts?

Select the account you wish to join the team with.

Select the account you wish to join the team with.

Select the account you wish to join the team with.

Create a Postman account

Enter email

apps@akshayn.com

Password

Create Free Account

or

Sign Up With Google

By creating an account, you agree to our Terms and Privacy Policy.

No account?

No account?

No worries. Join the team with a new account.

No worries. Join the team with a new account.

No worries. Join the team with a new account.

Copy invite link

Waiting for them to join?

Waiting for them to join?

Make it easier for them by sending an invite link.

Make it easier for them by sending an invite link.

Make it easier for them by sending an invite link.

Account management

To capture accounts created with a team’s domain, I designed a mechanism to verify domains owned by an Org.

After mapping pain points in the user's collaboration journey, I identified the jobs to be done at each step.

Once verified, they can take ownership accounts for security.

Akshayn

akshay.nkr@gmail.com

Dark-knight-Dev

apps@akshayn.com

Sign in with a different account

Existing accounts?

Existing accounts?

Select the account you wish to join the team with.

Select the account you wish to join the team with.

Select the account you wish to join the team with.

Create a Postman account

Enter email

apps@akshayn.com

Password

Create Free Account

or

Sign Up With Google

By creating an account, you agree to our Terms and Privacy Policy.

No account?

No account?

No worries. Join the team with a new account.

No worries. Join the team with a new account.

No worries. Join the team with a new account.

Copy invite link

Waiting for them to join?

Waiting for them to join?

Make it easier for them by sending an invite link.

Make it easier for them by sending an invite link.

Make it easier for them by sending an invite link.

Early Feedback → Quicker Wins

Early Feedback→

Quicker Wins

With the first release, we could only allow users to share all their personal workspaces with a team or none at all.

I pitched an improved design soon after we launched, presenting evidence that customers were not happy sharing all their personal workspaces with a team.

This lead to more workspaces being shared and more teams being created than ever before.

Wins

Wins

2x

2x

Invite acceptance

30%

30%

Teams being created

650

650

New teams created

in 6 months

2x

2x

Activity among users

in multiple teams

Activity of users

in multiple teams

This was the foundation for solving problems such as 'Sharing workspaces with external collaborators' and 'Smart URLs'.