PROJECT: CORD Dashboard

[sethmcknight]

Objective: Provide visibility to our portfolio to make strategic and tactical decisions

• FPMs are able to evaluate and manage their inventory in a central location
• SC Leadership is able to make portfolio decisions based on this information

┆Issue is synchronized with this Monday item by Unito

[sethmcknight]

Some Input from Users

It would be nice to have all the project-management info pertinent for ONE specific project on one project page ("dashboard") in DOMO.

What Field needs to manage

Things we do have today

• Progress percentages

• To know whether a Change to Plan is in progress

• Clarity of translation goals (single point of truth AIP)

  Things we don't have today

• Intacct financial data (budgets to actuals), both YTD and project lifetime

• Financial transfer info (there's a time delay baked-in with Financial Services' data entry)

• Long-term goals and projected completion towards long-term goals (in light of SC's anticipated/realistic commitment)

• Verbal context for a progress percentage

• Verbal context for financial variances

• Quarterly project progress assessments

  • Being built by Cord Field testing team and FOLT
  • Initially will just be in Comment box and eventually want to build it out more maturely (drop-down menus to categorize what type of note this is)
  • Project management purpose: knowledge transfer for staff transition

• Expected level of project disruption (due to influencing factors such as contextual limitations, competing priorities, stability of the environment, etc.).

  • Perhaps just set at project start?

    What the rest of the org needs for visibility

• Overall percentage complete to the long-term goals for lifetime engagement with SC

• Story of impact of Bible Translation

• Info/update on Translation team

• Prayer Requests

• Goals Completed last time period

• Goals Planned next time period

[sethmcknight]

Initially this will focus on managing and displaying additional information in CORD for Languages and Projects. Later we may look at building out additional functionality to surface insights and metrics relevant to the user.

Here are the sections we are looking at currently

• Display and Manage Language Data
• Preset Inventory Flag
• Add Language Engagement Data
• Embed Financial DOMO Cards
• Defined Posts
• Consulting Activities
• Embed DOMO Page/Cards

[sethmcknight]

Display and Manage Language Data

The existing Language Details page doesn't follow the same patterns used in other parts of the application, makes data management difficult, and is lacking key information for Portfolio Management and Investor communications.

We need to revisit the way the Language Page is laid out to improve data management and visibility. We should be intentional to adopt existing patterns used throughout the application or develop new patterns where needed.

Overview of Data

CORD Language

This is language information unique to Seed Company and CORD. It will be manually entered.

Data Fields

• Name
• Public Name
• Pronunciation Guide
• Population
• Provisional Code
• Registry of Dialects Code
• Is Dialect
• Is Sign Language
• Is Border/Cross Border Language
• First Scripture Produced outside of CORD
• Sensitivity
• Sign Language Code
• Sponsor Begin Date
• Estimate Sponsor End Year
• Is Least of These
• Least of These Reason
• Preset Inventory (Will exist on Language Engagement, but should also display on Language)

Ethnologue Data

This is language information maintained by SIL and is used across the Bible Translation movement to identify Languages.

We would like to look at pulling this data directly in from the Progress.Bible LivingLanguages API.

We should consider creating Ethnologue Language pages and simply linking an Ethnologue Language to a Seed Company Language.

Data Fields

• Ethnologue Name (Unit Name)
• Ethnologue Code (Unit Code)
• Ethnologue Population
• EGIDS Group
• EGIDS Value
• First Language Users (Population)
• First Language Users Grouping (Population Range)
• Primary Continent
• Primary Country Code
• Primary Country Name

All Access

This is information is maintained by ETEN and Progress.Bible, and determines what Languages should be focused on a received ETEN funding.

We would like to look at pulling this data directly in from the Progress.Bible LivingLanguages API.

Data Fields

• Is Active
• Is Confidential
• Is Potential Need
• Is Remaining Need
• In The Circle
• On The List
• Translation Status Name
• All Access Goal
• All Access Status

Lifetime Goals

This section articulates what people in this Language community would like to see developed in their Language in the long-term and tracks progress toward those goals.

Some of this data will be input by Seed Company.

We would like to look at pulling some of this data directly in from the Progress.Bible LivingLanguages API.

Data Fields Seed Company

• Type
• Scripture Range
• Medium(s)
• Progress/Completion

LivingLanguages API

• Publication Year
• Expressed Need
• Max Scripture
• Refined Max Scripture

People Group

This section will contain relevant information about the People Group that speak this Language across a number of categories. This will be manually input.

Data Fields Religion

• Select Dominant Religions and % of population that follow that Religion
• Date/Year Christianity was first introduced
• How Christianity was first introduced (text)

Daily Life

• How do religious practices and beliefs influence daily life? (text)
• What is a normal day (text)
• Unique cultural qualities/attributes (text)
• How do they make a living (text)
• What is the economic situation (text)

Geography/History

• Where do they live?
  • Pick List (Homeland, Urban Centers, Diaspora, etc.)
  • Description (text)
• What travel challenges do they face? (text)
• History of the People (text)

Social Life

• What other cultural groups are in the area? Do they interact? (text)
• Interethnic Attitudes (text)
• Social Issues Faced (text)

Related Entities

We would like to surface all entities related to a Language. We've already done this with Projects.

Should we have Cards for each Entity Type that show the total related and then click in to view the list (Like Team Members and Partnerships on a Project?)

Data Points

• Projects
• People
• Partners
• Languages (?)

[sethmcknight]

Preset Inventory Flag

Field will be selecting Preset Inventory for Advancement to connect Investors to as part of our Language Offering.

Project Managers will make this selection at the Project level, but it will be applied to the Language Engagements. If a Language Engagement has an Investor connected we may need to automatically flag new Language Engagements with that Language as Preset Inventory.

This flag will need to:

• Display on the Project
• Display on the Language Engagement
• Display on the Language
• Feed to the General Accounting Unit in Salesforce.

[sethmcknight]

Language Engagement Data

We are looking to pull partner Language Engagement data in from the SIL LanguageEngagementDetails API and track additional data on Language Engagements.

We need to apply any design patterns set on the Language Details or other parts of the application to the Language Engagement page.

We also need to capture the following data:

• Is Scripture Development
• Is Language Development
• Is Translation
• Preset Inventory

[sethmcknight]

Embed Financial DOMO Cards

We need to embed 2 DOMO Cards on the Project Budget Details screen. These should be displayed once a Project is Active and auto-filter based on the Project Name/ID.

• Project Budget to Actuals
• Project Transfers

[sethmcknight]

Defined Posts

We need a way to link posts to specific actions/entities in CORD.

These should display by the entity and in the Posts feed.

Some examples include:

• Post linked to a Change Request (like the current Change Request Summary)
• Post linked to a Step/Status Change
• Post linked to a Periodic Report
• Post linked to a Defined File

[sethmcknight]

Consulting Activities

We need a way to track consulting activities for Management Oversight and a Board Mandated Goal to track our Consultant-in-Training Mentorship.

Consultants need a way to select an Activity, link it to relevant entities, and input the number of weeks in a quarter they spent on the Activity.

Activities

• Preparing to Check
• Checking
• Training
• Other Mentoring

Linked Entities

• Team (Language Engagement)
• Mentee (Person)

Additional Data

• Weeks Spent
• Fiscal Year/Quarter
• Number of Weeks

[sethmcknight]

Embed DOMO Page

Once a relevant set of Portfolio Management cards are identified in DOMO, create a 'Dashboard' page that pulls in cards based on the users role(s) and auto-filters the cards for them.

[sync-by-unito[bot]]

➤ Seth McKnight commented:

Objective: Provide visibility to our portfolio to make strategic and tactical decisions

• FPMs are able to evaluate and manage their inventory in a central location

• SC Leadership is able to make portfolio decisions based on this information