Prism makes tracking body changes and results a reality. The bodymaps and body insights that Prism provides can be combined with already existing partner goals framework. See recommendations below for a generic goals framework:
| Partner main goals | Recommended Prism body metrics |
|---|---|
| Lose weight | Body fat & lean mass and specific body measurements (arms, waist, thighs). |
| Build strength | Lean mass and specific body measurements (arms, shoulders, thighs, calves, shoulders to waist ratio). |
| Get body definition | Lean mass, body fat and specific body measurements (arms, shoulders, thighs, calves, waist to hip ratio). |
| Get healthier | Body fat, lean mass, and specific measurements (waist). |
| Action/Event | Recommendation |
|---|---|
| When to take first bodymap | Ideally it should be one of the first asks to the users when setting up their account/starting their journey. Two main reasons: 1) get a baseline for the user, even if you don’t display progress right away; 2) once the results are ready, they can be used to help set body metrics within the goals framework, or very soon after. |
| How to set body metrics targets | Targets for body composition can be set against normal ranges for men and women per by age groups (link). |
| Body measurements targets can be set as a function of percent increase/decrease, normal body measurements (healthy waist, link) or ratios (healthy ratios, or activity-specific ratios). |
Prism has a health report API that outputs the main health standards and population percentiles for a given user scan. See more details here: ‣ | | When to take follow-up bodymaps | Just like measuring a person’s weight on a scale, bodymaps should be taken ideally on a schedule at around the same time and conditions. Preferably, before a workout and avoiding any large meals and drinking too many liquids, essentially anything that can significantly change the person’s body shape. | | How to display progress reports | Reports that display historical progress (quick insights/trends, side-by-side, plot views) and the user’s positioning amongst their peers via percentiles are typically found helpful by users. |
See DOs and DON’Ts section for a more visual version of these requirements: Do’s and Don’ts
Users should:
The space where the scanning happens should: