Team Training · Judgement

Thirty small rules that quietly decide how a career goes.

Daniel Pink spent six decades collecting the shortcuts nobody hands you on your first day. Thirty of them, in five levels — how to decide, how to be with people, how to finish things, how to work, how to live. None of them take a course to learn. All of them take a week to start.

Codes

Levels

~25

Minutes to read

Level One — Decisions

How to choose without the drama

Most bad outcomes in a business aren't caused by bad luck. They're caused by good decisions made at the wrong speed — three weeks of agonising over something reversible, and three minutes on something permanent. These six codes fix the speed.

01 The Tuesday Test

Judge it by an ordinary Tuesday, not by its best day

Every option sells itself on its highlight: the showroom on launch night, the job with the conference abroad, the apartment with the terrace you'd use four times a year. But you don't live in the highlight — you live in the median day. Ask what 2:30 on a normal Tuesday looks like, and let that answer carry most of the weight.

Takeaway: Trading 51 good Tuesdays for one spectacular Saturday is almost always a bad trade.

★

At Mozaik: Applies to hires, suppliers and software. A supplier who dazzles at the fair but takes nine days to answer an email is a bad Tuesday every week of the year.

02 Two Doors

Reversible decisions deserve speed, not deliberation

Some decisions are one-way doors: a factory line, a long lease, a senior hire, a brand repositioning. Walk through and there's no easy way back, so take your time. Most decisions are two-way doors — trial a tool, test a display, try a supplier on one order. If it's wrong you walk back out. Spending three weeks on a three-minute reversal is not caution; it's a tax you're charging yourself.

Takeaway: Before deliberating, ask one question: can I undo this? Save the agonising for the doors that only open one way.

★

At Mozaik: Trying a new fabric on one sofa in one showroom is a two-way door. Committing a season's order to it is a one-way door. They are not the same decision and shouldn't take the same amount of time.

03 The Dissent Check

Ask what would change your mind — and find someone who disagrees

If you can't name a single piece of evidence that would make you abandon your plan, you're not analysing it, you're defending it. The fix is uncomfortable but cheap: before a big commitment, find one intelligent person who thinks it's a mistake and let them make their case properly. You don't have to agree. You do have to hear it before you sign.

Takeaway: “Nothing would change my mind” is not confidence. It's the sound of a decision that stopped being examined.

★

At Mozaik: Give the sceptic a real slot in the meeting, not a corridor conversation afterwards. If the pricing model survives Zeynep's hardest objection, it will survive a customer's.

04 The Null Option

Price the do-nothing option before you price the others

Doing nothing is not the absence of a decision — it's one of the options, with its own cost and its own upside. Some problems are being fed by the attention we give them and shrink the moment we stop. Some situations get clearer on their own in a fortnight. The useful habit is to write down what happens if you simply wait, and compare it honestly against acting.

Takeaway: Sometimes the instruction isn't “don't just stand there, do something” — it's the reverse.

★

At Mozaik: Before reorganising a team or rewriting a process, write the one-paragraph version of what happens if we leave it alone for a month. Occasionally that paragraph wins.

05 Small Bets

Make many small bets: capped downside, uncapped upside

The useful risks are the ones that could change things if they work and cost you very little if they don't. One product in one window. One new channel for one month. One article, one conference, one pilot customer. Breakthroughs rarely arrive through a single heroic leap; they turn up somewhere in a portfolio of cheap experiments, and you almost never guess in advance which one.

Takeaway: Most of what works is found, not planned. Take more shots — just make sure a miss costs you a week, not a year.

★

At Mozaik: Marketing already runs this way and it shows — it's our highest share of new customers. The same logic belongs in Retail: test a display, a bundle or a follow-up script in one store before rolling it everywhere.

06 Process vs Outcome

Grade the decision, not only the result

A careful decision can produce a terrible outcome and a reckless one can get lucky — because results are part skill and part chance. If you only ever grade outcomes, you will faithfully copy the lucky mistakes and abandon the sound methods that happened to lose. Three questions after the fact: did I use the information I actually had, did I look at real alternatives, and did I understand what could go wrong?

Takeaway: One good quarter doesn't prove the method was right, and one bad quarter doesn't prove it was wrong.

★

At Mozaik: When a deal lands or dies, review what we knew at the time rather than what we know now. Otherwise the post-mortem just rewards whoever got lucky.

Level Two — People

The part nobody trains you on

You can be excellent at the work and still lose on this level. Six codes about what people actually want from you, why relationships quietly fade, and the one case where walking away is the wise move rather than the cruel one.

07 Before You Fix It

Ask what they want: advice, help, or just company

Not every problem someone describes is a request for a solution. Sometimes they want your answer, sometimes they want your hands, and very often they just want to say it out loud to someone who won't interrupt. Jumping straight to problem-solving mode when what was needed was attention is how well-meaning people end up being experienced as dismissive.

Takeaway: Seven words prevent most of it: “do you want ideas or just to talk?”

★

At Mozaik: Especially true in a one-to-one after a lost order. The first five minutes are almost never a request for coaching.

08 Generous Reading

Assume overload before you assume malice

The blunt reply, the ignored message, the decision made without you — these read like hostility and are usually something far duller: someone with sixty unread emails, a bad night's sleep, or a calendar they've lost control of. Genuinely hostile people exist, but they are rarer than overwhelmed ones. Starting from the generous explanation costs nothing and you can always revise it when the evidence piles up.

Takeaway: Most of what feels personal at work is simply someone else's bad week reaching you sideways.

★

At Mozaik: Between departments this matters most. A late spec from Aydınlatma is usually a queue problem, not a message about how much they respect your deadline.

09 The Curiosity Test

Notice who asks you questions

Curiosity is one of the most reliable signals you have about a relationship, and it's almost free to read. Who asks how the trip went, how the project landed, how your father is doing? And — more informative — who never does, no matter how long the conversation runs? This works on friendships, on new colleagues, on suppliers and on anyone selling you something.

Takeaway: People who are interested in you ask. People who are interested in an audience don't.

★

At Mozaik: In an interview, count the candidate's questions about the work itself. It predicts more than the CV does.

10 No Ledger

Don't keep score in relationships you want to keep

I called last time. I paid for dinner. I covered for him in August. The moment generosity gets a running total it stops being generosity and becomes an invoice waiting to be issued. Good relationships even out over years, not over weeks, and any particular month will look unfair if you measure it closely enough.

Takeaway: A spreadsheet is the wrong instrument for a friendship. If you're already keeping one, that's the finding.

★

At Mozaik: Same inside a team. The colleague who tracks every favour is usually the one everyone stops asking for favours.

11 Infrastructure

Give friendship an infrastructure

“Let's get together sometime” is how people leave your life without anyone deciding anything. The alternative is structural, not emotional: a standing monthly dinner, a Saturday walk, a call every second Sunday. And when you do want to see someone, issue a real invitation with a day and a time — a specific plan is a plan, while an open-ended one is a polite goodbye spread over several years.

Takeaway: Recurring beats spontaneous. The calendar entry is doing the work that goodwill alone never manages.

★

At Mozaik: Works for working relationships too: a standing fifteen minutes with a counterpart in another department prevents more problems than any escalation process.

12 Subtraction

Remove the people who consistently diminish you

Not everyone who is difficult is toxic — difficult people are often just honest, or tired, or under pressure. The distinction is a pattern: does this person reliably leave you smaller than they found you? If so, distance is the intervention, and the rule doesn't come with a family exemption. Shared history and shared DNA are not entitlements to treat you badly.

Takeaway: Distance isn't always cruelty. Sometimes it's the most responsible thing you do all year.

★

At Mozaik: At work the equivalent is rarely dismissal — it's redesigning who sits on which project, and doing it before the good people quietly leave instead.

Level Three — Getting Things Done

Finishing beats starting

Nothing here is about discipline. It's about shrinking the first step until it's too small to avoid, deciding in advance what finished looks like, and treating a permanently full calendar as a warning light rather than a trophy.

13 Define Done

Decide what finished looks like before you start

Any project without a definition of done quietly becomes infinite, because there is always one more revision available. Write the finish line first, in a sentence anyone could check. And when you're near it, remember that shipping is usually a decision about the clock rather than a discovery that the work has become perfect — most things go out because it's time, not because they're ready.

Takeaway: “Done” is a sentence you write on day one, not a feeling you wait for on day thirty.

★

At Mozaik: Put it at the top of every brief: “this is finished when the catalogue PDF is approved by both showrooms and uploaded.” Not “when the catalogue is good.”

14 Tiny First Step

Make the first step embarrassingly small

The size of the first step and the odds of taking it move in opposite directions. So don't write the report — write three sentences. Don't get fit — put the shoes by the door. Don't reorganise the stockroom — clear one shelf. The goal isn't the shelf; it's crossing the line from not-started to started, which is the only part your brain actually resists.

Takeaway: If a task keeps sliding down the list, it isn't a motivation problem. The first step is simply too big.

★

At Mozaik: The SOP documents nobody starts are a first-step problem. “Write the process” is too big; “list the five steps in the order they happen” takes ten minutes.

15 Permission

Let it be easy — difficulty is not evidence of virtue

Somewhere we picked up the idea that if a thing wasn't hard it didn't really count, and we've been paying for it ever since. Buy the version that's already assembled. Use the template. Take the route with no traffic. Delegate the part you're slow at. Choosing the harder path when the easier one works just as well isn't discipline — it's self-imposed cost with good PR.

Takeaway: Nobody hands out extra credit for the scenic route. Save the effort for the parts that genuinely require it.

★

At Mozaik: If a report takes four hours by hand and twenty minutes from the ERP, the four-hour version isn't thoroughness. It's a habit we haven't updated.

16 Tonight, For Tomorrow

Set up tomorrow's first move tonight

Your morning self is not a reliable negotiating partner. Remove its opportunities to negotiate: leave the document open at the paragraph you'll continue, lay the clothes out, and put the unpleasant task in the calendar with a specific day, time and place rather than a vague intention. An appointment is much harder to argue with than a plan, because there's nothing left to decide.

Takeaway: Willpower is unreliable. Appointments are boring and effective, which is the correct order of priorities.

★

At Mozaik: Works on the task everyone postpones: “chase the three overdue Kurumsal payments” with a slot on Tuesday at 09:30 gets done. On a to-do list it moves to next week forever.

17 Waiting For

Keep a “waiting for” list, not just a to-do list

We're reasonably good at tracking what we owe other people and genuinely bad at tracking what other people owe us — the quote someone is reviewing, the drawing that was promised, the approval blocking everything behind it. Put all of it in one visible place, with the name and the date you asked. Otherwise your memory keeps the list instead, and it prefers to read it back to you at three in the morning. The practice comes from David Allen's Getting Things Done.

Takeaway: Half of what stalls a project isn't work you haven't done. It's an answer nobody is chasing.

★

At Mozaik: One shared “waiting for” column in the project board — with who and since when — would remove most of what currently surfaces as a surprise in the weekly meeting.

18 Warning Light

Treat constant busyness as a warning, not a badge

Sometimes “I'm swamped” means a full and good life. Often it means something less flattering: priorities never set, choices never made, or a workload being carried because it's become part of how someone sees themselves. When everything feels urgent, the move is not to work faster. It's to subtract — cancel one thing, decline one thing, and leave some empty space where a walk, an odd idea or an unplanned conversation can actually happen.

Takeaway: Not every square on the calendar has to produce something. The empty ones are doing work too.

★

At Mozaik: If a department is permanently at capacity, that's a planning signal, not a performance one. Adding effort to a full system just moves the breakage somewhere less visible.

Level Four — Work

How to be the person people want on the project

Six codes about the unglamorous mechanics of being good to work with — writing things down, asking better questions about deadlines, bringing solutions instead of only problems, and owning the skill everyone else is avoiding.

19 Write It Down

Send the recap email

After any meeting that matters, send a short note: what we decided, who is doing what, and by when. It helps everyone else, but the real beneficiary is you — turning a conversation into three lines of writing is how you find out whether anything was actually agreed, and it surfaces the gaps while they're still cheap to fix. AI can tidy the wording; don't let it do the deciding, because the thinking is the point.

Takeaway: If you can't write the recap in five lines, the meeting didn't decide anything. Better to learn that today.

★

At Mozaik: Especially for anything crossing departments. Most of our “I thought you were doing that” moments would not survive a recap email.

20 Two Categories

Make your manager's job easier

Every manager, consciously or not, sorts their team into two groups: people who add to the load and people who take some of it off. Being in the second group isn't flattery or politics — it's understanding what your manager is actually being measured on, and removing one thing from that pile without being asked. Early in a career this matters more than almost anything else on your CV.

Takeaway: You don't become indispensable by doing your tasks well. You become indispensable by removing someone else's.

★

At Mozaik: Ask once a quarter: what's the thing on your plate I could take over completely? The answer is usually specific and usually available.

21 The Real Deadline

Ask for the deadline, then ask for the real deadline

“When do you need this?” and “when will someone actually use this?” produce different answers surprisingly often — Friday versus the board meeting three weeks away. Invented deadlines generate real panic, real overtime and real mistakes, all for nothing. Ask both questions, plan against the true one, and extend the same courtesy outward: don't hand other people an urgency you made up.

Takeaway: A fake deadline costs the same as a real one and buys nothing. Find out which one you're holding.

★

At Mozaik: Production and Sales lose days to this every month. One extra question at handover — when does the customer actually need it? — usually recovers them.

22 Ask First

Lead with the request, and bring a recommendation

Don't open an email with six paragraphs of context before the reader learns what you want — say the ask in the first line and put the background underneath for whoever needs it. And when you bring a problem, bring a proposed answer with it. Diagnosis is useful; a recommendation is what actually moves things. “This isn't working” starts a discussion. “This isn't working, I think it's because of X, and I'd suggest Y” starts a decision.

Takeaway: Anyone can name the problem. The person who names it and proposes the fix is the one who gets asked next time.

★

At Mozaik: Applies to escalation emails above all. Arriving with “here's what I recommend, do you agree?” shortens most of them to a single reply.

23 Undefended Ground

Get good at something valuable that everyone avoids

Everyone competes for the visible, glamorous work, which means the competition there is brutal. Meanwhile the messy spreadsheet nobody wants to own, the presentation nobody volunteers for, and the conversation everyone keeps postponing are sitting completely unclaimed. Those skills are valuable precisely because they're unpleasant, and being the person who reliably handles one of them is a very short path to being indispensable.

Takeaway: The crowded territory is crowded. Go where nobody is standing.

★

At Mozaik: In our case that's clean data. Whoever becomes the person who can actually reconcile ERP figures with what the showrooms report will be the most consulted person in the building.

24 For Anyone Who Leads

Be the manager you needed, not the one you had

Two lists, both short. First: what your worst managers did — the vanishing, the credit-taking, the feedback that arrived only once a year and only when it was bad. Don't do those. Second, and harder: what you badly needed from them and never got — clarity, honest criticism delivered early, encouragement at the exact moment you were about to give up, a second chance after a real mistake. Provide those to someone else now.

Takeaway: The second list is the one that changes a team. Most people can avoid the obvious sins and still leave the gap unfilled.

★

At Mozaik: Worth doing literally: write both lists once, keep them in a drawer, and read them before the next review cycle.

Level Five — Living

Where it either adds up to a life, or doesn't

The last six, and the most important one is at the end. Design your surroundings instead of relying on willpower, spend money where it actually lands, build the traditions you want rather than waiting for them — and learn which kinds of difficulty to delete and which to accept.

25 Environment

Design your surroundings around your behaviour

Keep things where you use them rather than where they're supposed to live. The book on the pillow if you want to read at night, the vitamins next to the kettle if you take them with breakfast, the folder on the desk if it's tomorrow's first job. And duplicate deliberately — two chargers, two pairs of scissors, reading glasses in three rooms. Redundancy is cheaper than remembering, and it works on days when you don't.

Takeaway: Redundancy beats self-discipline, because redundancy doesn't have bad days.

★

At Mozaik: Same principle on a showroom floor: the tape measure, the fabric samples and the order pad belong where the conversation happens, not in the back office.

26 Where Money Lands

Spend on removing recurring misery before occasional pleasure

A luxury weekend is three days a year. A mattress that hurts your back is every single night of it. The same arithmetic covers the shoes that pinch, the chair that aches, the laptop that takes four minutes to wake up and the commute you've never questioned. Money spent deleting a small daily irritation buys hundreds of improved days; money spent on a rare treat buys a few. Both are fine — just get the order right.

Takeaway: Multiply by frequency before you decide it's expensive. Daily beats annual almost every time.

★

At Mozaik: Budget logic too. The slow shared printer and the ten-year-old showroom lighting cost more in a year than the thing we keep postponing them for.

27 On Purpose

Build traditions deliberately

Rituals are what turn undifferentiated time into a life you can actually remember afterwards. The Sunday meal, the birthday breakfast, the same slightly ridiculous photo every year in the same spot. Almost none of them form by themselves — somebody decides once, repeats it twice, and by the third year it has become non-negotiable and everyone defends it. That somebody may as well be you.

Takeaway: Traditions aren't discovered, they're started. The first one always feels slightly silly.

★

At Mozaik: Teams need this as much as families. The end-of-season dinner, the photo when a big contract ships — small, repeatable, and remembered far longer than the bonus.

28 Stop Blending In

Stop trying to be normal

Normal is the most crowded place there is, and nobody has ever been remembered for arriving at it. The interesting people are interesting at exactly the points where they stopped asking whether something was normal and started asking whether it was right for them. The parts of you that don't quite fit are usually not the defects — they're the only parts that aren't interchangeable with anyone else's.

Takeaway: Swap the question. Not “is this normal?” but “is this right for me?”

★

At Mozaik: True of brands as well as people. The pieces that look like everyone else's compete only on price, which is a competition we don't want to win.

29 Change Opponent

Compete with your own past self

Comparing yourself to other people is a rigged game, because you're setting your unedited interior against their carefully selected exterior. You know every doubt you've had this week; you know only their announcements. The fix isn't to stop caring about progress — it's to change the opponent. Am I better at this than six months ago? Did I handle that conversation more wisely than I would have last year?

Takeaway: Aim for a personal best, not a medal in someone else's event.

★

At Mozaik: Read the sales board this way. A rep whose own numbers have climbed every quarter is doing well, whatever row they occupy on the leaderboard.

30 The Final Code

Delete unnecessary suffering. Accept necessary suffering.

Two kinds of difficulty, and almost everything depends on telling them apart. The first kind buys you nothing: the pointless commute, the manual process, the argument you keep re-entering, the harder route chosen only to prove something. Cut all of it without guilt. The second kind is the price of admission — anything worth having demands effort, criticism, uncertainty and sacrifice. When you meet that cost, don't assume you've taken a wrong turn. You may simply be paying for something real.

Takeaway: Difficulty is not a signal that you're doing it wrong. It's only a signal once you've checked which kind it is.

★

At Mozaik: This is the code the other twenty-nine sit underneath. Half of them exist to cut the first kind of difficulty — so that there's energy left for the second.

How to actually use this

Don't try all thirty. Pick two.

A list of thirty good ideas changes nothing on its own — it just becomes another thing you've read. So choose exactly two this week: one that removes friction you've been tolerating, and one you've been quietly avoiding because it costs something. Enter those two codes. Come back for the rest later.

01 — The easy one

Pick a code that deletes a recurring annoyance. You'll feel it within days.

02 — The hard one

Pick the code you flinched at while reading. That flinch is the signal.

03 — One week

Two codes, seven days. Then choose two more. Thirty at once is zero.