Leadership, Facilitation and Organizational Implementation

Introduction

Design thinking is often presented as a sequence of activities—empathising, defining, ideating, prototyping and testing. In practice, however, successful innovation depends less on the sequence itself than on the leadership, facilitation and organizational conditions surrounding it. A well-designed workshop can still fail when participants lack decision rights, when conflict becomes personal, when senior stakeholders dominate discussion, or when promising concepts cannot access resources for experimentation.

This chapter examines how leaders and facilitators enable multidisciplinary innovation. It focuses on four connected responsibilities: creating productive conditions for collaboration, guiding teams through ambiguity and conflict, aligning stakeholders around evidence and decisions, and embedding design capability through governance, portfolios, resources, incentives and change management. The chapter treats design leadership as a practical organizational capability rather than as charisma or authority alone.

Learning Objectives

By the end of this chapter, students should be able to:

1. Distinguish design leadership, innovation leadership and workshop facilitation.
2. Plan and facilitate multidisciplinary workshops that produce credible outcomes.
3. Manage ambiguity, disagreement and power differences constructively.
4. Establish psychological safety without reducing standards or accountability.
5. Align stakeholders through shared evidence, decision rules and appropriate communication.
6. Design governance, portfolio, resource and incentive mechanisms for innovation.
7. Apply change-management principles when embedding design capabilities.
8. Critically evaluate the limits and ethical risks of organizational design practices.

1. Design Leadership as a Distinctive Capability

Design leadership is the ability to create the conditions in which people can understand complex problems, generate alternatives, learn from evidence and move toward responsible action. It differs from conventional administrative management in three ways.

First, the object of management is uncertain. The team may not yet know which customer problem matters, which solution is feasible, or which business model is viable. Second, progress is iterative rather than linear. Learning may require revisiting earlier assumptions. Third, value is co-created across professional boundaries. A product designer, engineer, marketer, operations manager and user may each hold only part of the relevant knowledge.

Design leadership therefore combines several forms of work:

• Direction-setting: clarifying the strategic question without prematurely prescribing the answer.
• Sensemaking: helping the team interpret incomplete, conflicting or ambiguous information.
• Enabling: securing time, access, tools, expertise and decision authority.
• Integration: connecting user desirability, technical feasibility, organizational viability and ethical acceptability.
• Learning governance: deciding what should be tested, when evidence is sufficient and how learning affects investment.

A leader does not eliminate uncertainty. Rather, the leader makes uncertainty visible, bounded and actionable.

Leadership, management and facilitation

These concepts overlap but are not identical.

One person may occupy more than one role, but confusing them creates risks. For example, a sponsor who also facilitates may unintentionally suppress dissent; an expert who controls the workshop may narrow the solution space; and a facilitator who assumes decision authority may create false agreement.

2. Leading Multidisciplinary Innovation Teams

Multidisciplinary teams create value through difference, but difference also creates friction. Disciplines use different vocabularies, standards of evidence and time horizons. Engineers may privilege reliability, marketers may emphasize demand, finance may emphasize return, and users may emphasize dignity or convenience. The leader’s task is not to make all members think alike. It is to create a shared object of inquiry and a fair process for integrating perspectives.

Team design principles

A capable innovation team normally requires:

1. Relevant diversity: differences in expertise, experience, identity and proximity to the problem.
2. A clear challenge: a question broad enough to permit alternatives but bounded enough to support action.
3. Defined authority: clarity about who recommends, decides, approves and implements.
4. Access to users and evidence: direct contact is preferable to relying exclusively on internal assumptions.
5. Protected capacity: innovation work should not be treated as an unfunded addition to already full workloads.
6. A learning cadence: regular cycles of framing, experimentation, review and adaptation.

Team diversity is not automatically beneficial. It becomes productive when inclusion, shared norms and integration mechanisms allow differences to enter the conversation. Otherwise, diversity may increase silence, subgroup formation or decision delay.

T-shaped capability

A useful design-team model is the T-shaped professional. The vertical bar represents depth in a discipline; the horizontal bar represents the ability to collaborate across disciplines. Innovation teams need both. Generalists help connect perspectives, while specialists protect the quality and feasibility of decisions. A team composed only of generalists may generate attractive but technically weak ideas; a team composed only of specialists may optimize an existing solution without questioning the underlying problem.

Team contracting

At the beginning of an initiative, teams should explicitly agree on a working contract. It may specify:

• how decisions will be made;
• what constitutes evidence;
• how disagreement will be expressed;
• how confidential or sensitive data will be handled;
• how meeting time will be used;
• how credit and recognition will be shared; and
• how unresolved issues will be escalated.

A contract is not a substitute for trust, but it makes expectations discussable and provides a basis for correcting behaviour.

3. Facilitation of Design Workshops

Facilitation is the deliberate design of interaction so that a group can achieve a meaningful outcome. It includes preparation, activity sequencing, participation management, synthesis and follow-through. A facilitator is responsible for the process, not for manufacturing a predetermined conclusion.

Workshop architecture

A robust workshop typically contains six elements:

1. Purpose: What decision, learning goal or artifact must result?
2. Participants: Who possesses relevant knowledge, authority or lived experience?
3. Inputs: What research, constraints and prior decisions should participants see?
4. Activities: What individual and collective tasks will produce the required output?
5. Decision points: Where will the group choose, defer, test or escalate?
6. Closure: Who owns each action, by when and with what evidence of completion?

The sequence should alternate between divergent and convergent activity. Divergence expands the range of interpretations or possibilities; convergence selects, combines or prioritizes. Converging too early produces familiar solutions. Diverging without convergence produces enthusiasm without commitment.

Before the workshop

Preparation often determines workshop quality more than facilitation techniques. The facilitator should:

• formulate a neutral but purposeful challenge statement;
• identify power relationships and likely sources of resistance;
• invite participants with complementary knowledge;
• provide accessible pre-reading rather than excessive documentation;
• prepare physical or digital materials;
• establish accessibility and inclusion arrangements;
• define what is inside and outside the workshop’s authority; and
• agree with the sponsor on how outputs will be used.

A challenge such as “How might we reduce avoidable waiting for first-time patients?” is more generative than “How might we implement the new scheduling system?” The first frames a user-relevant outcome; the second embeds a solution.

During the workshop

Effective facilitators balance structure and emergence. They use timeboxes, visible artifacts and explicit instructions, but remain responsive to new evidence. Common techniques include:

• Silent generation: participants write ideas independently before discussion, reducing conformity and status effects.
• Round-robin sharing: each participant contributes in turn.
• Affinity mapping: observations or ideas are grouped by meaning rather than by the identity of their author.
• Assumption mapping: assumptions are classified by importance and uncertainty.
• Dot voting: a rapid prioritization method, useful for narrowing options but not a substitute for analysis.
• Role reversal: participants argue from another stakeholder’s perspective.
• Playback: the facilitator summarizes what has been heard and invites correction.
• Decision log: decisions, rationale, owner and evidence required are recorded visibly.

Voting should be used carefully. A majority preference may reflect hierarchy, confidence or familiarity rather than value. Important decisions should combine group judgment with explicit criteria and, where appropriate, user or technical evidence.

After the workshop

A workshop is incomplete until outputs become action. Within a short period, the facilitator or owner should circulate:

• the agreed problem framing;
• key insights and unresolved questions;
• selected concepts and selection criteria;
• assumptions requiring testing;
• decisions and non-decisions;
• owners, deadlines and resource needs; and
• the date and purpose of the next review.

The quality of a workshop can be assessed by whether it improves understanding, produces a traceable decision and enables the next experiment—not by energy or the number of ideas generated.

4. Ambiguity, Conflict and Decision Quality

Ambiguity concerns uncertainty about meaning, problem boundaries or causal relationships. Conflict concerns perceived incompatibility between views, interests or identities. Both are normal in innovation. The objective is not to remove them but to distinguish productive task conflict from destructive relationship conflict.

Productive disagreement

Task conflict can improve decisions when it challenges assumptions and introduces relevant evidence. It becomes destructive when disagreement is personalized, repetitive or disconnected from the decision. Leaders can improve conflict quality by asking:

• What exactly is being disputed?
• Is the disagreement about facts, values, predictions, authority or timing?
• What evidence would change each position?
• Which assumptions are hidden?
• Can the issue be converted into a test?
• Who has the legitimate authority to decide?

A useful practice is to separate positions from interests. A finance manager may oppose a pilot because of cost, while the underlying interest is protection against uncontrolled exposure. A designer may defend a concept because it represents user dignity, while the underlying interest is avoiding harmful simplification. Making interests explicit can reveal options that satisfy more than one concern.

Decision modes

Different decisions require different modes:

• Consultative: a leader decides after seeking input.
• Consensus-seeking: the group works toward a solution all can support or tolerate.
• Consent-based: a proposal proceeds unless a reasoned objection identifies unacceptable risk.
• Delegated: authority is given to the person or team closest to the issue.
• Advisory or expert-led: a qualified specialist decides within a defined domain.

Consensus is not always appropriate. It may be too slow, may reward the least ambitious option and may conceal disagreement. The chosen mode should be stated before the discussion, especially when participants have unequal power.

Managing ambiguity through staged commitments

Organizations often make a false choice between committing immediately and refusing to act until certainty exists. A better approach is staged commitment. Early decisions authorize learning; later decisions authorize scaling. For example, a small budget may fund user research, a larger budget may fund a prototype, and a further decision may fund a controlled launch. Each stage should specify the evidence required to proceed, pivot, pause or stop.

5. Psychological Safety with Accountability

Psychological safety is a shared belief that people can speak up, ask questions, admit mistakes and offer dissent without interpersonal punishment. It is not comfort, unconditional agreement or the absence of performance standards. A psychologically safe team can maintain demanding goals while treating errors and uncertainty as sources of learning.

Leaders build psychological safety through observable behaviour:

• acknowledge what they do not know;
• invite contrary views before stating their own;
• respond appreciatively to bad news;
• distinguish a failed experiment from negligent conduct;
• correct interruptions and status-based exclusion;
• explain decisions, including when suggestions are not adopted;
• protect people who raise legitimate risks; and
• model respectful challenge.

Psychological safety must be paired with accountability. The combination can be expressed as:

The model is a diagnostic aid, not a measurement formula. It reminds leaders that safety and standards are complementary rather than opposing objectives.

6. Stakeholder Alignment and Organizational Politics

Stakeholder alignment does not mean that everyone has identical preferences. It means that relevant parties understand the strategic intent, decision process, trade-offs, commitments and next steps well enough to coordinate action.

Stakeholder analysis

Stakeholders can be examined according to their influence, interests, impact and proximity to the problem. A simple matrix may distinguish:

• high influence/high interest: actively engage and involve in key decisions;
• high influence/low interest: keep satisfied and provide concise assurance;
• low influence/high interest: keep informed and create participation routes;
• low influence/low interest: monitor proportionately.

This matrix should not be used to silence low-power groups. People with limited formal influence may experience the greatest consequences. Ethical stakeholder practice therefore adds impact and vulnerability to conventional power analysis.

Alignment mechanisms

Alignment is strengthened by:

• a shared problem definition;
• explicit strategic principles;
• common evidence and assumptions;
• transparent prioritization criteria;
• decision rights and escalation routes;
• regular sponsor reviews; and
• narratives that connect user value with organizational value.

A persuasive innovation narrative usually answers five questions: Why does the problem matter? For whom? What have we learned? What will we test? What decision or support is required now?

7. Organizational Implementation: From Projects to Capability

A successful pilot does not automatically become an organizational innovation. Implementation requires changes in routines, skills, technology, incentives, budgets, roles and identity. The organization must be able to absorb the new practice.

Governance

Innovation governance defines how opportunities are selected, funded, reviewed and transferred. A practical governance system may include:

• Opportunity intake: a consistent way to capture problems and ideas.
• Discovery review: assessment of user need, strategic relevance and uncertainty.
• Experiment review: evaluation of learning quality, ethical risk and feasibility.
• Scale review: decision about adoption, adaptation, partnership or termination.
• Post-implementation review: examination of outcomes and unintended effects.

Governance should be light enough not to suffocate exploration and strong enough to prevent waste, duplication and hidden risk. Early-stage review should emphasize learning and risk reduction rather than conventional return-on-investment precision, because reliable forecasts may not yet be possible.

Portfolio management

Organizations should manage innovation as a portfolio rather than as a collection of unrelated projects. A portfolio may balance:

• incremental improvements and radical opportunities;
• short-term returns and long-term capability;
• internal efficiency and external growth;
• low-risk experiments and higher-uncertainty options.

Useful portfolio questions include:

1. Which strategic problems are overrepresented or neglected?
2. Are several teams testing the same assumption?
3. Does the portfolio contain credible pathways to scale?
4. Are resources being trapped in politically protected projects?
5. What risks are correlated across projects?

A portfolio perspective also permits termination without treating every stopped experiment as failure. Stopping a weak concept early can represent disciplined learning.

Resources and incentives

Innovation requires more than money. Relevant resources include time, skilled people, user access, data, legal advice, technical infrastructure, procurement flexibility and leadership attention. Resource allocation should match the maturity of the opportunity. Discovery requires access and learning capacity; implementation requires operational ownership and integration funding.

Incentives shape behaviour. If employees are rewarded only for predictable quarterly delivery, they may avoid uncertain but valuable work. If they are rewarded merely for idea volume, they may generate superficial concepts. Balanced incentives can recognize:

• quality of evidence;
• cross-functional contribution;
• responsible experimentation;
• learning that prevents waste;
• successful adoption; and
• measurable user and organizational outcomes.

Recognition should not encourage manipulation of metrics or concealment of negative evidence.

Change management

Embedding design practices involves individual adoption and organizational transition. Lewin’s unfreeze–change–refreeze model highlights the need to loosen existing assumptions, introduce new practices and stabilize them. Kotter’s change model emphasizes urgency, coalition-building, vision, communication, removal of barriers, short-term wins and institutionalization. These models are useful heuristics, but change rarely follows a perfectly linear sequence.

A contemporary implementation approach should combine:

• a compelling case for change;
• visible executive sponsorship;
• local champions and communities of practice;
• training linked to live work;
• redesigned routines and templates;
• measurement of adoption and outcomes;
• feedback channels; and
• adaptation based on experience.

Training alone rarely embeds design capability. People must have opportunities to apply new methods, receive coaching and see that organizational decisions actually respond to evidence.

8. Measuring Innovation and Design Capability

Measurement should support learning rather than produce an illusion of certainty. A balanced measurement system may include four categories:

Activity measures are easy to count but can be misleading. Outcome measures are valuable but may appear only after a long delay and may be influenced by many factors. Leaders should therefore use a portfolio of leading and lagging indicators.

A simple prioritization score can be useful when its limitations are understood. For example, a team might rate an opportunity from 1 to 5 on strategic fit, user value, feasibility and learning potential, then calculate an unweighted average:

Here, P is the priority score, and S, U, F and L are ratings for strategic fit, user value, feasibility and learning potential. The scale must be defined consistently, and the score should support—not replace—judgment. An unweighted average assumes that all four dimensions are equally important; that assumption may not hold in a safety-critical or highly regulated context.

9. Illustrative Case: Embedding Design Capability in a Regional Bank

Background

A regional bank experienced declining satisfaction among small-business customers applying for working-capital loans. Senior management commissioned a multidisciplinary team involving relationship managers, compliance specialists, data analysts, service designers, technology staff and two small-business owners.

Problem

The initial request was to “build a faster digital loan application.” Research revealed a broader problem: applicants did not understand document requirements, feared rejection and often repeated information already held by the bank. Compliance staff were concerned that simplification might weaken fraud controls.

Analysis

The team mapped the journey and identified three major assumptions:

1. Applicants would prefer a fully digital process.
2. Faster approval was the most important outcome.
3. Existing compliance checks could be moved online without changing risk exposure.

Interviews and observation showed that confidence, transparency and predictable communication mattered almost as much as speed. The team also discovered that branch staff compensated for weaknesses in the digital process, meaning that a digital-only solution could shift rather than reduce cost.

Approach and solution

The facilitator established a team contract, introduced silent idea generation and separated discussions about user desirability from discussions about regulatory feasibility. Instead of committing immediately to a full platform, the sponsor approved three staged experiments:

• a clearer document checklist;
• proactive status messages; and
• a staff-supported digital application for a limited customer segment.

The compliance specialist became a co-owner of the experiments rather than a late-stage gatekeeper. The governance group defined stop criteria for fraud indicators and escalation criteria for unusual applications.

Outcome

The experiments showed that clearer communication reduced avoidable contacts and that many customers valued assisted digital support. The organization therefore adopted a blended service model rather than a purely digital one. The most important organizational change was not the interface. It was the creation of a repeatable pathway linking customer research, compliance review, small experiments and staged investment.

Learning points

• Framing a solution too early can hide the real service problem.
• Compliance expertise is more valuable when included during exploration.
• Small experiments can reduce both customer uncertainty and organizational risk.
• Implementation requires operational ownership, not only a design team.
• A portfolio of evidence-based experiments is more informative than a single high-cost launch.

10. Ethical, Regulatory and Contemporary Considerations

Innovation leadership has ethical responsibilities because experiments affect real people. Teams should consider informed participation, privacy, accessibility, discrimination, safety, environmental impact and the distribution of benefits and burdens. Vulnerable users should not be exposed to disproportionate experimentation simply because they have less power to object.

Data-driven design requires particular care. Teams should examine whether data are lawfully obtained, representative, necessary and securely handled. Artificial intelligence can support synthesis, scenario generation and prototype development, but it can also reproduce bias, expose confidential information, fabricate evidence or obscure accountability. AI-generated outputs should be treated as provisional material requiring human verification, not as research findings.

Contemporary organizations are also moving toward distributed and hybrid innovation. Digital collaboration expands participation but can increase fatigue, exclusion and unequal visibility. Facilitators should design asynchronous contribution, accessible materials and clear documentation rather than assuming that video meetings create inclusion.

Challenges and Limitations

Several limitations deserve attention:

• Design methods can be appropriated as superficial workshop rituals without changing decisions.
• Senior sponsorship may disappear when early results are ambiguous.
• Psychological-safety language can be misused to avoid necessary performance conversations.
• Portfolio metrics may privilege what is easy to count over what is strategically important.
• Cross-functional teams may reproduce organizational power hierarchies.
• Staged experimentation can become endless deferral if decision thresholds are unclear.
• Change models may understate political interests, identity threats and informal networks.
• Innovation programs can unintentionally shift risk onto users, contractors or communities.

Critical leadership therefore requires reflexivity: leaders should examine whose knowledge counts, who bears the consequences, and whether the innovation process is creating genuine value.

Best-Practice Principles

1. Frame problems around outcomes and human needs, not predetermined technologies.
2. Make decision rights explicit before disagreement occurs.
3. Alternate divergent exploration with disciplined convergence.
4. Use conflict to test assumptions, not to attack people.
5. Model curiosity, fallibility and respectful challenge.
6. Pair psychological safety with clear standards and ownership.
7. Involve risk, legal, operational and implementation stakeholders early.
8. Fund learning in stages and define evidence thresholds for continuation.
9. Manage innovation as a balanced portfolio.
10. Measure adoption, learning and outcomes—not activity alone.
11. Treat ethics, accessibility and sustainability as design requirements.
12. Institutionalize practice through routines, incentives, coaching and governance.

Chapter Summary

Leadership and facilitation are central to design thinking because innovation is a social and organizational process, not merely a set of creative techniques. Design leaders frame uncertainty, secure enabling conditions, integrate different forms of expertise and govern learning. Facilitators create structured participation before, during and after workshops, ensuring that discussion becomes evidence, decisions and action.

Multidisciplinary teams require diversity, shared purpose, clear authority and protected capacity. Ambiguity and conflict should be made specific and converted, where possible, into testable assumptions. Psychological safety enables candour, but it must operate alongside accountability. Stakeholder alignment depends on shared framing, transparent criteria, decision rights and ethical attention to low-power groups.

Organizational implementation requires governance, portfolio management, appropriate resources, balanced incentives and change-management practices. Measurement should combine activity, learning, adoption and outcome indicators. Finally, responsible innovation demands attention to privacy, fairness, accessibility, sustainability and the limitations of AI and other technologies. The strategic objective is not simply to run better workshops, but to build an organization capable of learning and acting under uncertainty.

Key Terms

Design leadership: The practice of creating conditions for responsible learning, collaboration and innovation.

Facilitation: The intentional structuring of group interaction to achieve a meaningful outcome.

Multidisciplinary team: A team combining members from different professional or knowledge domains.

T-shaped professional: A person with deep disciplinary expertise and broad collaborative capability.

Divergence: Expansion of possible interpretations, ideas or solutions.

Convergence: Narrowing, selecting or integrating alternatives.

Psychological safety: A shared belief that people can speak up and take interpersonal risks without punishment.

Task conflict: Disagreement about ideas, evidence, priorities or methods.

Relationship conflict: Interpersonal tension involving identity, status or personal antagonism.

Stakeholder alignment: Coordinated understanding of purpose, trade-offs, decisions and commitments.

Decision rights: Explicit authority to recommend, decide, approve or implement.

Staged commitment: Progressive allocation of resources as evidence and confidence increase.

Innovation governance: Structures and rules for selecting, funding, reviewing and scaling innovation.

Innovation portfolio: A managed collection of innovation initiatives with different risks, horizons and objectives.

Assumption: A proposition treated as true but requiring evidence or testing.

Change management: Coordinated activity that supports adoption and institutionalization of new practices.

Leading indicator: An early measure that may signal future progress or risk.

Lagging indicator: A measure of an outcome that becomes visible after activity or change.

Responsible innovation: Innovation that considers ethical, social, environmental and regulatory consequences.

Review Questions

Short Answer Questions

1. How does design leadership differ from conventional administrative management?
2. What is the purpose of a team contract?
3. Distinguish divergence from convergence in a workshop.
4. Define psychological safety and explain why it is not the same as comfort.
5. What is meant by staged commitment?

Long Answer Questions

1. Explain how a facilitator should prepare, conduct and follow up a multidisciplinary design workshop.
2. Discuss how leaders can convert destructive conflict into productive task disagreement.
3. Analyse the relationship between psychological safety and accountability.
4. Explain how governance and portfolio management support organizational innovation.
5. Evaluate the role of incentives and change management in embedding design capability.

Analytical / Application Questions

1. A product team is dominated by a senior executive who rejects unfamiliar ideas before users are consulted. Diagnose the facilitation and governance problems, and propose an intervention plan.
2. An organization runs many innovation workshops but few concepts receive implementation funding. Use the chapter’s frameworks to identify likely structural causes and recommend changes.
3. Design a staged experiment plan for a public-service innovation. Specify stakeholders, decision rights, evidence thresholds, ethical safeguards and measures of learning and outcome.

Multiple Choice Questions with Answers

Question 1

Which responsibility most clearly distinguishes a design leader from a workshop facilitator?

A. Creating the conditions and direction for organizational learning

B. Recording participant comments on a shared board

C. Keeping an activity within its scheduled time

D. Grouping similar ideas after brainstorming

Correct Answer: A. Creating the conditions and direction for organizational learning

Question 2

What is the primary purpose of alternating divergent and convergent activities?

A. To ensure that every participant becomes a technical specialist

B. To expand possibilities before selecting or integrating alternatives

C. To eliminate the need for stakeholder involvement

D. To guarantee consensus on every decision

Correct Answer: B. To expand possibilities before selecting or integrating alternatives

Question 3

Which practice best reduces the effect of hierarchy during idea generation?

A. Allowing the most senior participant to speak first

B. Using silent individual generation before group discussion

C. Requiring the group to vote immediately

D. Restricting participation to subject-matter experts

Correct Answer: B. Using silent individual generation before group discussion

Question 4

Psychological safety is best defined as the belief that team members can:

A. Avoid performance standards

B. Guarantee that all suggestions will be adopted

C. Speak up and take interpersonal risks without punishment

D. Prevent disagreement from occurring

Correct Answer: C. Speak up and take interpersonal risks without punishment

Question 5

What is the main advantage of staged commitment?

A. It eliminates uncertainty before any resources are used

B. It authorizes learning before larger investments are made

C. It transfers all decisions to external consultants

D. It ensures that every pilot is eventually scaled

Correct Answer: B. It authorizes learning before larger investments are made

Question 6

Which measure is most directly a learning indicator?

A. Number of meeting invitations sent

B. Number of assumptions tested with evidence

C. Total annual payroll

D. Number of people in the organization

Correct Answer: B. Number of assumptions tested with evidence

Question 7

Why should compliance specialists be involved early in innovation work?

A. To prevent users from contributing to problem framing

B. To replace experimentation with formal approval

C. To identify constraints and co-design responsible experiments

D. To ensure that only existing solutions are considered

Correct Answer: C. To identify constraints and co-design responsible experiments

Question 8

An innovation portfolio is primarily used to:

A. Manage a balanced collection of opportunities with different risks and horizons

B. Rank employees according to creativity

C. Replace all project-level decision making

D. Measure workshop attendance only

Correct Answer: A. Manage a balanced collection of opportunities with different risks and horizons

Question 9

In the priority score P = (S + U + F + L) ÷ 4, what assumption is made by the unweighted average?

A. All four dimensions have equal importance

B. Feasibility is always greater than user value

C. The ratings are measured in monetary units

D. The score proves that an idea will succeed

Correct Answer: A. All four dimensions have equal importance

Question 10

Which action best embeds design capability after training has been delivered?

A. Ending leadership involvement immediately

B. Linking practice to live work, coaching and organizational routines

C. Measuring only the number of people trained

D. Avoiding changes to incentives and governance

Correct Answer: B. Linking practice to live work, coaching and organizational routines