Motivation and Leadership

Who waits when the home team pays late?

Take out your Week 13 cash calendar and turn to the late-payment case. The home team's NT$60,000 fee for game 1 was due on the Monday of test week 9 but arrived eight days late, on the Tuesday of test week 10. The company's freelancer payday fell on the Tuesday of test week 9, with NT$20,000 due to the performer and the translator for both games. Paying all of it would have left NT$110,000 in the bank, NT$10,000 above the NT$100,000 red line.

The company already had a pay protocol. Each freelancer agreement said when people are paid: half of the performer's fee before the game, and the rest, with the translator's hours, on the freelancer payday after the game. The protocol said nothing about a customer paying late, so Judy filled that gap herself.

Judy did not know when the home team would pay, and she wanted to keep cash near NT$130,000. So on payday morning, Mina sent two messages. The game 2 amounts would be paid as agreed. The performer's NT$6,000 second half for game 1 and the translator's NT$4,000 for her game 1 hours would be paid when the home team paid for game 1. That turned out to be one week later.

Nobody was angry at first. The translator replied with a thumbs-up. The performer's reply, passed on by the translator, was "OK, no problem." Judy sent them both a warm voice message to thank them for two great home games. Judy's staff felt close, as people often do after hard work together.

Look again, though. The floor was never at risk: the waiting protected a cushion that Judy preferred. The two people with the least power in the arrangement carried the whole delay.

They were told, not asked. The performer's answer came through the translator, who is also waiting for her own pay. Nobody knows whether "OK" meant agreement, politeness or worry about losing the next booking.

This is where founder closeness meets management. A small creator-led team often runs on personal trust: people answer quickly and accept unusual requests because they believe in the founder. That trust is valuable. As the company grows, it needs to become a system that people can understand, question and rely on, even when the founder is busy or the news is bad.

This chapter continues the practice scenario used since Week 4, in which Judy's company is running a 12-week test of Option A · Expansion (expand cheerleading and sports-entertainment talent management). The scenario is invented for learning. This week's question is: how can Judy's company keep people motivated and treat them fairly when money is tight, and what must move from personal trust into written authority?

Where this week fits

Week 13 showed that an eight-day delay by the home team pushed the cost of waiting onto someone, even though the floor was never at risk. Week 14 looks at the people who carry that cost, and at the leadership system that decides who they are. The result is a people system table: for each role, what the person contributes, what they may decide, where fairness could break and how they can speak up. Along the way, you test the company's existing pay protocol against the late payment and rewrite the part that failed. Week 15 uses the table to find risks around consent, refusal and voice.

Motivation, satisfaction and commitment

Three words are often used as if they meant the same thing. They describe different parts of a person's relationship with work, and they can move in different directions.

• Motivation is the direction, strength and persistence of a person's effort: what they work on, how hard and for how long.
• Satisfaction is how a person judges their experience of the work, such as the pay, the tasks or the way they are treated.
• Commitment is the bond a person feels with an organization or a course of action. It shapes whether they stay and keep investing effort when things are hard.

Here is how the three can separate. The translator may be strongly committed to working with the performer again, because she enjoyed the games and believes in the project. Her satisfaction with the pay arrangement may still drop after the delay.

For a while, her commitment may keep her motivated. But if commitment rests mainly on hope for the next booking, it can hide growing dissatisfaction until she suddenly leaves. A manager who sees only her thumbs-up sees none of this.

Self-determination theory gives useful words for what lies underneath. Gagné and Deci (2005) distinguish two kinds of motivation. Autonomous motivation is doing work because you value it or find it meaningful; controlled motivation is effort driven by pressure, guilt, fear or a reward.

Ryan and Deci (2020) describe three basic psychological needs. Autonomy is feeling that your actions are your own choice. Competence is feeling effective at what you do. Relatedness is feeling connected to others and cared for by them. When work supports all three, autonomous motivation is more likely.

Apply the three needs to the waiting message. Autonomy was undermined: the performer and the translator were informed, not asked, so the delay was not something they had chosen or agreed to. Competence was not in question, because both had done their work well, and the delay said nothing about their skill. Relatedness was strong, thanks to Judy's warm message. But relatedness should never become the price of accepting unfair terms, as in "if you are really one of us, you won't mind waiting".

Pay, recognition, development and belonging do different jobs

Money matters. Clear pay, payment on time, travel reimbursement and rest are basic conditions of a fair working relationship. Self-determination theory supports paying people well. What it adds is a question about how a reward is designed and how people read it.

Managers often offer one thing and believe they have offered four. Each does a different job:

• Pay is payment for agreed work, on the agreed date.
• Recognition shows a person that their contribution has been seen.
• Development builds the person's future skills, for example by training or a new responsibility with support.
• Belonging connects a person to the group.

Judy's voice message offered recognition and belonging. It did not change the pay date. A warm message cannot repair an unpaid invoice. Each management action should match the problem it is meant to solve.

Recognition also teaches people which work counts. Suppose the company publicly thanks only the performer after each game, because she is the one the fans see. The translator's accuracy and Mina's checks and messages stay invisible. Over time, invisible work tends to become unpaid work, and later it shows up as mistakes, delays or people leaving.

Four kinds of fairness

People judge fairness in more than one way. Researchers distinguish four kinds of fairness, which they call justice (Colquitt, 2001). The table applies each one to the decision to delay the performer's and the translator's pay.

The four kinds can point in different directions. Here, interpersonal justice was high, and that is exactly why the problem is easy to miss. A kind tone can make an unfair procedure feel acceptable, until the next time it happens.

Fair treatment sometimes means different treatment. Paying the performer, who is far away and depends on this income, before a company expense that can wait may be fairer than delaying everyone equally. What matters is that the reason is stated, the rule is known in advance and people can challenge a mistake.

Voice, silence and what "OK" means

Week 8 introduced psychological safety, a shared belief that a team is safe for speaking up, admitting errors and challenging a plan (Edmondson, 1999). This week applies it to a harder case: speaking up about money, to a founder you like, when the next booking may depend on her.

Voice is speaking up to improve how work is done. Silence is holding back a concern that could have been raised. Morrison (2014) reviewed research on voice and silence and explained why people stay quiet even when a leader says feedback is welcome. The reasons include fear, the belief that speaking will change nothing, the wish to protect a relationship and uncertainty about whether it is one's place to speak.

So a quiet reply is ambiguous. The performer's "OK" could mean she agrees. It could also mean she does not want to seem difficult, or that she did not understand the message. In a founder-led team, voice can feel personal: criticizing a payment decision may feel like criticizing Judy. A new international member may not know whether a direct question is expected or rude.

A four-step protocol for concerns

A team can make voice safer with a simple protocol. It works for small issues and serious ones.

1. Receive the concern without judging the person. Thank them, and record what they said.
2. Classify it as urgent (safety or pay due now), important (needs a decision this week) or for information.
3. Name who owns the response and when the person will hear back.
4. Close the loop. Tell the person what was decided and what changed, or explain why nothing could change.

Suppose the translator writes to Mina two days later: her rent is due, and one week matters to her. Under the protocol, Mina records it as urgent, Judy owns the response the same day, and the translator hears back within 24 hours. Psychological safety still includes standards. The company can accept the concern without blame and still ask everyone to keep the agreed quality of work.

From founder closeness to written authority

Founder closeness is the personal trust between a founder and the people around her. It speeds up coordination, because people share context and assume good intentions. As a team grows, the same closeness can spread information unevenly. Some people hear decisions in private. Some receive more flexibility because they have known the founder longer.

Gerstner and Day (1997) combined many studies of leader-member exchange and found that the quality of a leader's relationship with each member is linked to that member's performance and satisfaction. Different roles do need different information. The problem begins when closeness, rather than a stated reason, decides who gets information, opportunities, protection or a remedy.

Formal authority is the right to decide a stated kind of question, attached to a role and written down. In the late-payment case, nobody had written authority to change a payment date. Judy decided in a private chat and Mina sent the message. The Week 10 protocol, in use since test week 7, already required anything that affects safety, consent or pay to go into the meeting decision log. Judy skipped it. Had it been followed, the decision would have entered the log as proposed. It would have become approved, conditional or disputed only after the people affected had been told and could respond.

Authority should match accountability. Mina sent the message, but Judy made the decision, so Judy remains accountable for it. Delegating a task does not transfer the blame. Writing these roles down protects the relationship, because it reduces guessing.

Design the exception before the crisis

Rules become visible when normal work no longer fits them. Here is an earlier situation, Mina's request to move two evening rehearsals. It comes from test week 2, before game 1.

Mina cannot work after 6 p.m. because she cares for a family member (Week 8), but two rehearsals in the next six weeks had been planned for evenings. She asks Judy to move them. Judy likes Mina and says yes at once, in a private message. The translator also has evening duties, but she never asked, because she did not know that exceptions were possible.

The decision to help Mina may be right. The way it was made creates two problems. Nobody else knew about the change, so the rehearsal plan had to be redone at the last minute. And the translator, who is less close to Judy, never had the same chance to ask.

A short exception record solves both problems. It contains five entries:

• Work affected: the two evening rehearsals.
• Reason, in general terms: a family-care duty after 6 p.m. No private details are needed.
• Person accountable: Judy, who approved it.
• Protection for others: the rehearsals move to afternoons, and everyone is told of the change, and that such requests are possible.
• Review date: the end of the six weeks, in test week 8, when both games are over.

The test question is simple: would a person less close to the founder receive the same answer to the same request?

At the review date, ask four questions. Did the exception solve the work problem? Did it shift cost or risk to someone else? Could the people affected raise relevant information? Should the rule itself change, because a repeated exception often means the regular design is wrong?

Belonging that leaves room to say no

Ashforth and Mael (1989) explain how membership of a group becomes part of how people see themselves, and so shapes what they do. In a creator-led company, people may identify with the company, the performances or the founder's story. That identity can keep people going through hard work.

It can also make boundaries feel disloyal. "We are a family" can express mutual care. It can also suggest that normal rules about pay dates and working hours no longer apply. Identity itself is neither good nor bad. Its effect depends on the obligations attached to it.

Healthy belonging includes the right to say no. The performer should be able to refuse a later pay date, decline a schedule change or ask for a written contract without being seen as disloyal. People can care deeply about the company and still need explicit rights.

Leading across languages: who carries the message?

Week 4 showed how to compare settings by mechanisms, such as who approves and which language version counts, rather than by national character. This week adds one mechanism: the channel a message travels through. Kirkman and colleagues (2013) studied global work communities and show that psychological safety and the richness of the communication channels people use help explain how well those communities perform.

In the late-payment case, the performer liaison, a part-time staff member who speaks Korean, was off that day. So Mina asked the translator to put the waiting request into Korean for the performer. She was translating a message about her own delayed pay. That is a conflict of interest, however honest she is. She may soften the message, or the performer may hesitate to object through someone in the same position.

The design fix is concrete. A message about pay or terms should go to the performer in Korean, prepared by someone who is not affected by it, normally the performer liaison. It should say which language version counts and name a person she can answer directly. Because the performer is back in Korea, it should also allow time for her to reply before the decision takes effect.

Leadership behavior that fits the problem, and repair

Leadership is often described with one-word style labels, such as "inspiring" or "supportive". A label compresses many different actions into one word, so it does not tell a founder what to do on a Wednesday afternoon. Start from the work problem instead.

When safety is at risk, a clear instruction fits, and anyone who sees the problem should pass it up to Judy at once. When Judy's staff are designing something new, questions and disagreement are more useful. When someone is learning a task, coaching fits.

A creator founder has one extra challenge. Her public profile can make a request feel stronger than its formal status. A performer or junior staff member may agree because the request comes from a public figure. So the founder should say clearly whether a request is an invitation, a task, a paid change or a decision someone else must approve.

Good leadership also includes repair. After the late-payment message, Judy could name what happened and apologize for deciding without asking. She could pay a small late fee, or pay at once from another source. Then she could change the rule so that it does not happen again. A public statement of good intentions is not enough if the next payment cycle repeats the same harm.

Worked example: a people system table for the Option A test

This table is the week's artifact. It shows one possible design for the roles in the Option A test, including the performer liaison and the part-time bookkeeper from the Week 8 organization chart.

The table also shows where the existing pay protocol failed. Here is the protocol as it stood before test week 9, and the clause that one possible rewrite adds.

Pay protocol before test week 9. The performer receives half her fee before the game and half on the freelancer payday after it. The translator is paid for her hours on the same payday. Judy approves any spending above NT$5,000.

New clause: late customer payments. If a customer pays late, freelancers are still paid on the agreed date. If that would take cash below NT$100,000, Judy decides within two working days on another source, such as a short owner loan, and records the decision in the decision log. A freelancer may be asked to accept a later date only in writing, with the reason, the new date and a late fee of NT$500 per week. The freelancer may say no, and saying no has no effect on future bookings.

Test the rewritten protocol against the Week 13 numbers. Paying everyone on payday would have left NT$110,000, above the floor, so under the new clause nobody would have waited and no loan would have been needed.

The new clause does not forbid a bigger cushion. It says that if the company wants one, the company pays for it, for example with a short owner loan. It does not take the cushion from the pay of the two people with the least power. It also turns the next late payment into a known procedure rather than a private favor.

Notice three things about the table. Every role has a voice route that does not depend on being close to Judy. The authority column separates who decides from who delivers the message. And the fairness-risk column names problems before they happen, which is what Week 15 turns into a risk register.

Leadership tests for the three options

Each option asks something different of the people system. Option A · Expansion needs delegation, safety and scheduling rules for more people. Option B · Boutique (a small cross-border talent and advisory service for a few clients) depends on trust and founder expertise, which can concentrate everything around Judy.

Option C · Content-centered return (return to content, advertising, food service and personal brand) holds several kinds of work under one public identity. The table does not rank the options; in Week 17 you choose one and defend it. It shows that a strategy is also a people system.

AI-assisted people decisions: one risk to watch

Week 3 set the course rule that a person stays responsible for judgment when AI is used. Kellogg, Valentine and Christin (2020) describe how algorithms at work have become a new ground on which control over workers is contested. The risk specific to this week is a tool that ranks freelancers by how fast they reply. It would penalize the performer, whose replies go through the liaison and a second language, and anyone with evening care duties, such as Mina or the translator. No ranking of people should be used without a named reviewer and a way for the person to see and correct the data behind it.

Class practice: a people system table

This practice is done without AI tools. Your teacher will tell you which worksheet to use and how to submit it.

1. Choose one option and one tense moment, such as a late customer payment or a schedule change.
2. Fill a small people system table. For three roles, write what the role may decide, one fairness risk and one voice route.
3. Test one existing rule and rewrite it. Say who decides, who must be asked first and what happens if someone says no.
4. Check each other's work. Swap with a classmate, who checks whether the person with the least power can say no without losing future work. Revise one line.

Key points and what you bring to Week 15

• Motivation, satisfaction and commitment are different. A thumbs-up shows none of them reliably.
• Pay, recognition, development and belonging do different jobs. Match each action to the problem it is meant to solve.
• Fairness has four parts: outcomes, procedure, respect and explanation. A kind tone can hide an unfair procedure, such as asking people to wait to protect a cushion rather than the floor.
• Voice needs a route that works even when the person is far away, less powerful or waiting for pay.
• A founder can lead with warmth and still write the rule. Test each rule against a real event, as the pay protocol was tested here, and rewrite the part that failed.

For Week 15. Bring your people system table. Week 15 turns its fairness risks and voice routes into a risk register for the Option A test. Each risk, including late payment and the performer's consent, gets an owner, a trigger and a stop condition.