# My Development — Recommendations

![My Development — Recommendations](/docs-content/d5fe5012b2-01-recommendations.png.webp)

**Navigation:** Home → My Development → Recommendations  
**Visibility:** personal and private; only the signed-in user sees this page  
**Primary audience:** every user with an active role profile

## Purpose

Recommendations is the default post-login page. It converts authorized evidence from the user's work into private, practical guidance for improving role execution, communication, meeting participation, follow-through, collaboration, and professional skills. It supports self-development; it is not an employee ranking, performance score, or manager surveillance screen.

## Scope and headline information

The role focus identifies the role against which guidance is made, such as Project Manager. **How recommendations work** explains eligibility, evidence, privacy, and user control. The summary row shows active recommendations, practices scheduled for the current week, practices completed during the month, and evidence items awaiting the user's review.

The weekly practice-plan panel shows completion progress and dated practices. It helps the user turn longer-term guidance into small observable actions before relevant meetings or deadlines.

## Recommendation list

Each recommendation contains:

| Element | Meaning |
|---|---|
| Recommendation title | The concrete behavior to practise, such as closing every decision with an owner and date |
| Focus area | The professional capability affected, such as execution discipline, facilitation, risk leadership, inclusive participation, or communication care |
| Impact | Expected relevance to the user's role and current work |
| Evidence strength | How consistently the authorized evidence supports the recommendation; it is not a performance grade |
| Reason | Neutral explanation based on observable events or measurable facts |
| Practice | A specific technique the user can apply |
| Evidence summary | Number and type of permitted meetings, excerpts, decisions, or other sources supporting the guidance |

Filters narrow the list by focus area, expected impact, and evidence strength. Selecting a recommendation opens its rationale, related evidence, practice history, and prior decisions.

## Supporting panels

**Skills in focus** shows the capabilities currently being practised and their stage, such as New focus, Practising, or Strengthening. **Why this recommendation** displays authorized supporting moments and makes clear when human review is required. **Recommendation history** opens accepted, modified, dismissed, completed, challenged, and superseded guidance.

## Actions

- **Accept** adds the recommended practice to the personal plan.
- **Modify** lets the user adapt frequency, wording, or timing while preserving the original rationale.
- **Dismiss** removes it from the active plan and records an optional reason; dismissal does not alter source evidence.
- **View evidence** opens only sources the user is permitted to access.
- **Edit practice plan** changes dates and practical steps.
- **Challenge** starts a review when evidence, attribution, context, or interpretation appears wrong.

## Recommended procedure

Review the highest-impact item, open its evidence, confirm that the context is fair, and then Accept, Modify, Dismiss, or Challenge it. Keep the active plan small enough to practise deliberately. Use Progress to observe change over time rather than judging a single meeting.

## Interpretation and safeguards

Recommendations describe observable work practices. They do not infer attitude, personality, intent, emotion, or private characteristics. Speaking time alone never creates a recommendation. Sensitive guidance requiring human review remains clearly marked and cannot be treated as a confirmed conclusion.

## Related screens

[Today](/documentation/packages/bnd-development/screens/home-my-development-today) turns accepted guidance into today's plan. [Growth Priorities](/documentation/packages/bnd-development/screens/home-my-development-growth-priorities) organizes longer-term themes. [Evidence & History](/documentation/packages/bnd-development/screens/home-my-development-evidence-and-history) provides challenge and provenance controls.
