8617-702 Assignment Example

Developing and maintaining a high-performance culture is the Level 7 unit that examines the most complex leadership challenge: creating an organisational environment where exceptional performance is not dependent on individual heroism but is embedded in the way the organisation operates — its values, systems, behaviours, and leadership practices. Unit 8617-702 requires you to diagnose your organisation’s cultural health, design interventions that build sustainable high performance, optimise resource deployment, and evaluate whether the culture you are building produces the outcomes you intend.

This assignment example follows a managing director of a 180-person UK software development company navigating the transition from start-up culture (informal, founder-led, relationship-driven) to scale-up culture (structured, system-led, and sustainable beyond any individual).

Learning Outcome 1 — Understand How to Develop a High-Performance Culture

AC 1.1 — Analyse the Organisation’s Current Culture and Its Impact on Performance

The software company’s culture was diagnosed using Schein and Schein’s (2021) three-level model: artefacts (visible elements), espoused values (stated beliefs), and basic assumptions (unconscious, taken-for-granted beliefs that actually drive behaviour).

Artefacts: open-plan office with no assigned desks, a games room, flexible working hours, casual dress code, weekly all-hands meetings led by the founder, and a flat organisational structure with minimal hierarchy. These artefacts signal informality, accessibility, and egalitarianism. Espoused values: the company’s values statement identifies ‘innovation, autonomy, ownership, and customer obsession.’ These values are displayed on the office walls and referenced in recruitment materials. Basic assumptions: the company operates on three unconscious assumptions that drive behaviour more powerfully than the stated values. First, ‘the founder knows best’ — despite the flat structure, critical decisions are informally routed through the founder, creating a hidden hierarchy. Second, ‘heroic individual performance is what matters’ — promotions, recognition, and mythology celebrate individual developers who worked weekends to ship a product, rather than teams that delivered sustainably. Third, ‘process is the enemy of agility’ — any attempt to introduce structured processes (project management methodology, documentation standards, approval workflows) is culturally resisted as ‘bureaucracy.’

The performance impact is mixed. The culture produces genuine innovation — the company ships features faster than larger competitors and attracts talented developers who value autonomy. However, it also produces burnout (27% annual turnover, concentrated among developers in years 2-4), quality inconsistency (the company’s defect rate is 40% above industry benchmark because code review processes are culturally resisted), and scaling failure (three attempts to open a second office have failed because the culture depends on the founder’s physical presence). West (2021) identifies this as the ‘founder’s dilemma’ — the culture that enabled the start-up’s success becomes the barrier to its growth.