Low participation
Make the value of the next action and feedback clear.
Connect business objectives, user behavior, and game-based experiences in a clear journey.
Define the behavior and expected outcome before selecting a feature.
Make the value of the next action and feedback clear.
Design value and a reason to return.
Turn adoption of a key feature into an understandable mission.
Define progress and feedback for practice and completion.
Each program effect starts with a valid behavior.
Objective and target behavior.
Record valid behavior from an identified source.
Define when a behavior affects the program.
Turn an objective into a clear user action.
Define value aligned with the program and its economy.
Metrics and outcome evaluation.
Each component has a clear responsibility and intended outcome.
Record valid behavior from an identified source.
Define when a behavior affects the program.
Turn an objective into a clear user action.
Define value aligned with the program and its economy.
Show progress and clarify the next action.
Separate customer and employee experiences.
Explore objectives, audiences, campaigns, and review together.
Connect objectives, behaviors, missions, and outcomes. Decisions start with the program definition.
Approved design reference and conceptual view; figures in the image are illustrative, not customer results.
Clear missions, understandable feedback, and rewards aligned with the program.
Missions, progress, and rewards should be understandable. Start with the behavior you want to encourage.
Illustrative mission design
Approved design reference and conceptual view; figures in the image are illustrative, not customer results.
Metric definitions; these are not numeric customer results.
Starting the target behavior within a defined window.
Finishing a defined mission or journey.
Moving from one defined step to the next.
Returning within a defined time window.
Review integration categories against organizational needs; a category does not imply an available connector.
Integration category; each connector's requirements and contract are defined during technical review.
Integration category; each connector's requirements and contract are defined during technical review.
Integration category; each connector's requirements and contract are defined during technical review.
Integration category; each connector's requirements and contract are defined during technical review.
Integration category; each connector's requirements and contract are defined during technical review.
Integration category; each connector's requirements and contract are defined during technical review.
Integration category; each connector's requirements and contract are defined during technical review.
Explore current controls and deployment requirements on the security page.
The intended design process; AI capabilities are not active in this version.
A reviewable draft.
Evaluate the effect in an authorized environment.
Review by the responsible person.
Decision by an authorized approver.
Publish an identified version after approval.
Define your objective, audience, and challenge for the introduction.