Organisational psychology
Organisational culture: look at everyday behaviour
Understand organisational culture through decisions, rewards and everyday responses, then turn stated values into working practices you can review.
Your company says it values learning. A project misses its target, and the review focuses entirely on who should have predicted the result. The next team learns something clear: uncertainty is safer when it stays hidden.
Culture becomes visible in that gap between the words and the response. It lives in decisions, habits, rewards and assumptions about what happens when someone acts. A values page can describe an intention; it cannot establish how the organisation works.
If you want to change culture, start with an episode people recognise. What behaviour did the organisation encourage? What did it make costly? Which response would give the stated value a practical meaning?
Look beyond visible symbols
Office design, rituals and language are useful observations, but their meaning needs context. A casual dress code does not prove a low-status hierarchy. A busy social calendar does not prove that people can challenge a decision.
Mary Jo Hatch’s work on cultural dynamics examines relationships between assumptions, values, artefacts and interpretation. It is a reminder to study how people understand visible practices.
Denison and Mishra’s research on culture and effectiveness provides another research perspective. It does not justify claiming that any particular values exercise will create a predictable performance improvement.
For practical work, examine what people do when priorities compete. That is where a value has to become a choice. “Customer first” means little until the organisation explains how it handles a customer request that conflicts with a quality requirement or a team’s capacity.
Start with one value and one decision
Choose a stated value that affects an actual workflow. Avoid beginning with a complete culture redesign; that scope makes it difficult to know which practice changed.
Translate the value into a decision question. If the value is learning, ask what happens when a well-designed experiment produces an unwanted result. If it is collaboration, ask how two functions resolve a resource conflict. If it is ownership, ask which decisions a person can authorise.
Name the behaviour that would make the value visible. For learning, a review might distinguish the quality of the decision process from the eventual outcome. It might record what was understood, which assumption failed and what should change.
Then examine the current response. A new slogan will not matter if the organisation continues to reward only favourable outcomes and punish the disclosure of uncertainty.
Trace the consequences people actually experience
What gets praised, repeated, promoted or quietly tolerated? Which commitments are enforced, and which are waived when a powerful person requests an exception?
Look at ordinary processes: planning, approval, handover, review and recognition. Ask people to describe a recent episode rather than rate the company on an abstract adjective.
Separate the written rule from the experienced response. A policy may say anyone can raise a concern, while the meeting structure gives senior people the first and final word. The gap is actionable because you can change the sequence.
Be cautious about concluding that one incident describes the entire organisation. Different teams can develop different practices. Record where the episode happened and whether it is a repeated pattern. A local observation should remain local until you have broader evidence.
Make the trade-off explicit
Values often create tensions rather than simple instructions. A team may value both speed and careful work. The useful question is how it decides which constraint governs a particular situation.
Define the conditions for the trade-off. An internal draft may permit quick iteration. A customer-facing claim may require evidence and approval. These are different work contexts, not evidence that one group cares more about quality.
Give the trade-off an owner. Without one, people repeatedly negotiate the same boundary and culture becomes an argument about personal preferences.
Document examples of acceptable decisions and the reasoning behind them. A worked example helps colleagues interpret a value in a new situation. Keep space for judgement: the example should not quietly become a rigid rule covering cases it never considered.
A hypothetical culture change in an AI programme
Imagine an organisation that announces “responsible experimentation” while celebrating every AI demo that reaches production quickly. This is a hypothetical example. Teams receive little recognition for discovering an unsuitable use case.
A programme lead chooses one practice to change: the pilot review. Each proposal must state the task, required quality, excluded uses and evidence that would stop expansion. Reviewers assess the decision against those criteria, including when the recommendation is to pause.
The leadership team also changes its recognition. It names a contribution when a team documents an important limitation, rather than treating every limitation as a failure of ambition.
The organisation observes whether unsuitable cases are surfaced before rollout and whether pilot decisions contain usable evidence. It also checks whether the new review becomes an unnecessary obstacle for low-risk work.
The example promises no culture transformation. It makes a stated value visible in an ordinary decision. If rewards elsewhere still favour speed at any cost, the local practice will face conflicting signals.
Use a values-to-behaviour worksheet
Complete this with the people who participate in the workflow. Use a real organisational value and an ordinary decision, not an imagined ideal employee.
Swipe or use the arrow keys to see every column.
| Field | Question | Example for learning |
|---|---|---|
| Stated value | What does the organisation say matters? | Learning from experiments |
| Decision point | Where must the value affect a choice? | Reviewing a pilot with an unwanted result |
| Desired behaviour | What would someone do? | Report the failed assumption and propose a next step |
| Current consequence | What happens after that behaviour? | The result is discussed as a personal failure |
| Practice to change | Which response can you alter? | Review the decision process and the evidence separately |
| Owner | Who can maintain the change? | The programme review owner |
| Review evidence | How will you know the practice exists? | Review records explain what was learned and changed |
The worksheet is not a validated culture assessment. It helps move from an abstract statement to an observable working agreement. If the team cannot identify an owner who can change the consequence, escalate that structural issue rather than asking employees to embody the value harder.
Align recognition with the behaviour you request
Suppose you ask for collaboration but only recognise individual delivery. People may face a real choice between helping another function and meeting the criteria used to evaluate them.
Review the contribution you want to acknowledge. Make it specific: an improved handover, an early risk report or support that enabled a colleague to complete a difficult task. Explain why it mattered to the shared outcome.
Recognition should remain fair and proportionate. Do not make one visible presentation stand in for all the less visible work behind it. Ask the receiving team what support was useful and include different ways of contributing.
Use the guide to motivation and autonomy to connect recognition with task ownership. Values that ask for initiative need authority and resources, not only praise.
Keep dissent from becoming a culture-fit judgement
When someone questions a plan, the question can reveal a gap in the process. Describing that person as a poor cultural fit may bypass the substance.
Ask whether the conduct meets agreed standards and whether the concern is valid. These are separate questions. A person can raise a useful issue in an unhelpful way; you may need to address both.
Avoid defining culture as sameness of background, communication style or social preferences. A shared working standard should be connected to the task and understandable to the people expected to follow it.
The psychological safety guide explains how to keep concerns available. The article on task and relationship conflict helps distinguish a contested decision from harmful interpersonal behaviour.
Use evidence without turning culture into surveillance
Meeting records and voluntary accounts can show whether a practice is changing. They are usually more informative than a slogan awareness score.
Collect only what the decision needs. Tell participants how notes will be used and who will read them. In a small team, an apparently anonymous incident can still identify its author.
Do not covertly analyse private conversations to assign culture scores to employees. Besides the trust implications, such a score can obscure context and reward people who perform the expected language.
When you compare periods, consider changes in leadership, staffing and workload. A new process and a quieter quarter may occur together. You can document useful operational evidence without claiming that culture alone caused an outcome.
Choose a response you can make consistent
Select one value, one decision point and one response. Practise it in the next complete work cycle. At the review, ask whether people experienced the response as described and whether other incentives contradicted it.
For a wider analysis, use the organisational psychology guide. When introducing AI, resistance to AI change can reveal a mismatch between the stated ambition and the practical conditions.
The same distinction between a claim and observable evidence appears in consumer psychology. Saying that something creates trust is a hypothesis; people’s experience still needs investigation.
If your digital programme’s values and working practices send different signals, tell me which recurring decision exposes the gap. We can turn that value into a practical agreement with an owner and a review point.
Apply this to your project
Tell me the decision you are facing, the constraints and what you have already tried.
Keep exploring
Motivation at work: give autonomy a clear shape
Understand motivation and autonomy at work: clarify choices, support competence and design responsibilities people can exercise in practice.
Organisational psychology: a practical team guide
A practical guide to organisational psychology for digital teams: understand friction, clarify decisions and improve how people work together.
Psychological safety: help teams speak up
Build psychological safety through everyday team practices: invite concerns, respond to mistakes and keep clear standards for accountability.