Momenta Advisor

Modified on Mon, 11 Aug at 1:03 AM

This article explains the role of a Momenta Advisor on BTS digital projects, including their responsibilities across content authoring, journey setup, user management, testing, and dashboarding. It also outlines different support levels and how they map to PV estimates and project complexity.



Role Summary & PV Levels

A Momenta Advisor may be assigned based on the level of support a project requires. The table below outlines support levels and example responsibilities to help estimate PV (project value) and effort. These are general guidelines — actual scope may vary by project.

  • Level 1 (25%): Core responsibilities only. Content comes from consultant or standard library with minimal customization.
  • Level 2 (50%): Core responsibilities + one support category (e.g., standard authoring).
  • Level 3 (75%): Core responsibilities + two support categories.
  • Level 4 (100%): Full responsibilities across content, integration, rollout, and ongoing support.

Note: For new Advisors, add +1 day of PV per level to account for ramp-up.

Support Categories:

  1. Standard Content Authoring
  2. Expanded Content Authoring
  3. Extensive Rollout Support


Core Responsibilities

Estimated PV: +3 days of work per project

Communication & Planning

  • Join internal kickoff with AM/PL and consultant team
  • Confirm project components: Momenta, Coach, Pulse, Isomer, etc.
  • Share updates and coordinate across digital teams
  • Represent BTS on client calls for basic Momenta platform questions

Journey Configuration & User Management

  • Set up appearance, lifecycle, flow logic, and navigation
  • Provision author/JSM permissions
  • Add users (test and live), advise on access methods (SSO, LMS, etc.)

Program Launch & Rollout

  • Coordinate launch dates (Tues–Thurs recommended)
  • Test notifications and QA journey using test accounts
  • Provide participant support for login, access, and navigation
  • Create onboarding guides or one-pagers as needed

Dashboarding

  • Request dashboard setup from Data team
  • Coordinate updates post-launch


Standard Content Authoring

Estimated PV: +3 days of work per project

  • Build journey wireframe and content based on source doc
  • Customize and reuse standard content objects
  • Coordinate with consultants for updated assets

Coach OS Integration

  • Create cohorts and pathways
  • Load users and configure sessions
  • QA bookings and troubleshoot issues

Linking Existing Pulse/Isomer Sim

  • Coordinate with Mumbai PL / Digital to link simulations
  • Test integration within the journey


Expanded Content Authoring

Estimated PV: +3 days of work per project

New Pulse / Isomer Integration

  • Coordinate simulation build and integration steps

Translations

  • Coordinate with translation leads
  • Upload translated assets, content, and supporting visuals
  • Conduct language-based QA

Graphics/Design Ownership

  • Assume direct responsibility for image asset creation or design QA


Extensive Rollout Support

Estimated Time: 2–5 days per month (can be tracked via PM credit)

Complex User Management

  • High participant volume (thousands), with reschedules and weekly session management
  • Customized notifications per team or cohort
  • Examples: Takeda Inclusion Accelerated, Abbott Leading with Impact

Support/Helpdesk Management

  • Monitor and resolve issues from shared inbox or helpdesk channel
  • Participate in recurring support calls with clients

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article