The Human-Centred Organisation
30+ research-backed ways to design a company people actually want to work for.
In 2025, just 20% of people worldwide felt engaged at work. Four out of five were basically checked out, and that costs the global economy around $10 trillion a year. It's been sliding two years straight, and even the managers are going under (27% down to 22%).
How did we end up here? Well, most companies upgraded everything (new tech, new tools, AI) but left the actual people running on factory settings from the early 1900s. This is my attempt to help fix that by using real research insights.
What every human needs
The basics. Before anything else, these need to be in place first.
The three core needs
What it is: Psychologists have found three things every human needs to feel motivated. Autonomy - a feeling like you have a real say ("this was my call"). Competence - a feeling of being capable and growing in expertise ("I'm getting better, and my skills actually get used"). Relatedness - being properly connected to the people around you (real connection, not mandatory fun). A company's job is to set up the work so people get all three, regularly.
The research: This comes from self-determination theory by Deci and Ryan, one of the most tested theories of motivation we have. When all three needs are met, people get motivated from the inside, and they become more creative and more resilient. And when they're not, people disengage, burn out, or switch to autopilot.
A bad example: A company that micromanages everyone, hands out repetitive work with zero feedback, and runs surface-level team banter while nobody really cares or trusts anybody. That's all three needs starved at once. Impressive, in the worst possible way.
A human-centred approach: Agree the outcome with your team, then let people choose their own route to get there. Pitch work just above each person's current level and put support right next to it (a mentor, a regular check-in, a go-to person). And build connection through real collaboration, like pairing up on projects, rather than compulsory socials.
The result: People w ho want to do the work, not people who have to. You can't fake that kind of motivation, but you can absolutely design for it.
Resources buffer demands
What it is: Job demands must match the available resources. Demands are everything that takes effort: workload, deadlines, unclear expectations. Resources are everything that helps you cope: support, feedback, freedom, and knowing why the work is important. How hard a job feels has less to do with how much there is, and more to do with whether those two sides are in balance.
The research: This is the Job Demands-Resources model from Bakker and Demerouti. Demands drain your energy, and resources top it back up. High demands plus plenty of resources can actually feel energising (hello, flow state). High demands plus not enough resources can lead you to burnout.
A bad example: Leadership keeps piling on work and tightening deadlines, while cutting the feedback, freedom and context people need to cope. Demands up, resources down. And then everyone acts surprised when people find it harder and harder to cope.
A human-centred approach: Whenever you add demands, add resources to match. Before a busy push, get crystal clear on the top priorities, give people more say in how they do the work, speed up feedback, and explain why this push matters. Never raise the workload without asking what support needs to go up with it.
The result: Busy seasons that people get through with their energy (and their goodwill) still intact.
Burnout isn't personal
What it is: Burnout isn't a sign that someone is weak or not resilient enough. Burnout happens from the mismatch between a person and the way their work is set up.
The research: Christina Maslach has spent over 40 years studying burnout. She defines it by three signs: exhaustion, cynicism, and the feeling that nothing you do makes a difference. Her work with Michael Leiter found six causes, and every single one lives in the workplace, not the person: too much work, too little control, not enough reward, a broken sense of community, unfairness, and a clash of values.
A bad example: A team is visibly exhausted, so the company's big answer is a workshop on resilience and a free meditation app. (Breathing exercises won't fix a workload problem even if we wish it did)
A human-centred approach: Treat workload, fairness and recognition as management issues. You can use Maslach's six areas to ask your team which one is biting hardest (workload, control, reward, community, fairness or values) and then do what you can to fix that part of the system before any other intervention. An anonymous pulse survey works well here.
The result: You fix the thing that's actually causing issues for your people.
The brain treats social threat like danger
What it is: When something threatens our standing, sense of certainty, control, belonging, or sense of fairness, our brain can react in almost the same way as to physical danger. And a stressed brain doesn't think clearly. A good workplace is designed to keep people out of that threat mode.
The research: David Rock's SCARF model names the five social triggers: Status, Certainty, Autonomy, Relatedness, and Fairness. It's a model built on social neuroscience. Under stress, the parts of the brain we use for reasoning, creativity, and long-term planning work less well, and people get more reactive and narrow. It's just biology.
A bad example: Think surprise restructures, public telling-offs, favouritism, and goalposts that keep moving. This is when people spend their days in a threat mode, unable to think straight.
A human-centred approach: Give notice and an explanation for every change, keep feedback private and kind, expectations stable, and make fairness visible (e.g., by sharing how decisions like pay and promotions get made). Before any big announcement, you can run it through the five SCARF questions: could this threaten anyone's status, certainty, autonomy, relatedness, or sense of fairness? And if yes, how can you soften that?
The result: People can do their best thinking, because they're not wasting their energy waiting for the next surprise.
People need a real 'why'
What it is: People work much better when they can see why their work matters and who it helps. This one's about connecting everyday tasks to the bigger picture. A sense of meaning is actually one of the strongest performance drivers.
The research: Nietzsche wrote that someone with a "why" can bear almost any "how", and Viktor Frankl made the line famous. In Hackman and Oldham's job characteristics model, task significance (seeing how your work affects other people) is one of five core features of a motivating job. People also need to actually see the effect of their work, which is why feedback loops are essential, not a nice extra.
A bad example: People get handed tasks with no view of the bigger picture. Priorities lurch around with no explanation, and recognition is a generic "amazing work, team!" dropped in the group chat.
A human-centred approach: Describe every role by the difference it makes, not just the tasks on the list. Show people the impact of what they deliver (customer feedback, results, real stories). And whenever priorities change, take at least a couple of minutes to explain why.
The result: Work that feels like building something, and people who are motivated to do the building.
Build for difference
Build your organisation for the varied humans you hired.
Treat differences as a strength
What it is: Workplaces are frequently designed around an imaginary "standard" employee who doesn't actually exist. So this one's about shaping roles around the real strengths, quirks and working rhythms of the people you have.
The research: ISO 27500 (2016), the international standard for human-centred organisations, puts this first on its list of principles: individual differences should be treated as a strength. Yet a lot of workplaces are built for one default profile (thinks out loud, responds in real time, copes fine with open-plan offices, happy working in eight-hour blocks). Plenty of people don't fit that "ideal", and that's completely fine. Designing for the real range of people lets everyone do their best work.
A bad example: There's one mandatory way to work for everyone: same hours, same desk, same "pitch it live in the meeting" format. The people who don't fit underperform, or simply eventually leave.
A human-centred approach: Ask each person how they work best (out loud or on paper, mornings or afternoons, live or written) and shape their role around it as much as possible. You should also offer more than one way to contribute: live sessions for the out-loud thinkers, and 24 hours to reply for the deep thinkers.
The result: You get people's best work and keep them comfortable so they don't feel that they need to fight against their nature all the time.
Make usability and accessibility real goals
What it is: Usability means a tool or process is easy to use. Accessibility means it works for everyone, including disabled people and people with different needs. This one's about checking both before you roll out any new internal tool, process or policy, and treating them as must-haves, not nice-to-haves.
The research: ISO 27500 names usability and accessibility as real business goals, not afterthoughts saved for customers. A process that needs a PhD to navigate, or a tool nobody tested with the people who'll actually use it, will tax everyone, every single day.
A bad example: A new system gets bought at the top and dropped on the team. It's clunky, half of it doesn't work with a screen reader, and it adds 20 minutes to everyone's day just to navigate, and everyone is forced to use it.
A human-centred approach: Before you roll out any tool, process or policy, test it with the people who'll actually use it. Ask them things like: does this make your work easier or harder? Fix the friction they find, and check it works with assistive technology and for different needs before it goes live.
The result: Tools and processes that give people time back instead of wasting it.
Real inclusion is belonging plus uniqueness
What it is: Inclusion isn't treating everyone exactly the same, but two things happening at once: people feel they belong, and the things that make them different are valued, not ironed out.
The research: Shore and colleagues' research defines inclusion as belonging plus uniqueness. Belonging without uniqueness is just assimilation, because everyone conforms to the dominant group. For example, the person with ADHD hides how they work, and the introvert performs being an extrovert. It can feel like suppression.
A bad example: A company that says "we treat everyone the same," but in practice it just means everyone has to behave like the dominant group to fit in.
A human-centred approach: Say out loud that difference is welcome and then back it up. Spot and drop the unwritten rules that reward one "right" way to be. In discussions, ask for the perspective that hasn't been heard yet, so difference becomes a resource rather than something people hide.
The result: People stop spending energy on fitting in and can focus on doing their jobs. You also get the benefit of diverse thinking.
Neurodiversity as design, not accommodation
What it is: Neurodiversity is the idea that human brains naturally work in different ways (think ADHD, autism, dyslexia, dyspraxia and more). Instead of building one system and making exceptions later, this one's about designing for different brains from the very start.
The research: Organisational psychologist Nancy Doyle estimates that around 15 to 20% of people are neurodivergent in some meaningful way, often with real strengths in things like pattern recognition, hyperfocus and creative, divergent thinking. Teams with more variety in how people think were found to solve new, complex problems faster.
A bad example: There's one standard system, and neurodivergent people have to ask for exceptions just to cope with it. Which eventually makes the company view them as a problem they are being kind to put up with.
A human-centred approach: Make flexibility a default, not an exception. Offer several ways to communicate (written, live, async), protect solo focus time, and allow flexible routes to the same result. And if someone has to ask for an adjustment just to cope, take that as a sign that the whole system might need redesigning.
The result: You get different thinking, innovative ways to solve problems, and people who feel like actual members of the team.
Trust, safety and communication
How people relate, decide, and lead once you swap control for trust.
Build psychological safety on purpose
What it is: Psychological safety is a shared feeling in a team that you won't be punished or embarrassed for speaking up. It means you can ask the "dumb" question, admit a mistake, challenge an idea, or share a half-formed thought without being penalised.
The research: Amy Edmondson coined the team version of this idea, and her early hospital study showed that the best-run units reported more errors, not fewer, because people felt safe enough to bring them up. Her later study then showed that psychological safety drives team learning. And later, Google's Project Aristotle found it was the single biggest factor in what made their teams effective, ahead of who was actually on the team. You build it by leaders going first (admitting uncertainty, owning their mistakes), framing work as learning, and reacting well the very first time someone brings bad news. That first reaction sets the tone for everything after it.
A bad example: The first time someone owns up to a mistake, the manager makes an example of them. From then on, nobody shares problems until they explode, and nobody challenges the senior person's ideas and opinions.
A human-centred approach: Share your own uncertainty and recent mistakes out loud, so that others would feel safe to do that, too. And decide in advance how you'll react to bad news, mistakes, and accidents, so that your first response is always something similar to "thanks for flagging this early."
The result: Problems are shared early, while they can still be fixed, and bad ideas get challenged and improved.
Make disagreement and feedback normal
What it is: Healthy teams don't avoid conflict, they argue well. This one's about everyday habits where everyone gets a say, mistakes become lessons, and feedback flows in every direction.
The research: Woolley and colleagues found that one of the clearest signs of a collectively smart team is balanced turn-taking: no single voice hogs the conversation. Teams also learn more when they look back at failures to understand them, rather than blaming someone. And feedback works best when it's frequent, honest, and two-way, part of the normal rhythm rather than a thing that happens once-a-year.
A bad example: In all meetings, only the two loudest voices can be heard. Failures and mistakes trigger a blame hunt, and feedback only ever shows up in the annual review.
A human-centred approach: Share speaking time on purpose. Invite quieter people in (never force them), and try going round the room or collecting written thoughts before the discussion starts. Run a no-blame debrief after every failed project (never attack a person; discuss the situation and events). And make feedback small, frequent and two-way, including upward to leaders.
The result: Better decisions due to different perspectives and a team that keeps getting smarter instead of repeating the same mistakes.
Default to transparency
What it is: Transparency means people can see the information that affects them, without having to dig for it. This one's about making openness the default: meeting notes, the reasoning behind decisions, the roadmap, even the basic finances (unless there's a good reason not to).
The research: ISO 27500 lists being open and trustworthy as a core principle, and that means real openness, not "pretend-transparency" where the good bits get shared and the rest stays hidden. When people can see all the information, they make better calls on their own and catch mistakes earlier.
A bad example: Slick all-hands meetings, but leadership controls what gets said. Decisions appear out of nowhere, the finances are a secret, and bad news arrives late and somehow beautifully wrapped.
A human-centred approach: Make sharing the default and secrecy the exception. Write up the reasoning behind decisions, share meeting notes openly, and show people the roadmap and the basic money picture. And share bad news as quickly as you'd share good news.
The result: More trust amongst people, more independence, and more people willing to speak up when they need to.
Write important things down
What it is: I know, documentation sounds boring. But writing down decisions, processes, and feedback means nobody has to rely on someone's memory, or on having been in the right meeting.
The research: When decisions are written down with their reasoning (not just the conclusion), people who weren't in the room can understand them and act. When processes are written down, new starters can find their feet without exhausting your most experienced people with their questions. When feedback is written down, it can be revisited instead of fading into a fuzzy memory.
A bad example: Everything lives in someone's head, or everything that was said in a meeting has now been forgotten. New people keep coming to senior people with questions, and old decisions keep getting rediscussed all over again because nobody remembers why they were made in the first place.
A human-centred approach: Pick one easy-to-find home for decisions, processes, and how things work (like a shared wiki or Notion space). Record decisions with their reasoning, not just the outcome. And make writing it down part of the thing, not something to be done later (and forgotten).
The result: Fewer bottlenecks, faster onboarding, and people who always know and understand what's exactly happening.
Lead by serving
What it is: Instead of being the most important person in the room, the leader's job is to help their people grow and do their best work. That means clearing blockers, keeping the purpose clear, developing people, protecting the team's boundaries, and keeping an eye on the company as a whole.
The research: Van Dierendonck's research review linked servant leadership to trust, fairness, better job attitudes, and performance. A bigger review of 285 studies later mapped how it connects to a wide range of outcomes for people and teams. It turns out that the real job of a leader isn't directing everyone, but creating the conditions for good work.
A bad example: A founder leads by being the most important and smartest person in every room. They hoard decisions and credit, and measure their worth by how much they control.
A human-centred approach: Spend your week clearing blockers, getting the team what it needs, reminding everyone why their work is important, and growing people. Ask your team what's in their way regularly to find ways to help them out. Use 1:1s to catch early wobbles, and treat your people as peers.
The result: More trust, better work, and people who enjoy working with you.
Push decisions to where the information is
What it is: The person closest to the work usually knows the most about it, so they should make the everyday decisions related to it (within clear limits). Bigger decisions go to small groups who know the area, and big-picture strategy sits with leadership, with real input from whoever it affects.
The research: Centralised decision-making (everything goes through the top) is a common issue in small, founder-led businesses. Decisions work best when they're made as close as possible to the people with the relevant information, which is not only faster but also respects people's skills and judgement. Some teams use the advice process: anyone can make a decision, but only after asking for advice from the people it affects and the people who know the area best.
A bad example: Every tiny call needs the founder's sign-off. Work piles up waiting, and people stop using their judgement because nobody wants it anyway.
A human-centred approach: Set clear limits for each role, and then let the person doing the work make the calls inside them. For bigger decisions, use the advice process: whoever decides asks the people affected and the people with expertise for input, then writes down their reasoning. Keep an eye on how many decisions still wait on the founder, and try to reduce that number.
The result: Faster decisions, fewer bottlenecks, and people who feel trusted and capable.
Onboard new people properly
What it is: Onboarding is everything that happens when someone new joins. This one's about designing a new person's first few months on purpose, around four things they need: understanding the culture, knowing exactly what their role is, feeling confident, and feeling like they belong.
The research: Bauer and colleagues' meta-analysis found that role clarity, confidence and feeling accepted shape how a new hire's experience turns out, and Talya Bauer's SHRM Foundation guide adds understanding the culture as the fourth. Get them right and newcomers get productive faster, feel happier, and are far more likely to stay. Getting them wrong can lead to confusion, isolation, sinking confidence, and, of course, an early exit.
A bad example: A new hire gets a laptop, a quick tour, and a cheerful "shout if you have any questions!" Three weeks in and they still don't know what they're responsible for or who to ask, and they're already considering leaving.
A human-centred approach: Plan the first 90 days around four things: culture, role clarity, confidence and belonging. Schedule structured check-ins, pair the new person with a buddy who isn't their manager, give them real work early, walk them through all the unwritten rules, and help them map out who to build relationships with.
The result: People get good faster, feel happier, and want to stay longer.
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: A good role does two things at once: it's clear enough that people know exactly what they own, and loose enough that they're openly invited to go beyond it.
The research: Fuzzy roles are a well-documented cause of stress. If a person can't tell what they're responsible for, they feel anxious and never feel good at their job. But Sharon Parker's research showed that people with high role breadth self-efficacy (the belief that they can contribute beyond their formal job) tend to be more proactive at work. So 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, of course, start slipping through the cracks, work gets done twice and sometimes by different people at the same time, and everyone is vaguely kind of responsible for everything (which means nobody is).
A human-centred approach: Write down each person's core role and the things they clearly own. Then add a standing invitation to stretch into nearby work, with support. Review both every few months, because roles drift as the company grows and/or changes.
The result: Less anxiety, clearer ownership, and more engagement and initiative from people.
Let people craft their work
What it is: Job crafting is when people reshape their own job so it fits them better. That can mean changing which tasks they do, who they work with, or how they think about their work.
The research: Wrzesniewski and Dutton showed that job crafting happens in three ways: task crafting (changing what you do), relational crafting (changing who you work with), and cognitive crafting (changing how you see the purpose of your work). A meta-analysis of 122 samples also found that people who craft their jobs tend to be more engaged at work.
A bad example: Roles are very rigid job descriptions enforced to the letter, and "that's not your job" shuts down anyone trying to steer their work toward what energises them.
A human-centred approach: Ask one additional question in your regular check-ins: "Is there a way we could shape this so it fits you better?" If they say there is, let people lean into the tasks, relationships and meaning that energise them, as long as the core work still gets done.
The result: People feel more engaged and motivated because they can redesign their work into something they're more excited to do.
Async by default
What it is: Asynchronous (or async) communication means people don't have to be online at the same time. Think written updates, comments and messages people answer when they're ready, instead of instant replies and back-to-back calls. This one's about making that the default for knowledge work, and only going live when a real-time conversation is really necessary
The research: Async works when writing is treated as a proper way to work: questions come with enough context to answer without a meeting, and it's the sender's job to be clear. Leslie Perlow studied software engineers and found that a culture of constant interruptions left them with too little uninterrupted time to do their actual work. Async can protect the long stretches of attention that are needed for real thinking.
A bad example: Everyone's expected to reply instantly, all day long. Requests arrive with no context and people lose half an hour decoding them. Due to calls and meetings, real work only happens after hours.
A human-centred approach: Make written, async communication the default. Agree response windows as a team (within one working day, for example) instead of expecting instant replies. Ask people to include enough context in every request to answer it without a meeting, and save live time for the conversations that really need it.
The result: Calmer, more focused days for everyone, with fewer pointless pings.
Protect deep work
What it is: Deep work is the uninterrupted, brain-heavy kind of work: think solving a hard problem, building, or writing something complex. It's about creating blocks for focus and deep work, with small tasks batched together. And, of course, reducing unnecessary calls and meetings.
The research: Gloria Mark's research at UC Irvine found that people took on average around 23 minutes to get back to an interrupted task. Her 2008 study also found that interrupted people make up for it by working faster, but with more stress and frustration. Meetings are a big part of the problem by the way: in a survey of 182 senior managers, 71% said their meetings were unproductive and 64% said meetings came at the expense of deep thinking. And John Pencavel, studying munitions workers in the First World War, found that past about 50 hours a week, extra hours add very little extra output.
A bad example: Meetings sprinkled throughout the day, notifications pinging all over the place, and being "always on" worn like a badge of commitment. The actual work gets squeezed into the mini gaps, after work, or doesn't happen at all.
A human-centred approach: Protect focus blocks with shared team agreements (no-meeting mornings are a great place to start). Batch small tasks like email and admin into set windows. And before booking any meeting, ask yourself whether a live conversation is really worth the interruption.
The result: More real thinking, fewer mistakes, and the complex real work actually happening during work hours, not after.
Pay fairly and recognise specifically
What it is: Two things here. First, fair pay, with as much openness about pay as you can manage. Second, specific recognition: instead of a vague "great job," naming exactly what someone did and the difference it made.
The research: Not enough reward is one of Maslach's six causes of burnout, and unfairness sets off the SCARF threat response. Deci, Koestner and Ryan's analysis of 128 studies also showed that rewards that are tangible, expected, and tied to performance can actually undermine people's inner motivation, because they start to feel that they do something only because they get rewarded for it, not because they actually want it. So the answer is to pay well and fairly, then make recognition specific, rather than rewarding people with tangible things.
A bad example: Pay is secret and negotiated case by case. Recognition is the odd shout-out in passing, and bonuses depend on a single metric that everyone knows how to game.
A human-centred approach: Pay fairly and, where you can, openly, with clear pay bands. Make recognition specific: name what the person did and the difference it made. And avoid tying rewards to a single number that's easy to game.
The result: Less comparison and a stronger sense of fairness amongst everybody.
Invest in growth
What it is: This one's about treating learning and development as a core part of the company's way of working, not a perk.
The research: Competence is one of the three core needs from self-determination theory. Carol Dweck argued that a growth mindset (believing your abilities can develop through effort) changes how people handle challenges and setbacks. And even though later meta-analyses found the real-world effect is smaller than the hype suggested, it isn't zero. Ericsson and colleagues found that a big part of real skill comes from deliberate practice: focused work on your weak spots, with quick feedback, kept up over time (later research shows practice explains less than they first thought, but it still helps). Stretch assignments grow people when they're just beyond their current level and come with support, because throwing someone in the deep end with no support isn't helping - it just makes people stressed.
A bad example: "Development" means an unspent training budget and a long-forgotten e-learning login, or people are given stretch assignments with no support, expected to either swim or sink.
A human-centred approach: Build learning into the working week: skill-sharing sessions, honest retrospectives, mentoring and protected learning time. Give people stretch projects with real backup, but ask if they want it first. Teach people to say "I don't know how to do this yet, can you show me?" so it becomes normal.
The result: People keep getting better and more competent, which makes them stay longer and be more engaged.
Energy, rhythm and rest
Working with human biology and energy, instead of fighting it every step of the way.
Work in 90-minute cycles
What it is: Our attention isn't a flat line that stays the same all day. It comes in waves. This one's about working in focused blocks of roughly 90 minutes, then properly resting, instead of grinding nonstop.
The research: Nathaniel Kleitman proposed that a 90- to 120-minute rhythm keeps running during the day, moving from sharp focus into restlessness, yawning, and more mistakes, because the body wants a break. The evidence for this daytime rhythm is mixed, but you can still test it by treating a dip in focus as a signal to take some rest to recharge.
A bad example: People are expected to power through eight-plus hours straight on caffeine and willpower.
A human-centred approach: Help people organise work into focused sprints of roughly 90 minutes, with real breaks in between. Make it normal to step away when focus drops, and never side-eye anyone for doing it.
The result: Better work from the same hours, more focus, and more energy.
Design for real recovery and breaks
What it is: This one's about protecting breaks that actually restore energy.
The research: Sabine Sonnentag and Charlotte Fritz found that rest works best when it includes detachment (you stop mentally running work in the background), relaxation, a sense of mastery (doing something you're good at, outside work) and some control over your own time. Hunter and Wu found that breaks restore people more when they're taken earlier in the day and spent on something they actually enjoy. Attention Restoration Theory adds that time in nature is what helps tired attention recover especially well. Scrolling at the desk is apparently not helpful, because it keeps our worn-out attention busy (so no, doomscrolling doesn't count as a proper break).
A bad example: People eat their lunch at their desks between emails and/or "breaks" mean scrolling apps.
A human-centred approach: Make real breaks normal (a walk, a chat, some fresh air), and encourage taking them earlier in the day. Discourage after-hours messages and doomscrolling during breaks. Treat holiday as a well-deserved right, and make sure work is properly covered so people can actually switch off.
The result: People come back recharged, so good performance lasts much longer.
Resist the always-on culture
What it is: This one's about protecting a decent working week and judging people on what they produce, not how present they look at work.
The research: John Pencavel, studying First World War munitions workers, found that output keeps rising with hours only up to a point. Past roughly 50 hours a week, it flattens out, so the extra hours add almost nothing. For brain-heavy work, the useful limit is probably even lower, because there are only so many hours of deep focus in a day. "Always on" cultures tend to create more visible work (emails, meetings) while the real thinking suffers.
A bad example: Commitment is measured by who's online latest. People perform busyness, answer messages at 10 pm, and burn out simply by trying to look very productive.
A human-centred approach: Make reasonable hours the norm, and have leaders visibly log off (lead by example). Judge people on what they produce, not how present they look. And if late-night messages are common, treat that as a workload or planning problem to fix, not as something to praise.
The result: Better thinking, fewer mistakes, and people who can keep this up for years.
Respect chronotypes
What it is: Our chronotype is our body's natural timing. Not every brain switches on at 9am! Where the work allows, this one's about letting people work around their own energy peaks.
The research: Till Roenneberg and colleagues found that chronotype varies a lot from person to person. Most people sit somewhere in the middle, with smaller groups of strong larks and strong owls. It's largely biological, as our genes and age play a big role. Roenneberg's team also described social jetlag: the gap between when our body wants to be awake and when our work schedule forces us to be.
A bad example: Everyone starts at 9am (or earlier!) whether they're a lark or an owl, so part of the team is doing its hardest thinking at its worst hour.
A human-centred approach: Offer flexible start and finish times where the work allows. Schedule collaborative work in the middle of the day, when everyone's awake, and trust people to plan their focus work around their own peak.
The result: You get people's best hours instead of their groggiest, plus the goodwill that comes from not fighting their biology every morning.
Test a 4-day week
What it is: A 4-day week means working four days instead of five, with no pay cut. The point isn't to cram five days of work into four, but to cut the performative busywork and keep the work that's actually important.
The research: The big UK pilot run by 4 Day Week Global with Autonomy, the University of Cambridge and Boston College is the clearest evidence so far. Staff turnover dropped 57%, 71% of people reported less burnout, sick days fell 65%, and revenue stayed broadly the same. Afterwards, 56 of the 61 companies decided to continue with it. The reason it works seems to be focus: less time forces teams to drop the busywork and focus on things that really move the needle.
A bad example: Everyone's on the same five-day-per-week schedule, commitment is measured by hours spent looking busy, and any conversation about working time is treated as a real threat to productivity.
A human-centred approach: Run a proper pilot to see if a 4-day work week could work for your team. First, redesign meetings and workflows to cut the waste, measure results instead of hours, and offer an equal kind of flexibility for roles where four days won't fit.
The result: Far less burnout and turnover, and a team with a sharper focus.
Structure, space and the wider world
The structures, spaces and wider world the work sits inside. Zooming out, basically.
Design the operating system on purpose
What it is: A company's operating system is how it actually runs: its structure, its processes, and who gets to decide what. Every company has one, even if nobody ever sat down and designed it on purpose. This one's about designing it intentionally.
The research: In most companies, "operations" is really a pile of habits and decisions made without that much thought. ISO 27500 asks organisations to take a whole-system approach: an underperforming team is usually a symptom of something further up the chain, like unclear priorities or clashing incentives.
A bad example: Something keeps going wrong and it's fixed with a new policy instead of trying to understand why it's happening and fixing the root cause.
A human-centred approach: Check your structure and ask whether it's helping your team or draining it. If something repeatedly goes wrong, find the root cause by asking "why" multiple times until you get to the bottom of it. Then fix that.
The result: Problems get solved at the root instead of coming back, and the company stops drowning in policies that don't solve real problems.
Stay small on purpose
What it is: Small companies have one big advantage that large ones can't buy: everyone is close to everyone else. This one's about using that closeness for speed and connection, instead of pretending to be a big corporation.
The research: Small organisations (roughly 5 to 50 people) have short feedback loops, can adapt quickly, and decision-makers are still accessible. The common mistake is importing big-company hierarchies and approval chains, without the scale that would justify them. This is how you end up with the bureaucracy of a corporation and the resources of a startup.
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 benefits of being big.
A human-centred approach: Lean into being small. Keep things flat, fast, and built on relationships. Make decisions close to the work, and only add structure when your actual size needs it.
The result: Speed and closeness a big company can't match.
Keep teams small
What it is: The best size for a knowledge-work team is small, roughly 4 to 6 people.
The research: Richard Hackman's research on teams found that how well a team performs depends more on how it's set up than on the individual talent in it, and he pointed to small teams as the sweet spot. The thing is that the number of communication links grows much faster than the number of people: five people have 10 links between them, and ten people have 45. Bigger groups also make it easier for some people to coast (psychologists call this social loafing). Jeff Bezos called it the two-pizza rule at Amazon.
A bad example: Teams contain 12 "so everyone's included." Meetings sprawl, it gets unclear who's responsible for what, and a few people coast while the links multiply.
A human-centred approach: Organise work into small teams of 4 to 6 with clear ownership. Split big projects across several small teams rather than one giant one. And if a team needs more than two pizzas, it's time to split it.
The result: Tighter communication, clearer responsibility, and people feel safer to speak up.
Keep a predictable rhythm
What it is: This one's about giving the working week a clear shape where everyone knows what to expect. They know when they'll get to collaborate, when they'll have meetings about something, and when they'll be able to have focused time.
The research: In Deep Work, Cal Newport argues that focused work needs protected, predictable time, and Sabine Sonnentag's recovery research shows that people need space to switch off and recover. A predictable rhythm supports both. It doesn't mean that you need to introduce identical schedules for everyone, but a clear, shared idea about how people can expect their weeks to look.
A bad example: Meeting invitations arrive at random, priorities change from week to week, and "urgent" tasks appear out of nowhere. Nobody can plan a focused week because they know that everything can change at any moment.
A human-centred approach: Agree a clear weekly rhythm that everyone knows: set times for collaboration, set times for focus work, and a known pattern for when meetings happen.
The result: Calmer, more predictable and focused weeks.
Design the physical and digital workspace
What it is: Your workspace (both the office and the digital tools you use every day) shapes how people behave too. This one's about giving people light, quiet, a comfortable temperature, and some control over their own space, and keeping the digital tools simple.
The research: Bernstein and Turban studied two large companies that moved to open-plan offices, and found face-to-face conversation dropped by roughly 70%. Strange, isn't it? People retreated into email and headphones instead, because they apparently they need some control over their own space, and when it's taken away, the SCARF threat response kicks in. Research from Helsinki University of Technology and Lawrence Berkeley National Laboratory also found that performance peaks at around 21 to 22°C.
A bad example: Everyone is working from a packed, noisy open-plan floor with no control over light, temperature, or desk.
A human-centred approach: Create quiet zones, make the most of natural light, add plants, and keep the temperature comfortable (around 21 to 22°C). Give people some control over their own setup. And keep your digital tools to a small, well-chosen set.
The result: Lower stress and clearer thinking.
Office or remote, by choice
What it is: This one's about letting people choose the office or remote work where the job allows, and designing around the real pros and cons of each.
The research: Nick Bloom's randomised trial at the Chinese travel company Ctrip found people working from home were about 13% more productive. Later research by Bloom and colleagues found people value the flexibility at around 8% of their salary. Fully remote work has real risks too, such as isolation, less learning from colleagues, and proximity bias (people in the office getting picked for promotions more). So the job is to design around those risks, not to ban remote work or pretend the downsides don't exist.
A bad example: Remote work is banned on principle, or technically allowed but in reality held against people. People go along with it but resent it, and the best ones leave for somewhere more flexible.
A human-centred approach: Let people choose office or remote based on the work. Actively design around the downsides of remote: isolation, less learning from colleagues, and proximity bias. Give roles that need people in person an equal kind of flexibility somewhere else.
The result: Happier, more satisfied people, better productivity, and access to talent a strict office-only rule would lose.
Be a good citizen
What it is: Being a good citizen means building social and environmental responsibility into how decisions get made.
The research: ISO 27500 lists acting in a socially responsible way as a core principle. A company's decisions ripple out to its local community, its supply chain, the environment, and the wider community. In practice, this looks like respecting cultural differences, giving people time to volunteer, and offering payroll giving or donation matching.
A bad example: People, customers, and the planet are treated as resources to use and manipulate. The wider impact is ignored, and a token "social responsibility" page goes on the website for show only.
A human-centred approach: Build responsibility into how decisions get made, respect cultural differences, offer people time to volunteer, and make payroll giving or donation matching standard.
The result: A good reputation and more people who genuinely want to join you just to be a part of whatever it is you're building.
Anchor the company in purpose and accountability
What it is: Purpose is being clear about why the company exists beyond making money. Accountability is the company answering to the people its decisions affect (workers, customers, the community), not just to shareholders.
The research: This is the worker-focused heart of B Lab's Purpose & Stakeholder Governance standard: a clear mission, ethical behaviour, openness, and real accountability to everyone affected, written into how the company runs. Scotland's Fair Work Framework describes respect and having a voice as a two-way deal between employer and worker. Companies that build purpose and accountability into their structure, their decisions, and what they choose to measure, tend to keep their values even when things get hard.
A bad example: There's a lovely mission statement on the wall, but the moment revenue dips, everyone forgets it.
A human-centred approach: Make your purpose specific and check every big decision against it. Hold yourself accountable to workers, customers and the community: measure how you're doing, share it, and own it honestly when you fall short.
The result: Trust that survives hard times, because people can see the company means what it says.
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
Helping founder-led organisations become more effective without losing their humanity.