The Human-Centred Organisation

Treat differences as a strength

What it is

Stop designing around an imaginary 'standard person.' Build roles around the actual strengths, quirks and rhythms of the people you hired.

The research

ISO 27500 (2016) puts individual differences at the foundation. Most workplaces are quietly built for one default profile (linear thinker, talks in real time, copes with open-plan, happy in 8-hour blocks), who isn't actually the majority. Designing for the real range, rather than the average, is what lets people do their best work.

A bad example

One mandatory way to work for everyone: same hours, same desk, same 'pitch it live' format. The people who don't fit the mould quietly underperform or leave.

A human-centred example

Roles get shaped around what each person is great at. The out-loud thinker gets live sessions; the deep writer gets 24 hours and delivers something three times better.

The result

You get people's best work instead of a watered-down version where everyone's squeezed into the same box.

Make usability and accessibility real goals

What it is

Before you roll out a new internal tool, process or policy, check it actually works for the people who'll live in it. Accessibility included, by default.

The research

ISO 27500 names usability and accessibility as real organisational goals, not afterthoughts reserved for customers. A process that needs a PhD to navigate, or a tool nobody tested with its actual users, quietly taxes everyone every single day.

A bad example

A new system gets bought top-down and dropped on the team. It's clunky, half-inaccessible, and adds 20 minutes to everyone's day, but it's here now, so deal with it.

A human-centred example

Before rollout, someone asks the people who'll use it whether it makes work easier or harder, fixes the friction, and makes sure it works for different needs.

The result

Tools and processes that give time back instead of taxing it, and people who feel their day-to-day actually matters to whoever designs it.

Real inclusion is belonging plus uniqueness

What it is

Inclusion isn't everyone being treated 'the same.' It's people feeling they belong AND that what makes them different is valued.

The research

Shore et al. (2011) and Randel et al. (2018) define inclusion as belonging plus uniqueness. Belonging without uniqueness is assimilation, where everyone quietly conforms to the dominant group: the person with ADHD masks their style, the introvert performs extraversion. It looks like harmony. It's really suppression.

A bad example

A company prides itself on 'we treat everyone the same,' which in practice means everyone is expected to behave like the dominant group to fit in.

A human-centred example

People are fully part of the team and can bring their actual style, background and way of thinking, because difference is treated as a resource rather than something to smooth over.

The result

People stop spending energy masking and put it into the work, and you get the full benefit of the diverse team you hired.

Build for difference

People aren't interchangeable. Build for the actual range of humans you hired.

Neurodiversity as design, not accommodation

What it is

Around 15 to 20% of people are neurodivergent. Build for different brains from the start instead of making exceptions later.

The research

Estimates put 15 to 20% of people as neurodivergent in some meaningful way (ADHD, autism, dyslexia, dyspraxia and more), often with real strengths in pattern recognition, hyperfocus and divergent thinking. Reynolds & Lewis (2017) found cognitively diverse teams crack new, complex problems faster. What matters for performance is diversity of thinking style, not appearance.

A bad example

There's one standard system, and neurodivergent people have to request exceptions to cope with it, which quietly frames them as a problem being kindly accommodated.

A human-centred example

The system offers multiple communication modes, protected solo deep-work, and flexible routes to the same result, so different brains work well by default, no special pleading required.

The result

You get different thinking, the kind that solves the problems the homogeneous team kept getting stuck on, and people feel like members, not exceptions.

Trust, safety and communication

How people relate, decide and lead once you're going for trust instead of control.

Build psychological safety on purpose

What it is

Make it safe to ask the dumb question, own the mistake, challenge the idea, or float a half-baked thought without bracing for impact. Then build it deliberately.

The research

Edmondson (1999) found psychological safety is the strongest predictor of team learning and performance, above raw talent, and Google's Project Aristotle later agreed. The counterintuitive proof: her best hospital units reported MORE errors, because people felt safe enough to surface them. You build it by leaders going first (admitting uncertainty, owning mistakes), framing work as learning, and responding well the first time someone brings bad news.

A bad example

The first time someone owns a mistake, the manager makes an example of them. After that, problems hide until they explode and nobody challenges the senior person's bad idea.

A human-centred example

A leader names their own uncertainty and recent mess-ups, treats problems as shared puzzles, and meets bad news with 'thanks for flagging this early.'

The result

Problems surface while they're still cheap, ideas get challenged and improved, and the team learns faster than competitors busy covering their backs.

Make disagreement and feedback normal

What it is

Healthy teams argue well. Build the habits that spread the talking, treat failure as learning, and keep feedback flowing both ways.

The research

Woolley et al. (2010) found balanced conversational turn-taking, where no single voice dominates, is a fingerprint of collectively smart teams. High-safety teams also ask more than they tell (active inquiry) and debrief failure rather than hunt for blame. Frequent, honest, two-way feedback is part of the normal rhythm, not a once-a-year event.

A bad example

Meetings are the loudest two people talking, failures trigger a blame hunt, and feedback only appears in a dreaded annual review.

A human-centred example

Speaking time is spread (quiet people invited, never forced), failed projects get a no-blame debrief, and feedback is small, frequent and goes upward too.

The result

Better decisions, because more perspectives actually reach the table, and a team that keeps getting smarter instead of repeating the same mistakes.

Default to transparency

What it is

Let information flow up as freely as it flows down. Share meeting notes, the reasoning behind decisions, the roadmap, even the finances, by default.

The research

Every company has an information architecture, who knows what and when, and most never designed it; it just emerged from politics and who was in the room. ISO 27500 asks for real openness over 'transparency theatre,' where loads gets shared but only the flattering bits. When people can see the information, they make better calls on their own and catch errors earlier.

A bad example

Slick town halls, but leadership controls exactly what's said. Decisions appear with no reasoning, finances are secret, and bad news arrives slowly and pre-spun.

A human-centred example

Decisions are documented with the why, notes are shared by default, and people can see the roadmap and the basic money picture. Bad news travels as fast as good.

The result

More trust, more autonomy, and more people willing to speak up, all of which catch problems earlier and spark more ideas.

Write things down as care

What it is

Treat documentation as a form of respect, not bureaucracy. Decisions, processes and feedback that live in writing outlast both memory and the meeting.

The research

When decisions are documented with their reasoning (not just the conclusion), people who weren't in the room can understand and act. When processes are written, new starters onboard without exhausting your most experienced people. When feedback is written, it can be revisited instead of dissolving in the fog of memory. It quietly says: your attention is valuable.

A bad example

Everything important lives in someone's head or an unminuted meeting. New people drain senior colleagues for months, and decisions get relitigated because nobody remembers the why.

A human-centred example

Decisions, the reasoning behind them, and how-things-work all get written somewhere findable, so people can act without chasing the one person who knows.

The result

Less bottlenecking, faster onboarding, and an organisation that remembers its own reasoning instead of going in circles.

Lead by serving

What it is

Make the leader's job the growth and effectiveness of their people, not their own status or vision. Clear blockers, hold the meaning, grow people, guard the boundaries, notice the system.

The research

'Servant leadership' was coined by Greenleaf in 1970 and backed by five decades of research. Van Dierendonck's (2011) meta-analysis links it to more psychological safety, engagement, meaning, creativity and trust, and to less turnover, burnout and counterproductive behaviour. The real work isn't directing every move, it's creating the conditions for good work.

A bad example

A founder leads by being the cleverest person in every room, hoarding decisions and credit and measuring their worth by control. The best people feel blocked and leave first.

A human-centred example

A leader spends the week clearing blockers, getting the team what it needs, naming why the work matters, growing people, and catching early wobbles. They treat their people as peers.

The result

More engagement, trust and creativity, and far less burnout and turnover, because people can feel their leader is in their corner.

Push decisions to where the information is

What it is

Let the person doing the work make the operational calls within clear guardrails. Reserve tactical calls for small expert groups and strategy for leadership, with real input from whoever it affects.

The research

Centralised decision-making is the classic small-company trap, especially in founder-led firms (founder dependency: a systems problem dressed as a management style). Research on decision architecture shows decisions are best made as close to the relevant information as possible, which is faster and respects competence and autonomy. Some teams use the advice process: anyone can decide, but only after seeking advice from those affected and those who know the area.

A bad example

Every small call needs the founder's sign-off. Work piles up waiting, people stop using judgment because nobody wants it, and the company moves at the speed of one tired inbox.

A human-centred example

Clear guardrails are set, then the doer decides. Bigger calls use the advice process: decide, but seek advice first and write down the reasoning.

The result

Faster decisions, fewer bottlenecks, and people who feel trusted and capable, so the company scales its judgment instead of funnelling everything through one person.

Onboard like it matters

What it is

Design the first 90 days on purpose around four things: a feel for the culture, role clarity, confidence, and a sense of belonging.

The research

Bauer's research for the SHRM Foundation (2010), with Bauer et al. (2007), found those four outcomes are largely set in the first 90 days. Get them right and newcomers get productive faster, happier, and far more likely to stay; get them wrong and you get the same spiral: confusion, isolation, sinking confidence, early exit. Most companies waste this with a laptop-and-a-checklist.

A bad example

A new hire gets a laptop, a quick tour, and 'shout if you have questions.' Three weeks in they still don't know what they own or who to ask, and they're back on the job boards.

A human-centred example

Structured check-ins through 90 days, a buddy who isn't their manager, real work early, an honest tour of the unwritten rules, and a plan for building relationships.

The result

People get good faster, feel happier, and the expensive churn of early leavers mostly disappears.

Design the work

Shaping the actual work so it fits how humans think, focus and grow.

Get roles right: clarity without rigidity

What it is

Clear enough that people know what they own, loose enough that they're openly invited to reach past it.

The research

Fuzzy roles are a documented stressor: if you can't tell what you're responsible for, you're anxious and can never feel competent. But Parker (1998) found people with high 'role breadth self-efficacy,' the belief they can contribute beyond their formal job, are more proactive, engaged and innovative. The fix is a clear core plus an explicit invitation to stretch.

A bad example

A startup runs on 'we all wear many hats,' so nobody knows who owns what. Things slip, work gets duplicated, and everyone's vaguely responsible for everything.

A human-centred example

Each person has a written core they clearly own, plus a standing invite to wander into the next-door work with support.

The result

Less anxiety, clearer ownership, more initiative. People feel competent because they know what's theirs, and engaged because they can grow past it.

Let people craft their work

What it is

Give people room to reshape the tasks, relationships and meaning of their work to fit who they are. That's job crafting.

The research

Wrzesniewski & Dutton (2001) showed job crafting happens three ways: task crafting (changing what you do), relational crafting (who you work with), and cognitive crafting (how you frame why it matters). People who craft their jobs are more engaged and find more meaning, and it costs the company almost nothing to allow.

A bad example

Roles are rigid job descriptions enforced to the letter. 'That's not your job' shuts down anyone trying to shape their work toward what energises them.

A human-centred example

Managers run check-ins that ask 'is there a way we could shape this so it fits you better?' and let people lean into the parts they're best at.

The result

People quietly redesign their work into something they're more motivated to do, which lifts engagement without a single new hire.

Async by default

What it is

Make written, asynchronous communication the default for knowledge work. Go live only when real-time dialogue earns the interruption.

The research

Written documentation gets treated as first-class: questions come with enough context to answer without a meeting, and the burden of clarity sits with the sender. Perlow (1999) showed that always-on, reply-this-second pressure is one of the most reliable predictors of cognitive overload. Async protects the long stretches of attention real thinking needs.

A bad example

Everyone's expected to reply instantly, all day. Requests arrive with no context, so people lose half an hour decoding each one, and real work only happens after hours.

A human-centred example

Questions are written clearly, answered within agreed windows rather than instantly, and live time is saved for the conversations that actually need it.

The result

Calmer days, fewer pointless pings, and the deep stretches of focus that knowledge work depends on.

Protect deep work

What it is

Treat uninterrupted, brain-heavy time as a structural necessity. Protected deep-work blocks, batched shallow work, and a hard look at meetings.

The research

Gloria Mark's research at UC Irvine (2008) found it takes about 23 minutes to get back to full focus after an interruption, because focus is a mode, not just a quantity, and switching has a real neurological cost. By one much-quoted estimate (Atlassian, an industry figure, not peer-reviewed), pointless meetings cost US businesses around $37 billion a year. Pencavel (2015) adds that past a threshold, longer hours bring steeply diminishing returns.

A bad example

Meetings sprinkled through every afternoon, notifications all day, and 'always on' treated as commitment. The actual thinking gets squeezed into the gaps, or doesn't happen.

A human-centred example

Deep-work blocks are protected by shared norms, shallow work is batched into set windows, and a meeting only gets booked when live dialogue is worth the interruption.

The result

More real thinking, fewer errors, and the complex, valuable work finally happening in working hours instead of at 10pm.

Pay fairly and recognise specifically

What it is

Fair pay, transparency where you can manage it, and recognition that names what someone did and the difference it made.

The research

Reward is one of Maslach's six burnout drivers, and fairness hits the SCARF threat response hard. The surprising bit is Deci, Koestner & Ryan's meta-analysis of 128 studies (1999): tangible, expected, performance-contingent rewards can undermine intrinsic motivation, quietly turning 'I do this because it matters' into 'I do this for the payout.' So pay well and fairly, then make recognition specific rather than hanging everything on one gameable number.

A bad example

Pay is secret and haggled case by case, recognition is the odd generic shout-out, and bonuses hang off a single metric everyone games.

A human-centred example

Pay is fair and, where possible, transparent with clear bands. Recognition names the actual contribution and its impact, and reward isn't held hostage by one number.

The result

Less quiet suspicion and comparison, a stronger sense of fairness, and people who feel seen rather than fobbed off with a generic 'great job.'

Invest in growth

What it is

Treat development as core plumbing, because when people stop growing they start leaving, in their heads first, then for real.

The research

Competence is one of SDT's three needs and it isn't static. Dweck (2006) showed a growth mindset (abilities develop through effort) changes how people handle challenge and setbacks. Ericsson et al. (1993) showed real skill comes from deliberate practice: targeted work on weak spots with immediate feedback, sustained over time. Stretch assignments grow people when they sit slightly beyond current level with support; the deep end without support is trauma, not development.

A bad example

'Development' is an unspent budget and a forgotten e-learning login. People do the same work at the same level for years, and asking for help reads as weakness.

A human-centred example

Learning is built into the week: skill-sharing, honest retros, mentoring, protected learning time, and stretch assignments with backup. 'I don't know how yet, show me?' is normal.

The result

People keep getting better and feel it happening, one of the biggest reasons good people stay, and the company compounds its own skill instead of exporting it.

Work in 90-minute cycles

What it is

Human attention runs in waves, not flat lines. Work in focused blocks of around 90 minutes, then really rest, instead of grinding straight through.

The research

Kleitman, who discovered REM sleep, also identified a 90-to-120-minute ultradian rhythm that runs all day, sliding from sharp focus into restlessness, yawning and rising errors when the body wants a break. Treating that signal as biological information rather than a willpower failure produces better output than sustained grinding.

A bad example

People are expected to power through 8-plus hours straight, fuelled by caffeine, treating the mid-cycle dip as a discipline problem to override.

A human-centred example

Work is organised into focused sprints with real breaks between, and nobody's side-eyed for stepping away to recharge when their focus dips.

The result

More output and better-quality output from the same hours, because people work with their biology instead of flogging against it.

Design for real recovery and breaks

What it is

Rest is part of the work. Protect breaks that actually restore people, and boundaries that let them switch off.

The research

Sonnentag's recovery research (2003, 2012) found rest only works with real detachment (you stop mentally running work in the background), relaxation, mastery, and some control over your time. Hunter & Wu (2015) found the most restorative breaks involve nature, positive social contact, or something freely chosen, which fits Attention Restoration Theory (Kaplan & Kaplan, 1989). Scrolling at your desk does the opposite, it keeps the depleted attention system working.

A bad example

Lunch is eaten at the desk between emails, breaks mean scrolling, and after-hours messages mean nobody ever fully detaches. People never actually recover.

A human-centred example

Real breaks are normal (a walk, a chat, fresh air), after-hours pinging is discouraged and modelled by leaders, and holiday is treated as a real right.

The result

People come back recharged instead of slowly draining, so good performance is sustainable rather than a sprint into the wall.

Energy, rhythm and rest

Working with human biology and energy instead of flogging against it.

Resist the always-on culture

What it is

Long visible hours aren't the same as good work. Protect a sane working week and judge output, not presence.

The research

Pencavel (2015), studying working hours, found output rises at a decreasing rate beyond a threshold and eventually falls, with errors climbing as hours stretch. For knowledge work the usable ceiling is lower still: most people only have a few hours of deep, focused work in them a day. 'Always on' tends to generate more visible work (email, meetings) while the real thinking quietly suffers.

A bad example

Commitment is measured by who's online latest. People perform busyness, answer messages at 10pm, and quietly burn out while looking productive.

A human-centred example

Reasonable hours are the norm, leaders model logging off, and people are judged on what they actually produce, not how present they look.

The result

Better thinking, fewer errors, and people who can keep this up for years instead of flaming out in eighteen months.

Respect chronotypes

What it is

People's brains don't all switch on at 9am. Where the work allows, let people work around their own energy peaks.

The research

Chronotype, your biologically driven peak time, varies a lot: roughly a quarter of people are true morning types, a quarter evening types, the rest in between (Roenneberg et al., 2007), and it's set by clock genes and body temperature, not laziness. Evening types forced into early starts can perform up to 30% worse, with the prefrontal cortex taking the biggest hit.

A bad example

Everyone starts at 9 regardless of whether they're a lark or an owl, so half the team is doing its hardest thinking at its worst hour.

A human-centred example

Flexible start and finish times, collaborative work parked in the midday overlap when everyone's awake, and trust for people to schedule deep work around their own peak.

The result

You get people's best hours instead of their groggiest, plus the goodwill of not fighting their biology every morning.

Test a four-day week

What it is

Trial a shorter week with no pay cut, aimed at cutting performative busywork rather than the work that actually matters.

The research

The big 4 Day Week Global UK pilot (June to December 2022, with Autonomy and Boston College, 61 companies, ~2,900 people) is the cleanest evidence: staff turnover fell 57%, 71% of people reported less burnout, sick days dropped 65%, and revenue held broadly flat. Afterwards, 56 of the 61 companies kept it. The mechanism is intentionality: less time forces teams to bin the busywork and protect what counts.

A bad example

Everyone's on a rigid 5-day, 9-to-5, commitment is measured by hours looking busy online, and any chat about working time is treated as a threat to productivity.

A human-centred example

A proper four-day pilot, with meetings and workflows redesigned to cut waste, outcomes measured instead of hours, and equivalent flexibility offered where four days won't fit a role.

The result

Way less burnout and turnover with output holding steady. People get a life back and bring sharper focus to the days they do work.

Structure, space and the wider world

The structures, spaces and wider world the work sits inside.

Design the operating system on purpose

What it is

Your structure, processes and decision rights are a design choice, even when nobody chose them. Design them on purpose, and fix root causes instead of symptoms.

The research

In most companies, 'operations' is the accumulated residue of decisions made without thinking, habit that quietly became load-bearing. ISO 27500's systems principle: an underperforming team is usually a symptom of something upstream (fuzzy priorities, clashing incentives, a feedback loop that loops back nowhere). Patch the symptom and it returns; fix the system and it doesn't.

A bad example

Something keeps going wrong, so the fix is always a new policy bolted onto the symptom, while the real upstream cause keeps churning out the same problem.

A human-centred example

Structure gets checked against one honest question, does this serve the people inside it or drain them, and when something repeatedly breaks, someone keeps asking why until they reach the system, then fixes that.

The result

Problems get solved at the root instead of recurring, and the company stops drowning in policies that treat symptoms.

Stay small on purpose

What it is

Small companies have a real structural edge: proximity. Use it for speed and closeness instead of cosplaying as a big corporation.

The research

Small organisations (roughly 5 to 50 people) have short feedback loops, fast adaptation, and decision-makers who are actually reachable. Research on structure consistently shows smaller setups win on cohesion, psychological safety and speed of learning (Hackman, 2002). Most waste the advantage by importing big-company hierarchies and approval chains without the scale that would justify them.

A bad example

A 25-person company runs the org chart, approval layers and policy stack of a 2,000-person corporation. It gets all the bureaucracy and none of the scale benefits.

A human-centred example

The company leans into being small: flat, fast, relationship-based, decisions close to the work, and structure that fits its actual size.

The result

Speed and cohesion a big company can't match, which is the whole point of being small in the first place.

Keep teams small

What it is

The ideal knowledge-work team is 4 to 6 people. If two pizzas can't feed it, it's probably too big.

The research

Hackman's research found team effectiveness is mostly about structure, not individual talent, and pointed to 4 to 6 as the sweet spot. The maths is unforgiving: communication links grow exponentially with size (5 people is 10 links, 10 is 45), psychological safety gets hard above 8 to 10, and social loafing creeps in above 6 to 8. Bezos called it the two-pizza rule.

A bad example

Teams balloon to 12 'so everyone's included.' Meetings sprawl, accountability blurs, and a few people quietly coast while the links multiply.

A human-centred example

Work is organised into small teams of 4 to 6 with clear ownership, and big efforts get split into small teams rather than one giant one.

The result

Tighter communication, clearer accountability and higher safety, so small teams consistently outrun the bloated ones.

Keep a predictable rhythm

What it is

Give the week a clear, shared shape: when decisions get made, when you collaborate, when deep work is protected. Predictable time lowers cognitive load.

The research

One of the steadier findings in organisational research is that temporal predictability reduces cognitive load and enables deeper work (Newport, 2016; Sonnentag, 2003). It doesn't mean identical schedules for everyone, just a shared skeleton everyone understands, so people aren't constantly bracing for the next surprise meeting or scramble.

A bad example

Meetings land at random, priorities lurch week to week, and 'urgent' can detonate at any moment, so nobody can plan a focused stretch with any confidence.

A human-centred example

A clear weekly cadence everyone knows: set windows for collaboration, set windows for deep work, and a steady rhythm for when decisions happen.

The result

Calmer, more focused weeks, because people can plan their best work around a structure they can actually trust.

Design the physical and digital workspace

What it is

The space shapes behaviour before any policy does. Give people light, quiet, sane temperature and some control over their patch, and keep the digital tools minimal.

The research

Bernstein & Turban's 2018 study (Royal Society) found that when two Fortune 500 firms moved to open-plan, face-to-face interaction dropped by roughly 70%; people withdrew into email and headphones. We need some territorial control over our space; remove it and the SCARF threat response kicks in. Natural light, plants and a view lower stress, and productivity peaks in a narrow band around 21 to 22C (Helsinki University of Technology and Lawrence Berkeley, 2006).

A bad example

Everyone's packed onto a noisy open-plan floor with no control over light, temperature or desk, and the 'wellbeing' answer is a pool table in the corner.

A human-centred example

Quiet zones, natural light, plants, a sane temperature, some personal control over your setup, and a minimal, well-chosen set of digital tools.

The result

Lower stress and sharper thinking straight from the environment, before a single policy or pep talk.

Office or remote, by choice

What it is

Where people work is a design question, not a mandate. Let people choose office or remote where the work allows, and design around the real trade-offs.

The research

Bloom's Stanford randomised trial at Ctrip (2015) found home workers were about 13% more productive, and later work shows people value the flexibility at roughly 8% of salary. Fully remote has real risks too (isolation, weaker informal learning, proximity bias at promotion time), so the job is to design around them, not to ban remote or ignore the downsides.

A bad example

Remote is banned on principle, or technically allowed but quietly held against you at promotion time. People comply resentfully and the best ones leave for somewhere flexible.

A human-centred example

People choose office or remote based on the work, the downsides of remote are actively designed around, and roles that need presence get equivalent flexibility elsewhere.

The result

A perk people value as much as real money, better productivity, and access to talent a rigid in-office mandate would lose.

Be a good citizen

What it is

See the company as part of something bigger than its own revenue, and build social and environmental responsibility into how decisions actually get made.

The research

ISO 27500's social-responsibility principle: a company's decisions ripple out to its community, supply chain, environment and people it'll never employ. Companies that act as if they live in a bubble tend to find the bubble works both ways, in talent, trust and reputation. In practice it looks like respecting cultural differences, giving people real time to volunteer, and offering payroll giving or donation matching.

A bad example

People, customers and the planet get treated as inputs to squeeze, the wider footprint is ignored, and a token CSR page goes on the website for show.

A human-centred example

Responsibility is built into how decisions get made, with cultural differences respected, volunteering time offered, and payroll giving or matching as standard.

The result

A reputation and a pull on talent that compound over time, because people are proud to work somewhere whose impact they can actually defend.

Anchor the company in purpose & accountability

What it is

Be clear about why the company exists beyond profit, and build in real accountability to the people your decisions affect (workers, customers, community), not just shareholders.

The research

This is the worker-relevant heart of B Corp's Governance area: a clear mission, ethical conduct, transparency, and real accountability to stakeholders, written into how the company actually governs itself rather than a values page nobody reads. The Fair Work Framework (Scotland, 2016) frames respect and voice as a two-way deal between employer and worker, which only holds if the company is on the hook for keeping its side. Companies that hard-wire purpose and stakeholder accountability (through their structure, their decisions, and what they choose to measure) tend to keep their values intact under pressure, exactly when it's easiest to quietly drop them.

A bad example

There's a lovely mission statement on the wall, but the moment revenue dips the values are first out the window: people get squeezed, promises get broken, and nobody is actually accountable for the gap between what's said and what's done.

A human-centred example

Purpose is specific and lived, big decisions get checked against it, and the company holds itself accountable to workers, customers and community, measuring how it's doing and owning it honestly when it falls short.

The result

Trust that survives the hard times, because people can see the company means what it says, plus a real reason for values-driven talent and customers to stick around.

Sources include Gallup, ISO 27500, the Fair Work Framework, B Corp, Deci & Ryan, Edmondson, Maslach, Rock, Hackman, Bernstein & Turban, Bloom and others.

What it feels like inside one of these?

• People stop performing busyness, because they're judged on outcomes and growth, not on how visibly present they look.

• Disagreement is healthy. People push back on ideas comfortably and offer their own all the time.

• Attention isn't fractured and reactive. There's real room for the deep thinking where problems actually get solved, not just managed.

• People get treated as people, not role-holders. Their strengths are known and used, their struggles known and supported, and the work flexes to fit the human.

• Bad news travels early, because everyone knows early information beats late information every time.

• People become real fans of the place, because the work means something and the whole system clearly cares about who they are.

  
  So let's change the world by making companies great places to work. One small company at a time.

Consciously

Designed

© 2026 Consciously Designed