@forwardimpact/schema 0.9.1 → 0.10.0

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