Internal Team Intelligence and Personal Development
Internal Team Intelligence and Personal Development
On this page
Internal coordination, private recommendations, role practice, progress, evidence, and management guidance. This package has its own data model, workflows and interface contributions. Its documentation applies wherever the package is installed, not only to one industry solution.
Overview
Package: BND-DEVELOPMENT · Type: Business capability · Documentation: 1.0
Marketplace listing · Technical reference
Coaching is not an ethics investigation or a hidden performance ranking. Managers receive only explicitly authorized guidance, not unrestricted access to private recommendations.
User guide
- Review a private recommendation with supporting examples, counterexamples and the professional skill it addresses.
- Use personal practice and growth priorities to work on communication, respectful wording, participation or follow-through.
- Compare progress with your own baseline and record disagreement or a correction when context is incomplete.
Screens owned by this package
- My Development — Recommendations —
SCR-DEV-01. - My Development — Today —
SCR-DEV-02. - My Development — Growth Priorities —
SCR-DEV-03. - My Development — Progress —
SCR-DEV-04. - My Development — Evidence & History —
SCR-DEV-05.
Contributions to other screens
- Overview — owned by
BND-OVERVIEW; this package contributes analysis or interface content. - Meeting — Findings — owned by
BND-FINDINGS; this package contributes analysis or interface content.
Configuration
| Setting | Purpose and behavior |
|---|---|
| Role and skills | Choose relevant professional skills and observable practice criteria. |
| Privacy boundaries | Separate personal recommendations from authorized team-level process guidance. |
| Progress windows | Set baseline periods and minimum evidence coverage for progress comparisons. |
Configuration changes are versioned overlays. Preview the changed permissions, schemas, workflow bindings and interface contributions in Development; qualify them in Testing and Staging before authorized Production promotion. A business administrator configures permitted solution settings; platform deployment authority is separate.
Technical reference
The implementation reference identifies DM-DEVELOPMENT, WFP-DEVELOPMENT-GUIDANCE, 3 owned agents, interface contributions, policies and evaluation profiles. Shared platform services execute these definitions; they do not hard-code this package's business meaning.
Compatibility and dependencies
- Meeting and Conversation Intelligence —
BND-MEETING. - Finding Lifecycle, Evidence Assurance, and Review —
BND-FINDINGS. - Decisions, Commitments, Actions, and Follow-Up —
BND-WORK.
Other compatible packages can consume its declared capabilities without changing ownership.
Dependencies declare compatible ranges; the installation resolver records exact signed versions and digests in the environment lock. This documentation's version is not an installed-package version. Before updating or removing the package, inspect dependent workflows, records, interface slots and retained artifacts. Never delete referenced evidence or silently remove a required capability.
Extensions and enrichment
Add role-specific coaching playbooks, skills and practice measures. Personal evidence remains scoped to the person and the declared purpose.
Extensions declare their own package identity, dependencies, provided capabilities and evaluation evidence. They preserve the publisher's original package and are qualified with the complete resolved composition. See the developer extension guide.
Versions and upgrades
The documentation describes the current 1.x solution composition and the package's declared capabilities. The exact installed package, model, prompt and schema versions are shown in the environment lock and run provenance; no historical release sequence is implied.
- Compare release manifests, permission changes and migrations against the current lock.
- Test package behavior and affected dependent workflows with representative, authorized evidence.
- Promote the signed release after approval and record the resulting lock.
- Roll back only when schema/data compatibility and retained artifacts permit it. Irreversible migrations require a tested recovery or forward-fix plan; completed external actions require compensation, not a software rollback.
Used in solutions
Technology Consulting & Delivery includes this package as default active. That activation rule belongs to this solution; it does not make every business capability mandatory for every Telynt deployment.