icon picker
V2 Launch Agenda

A plan of attack for launching V2

Overview

V2 Needs to get developed in stages
Complete Architecture
Document User Access Patterns
Layout V2 Design Library & Component Library
Build Prototypes & Mockups
Assert Prototypes/Mockups meet requirements
Implement Beta V2 Inbox
Get first User in V2
Build Data Architecture for measuring success
Assert V2 > V1 in terms of Trial conversion, activation, and retention
Divide and Conquer
Tinker with V2 until we surpass V1 metrics → continue to accommodate user personas and route more V1 users to V2
Broadcast?
Reporting?
Multi-phone number?
Multi-workspace
Expand Integration Footprint → needs to go live in Q1 2024
R&D into new Products → Voice & Chat → needs to go live in Q1 2024

V2 Overview

🎯 V2 Key Objectives/Epics
0
Complete V2 Infrastructure
V2 Design Library, Access Patterns and Wireframes
Launch V2 Beta Prototype
Build V2 Data Infrastructure
Expand V2 Features & Products
V2 Integration Architecture
Team Inbox & Workflows

Milestones by objective:
6

Word Chart for V2:

V2 Roadmap by Epic:

Filter by quarter :
All

Objective/Epic
Milestones
Quarter
Status
% Complete
Outcomes
Notes
Complete V2 Infrastructure
🏆 Complete Alpha Inbox 🏆
Q3 23
Not started
000
0
Basic Inbox Functionality
Tertiary Feature Functionality: Contacts, Settings, Workspaces, phone number
Native Device Support (Desktop/Mobile)
Web app support
Open
R&D V2 Architecture
Q2 23
Done
000
100
Research potential paths forward for V2 and analyze existing issues in V1
Pitch V2 architecture to team and get team buy in
Open
Determine V2 Architecture & Tech Stack
Q2 23
Done
000
100
Finalize the V2 architecture and present to team
Open
Complete Backend Architecture
Q2 23
In progress
000
30
Lay the initial patterns for V2 architecture
Achieve a point of stability that enables other developers to contribute to V2 and follow the existing patterns
Open
Design V2 Prototype
Q2 23
In progress
000
20

Open
🏆 Team Onboarding into Flutter/Dart 🏆
Q2 23
In progress
000
30
Onboarding team into Flutter and Dart
Open
V2 Design Library, Access Patterns and Wireframes
🏆 User Access Pattern x Mockup Testing 🏆
Q3 23
Not started
000
Once the mockups are created, we need to test them and confirm that they meet the required access patterns.
🔴 We can’t hand off the mockups for Beta development until we confirm they meet the requirements
✅ By completing this step, we’ll have a high degree of confidence we are building the right thing in V2
Open
Define V2 Access Patterns
Q2 23
In progress
000
70
Identify user personas
Identify access patterns for each user
Identify Feature workflows for each user persona
Open
Build V2 Design Library based on Flutter
Q2 23
In progress
000
60
Build out a design library that is 1-to-1 with the base widgets in flutter’s cupertino library
identify required “material” widgets that will be used throughout designs
Uncover limitations of base component libraries
scope custom component usage and limitations for usage
Open
V2 Inbox Wireframes & Mockups
Q2 23
In progress
000
30
Wireframes for each major access pattern in the inbox
High fidelity Mockups for major access patterns in the inbox
Open
Launch V2 Beta Prototype
Create AB Pathway for routing users between V1 & V2
Q3 23
Not started
000
when launching V2, we will need a way to reroute new signups to V2 vs V1. We’ll need a system for managing this that lets us determine what percentage of users drop into each version.
Open
Implement MVP of Workspace Management
Q3 23
Not started
000
To go live with V2, we’ll need an MVP of multi-workspace management
Open
Implement MVP of user facing Inbox workflows
Q3 23
Not started
000
Inbox workflows we need in MVP V2
Add/remove tag
Organize inbox by tag
Assign conversation
schedule message
etc (see user access patterns)
Open
Implement MVP of V2 Subscription Settings
Q3 23
Not started
000
To go live with V2, we’ll need a mvp version of our subscription settings
Open
🏆 Get first V2 Trialing User
Q4 23
Not started
000
Open
🏆 Get first V2 paying User
Q4 23
Not started
000
Open
🔴 how do we manage 2 mobile apps at once?
Q4 23
Not started
000
Open question: how do we manage 2 mobile apps at once that can both be downloaded by anyuser?
Open
Build V2 Data Infrastructure
R&D for Data Architecture & Warehouse
Q3 23
Not started
000
what is our short term data goal? → analyze v2 vs v1 what is our long term data goal? → understand correlation & causation between in-app workflows and core business metrics like conversion, activation and retention rate
Open
Design Initial Database relationship
Q2 23
In progress
000
25
Define the entity-relationships between individual objects in the V2 database
Understand the 1-to-many, many-to-1 and 1-to-1 relationships and how that translates to the user experience and interface
Open
Identify Core Business cases for Data Architecture moving forward
Q2 23
Not started
000
From a business perspective, what type of insights do we need from our data moving forward?
Open
Data Pipeline Architecture
Q4 23
Not started
000
Simple Data Pipeline that pumps product data to datawarehouse
Unification of product, revenue and usage data into a datawarehouse
Data map that outlines what data is needed to capture key business/product insights
Basic Visualization tools that provide necessary insights
Open
Activation Rate Tracking
Q4 23
Not started
000
V2 is only successful if a certain percentage of users “activate” during their free trial
What is our activation metric?
How do we calculate/track it?
Where do we view/visualize it?
Open
Expand V2 Features & Products
V2 Automated Routing
Q3 23
Not started
000
Automated routing is like background filtering (similar to gmail). It’s a way to set a filter as a user and make a rule for any message that matches those filters.
i.e. If channel is waiting > 30 minutes, apply the “Red Flag” label
Open
V2 Search & Filtering
Q2 23
Not started
000
Search is the act of a user trying to find a single entity
Filtering is the act of trying to find a list of entities that match a query
Filtering is the workflow for taking bulk actions
Search is the workflow for finding a single entity and navigating to it
Both functions serve as the backbone to our inbox routing features → how easy is it find the right conversation at the right time
Open
Multi-Workspace Handling
Q2 23
Not started
000
the Creation, management and deletion of workspaces in MessageDesk tenants
Open
Multi-Phone Number Handling
Q2 23
Not started
000
the creation, addition, removal and management of phone numbers in workspaces
Open
V2 Broadcast
Q4 23
000
We feel confident about copying/pasting V1 Broadcast as is into V2
Open
V2 Voice
Q4 23
Not started
000
This is a brand new feature/product. It will take a lot of R&D to get this to an MVP that drives business value.
🔴 We don’t want to create a voice roadmap that shifts our focus away from our core inbox offering - we want voice to be a complementary inbox feature
Open
Reporting and Analytics
Q2 24
Not started
000
Open
V2 Automated Messaging
Q1 24
Not started
000
Automation should be triggered by core routing features such as label applied/removed.
Open
V2 Integration Architecture
R&D Integration Architecture
Q4 23
Not started
000
what “types” of integrations are there? Data and messaging?
What are some example integrations and how are they executed
What is the business benefit of integration? what integrations lead to the most short term vs long term gains
Open
Market Analysis for Integration Types → what integration do we implement first and why?
Q4 23
Not started
000
Decide what our ‘first v2 integration” is and why. This is a business case challenge → what integration is a med/low severity build that delivers significant business value in short and long term
Open
Develop MVP of Integration
Q1 24
Not started
000
We decided what we are integration with, now we need to develop the MVP of that integration
Open
GTM launch of Integration
Q1 24
Not started
000
We need to drive business value for the MVP before further development, whats our go-to-market strategy?
Open
Team Inbox & Workflows
User and Team Permissions
Q4 23
000
Dynamic user permissions and ability to create advanced user permissions
Organization of users into “Teams” within a workspace
Open
Team Comments & Mentions
Q4 23
Not started
000
The ability for teammates to post comments at one another inline of a channel
Ability to view ‘mentions” in the inbox
Ability to view comments in aggregate for channel or contacts
Open
Team Inbox Workflows
Q4 23
Not started
000
Assigning conversations, organizing by assignee, team management and permissions
Open



Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.