Phase 3 - Team Rollout

Here’s a quick checklist for the phase 3 setup -

Pre-Launch Demo

We recommend conducting a product walkthrough session with the entire team to introduce the product. A few suggested talking points:

• Position Typo as a platform introduced to help improve the overall engineering efficiency across teams

• This step is a data-driven approach to bring transparency in the system

• Not a system to rate developers/teams, but more towards bringing visibility across the delivery cycle

• Show the developer view to give confidence on how they would be able to visualize data. Plus, code review automation/alerts to fasten their workflows

If required, our team can also be a part of this call to conduct the demo alongside you. Once done, then grant access to the users.

Granting Access

While inviting users, 3 types of roles to be assigned :

• Admin

  • Views entire data

  • Able to configure the entire platform

• Manager

  • Only views data of the teams assigned to them

  • Able to configure only for their respective teams

• Developer

  • Only views their data - Git commits/PRs/Tickets/Goals

  • Able to view their teams’ DORA metrics

Here’s a detailed guide to managing access of your team members

The users can log in either with their Git accounts or Google account. We recommend Git users use their Git account login only.

Post-Launch Support

We recommend creating a new Slack channel where some of your team members (a mix of managers/devs) can be added alongside our team members to have direct feedback discussions.

Here’s a detailed protocol of our Customer Support on Slack Channel -

Primary Support Channel

• Dedicated Slack channel "#typo-company_name>"

• The channel monitored 24/5 by the Typo team

• SLA: Critical issues - 2-4 hours, General queries - 24 hours

Channel Members

• Engineering leads/heads from your team

• Selected developers (power users)

• Typo support engineers

Support Protocol

• Use thread replies for issue discussions

• Pin important announcements and resources

• Standardized issue reporting format:

  Issue Type: [Bug/Question/Feature Request]
  Priority: [High/Medium/Low]
  Description:
  Steps to Reproduce:

New Releases

• Feature announcements in the channel

• Optional demo sessions on request

• Beta testing opportunities for power users

Available support resources and documentation links are pinned to the channel.