...
Code Block |
---|
{ "$schema": "http://json-schema.org/draft-07/schema#", "title": "People-Capability Relationship Schema", "description": "Schema for relationships between People domain and Capability domain", "type": "object", "required": ["relationshipID", "peopleID", "title", "relationshipType"], "properties": { "relationshipID": { "type": "string", "description": "Unique identifier for this relationship" }, "peopleID": { "type": "string", "description": "ID of the people element" }, "title": { "type": "string", "description": "Name of the capability" }, "relationshipType": { "type": "string", "description": "Nature of the relationship", "enum": ["enabling", "supporting", "dependent", "enhancing", "limiting", "critical", "developing", "other"] }, "relationshipStrength": { "type": "integer", "description": "Importance of this relationship (1-5)", "minimum": 1, "maximum": 5 }, "talentContribution": { "type": "string", "description": "How talent contributes to capability" }, "capabilityRequirements": { "type": "array", "description": "Requirements the capability places on talent", "items": { "type": "object", "properties": { "requirementDescription": { "type": "string", "description": "Description of requirement" }, "importance": { "type": "string", "description": "Importance level", "enum": ["low", "medium", "high", "critical"] }, "fulfillmentLevel": { "type": "string", "description": "How well requirement is met", "enum": ["unmet", "partially-met", "mostly-met", "fully-met"] }, "improvementNeeds": { "type": "string", "description": "Areas needing improvement" } } } }, "talentMaturity": { "type": "object", "description": "Maturity of talent for capability needs", "properties": { "maturityLevel": { "type": "string", "description": "Current maturity assessment", "enum": ["initial", "developing", "defined", "managed", "optimizing"] }, "maturityGaps": { "type": "array", "description": "Key maturity gaps", "items": { "type": "string" } }, "maturityTargets": { "type": "string", "description": "Target maturity state" }, "developmentRoadmap": { "type": "string", "description": "Plan for talent development" } } }, "performanceMetrics": { "type": "array", "description": "Metrics for measuring talent contribution", "items": { "type": "object", "properties": { "metricName": { "type": "string", "description": "Name of metric" }, "metricDescription": { "type": "string", "description": "Description of what is measured" }, "currentValue": { "type": "string", "description": "Current performance" }, "targetValue": { "type": "string", "description": "Target performance" }, "impactOnCapability": { "type": "string", "description": "How this metric affects capability" } } } }, "developmentInitiatives": { "type": "array", "description": "Initiatives to improve talent for capability", "items": { "type": "object", "properties": { "initiativeName": { "type": "string", "description": "Name of initiative" }, "initiativeDescription": { "type": "string", "description": "Description of initiative" }, "expectedBenefits": { "type": "string", "description": "Capability benefits expected" }, "status": { "type": "string", "description": "Current status", "enum": ["planned", "in-progress", "completed", "ongoing"] } } } }, "resourceAllocation": { "type": "object", "description": "Resources allocated to talent for capability", "properties": { "budgetAllocation": { "type": "string", "description": "Budget allocated" }, "personnelAllocation": { "type": "string", "description": "Personnel allocated" }, "trainingInvestment": { "type": "string", "description": "Training investments" }, "allocationRationale": { "type": "string", "description": "Rationale for resource allocation" } } } } } |
People Domain
...
Properties
People Domain Attributes
Property | Description | Example |
---|---|---|
peopleID | Unique identifier for the people element | "PEOPLE-WORKFORCE-001" |
title | The name or title of the people element | "Product Engineering Team" |
description | A detailed explanation of the people element | "Core product development engineering workforce responsible for design, development, and maintenance of enterprise software products." |
talentCategory | Classification of people element type | "technical" |
orgUnitTitle | The organization unit responsible for this people element | "Engineering Division" |
orgUnitRoles | Specific roles within the organization unit that manage this people element | ["Chief Technology Officer", "VP of Engineering", "Talent Acquisition Manager"] |
orgUnitsCovered | Organizational units affected by this people element | ["Product Development", "Quality Engineering", "DevOps"] |
workforceSize | Quantitative metrics about the workforce | {"currentHeadcount": 125, "plannedHeadcount": 150, "timeframe": "EOY 2025", "vacancies": 15} |
skillsProfile | Skills and competencies represented | {"technicalSkills": ["Full-stack development", "Cloud architecture"], "coreCompetencies": ["Problem solving", "Technical design"]} |
competencyFramework | Competency structure used | "Engineering Excellence Framework" |
talentDevelopmentApproach | Approach to developing talent | {"developmentMethodology": "70-20-10 learning model", "formalPrograms": ["Technical mentorship program"]} |
talentAcquisitionStrategy | Approach to acquiring talent | {"sourcingChannels": ["Technical referrals", "University partnerships"], "selectionCriteria": ["Technical assessment"]} |
culturalValues | Core values represented | ["Innovation", "Technical excellence", "Continuous learning", "Collaboration"] |
leadershipModel | Leadership approach | {"leadershipStyle": "Servant leadership with technical expertise", "decisionMakingApproach": "Distributed authority"} |
engagementMetrics | Measurement of engagement | {"overallEngagementScore": 82, "benchmarkComparison": "7 points above technology industry average"} |
knowledgeManagementApproach | How knowledge is handled | {"primaryKnowledgeSharing": "Documentation-as-code in internal wiki", "technicalDocumentation": "Mandatory for all systems"} |
performanceManagementSystem | Performance approach | {"reviewCycle": "Quarterly objectives with annual in-depth review", "performanceCriteria": ["Technical contribution"]} |
workforceFlexibility | Adaptability characteristics | {"workModel": "Hybrid with 2 core in-office days", "geographicDistribution": "65% headquarters, 35% distributed"} |
diversityMetrics | Diversity and inclusion measures | {"genderDiversity": "28% women in engineering roles", "ethnicDiversity": "Representation matches regional demographics"} |
strategicAlignment | Alignment with business strategy | {"alignmentDescription": "Engineering workforce directly enables product innovation strategy"} |
Workforce Element Schema
Property | Description | Example |
---|---|---|
workforceID | Unique identifier for the workforce element | "WORKFORCE-ENG-001" |
workforceTitle | Name of the specific workforce segment | "Backend Engineering Team" |
workforceType | Category of workforce | "permanent" |
workforceDescription | Detailed explanation of the workforce segment | "Core backend development team responsible for API and database architecture" |
orgUnitTitle | Organization unit this workforce belongs to | "Engineering Division" |
peopleID | ID of the people domain this workforce belongs to | "PEOPLE-WORKFORCE-001" |
workforceSize | Size metrics for this segment | {"headcount": 42, "fullTimeEquivalent": 40.5, "contractorPercentage": 10} |
workforceLocation | Geographic distribution | {"locations": [{"name": "Headquarters", "percentage": 70}, {"name": "Remote", "percentage": 30}]} |
workSkills | Skills and capabilities | {"criticalSkills": ["Node.js", "Microservices architecture"], "skillProficiency": "Advanced"} |
workExperience | Experience profile | {"averageYearsExperience": 8.5, "seniorityProfile": "65% senior, 25% mid-level, 10% junior"} |
workforceAvailability | Availability characteristics | {"utilizationRate": "85%", "leaveRate": "3%", "overtimePercentage": "5%"} |
workforceCost | Cost structure | {"averageSalary": "$120,000", "fullyLoadedCost": "$155,000", "annualCostIncrease": "3.5%"} |
workforceRisks | Risk factors | [{"riskName": "Turnover", "riskLevel": "moderate", "mitigation": "Enhanced retention program"}] |
successionPlanning | Succession approach | {"criticalRolesCovered": "85%", "benchStrength": "2.1 candidates per critical role"} |
workforceStrategy | Strategic approach to this segment | {"growthStrategy": "Organic growth with selective hiring", "developmentFocus": "Cloud-native architecture"} |
Culture Element Schema
Property | Description | Example |
---|---|---|
cultureID | Unique identifier for the culture element | "CULT-INNO-001" |
cultureAttributeTitle | Name of the specific culture attribute | "Innovation Culture" |
attributeDescription | Detailed explanation of the culture attribute | "The organization's capacity to generate and implement novel ideas and solutions" |
orgUnitTitle | Organization unit responsible for this attribute | "Organizational Development" |
peopleID | ID of the people domain this culture element belongs to | "PEOPLE-CULTURE-001" |
currentState | Present condition of this attribute | {"maturityLevel": "defined", "consistencyLevel": "variable across units"} |
desiredState | Target condition for this attribute | {"maturityLevel": "optimizing", "consistencyLevel": "high across organization"} |
culturalImportance | Strategic significance | {"importanceLevel": "critical", "businessImpact": "Drives competitive differentiation and product leadership"} |
supportingBehaviors | Behaviors reinforcing this attribute | ["Experimentation", "Psychological safety", "Recognition of creative efforts"] |
counteringBehaviors | Behaviors working against it | ["Risk aversion", "Perfectionism", "Excessive process focus"] |
measurementApproach | How attribute is assessed | {"assessmentMethod": "Annual culture survey with innovation index", "leadingIndicators": ["Idea submission rate"]} |
reinforcementMechanisms | How attribute is strengthened | {"formalMechanisms": ["Innovation time allocation", "Idea incubator program"], "informalMechanisms": ["Leadership storytelling"]} |
leadershipInfluence | Leadership impact on attribute | {"leadershipAlignment": "Strong at executive level, mixed at middle management", "keyLeadershipBehaviors": ["Modeling experimentation"]} |
culturalBarriers | Obstacles to developing attribute | [{"barrierName": "Functional silos", "impactLevel": "significant", "mitigationApproach": "Cross-functional initiatives"}] |
culturalEnablers | Factors supporting attribute | [{"enablerName": "Technology platform flexibility", "contributionLevel": "high"}] |
Competency Framework Element Schema
Property | Description | Example |
---|---|---|
frameworkID | Unique identifier for the competency framework | "COMP-ENG-001" |
frameworkTitle | Name of the specific competency framework | "Engineering Excellence Framework" |
frameworkDescription | Detailed explanation of the framework | "Comprehensive model defining technical and behavioral competencies for engineering roles" |
orgUnitTitle | Organization unit responsible for this framework | "Engineering Development" |
peopleID | ID of the people domain this framework belongs to | "PEOPLE-WORKFORCE-001" |
competencyCategories | Major categories in the framework | [{"categoryName": "Technical Skills", "description": "Core technical capabilities"}, {"categoryName": "Leadership", "description": "Team and project leadership capabilities"}] |
competencyLevels | Progression levels in the framework | [{"levelName": "Foundational", "description": "Entry-level proficiency"}, {"levelName": "Advanced", "description": "Expert-level mastery"}] |
assessmentMethods | Evaluation approaches | {"primaryMethod": "Manager assessment with peer feedback", "calibrationProcess": "Cross-functional review panels"} |
developmentPaths | Progression routes | [{"pathName": "Technical Expert", "description": "Progression toward technical mastery"}, {"pathName": "Engineering Leader", "description": "Progression toward leadership roles"}] |
certificationRequirements | Formal certifications | {"internalCertifications": ["System Design", "Code Quality"], "externalCertifications": ["Cloud Platform Certifications"]} |
competencyOwner | Responsible entity | {"primaryOwner": "VP of Engineering", "supportingRoles": ["Engineering Managers", "Learning & Development Team"]} |
frameworkAdoption | Usage across organization | {"adoptionRate": "85% of engineering organization", "implementationApproach": "Role-specific competency profiles"} |
frameworkReviewCycle | Update process | {"reviewFrequency": "Annual with quarterly check-ins", "lastReviewDate": "2024-11-15"} |
alignmentToStrategy | Strategic alignment | {"alignmentLevel": "high", "strategicObjectives": ["Technical excellence", "Innovation capability"]} |
industryStandards | Relevant external standards | {"referenceStandards": ["IEEE Software Engineering Body of Knowledge", "ACM Computing Classification System"]} |
Knowledge Management Element Schema
Property | Description | Example |
---|---|---|
knowledgeID | Unique identifier for the knowledge element | "KM-ARCH-001" |
knowledgeAssetTitle | Name of the specific knowledge asset | "System Architecture Knowledge Base" |
assetDescription | Detailed explanation of the knowledge asset | "Repository of architectural decisions, patterns, and principles for core systems" |
orgUnitTitle | Organization unit responsible for this asset | "Enterprise Architecture" |
peopleID | ID of the people domain this knowledge asset belongs to | "PEOPLE-KNOWLEDGE-001" |
knowledgeType | Category of knowledge | "explicit" |
knowledgeCriticality | Strategic importance | {"criticalityLevel": "high", "businessImpact": "Ensures consistent architectural decisions and prevents technical debt"} |
knowledgeSources | Origin points | {"primarySources": ["Architecture review meetings", "Design documentation"], "contributorRoles": ["Enterprise Architects", "Technical Leads"]} |
knowledgeUsers | Consumers | {"primaryUsers": ["Development Teams", "Solution Architects"], "usageContext": "During design and implementation phases"} |
captureMethod | How knowledge is captured | {"method": "Architecture Decision Records", "captureProcess": "Post-decision documentation with structured templates"} |
storageApproach | How knowledge is stored | {"storageSystem": "Enterprise wiki with version control", "organizationMethod": "Taxonomical categorization with tagging"} |
accessControls | Who can access | {"accessRestrictions": "Read access for all technical staff, write access for architects and tech leads", "securityLevel": "Internal only"} |
sharingMechanisms | How knowledge is shared | {"formalMechanisms": ["Architecture forums", "New hire onboarding"], "informalMechanisms": ["Communities of practice"]} |
utilizationMetrics | How usage is measured | {"usageMetrics": ["Page views", "Reference citations in design documents"], "utilizationRate": "73% of eligible staff access monthly"} |
knowledgeRisks | Risk factors | [{"riskName": "Knowledge decay", "riskLevel": "medium", "mitigation": "Quarterly review and refresh process"}] |
retentionStrategy | How knowledge is preserved | {"retentionMethod": "Living documentation with ownership assignments", "successorProgram": "Architect mentoring program"} |