Doorman
Description: What is it?
Doorman is an AI-powered access approval copilot for IT admins at large tech companies. The platform integrates with existing ticketing software like Jira and access provisioning software like Okta, as well as company policy and team communication software to streamline context gathering.
Problem: What problem is this solving?
Our solution solves the issue where PMs and other employees experience delays in access approval for different applications. Once a PM submits a ticket, IT admins have to reach out to the necessary authorities to figure out whether to grant access, which can be a long and complicated process. This leads to delays in projects.
Why: How do we know this is a real problem and worth solving?
In our needfinding interviews 5 out of 10 PMs mentioned facing waiting time challenges for tool access. We also investigated IT admin workflows and found that context gathering is a major bottleneck and a very manual process at the moment.
Success: How do we know if we’ve solved this problem?
We know we’ve solved this problem if IT admins take less median time to resolve access provisioning tickets. Qualitatively, we can look at whether IT admins feel like the product saves them time and effort. We can also indirectly measure success by whether there is reduced downtime for engineering and product teams at large tech companies using our product.
Audience: Who are we building for?
We are building a product to help IT admins at large companies with access approval, which ultimately benefits PMs and other employees who need to request access to different platforms. Our business plan is to charge per seat with flat subscription tiers and usage limits. We will offer a 14 day free trial to acquire customers.
What: Roughly, what does this look like in the product?
A PM submits a ticket on Jira, and our tool gathers context from company policy, past tickets, and communication platforms to provide a recommendation to the IT admins. Our product also proactively reaches out to the right managers to confirm the recommendation and receive additional information if necessary.
How: What is the experiment plan?
On top of our test cards, we will select 2-3 IT admin teams and a few associated product/engineering teams (e.g., ~20 PMs) to use Doorman for all access requests over a 4-week period. We will measure average ticket resolution time in the previous month as a baseline and track the new median time to resolve, as well as conduct interviews with IT admins and product and engineering employees to measure time savings and perceived effort.
When: When does it ship and what are the milestones?
We ship Doorman when we know it takes 50% less time to resolve access provisioning tickets and it has a median 90% confidence rating.
Values: What are our team’s values and how will we uphold them while building?
We value integrity, so we want to ensure we’re honest about potential risks with our product. For example, below our tool’s approval recommendation, we will include a disclosure stating that our product could come to an incorrect conclusion based on the context, and so it’s crucial for IT admins to review the context themselves when flagged. This will make it clear that our product isn’t a replacement of human IT admins since human judgement is still necessary.
Reading Insight:
From “My favorite product management templates,” we found the template from the slide deck titled “Building a shared team vision by Google.” We incorporated this slide deck into our one-pager draft by adding a section for our team’s values and how we will ensure we uphold them.
