Table of Contents

Problem Statement

An imaginary, fictional SaaS authentication called Protekt requires a structured plan and execution of documentation that is helpful for developers to adopt the service quickly and use it to facilitate authentication. In this case study, I am going to outline some tactics to bring more and more reliable developers on board to try this authentication service. Additionally, several ways to make a smooth adoption of authentication will be discussed.

USP: “Protekt gives developers a hassle-free, ready-to-run authentication sandbox with real-world test identities and environments: no setup, no credit card, no vendor lock-in.”

The company is experiencing two challenges:

1. Difficulty in integrating the Protekt without proper documentation support.
2. Lack of visibility for Product Managers to utilise the features completely.

The objective of this project is to design, create, and roll out concise, developer-first documentation that enables self-service integration, reduces support requests, and assures retention of users.

Assumptions

To broaden the perspective of this case study, the following assumptions are made:

• User: Developers (primary), Product Managers (secondary).
• Core Product Features: Authentication APIs, SDKs, SSO, MFA, Role-Based Access Control (RBAC), and real-time Sandbox.
• Pain Point: Lack of clarity on the documentation part, leading to massive support ticket generation for integration..
• Platform: A sample of documentation will be written on Docusaurus, an open-source platform, hosted on GitHub and deployed on Vercel.