@forwardimpact/schema 0.9.0 → 0.9.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (17) hide show
  1. package/examples/capabilities/delivery.yaml +2 -2
  2. package/examples/questions/capabilities/business.yaml +37 -40
  3. package/examples/questions/capabilities/delivery.yaml +32 -36
  4. package/examples/questions/capabilities/people.yaml +37 -40
  5. package/examples/questions/capabilities/reliability.yaml +35 -38
  6. package/examples/questions/capabilities/scale.yaml +35 -36
  7. package/examples/questions/skills/architecture_design.yaml +59 -49
  8. package/examples/questions/skills/cloud_platforms.yaml +53 -41
  9. package/examples/questions/skills/code_quality.yaml +81 -31
  10. package/examples/questions/skills/data_modeling.yaml +43 -39
  11. package/examples/questions/skills/devops.yaml +46 -39
  12. package/examples/questions/skills/full_stack_development.yaml +41 -36
  13. package/examples/questions/skills/sre_practices.yaml +40 -37
  14. package/examples/questions/skills/stakeholder_management.yaml +37 -36
  15. package/examples/questions/skills/team_collaboration.yaml +39 -33
  16. package/examples/questions/skills/technical_writing.yaml +39 -35
  17. package/package.json +1 -1
package/examples/questions/skills/devops.yaml CHANGED
@@ -3,39 +3,40 @@
3
3
  professionalQuestions:
4
4
  awareness:
5
5
  - id: devops_pro_aware_1
6
- text:
7
- What do you understand about CI/CD pipelines? How have you used them?
6
+ text: What do you understand about CI/CD pipelines? How have you used them?
8
7
  lookingFor:
9
- - Basic understanding of automated builds and deployments
10
- - Experience using pipelines defined by others
8
+ - Understands that pipelines automate build, test, and deploy steps
9
+ - Describes personal experience using pipelines, even basic usage
11
10
  expectedDurationMinutes: 5
12
11
  foundational:
13
12
  - id: devops_pro_found_1
14
13
  text: Describe how you would set up a basic CI pipeline for a new project.
15
14
  lookingFor:
16
- - Understanding of CI fundamentals
17
- - Basic pipeline configuration knowledge
18
- expectedDurationMinutes: 8
15
+ - Identifies key pipeline stages like build, test, and feedback
16
+ - Considers what checks provide the most value early in the pipeline
17
+ - Thinks about developer experience and fast feedback loops
18
+ expectedDurationMinutes: 5
19
19
  working:
20
20
  - id: devops_pro_work_1
21
21
  text:
22
- Tell me about a deployment pipeline you've built. What stages did it
23
- include?
22
+ How do you design a deployment pipeline that balances safety with speed?
24
23
  followUps:
25
- - How did you handle failures?
26
- - What monitoring did you add?
24
+ - How do you handle pipeline failures?
25
+ - How would AI tools change your approach to pipeline design?
27
26
  lookingFor:
28
- - End-to-end pipeline experience
29
- - Infrastructure as code awareness
30
- expectedDurationMinutes: 10
27
+ - Designs pipelines with progressive confidence stages
28
+ - Builds in rollback mechanisms and monitoring gates
29
+ - Considers the developer experience of the pipeline
30
+ expectedDurationMinutes: 8
31
31
  practitioner:
32
32
  - id: devops_pro_pract_1
33
33
  text: How have you improved deployment practices in your team?
34
34
  followUps:
35
35
  - How did you measure improvement?
36
36
  lookingFor:
37
- - DevOps leadership
38
- - Metrics-driven improvement
37
+ - Identifies specific bottlenecks and addresses them with data
38
+ - Drives measurable improvements in deployment frequency or reliability
39
+ - Mentors team members on DevOps practices and tooling
39
40
  expectedDurationMinutes: 8
40
41
  expert:
41
42
  - id: devops_pro_expert_1
@@ -43,51 +44,57 @@ professionalQuestions:
43
44
  followUps:
44
45
  - What cultural changes did you drive?
45
46
  lookingFor:
46
- - Organizational DevOps transformation
47
- - Culture change leadership
47
+ - Defines DevOps standards that teams adopt because they reduce pain, not because they're mandated
48
+ - Drives cultural shift from ops-as-separate-team to shared operational ownership
49
+ - Measures transformation success through deployment frequency and recovery time, not compliance
48
50
  expectedDurationMinutes: 10
49
51
 
50
52
  managementQuestions:
51
53
  awareness:
52
54
  - id: devops_mgmt_aware_1
53
- text: How do you ensure your team can deploy their changes reliably?
55
+ text:
56
+ How do you ensure your team understands the importance of CI/CD practices?
54
57
  lookingFor:
55
- - Basic deployment awareness
56
- - Team enablement understanding
58
+ - Communicates pipeline value in terms of team confidence and speed
59
+ - Ensures the team understands pipeline stages and their purpose
57
60
  expectedDurationMinutes: 5
58
61
  foundational:
59
62
  - id: devops_mgmt_found_1
60
- text: How do you manage deployment frequency and risk in your team?
61
- followUps:
62
- - How do you handle deployment failures?
63
+ text:
64
+ How do you support team members in developing DevOps skills?
63
65
  lookingFor:
64
- - Deployment risk management
65
- - Team process awareness
66
- expectedDurationMinutes: 8
66
+ - Creates hands-on learning opportunities for DevOps skills
67
+ - Pairs less experienced engineers with DevOps-strong colleagues
68
+ - Makes DevOps work visible and valued, not just ops burden
69
+ expectedDurationMinutes: 5
67
70
  working:
68
71
  - id: devops_mgmt_work_1
69
- text: How do you balance deployment velocity with stability in your team?
72
+ text:
73
+ How do you establish deployment practices and standards in your team?
70
74
  followUps:
71
- - What metrics do you track?
75
+ - How do you balance deployment speed with risk?
72
76
  lookingFor:
73
- - DevOps metrics understanding
74
- - Trade-off management
77
+ - Creates deployment standards that improve confidence rather than slow teams down
78
+ - Communicates deployment risk in terms stakeholders can act on
79
+ - Uses progressive rollout and feature flags to manage risk without blocking releases
75
80
  expectedDurationMinutes: 10
76
81
  practitioner:
77
82
  - id: devops_mgmt_pract_1
78
- text: How do you build DevOps capabilities and culture within your team?
83
+ text:
84
+ How do you drive DevOps culture and continuous improvement in your team?
79
85
  followUps:
80
- - How do you handle resistance to change?
86
+ - How do you communicate deployment metrics to stakeholders?
81
87
  lookingFor:
82
- - DevOps culture development
83
- - Team capability building
88
+ - Makes deployment metrics visible and uses them to drive improvement conversations
89
+ - Creates psychological safety around deployment failures so the team learns rather than hides
90
+ - Coaches team members to own the full lifecycle from commit to production
84
91
  expectedDurationMinutes: 8
85
92
  expert:
86
93
  - id: devops_mgmt_expert_1
87
94
  text:
88
- How do you drive DevOps transformation and platform strategy across
89
- multiple teams?
95
+ How do you shape organizational DevOps strategy and transformation?
90
96
  lookingFor:
91
- - Cross-team DevOps leadership
92
- - Organizational transformation
97
+ - Defines DevOps maturity models that meet teams where they are and guide progression
98
+ - Creates shared platform investments that accelerate all teams without constraining them
99
+ - Influences organisation-wide culture toward continuous delivery and operational ownership
93
100
  expectedDurationMinutes: 10
package/examples/questions/skills/full_stack_development.yaml CHANGED
@@ -5,8 +5,8 @@ professionalQuestions:
5
5
  - id: fs_pro_aware_1
6
6
  text: What layers of a typical web application are you familiar with?
7
7
  lookingFor:
8
- - Basic understanding of frontend, backend, database
9
- - Awareness of how layers interact
8
+ - Understands the main layers (frontend, backend, data) and their roles
9
+ - Describes how layers communicate and depend on each other
10
10
  expectedDurationMinutes: 5
11
11
  foundational:
12
12
  - id: fs_pro_found_1
@@ -14,20 +14,22 @@ professionalQuestions:
14
14
  Walk me through building a simple feature that touches the UI, API, and
15
15
  database.
16
16
  lookingFor:
17
- - Understanding of full-stack flow
18
- - Basic implementation across layers
19
- expectedDurationMinutes: 10
17
+ - Thinks through the full flow from user action to data storage
18
+ - Considers how changes in one layer affect others
19
+ - Plans the implementation order pragmatically
20
+ expectedDurationMinutes: 5
20
21
  working:
21
22
  - id: fs_pro_work_1
22
23
  text:
23
- Describe a complete feature you delivered end-to-end. How did you
24
- approach each layer?
24
+ How do you approach delivering a complete feature end-to-end across the
25
+ stack?
25
26
  followUps:
26
- - What challenges did you face?
27
+ - How do AI tools help you work across unfamiliar layers?
27
28
  lookingFor:
28
- - Independent full-stack delivery
29
- - Pragmatic technology choices
30
- expectedDurationMinutes: 10
29
+ - Delivers independently across all layers without specialist handoffs
30
+ - Makes pragmatic technology choices based on the feature needs
31
+ - Identifies and addresses gaps in their own stack knowledge
32
+ expectedDurationMinutes: 8
31
33
  practitioner:
32
34
  - id: fs_pro_pract_1
33
35
  text:
@@ -36,60 +38,63 @@ professionalQuestions:
36
38
  followUps:
37
39
  - How do you handle areas outside your expertise?
38
40
  lookingFor:
39
- - Speed of end-to-end delivery
40
- - Self-sufficiency across the stack
41
+ - Delivers end-to-end features in days by working across the full stack confidently
42
+ - Uses AI tools to accelerate work in less familiar layers rather than blocking on others
43
+ - Knows when their cross-stack work needs specialist review versus when it's solid enough
41
44
  expectedDurationMinutes: 10
42
45
  expert:
43
46
  - id: fs_pro_expert_1
44
47
  text: How do you enable rapid full-stack delivery across teams?
45
48
  lookingFor:
46
- - Organizational full-stack enablement
47
- - Removing specialist dependencies at scale
49
+ - Creates shared tooling and patterns that make cross-stack work accessible to all engineers
50
+ - Removes specialist bottlenecks by building team capability rather than centralising expertise
51
+ - Shapes hiring and development to value versatility alongside depth
48
52
  expectedDurationMinutes: 10
49
53
 
50
54
  managementQuestions:
51
55
  awareness:
52
56
  - id: fs_mgmt_aware_1
53
57
  text:
54
- How do you ensure your team can work across the full stack when needed?
58
+ How do you ensure your team understands the full scope of features they deliver?
55
59
  lookingFor:
56
- - Basic understanding of full-stack team needs
57
- - Awareness of skill coverage
60
+ - Encourages engineers to trace features end-to-end, not just their layer
61
+ - Ensures demos show the complete user experience, not just isolated components
58
62
  expectedDurationMinutes: 5
59
63
  foundational:
60
64
  - id: fs_mgmt_found_1
61
- text: How do you handle skill gaps across the stack in your team?
62
- followUps:
63
- - When do you bring in specialists vs develop skills internally?
65
+ text:
66
+ How do you help team members develop skills across the full stack?
64
67
  lookingFor:
65
- - Skill gap management
66
- - Team capability planning
68
+ - Assigns cross-layer tasks that stretch engineers beyond their comfort zone
69
+ - Pairs specialists together so knowledge transfers through real work
70
+ - Creates safety for engineers to work in unfamiliar layers without fear of judgment
67
71
  expectedDurationMinutes: 10
68
72
  working:
69
73
  - id: fs_mgmt_work_1
70
74
  text:
71
- How do you balance specialist depth vs full-stack breadth in your team
72
- composition?
75
+ How do you balance specialist depth with full-stack breadth in your team?
73
76
  followUps:
74
- - How does this affect your hiring and development?
77
+ - How do you assign work to build versatility?
75
78
  lookingFor:
76
- - Team composition strategy
77
- - Skill development planning
79
+ - Maps the team's skill portfolio and identifies risky concentrations
80
+ - Assigns work deliberately to build versatility while respecting delivery commitments
81
+ - Uses AI tools' ability to fill knowledge gaps as a lever for cross-stack confidence
78
82
  expectedDurationMinutes: 10
79
83
  practitioner:
80
84
  - id: fs_mgmt_pract_1
81
- text: How do you build full-stack capabilities within your team?
82
- followUps:
83
- - How do you reduce dependencies on external specialists?
85
+ text:
86
+ How do you build a team culture of end-to-end ownership and delivery?
84
87
  lookingFor:
85
- - Full-stack capability development
86
- - Team self-sufficiency strategies
88
+ - Creates expectations that engineers own features from commit to production
89
+ - Removes structural barriers that force specialist handoffs between layers
90
+ - Celebrates engineers who step outside their primary expertise to unblock delivery
87
91
  expectedDurationMinutes: 10
88
92
  expert:
89
93
  - id: fs_mgmt_expert_1
90
94
  text:
91
- How do you enable autonomous full-stack delivery across multiple teams?
95
+ How do you shape organizational approaches to full-stack delivery and team structure?
92
96
  lookingFor:
93
- - Cross-team full-stack enablement
94
- - Organizational capability strategy
97
+ - Designs team topologies that minimise cross-team handoffs for feature delivery
98
+ - Creates organisational patterns for building versatile teams at scale
99
+ - Influences hiring practices to value T-shaped engineers over narrow specialists
95
100
  expectedDurationMinutes: 10
package/examples/questions/skills/sre_practices.yaml CHANGED
@@ -3,35 +3,39 @@
3
3
  professionalQuestions:
4
4
  awareness:
5
5
  - id: sre_pro_aware_1
6
- text: What do you understand by SLIs, SLOs, and error budgets?
6
+ text: How do you know when a service is healthy enough for your users?
7
7
  lookingFor:
8
- - Basic SRE concepts understanding
9
- - Awareness of reliability metrics
8
+ - Thinks about health from the user's perspective, not just uptime
9
+ - Shows awareness that different users have different expectations
10
+ - Recognizes that monitoring and alerting help detect problems early
10
11
  expectedDurationMinutes: 5
11
12
  foundational:
12
13
  - id: sre_pro_found_1
13
14
  text: How would you set up basic monitoring and alerting for a service?
14
15
  lookingFor:
15
- - Understanding of observability basics
16
- - Experience with monitoring tools
16
+ - Monitors the metrics users care about, not just system internals
17
+ - Sets alert thresholds that catch real problems without alert fatigue
18
+ - Builds dashboards that help someone unfamiliar diagnose issues quickly
17
19
  expectedDurationMinutes: 8
18
20
  working:
19
21
  - id: sre_pro_work_1
20
22
  text:
21
- Describe how you've handled an incident in production. What was your
23
+ How do you approach handling incidents in production? What is your
22
24
  process?
23
25
  followUps:
24
- - What did you learn from it?
26
+ - What do you learn from incidents and how do you apply it?
25
27
  lookingFor:
26
- - Incident response experience
27
- - Post-incident improvement
28
- expectedDurationMinutes: 10
28
+ - Follows a structured incident response process, not ad-hoc firefighting
29
+ - Documents findings and drives follow-up improvements
30
+ - Communicates incident status clearly to affected stakeholders
31
+ expectedDurationMinutes: 8
29
32
  practitioner:
30
33
  - id: sre_pro_pract_1
31
34
  text: How do you balance reliability with feature velocity in your team?
32
35
  lookingFor:
33
- - Error budget management
34
- - Pragmatic reliability decisions
36
+ - Uses error budgets to make objective speed-vs-reliability decisions
37
+ - Adjusts reliability investment based on user impact data, not fear
38
+ - Coaches team to treat reliability work as enabling velocity, not opposing it
35
39
  expectedDurationMinutes: 8
36
40
  expert:
37
41
  - id: sre_pro_expert_1
@@ -39,56 +43,55 @@ professionalQuestions:
39
43
  How have you established reliability culture and practices across an
40
44
  organization?
41
45
  lookingFor:
42
- - Organizational reliability leadership
43
- - Systematic reliability improvement
46
+ - Creates reliability standards and SLO frameworks adopted across the business unit
47
+ - Builds organisational capability for incident response and learning
48
+ - Influences engineering leadership to invest in reliability as a business enabler
44
49
  expectedDurationMinutes: 10
45
50
 
46
51
  managementQuestions:
47
52
  awareness:
48
53
  - id: sre_mgmt_aware_1
49
54
  text:
50
- How do you ensure your team understands the reliability expectations for
51
- their services?
55
+ How do you ensure your team understands reliability concepts and their importance?
52
56
  lookingFor:
53
- - Basic reliability awareness
54
- - Team expectation setting
57
+ - Connects reliability to user impact in team discussions, not abstract metrics
58
+ - Makes reliability part of feature discussions rather than a separate concern
55
59
  expectedDurationMinutes: 5
56
60
  foundational:
57
61
  - id: sre_mgmt_found_1
58
62
  text:
59
- How do you manage on-call rotations and incident response in your team?
60
- followUps:
61
- - How do you prevent burnout?
63
+ How do you support team members in developing reliability engineering skills?
62
64
  lookingFor:
63
- - On-call management
64
- - Team wellbeing awareness
65
+ - Creates hands-on learning through incident response participation and on-call rotations
66
+ - Pairs less experienced engineers with SRE-skilled colleagues on reliability tasks
67
+ - Reviews reliability practices in design discussions and code reviews
65
68
  expectedDurationMinutes: 8
66
69
  working:
67
70
  - id: sre_mgmt_work_1
68
71
  text:
69
- How do you balance reliability investment with feature delivery in your
70
- team's roadmap?
72
+ How do you handle incidents and facilitate post-incident learning?
71
73
  followUps:
72
- - How do you prioritize reliability work?
74
+ - How do you communicate incidents to stakeholders?
73
75
  lookingFor:
74
- - Reliability vs velocity trade-offs
75
- - Roadmap prioritization
76
+ - Runs blameless incident reviews that produce actionable improvements
77
+ - Communicates incident status and impact clearly to non-technical stakeholders
78
+ - Tracks whether post-incident actions are completed and effective
76
79
  expectedDurationMinutes: 10
77
80
  practitioner:
78
81
  - id: sre_mgmt_pract_1
79
- text: How do you build a reliability-focused culture within your team?
80
- followUps:
81
- - How do you learn from incidents?
82
+ text:
83
+ How do you drive reliability culture and balance it with feature delivery pressure?
82
84
  lookingFor:
83
- - Reliability culture development
84
- - Incident learning practices
85
+ - Uses error budgets to make transparent trade-off decisions with stakeholders
86
+ - Frames reliability investment as protecting delivery velocity, not slowing it
87
+ - Creates team norms where reliability is everyone's responsibility, not an SRE team's
85
88
  expectedDurationMinutes: 8
86
89
  expert:
87
90
  - id: sre_mgmt_expert_1
88
91
  text:
89
- How do you drive reliability practices and culture across multiple
90
- teams?
92
+ How do you shape organizational reliability strategy and practices?
91
93
  lookingFor:
92
- - Cross-team reliability leadership
93
- - Organizational reliability strategy
94
+ - Defines reliability practices and SLO frameworks adopted across organisational boundaries
95
+ - Creates incident response capabilities that work across teams and business units
96
+ - Influences organisational culture so reliability is valued as a business differentiator
94
97
  expectedDurationMinutes: 10
package/examples/questions/skills/stakeholder_management.yaml CHANGED
@@ -7,8 +7,8 @@ professionalQuestions:
7
7
  Who are the key stakeholders you work with and how do you keep them
8
8
  informed?
9
9
  lookingFor:
10
- - Stakeholder identification
11
- - Basic communication practices
10
+ - Identifies who depends on their work and who they depend on
11
+ - Keeps stakeholders informed proactively rather than waiting to be asked
12
12
  expectedDurationMinutes: 5
13
13
  foundational:
14
14
  - id: stk_pro_found_1
@@ -16,19 +16,20 @@ professionalQuestions:
16
16
  How do you set expectations with stakeholders about timelines and
17
17
  deliverables?
18
18
  lookingFor:
19
- - Expectation management
20
- - Proactive communication
19
+ - Sets realistic expectations early rather than over-promising
20
+ - Communicates changes to timelines proactively with reasons and alternatives
21
+ - Builds trust through consistent follow-through on commitments
21
22
  expectedDurationMinutes: 5
22
23
  working:
23
24
  - id: stk_pro_work_1
24
25
  text:
25
- Describe a situation where you had to manage conflicting stakeholder
26
- priorities.
26
+ How do you manage conflicting priorities from different stakeholders?
27
27
  followUps:
28
- - How did you resolve it?
28
+ - How do you decide whose priorities take precedence?
29
29
  lookingFor:
30
- - Conflict navigation
31
- - Prioritization skills
30
+ - Identifies the underlying needs behind each stakeholder's position
31
+ - Facilitates trade-off discussions rather than unilaterally deciding
32
+ - Communicates decisions and reasoning back to all affected parties
32
33
  expectedDurationMinutes: 8
33
34
  practitioner:
34
35
  - id: stk_pro_pract_1
@@ -36,64 +37,64 @@ professionalQuestions:
36
37
  How do you build trust with senior stakeholders and influence their
37
38
  decisions?
38
39
  lookingFor:
39
- - Executive relationship building
40
- - Influence without authority
40
+ - Builds credibility through consistent delivery and transparent communication
41
+ - Influences decisions by framing technical choices in business terms
42
+ - Adapts their communication style to match each stakeholder's priorities and preferences
41
43
  expectedDurationMinutes: 10
42
44
  expert:
43
45
  - id: stk_pro_expert_1
44
46
  text:
45
47
  How do you manage complex stakeholder landscapes across an organization?
46
48
  lookingFor:
47
- - Enterprise stakeholder management
48
- - Political navigation
49
+ - Maps and navigates complex stakeholder networks with competing interests
50
+ - Builds coalitions to drive organisational change across boundaries
51
+ - Resolves conflicts between powerful stakeholders while preserving relationships
49
52
  expectedDurationMinutes: 10
50
53
 
51
54
  managementQuestions:
52
55
  awareness:
53
56
  - id: stk_mgmt_aware_1
54
57
  text:
55
- How do you ensure your team communicates effectively with stakeholders?
58
+ How do you ensure your team understands who their stakeholders are?
56
59
  lookingFor:
57
- - Basic stakeholder communication guidance
58
- - Team communication awareness
60
+ - Makes stakeholder context visible to the team during planning and execution
61
+ - Helps team members understand how their work impacts other teams and users
59
62
  expectedDurationMinutes: 5
60
63
  foundational:
61
64
  - id: stk_mgmt_found_1
62
65
  text:
63
- How do you shield your team from stakeholder pressure while maintaining
64
- relationships?
65
- followUps:
66
- - How do you handle unrealistic demands?
66
+ How do you help team members develop stakeholder management skills?
67
67
  lookingFor:
68
- - Team protection practices
69
- - Stakeholder boundary setting
68
+ - Creates opportunities for engineers to interact directly with stakeholders
69
+ - Coaches team members on communication style for different audiences
70
+ - Models effective stakeholder communication in their own interactions
70
71
  expectedDurationMinutes: 5
71
72
  working:
72
73
  - id: stk_mgmt_work_1
73
74
  text:
74
- How do you represent your team's interests to stakeholders while
75
- maintaining trust?
75
+ How do you manage stakeholder expectations on behalf of your team?
76
76
  followUps:
77
- - How do you handle conflicting stakeholder demands?
77
+ - How do you shield your team while maintaining transparency?
78
78
  lookingFor:
79
- - Team advocacy
80
- - Stakeholder relationship management
79
+ - Manages expectations proactively by surfacing risks and trade-offs early
80
+ - Shields team from context-switching without hiding information from stakeholders
81
+ - Maintains trust through transparency even when delivering difficult news
81
82
  expectedDurationMinutes: 8
82
83
  practitioner:
83
84
  - id: stk_mgmt_pract_1
84
- text: How do you develop stakeholder management skills within your team?
85
- followUps:
86
- - How do you delegate stakeholder relationships?
85
+ text:
86
+ How do you navigate conflicting stakeholder priorities and build trust across groups?
87
87
  lookingFor:
88
- - Team stakeholder capability building
89
- - Delegation of relationships
88
+ - Facilitates alignment discussions rather than choosing sides unilaterally
89
+ - Builds trust with multiple stakeholder groups through consistent and fair treatment
90
+ - Creates transparent decision frameworks so stakeholders understand how priorities are set
90
91
  expectedDurationMinutes: 10
91
92
  expert:
92
93
  - id: stk_mgmt_expert_1
93
94
  text:
94
- How do you build strategic stakeholder relationships that benefit
95
- multiple teams?
95
+ How do you shape organizational approaches to stakeholder engagement?
96
96
  lookingFor:
97
- - Cross-team stakeholder strategy
98
- - Organizational relationship building
97
+ - Defines stakeholder engagement practices adopted across organisational boundaries
98
+ - Creates frameworks for managing complex stakeholder landscapes at enterprise scale
99
+ - Influences organisational culture toward transparent, trust-based stakeholder relationships
99
100
  expectedDurationMinutes: 10