At work
At work: fair workloads, clear messages, real appreciation
Most friction at work is not about people being difficult. It comes from jobs nobody clearly owns, messages that land harder than they were meant, and thanks that doesn’t fit. This page gathers simple, free tools for all three. It is written so a team lead or HR manager can share it with a team as it is. There is also a section for running a business together, and one for anyone who is autistic at work.
If you’re autistic at work: three things you could say. More on telling people and asking for adjustments ↓
Words you could use
Asking for it in writing: “Could you send that to me in writing, with the deadline? I take things in better that way.”
Taking a quiet break: “I need 15 minutes somewhere quiet. I’ll be back at 2:15.”
When someone says you came across as rude: “Thanks for telling me. I’m direct because I want to be clear, not unkind. If something lands badly, tell me and I’ll rephrase it.”
- Fair workloads
- Running a business together
- Team one-owner list
- Team check-in
- Messages that land
- Appreciation that counts
- Getting on as a team
- A 45-minute team session
- Better one-to-ones
- Feedback and hard talks
- ADHD and neurodiversity
- If you’re autistic at work
- Go deeper
Fair workloads
Every team runs on work that never appears on a project plan: sending the follow-up after a meeting, keeping the notes, booking the room, chasing the missing figure, remembering the deadline nobody wrote down, welcoming the new starter. This is coordination work. It keeps everything moving, and it is easy to miss for three reasons.
- It is invisible when it works. Nobody notices the reminder that went out. They only notice when it doesn’t.
- It drifts to whoever is reliable. The person who did it once becomes the person who always does it, without anyone deciding that.
- It rarely shows up in a review. Over time the person carrying it does more and gets less credit, and resentment builds quietly.
When a job belongs to “everyone,” it often ends up belonging to no one, or to the same one person every time. The fix is not to blame anyone. It is to write the recurring jobs down and give each one a single owner, with a backup for holidays and busy weeks. Fix the setup, not the person.
Running a business together
Co-founders, co-owners and partners in a small business have the same setup problem as any team, with more riding on it: the business and the friendship share one table. The work customers see (the baking, the selling, the clients) tends to get the credit. The admin that keeps the doors open (payroll, suppliers, permits, tax) is invisible until something goes wrong.
- One owner and a backup for every recurring job. Fill in the one-owner list together, then send it to each other so you both have the same list.
- Agree who owns how, not just who does it. The owner decides how their job is done. If you think it should change, bring it to them; don’t quietly redo it your way.
- A weekly check-in, ten minutes. How full was the week, one thank-you, one thing that slipped. The team check-in works just as well for two.
- Thank the admin out loud. It rarely gets noticed unless it goes wrong, so name it when it goes right.
- Equal hours aren’t the goal. Different jobs take different hours. The real question is whether the split matches what you agreed, and whether you’d both agree to it again.
Words you could use
“Can we each list everything we did this week, the admin too? I want us both to see the whole picture.”
“You own the supplier orders. If I think something should change, I’ll bring it to you instead of doing it my way.”
“Thanks for sorting the VAT return. I know it took your whole Sunday.”
“I’m the only one who knows how payroll works. Could you be my backup, so the business isn’t stuck if I’m ill?”
Money, ownership, or thinking of walking away? If a disagreement is about money, ownership or the partnership agreement itself, or you’re so tired you’ve thought about leaving the business, that is a conversation for an accountant or a lawyer, not this page. Being worn out is real; it’s worth getting proper advice before deciding anything.
Got a message from your partner that stung? Read it slowly before you answer →
Team job list: one owner per job, and a 10-minute weekly round
Team one-owner list
List the jobs that come round again and again. Give each one an owner, a backup and how often it happens. This is the team version of the site’s One owner per job worksheet.
| Recurring job | Owner | Backup | How often | Remove |
|---|
Who carries what
Private: this list is kept only in this browser, on this device. Nothing is sent anywhere, and your team can’t see it unless you print or share it yourself.
A few tips. Start with the five jobs that cause the most “I thought you were doing that.” Agree the list together, rather than handing it out. Give the jobs nobody wants a rotation, so they don’t settle on one person. And look at the list again every month or two: owners change as work changes.
Team check-in 10 minutes
Once a week, go round once. Each person says how full their week is, one thank-you, and one thing that slipped. Then name any job that needs a new owner. No debating, and nobody is rated: a full week is useful information, not a complaint. Print it, or keep it on a shared screen.
Type your team’s names in the one-owner list above, and a line for each person appears here.
Not in the same room? Each person can fill in their own line, then send the check-in back. It goes with the one-owner list, inside the link. Nothing is uploaded.
Changed something since you sent it? Send a new link: an old one won’t show the change.
Private: kept only in this browser, on this device, with the one-owner list. Nothing is sent anywhere unless you send a link yourself. “Erase what’s saved” above removes both.
Messages that land
At work, a short message carries more than its words. Pay, reviews and reputation sit underneath it, so a quick line can read as a criticism, an order or a hidden note about someone’s competence, even when it wasn’t meant that way. A little extra clarity costs a few seconds and saves a lot of second-guessing.
The Chat analyzer is a free tool for checking a message before you send it. Type the sentence (this link opens it on the work-message setting), and it shows how it may land and offers a clearer, kinder way to say it. What you type stays on your device.
Three before-and-after examples
Before “Per my last email, the figures are attached.”
After “Sending the figures again here in case the first email got buried. The totals are on page 2.”
Why: “per my last email” is often read as “you didn’t read it.” The new version gives the same information without the sting.
Before “We need to talk about your performance.”
After “Could we meet Thursday at 2 for twenty minutes? The last two client reports went out a few days late, and I’d like to work out together what would help.”
Why: a vague, heavy opener leaves someone worrying for days. Being specific about the topic, the time and the aim is kinder, not harsher.
Before “Just circling back on this.”
After “Could you send the signed contract by Friday at noon? If that date doesn’t work, let me know what would.”
Why: “circling back” hints that something is late without saying what is needed. A clear ask with a date is easier to answer.
Fact, impact, request
Elsewhere on this site, a hard message has three parts: a fact, a feeling and an ask. At work, the same shape becomes fact, impact, request.
- Fact. What happened, in words a camera could record. No labels like “careless” or “always.”
- Impact. What it meant for the work, the customer or the team. You can say how it affected you, briefly: “I was caught off guard.”
- Request. One clear, small ask, with an owner and, if it helps, a date.
For example
“The report went out on Monday without the March figures. The client asked about them on the call and I didn’t have an answer. Could we add a check of the figures to Friday’s list, and could you own that check?”
Appreciation that counts
People like to be thanked in different ways at work. One person loves public praise in the team meeting; the person at the next desk would much rather have a quiet note. Appreciation at work walks through five kinds: specific words, real attention, practical help, a small thoughtful token, and (for those who welcome it) a handshake or a high-five.
An honest word about the evidence: the “five languages of appreciation” idea is popular in workplaces but has been tested very little. The sturdier finding is simpler. People tend to value appreciation that is specific, timely, sincere and given in a way that fits them. So use the five as prompts for a question, not as labels for coworkers.
- Ask. “When something goes well, how do you like to be thanked: in public, or one-to-one?”
- Be specific. “Thank you for catching that error. It saved us a day.”
- Check who you’ve missed. Once a month: “Whom have I not thanked in a while?” The coordination work above is often the first thing to go unthanked.
Thanks never replaces fair pay or a fair workload. Appreciation that goes with fair treatment feels real. Appreciation used in place of it, or to avoid a harder conversation about pay, workload or boundaries, tends to feel hollow.
Bonding tips: getting on as a team
Teams that trust each other raise problems earlier and cover for each other more easily. That trust comes from small, ordinary contact, not from away-days. Nobody has to be friends with everyone, and joining in should always be optional.
- Start one meeting a week with a quick round. “One good thing and one thing on your plate.” Two minutes, and anyone can pass.
- Ask about the work behind the work. “How did you get that report together so fast?” Being curious about how someone does their job is a kind of respect.
- Eat or take a break together now and then, with options that work for everyone: a lunch at work hours, not only drinks after work, and no pressure to come.
- Welcome new people properly. Name one person they can ask anything, and introduce them to the people they will rely on.
- Remote or on different shifts? Keep a channel for non-work things, like photos of pets or lunch, and leave cameras optional.
Words you could use
“A few of us are getting lunch on Thursday. Want to come? No worries if not.”
More ideas: Bonding, how closeness grows → · Get an idea now
A 45-minute team session
An outline for a team of about three to ten people, adapted from the site’s guide for leading a group. You don’t need a facilitator. Anyone on the team can host it. Bring this page on a screen, or print the one-owner list above.
Ground rules read aloud at the start
- No one has to share. Listening is taking part, and “pass” is a full answer.
- Talk about the work, not personalities. Jobs, handoffs and messages, not who someone is.
- No one is rated. Nothing said here goes into a review, a file or a scorecard.
Opener 5 minutes
Go round the table: “Name one small thing someone on this team did recently that made your week easier.” Anyone can pass.
The one-owner list 15 minutes
Together, list the recurring jobs that keep the team running, especially the invisible ones: notes, follow-ups, onboarding, the shared inbox, the rota. For each, agree one owner and one backup. If a job has no volunteer, give it a rotation. Use the team one-owner list on a shared screen.
Messages that land 15 minutes
In pairs, each person brings one ordinary, low-stakes message: a request, a reminder, a handover. Rewrite it using fact, impact, request, or run it through the Chat analyzer. Swap and ask: “How does this land for you?” Keep examples general. Nobody brings a real complaint about a colleague.
Agreements 10 minutes
Agree two or three small things to try for the next month, such as “every meeting ends with one owner per action” or “deadlines go in the first line of the message.” Write them down and set a date to look back.
Keep it voluntary, and keep it separate from performance. This is a session about how the team works, not about how well any one person works. Never use what people say or write here to evaluate anyone. If an issue with one person comes up, take it to a private conversation, not the group.
Better one-to-ones
A regular one-to-one between a manager and a team member works best as a short, calm talk, not a status report. The site’s check-in idea fits it well.
- A set time. Same day, same time, kept. Moving it once is fine; cancelling it again and again tells someone they’re not a priority.
- One topic. Pick the one thing that matters most this week. If another comes up, write it down for next time.
- Hear it back before you answer. One person says what happened and how it landed. The other says back what they heard and asks, “Did I get that?” Solutions wait until both have been heard.
Words you could use
“What’s the one thing that would make next week easier?”
“Let me check I’ve understood: the handover from sales is arriving without the contract details, and you’re losing a day chasing them. Did I get that?”
“I don’t have an answer yet. I’ll come back to you by Wednesday.”
Talking about it: feedback and hard talks at work
At work, people avoid hard talks because of power, deadlines and being seen. So small problems go unsaid until they show up in a review, or in someone leaving. Clear, kind feedback, given early, is a kindness.
- Be specific and timely. One thing that happened this week, not a pattern from last quarter. Fact, impact, request gives it a shape.
- Ask for their side before you decide. There is often a process problem behind it.
- End with one clear ask and a check-back date.
- Managers: ask for feedback too, and thank people for it, or it stops coming.
- Hard talks in person or on a call, not in a group channel.
Words you could use
“Can I give you some feedback on the report? The numbers were great. The summary was hard for the client to follow. Could we look at it together before Friday?”
“What’s one thing I could do differently that would make your week easier?”
Check a work message first in the Chat analyzer (or open it on manager and team member). After a thread that went sideways, paste the whole thread into it. If someone at work threatens or frightens you, that is a matter for HR or a union, not better wording. More: Effective communication: feedback → · with managers →
ADHD and neurodiversity at work
People focus and take in asks in different ways. One person catches every word in a meeting; another needs it written down; someone else loses a spoken ask by the time they’re back at their desk, however much they care. That is wiring, not effort, and a few small habits help everyone, not only the people who mention it. If you’re autistic, there are words you could use just below.
- Written asks after meetings. One line per action: what, who owns it, and by when. Send it the same day, so nobody has to rely on memory.
- One ask per message. Put the deadline in the first line, and say plainly if something is urgent or can wait.
- Protect focus time. Agree blocks with no meetings and no pings, and one clear way for a real emergency to reach someone.
- Ask how people work best, not what’s wrong. “Do you prefer asks in writing or out loud?” works for everyone.
- Share how you’re wired, if you want to. The Wiring Card makes a short card about how you focus, take in asks and like feedback. Its team version, “Copy as a team snippet”, drops each person’s card into a team wiki or channel.
Disclosure is a personal choice. Nobody has to share a diagnosis, or explain why a habit helps them. Offer the helpful habits to the whole team, so nobody has to ask. If someone does tell you, keep it to yourself unless they say otherwise.
If you’re autistic at work
A lot of work friction for autistic people comes from rules nobody writes down: vague asks, noise, small talk, and being read as rude when you are being clear. You don’t owe anyone an explanation. A few plain sentences can still get you what you need.
Three things you could say, for written asks, a quiet break, and being told you came across as rude, are at the top of this page ↑.
Telling people, and asking for adjustments
- You don’t have to disclose. You can ask for what helps (written asks, a quieter desk, headphones, short breaks) without naming a diagnosis.
- Ask for one change at a time. Say what is hard, what would help, and how it helps the work: “Spoken instructions in meetings are hard for me to hold onto. A short written list afterwards would help me get things right first time.”
- Put the ask in an email to your manager or HR, and keep a copy. In many places the law asks employers to consider reasonable adjustments for disabled staff, and autism can count. HR or a local disability advice service can tell you what applies where you are.
- If you do tell someone, you choose how much. “I’m autistic. The main thing for me is clear, written asks” is enough.
- Make a short card for your manager. The Wiring Card sums up how you take in asks, focus and like feedback. Send it with one line: “This is how I work best. Happy to talk it through.”
Go deeper
- Systems and teamsThe research on clear owners, handoffs, blameless reviews and why shared jobs slip.
- Coworkers and teamsHow invisible work shows up at work, and which tools fit a team.
- Method and limitsHow every score on the site is worked out, and what it cannot tell you.
- The Wiring CardA short card about how you focus, take in asks and like feedback, to give to a manager or a team.
- Appreciation at workFive ways people like to be thanked, as a menu rather than a label.
- The Chat analyzerCheck how a message may land before you send it, with a clearer way to say it. Or paste a thread that went wrong and see where it turned.
- Upset right now?For heated moments: a pause line with a return time, a breathing pacer, and how to come back.
To share this page without decorations, use the link spreadloveandacceptance.com/work.html — it opens in work mode. Any page can open in work mode by adding ?work=1 to its address.
This page shares general ideas about how teams work. It is not legal, HR or medical advice, and it is not a tool for evaluating anyone’s performance.