Project Management

Page history last edited by Aaron 1 yr ago

 

Project Mgmt components

 

Intentions

Milestones

Calendar

Constraints

Prioritization Matrix

 

 

 

 

 

 

 

 


RNT Rollout Phases & Plan

 

Timeline:

 

Currently: Week of April 21

 

1. Defining the data mapping process to migrate data from LM to RNT

2. Beta-testing RNT with Inbound and Sales

    Goals of beta-testing: 1. design the interfaces to be as easy to use for them as possible, 2. Get their buy-in on the new interface, 3. Make sure there are NO SURPRISES.

 

Week of April 21

          - Mon April 21: final preparation for data migration (go / no go)

          - After work on Tues April 22: Data migration from Leads360 into RNT (work with Chris Jackson on this)

        - Wed April 23 (tentative): Sales goes onto RNT.  Will still use LM for several days as the data migration/RNT is tuned/fixed/tweaked

 

Week of April 28th

        - New website launched (april 26th?)

          - All new inbound leads will go into RNT (confirm w/ Isaac)

          - Inbound team goes 100% on RNT

 

May 1+ - New hires can begin

 

 

 


 

DATA MIGRATION

Migrate Data from Lead Manager to Rnt

     Target date is Tuesday 4/22

     Business needs to decide what leads to migrate (probably based on status) by 4/21

 Business needs to decide which fields in Lead Manager match up to which fields in RnT by 4/21

 Aaron Ross will confirm with Trang and Nick that no mass emails are scheduled for the week of 4/21

     Josh will make sure that sales schedules the smallest amount of appointments possible for Wednesday 4/23

            (There will be training / data cleanup / etc for sales on 4/23)

 

Synch RnT and the Admin

    Target date will be post 4/22

Kevin and Bill will figure out how the current synch between Lead Manager and the Admin is setup

    The current hope is that we will set up the synch between RnT and the Admin in the same manner.  I ran this by Charles and he wants to look at the document before we actually do the work, but conceptually he agrees.

 

Workflow in RnT from Sales to Pro Serv

      Aaron Ross will begin to work on this

 

 

Lead flow from L360 web site into Rnt

   Aaron Ross will work with Avi and Issac on this

    Goal is to set this up with the launch of the new web site so that the new web site is never connected to the current web site

 


 

Weekly Intentions / Vision

 

By the end of April:

* Outbound is 100% on RNT, are executing email campaigns that generate 3-5 valid email responses a day, and are beginning to get a flow of productive business conversations every week (even if some are with small companies).  Outbound can feel it beginning to come together and can see how in May they'll begin to repeatably generate new sales opportunities.  By the end of April, outbound is totally focused on targeting companies with at least 15 potential users.

 

* Inbound is on both RNT and LeadManager (pending the new website) for most of the month, and gets comfortable using RNT.  Inbound moves fully to RNT after the new website is launched.  Dave & Stew also begin getting exposed to the outbound process, so that when they move to outbound in May, they're better prepared to hit the ground running.

 

* Sales moves 100% onto RNT after a week of betatesting RNT and after a successful data migration.  The week of beta testing lets sales kick the tires and provide great feedback on improving the interfaces and workflow, ensuring it really works for them.  The data in RNT is migrated successfully and we can begin to generate reports from it.  Sales updates all their opportunities in RNT (or the stages are updated in the migration) to reflect the new sales stages, so that sales can, with a few clicks, run reports that tell them exactly where their different sales opptys are in their pipeline, how much pipeline they have overall, what should close this month, and what they have in the hopper for next month.

 

Week 2 (April 7-11)

Outbound: By the end of the week, outbound is 100% on RNT and independently executing mass email campaigns.   Outbound has the basics of the outbound process in place and working, are getting email responses, and are ready to begin the next level of outbound training.

 

Week 3 (April 14-18)

Outbound: By the end of the week, Drew and Raul are getting more and more positive email responses through a) better templates and b) better target contacts/lists.  They're logging responses and updating contacts and organizations consistently.  Outbound is handing some appointments to Sales.  They also feel comfortable running and editing reports in RNT.   Our "Project Matrix" on the whiteboard is pretty complete and organized.

 

Inbound/Sales: Inbound and Sales spend some time kicking RNT's tires, beta testing it and providing specific feedback to improve it.  By the end of the week, Matt has configured RNT to both Sales & Inbound's requests, and we're ready to have them actually start using it next week after the data migration. Inbound and Sales are comfortable that RNT will be helpful to their success, and they aren't worried about surprises with RNT.

 

Week 4 (April 21-25)

Outbound: By the end of the week, outbound is generating appointments for Sales consistently, and Sales is using RNT to follow up on the appointments.

 

Sales: Sales smoothly moves to RNT and their opportunities are updated so that Sales can run accurate pipeline reports.  After a few days of intensive tweaks and config changes (because things always come up), Sales is off and running, ready to really use RNT as their system.  They have questions, but essentially understand how everything works and can get by with minimal help for the most part.

 

Week 5 (April 28- May 2)

Sales closes the month.  Aaron, Matt and Josh work on developing pipeline reports and fixing/updating the underlying data and processes to make sure the reports are useful and accurate.

 

Outbound & Inbound's plan for May is prepared, which includes specific activity and results goals.

 

Comments (0)

You don't have permission to comment on this page.