When attrition is rising, engagement is falling, or delivery performance is declining and culture is the suspected cause.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Tech Communication & Leadership - Use case: Engineering Culture Audit - Source task: - Conduct an engineering culture audit for {{describe_organisation}}. Signals provided: {{describe_attrition_rate_enps_score_delivery_velocity_trends_qual}}. - Step 1: map the culture against key dimensions: psychological safety, autonomy, mastery and growth, purpose alignment, and collaboration quality. - Step 2: identify the 3 most critical culture risks. - Step 3: root cause analysis : what leadership behaviours, structural issues, or historical events created each risk? - Step 4: culture change interventions for each risk, with expected timeframes (culture change is slow : be realistic). - Step 5: how to measure culture change. # Goal Culture dimension assessment, 3 critical risks with root causes, change interventions, and culture measurement approach. # Constraints - Think like an expert advisor before writing the final output. - Ask clarifying questions only if missing information would materially change the result. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Culture dimension assessment, 3 critical risks with root causes, change interventions, and culture measurement approach.
{{double-curly}} with your real context.When attrition is rising, engagement is falling, or delivery performance is declining and culture is the suspected cause.
Culture is upstream of everything — performance problems, delivery slowdowns, and retention issues almost always have a culture root cause.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.