Management Functions In Fintech

OB is interdisciplinary by nature. Psychology helps explain individual traits and learning. Sociology and anthropology help explain how norms, roles, and culture shape behavior. In a FinTech context, this matters because your “system” is not only software; it’s also people and routines. For example, a team can have a strong security design, but if employees ignore alerts due to stress, unclear responsibility, or weak training, the design fails in practice. Ask yourself: when things go wrong in your workplace, do they mostly fail in the process - or in how people interpret what the process asks them to do?

A useful starting point is individual behavior. Personality is one building block. Two common frameworks you’ll see in OB are MBTI (Myers-Briggs Type Indicator) and the Big Five model (also called OCEAN: Openness, Conscientiousness, Extraversion, Agreeableness, Neuroticism). MBTI groups people into types based on preferences (like how they take in information and make decisions). It can help teams talk about work styles, but it should not be treated like a label that “fixes” behavior. The Big Five model is more grounded: it describes tendencies rather than boxes. In FinTech, you’ll notice how traits connect to day-to-day work. High Conscientiousness often supports careful review of KYC (Know Your Customer) steps. Higher Openness can support experimentation with new onboarding flows. Higher Neuroticism can make stress management more important during incidents and outages. None of this means “good” or “bad” - it means you can predict where support and clarity are needed.

Values and attitudes are another building block. Values are deeper beliefs about what is important; attitudes are how someone feels about something. Terminal values are end goals (like personal security or achievement). Instrumental values are ways to behave to reach those goals (like honesty, discipline, or ambition). In FinTech, values show up when people decide what to prioritize during trade-offs. When the team is under time pressure, do they still treat compliance checks as non-negotiable? That’s values in action. Attitudes can be studied using the ABC model of attitude: Affective (feelings), Behavioral (actions), and Cognitive (beliefs). If a risk analyst “feels” that compliance is slowing them down (Affective), they may start “skipping” steps (Behavioral), even if they still “believe” the policy is important (Cognitive). The ABC model helps you see that changing only the written policy might not change real behavior unless the feelings and beliefs also shift.

FinTech Case Study / Example (Individual Behavior: Values and Attitudes in Payments) A common pattern in digital payments teams is that new features go live faster than support teams can fully understand edge cases. Suppose a wallet app adds a new QR payment flow. Some support agents may believe the feature is “good for customers” (Cognitive), but they may feel frustrated because refunds take longer than before (Affective). Over time, their behavior can shift - more “template replies,” more escalation delays, and fewer careful troubleshooting steps. The issue isn’t lack of effort; it’s attitude mismatch. Teams that fix this usually don’t only update the SOP (standard operating procedure). They also run short training sessions using real tickets, so agents feel more confident, believe the process is workable, and then behave differently when customers report failed payments. That’s OB showing up in a practical, measurable way: customer resolution time improves when attitudes align with the intended process.

A final piece under individual behavior is learning. People don’t only “know” - they learn from what happens around them. Classical conditioning is learning through association. Operant conditioning is learning through consequences (rewards and punishments). Social learning theory (learning by observing others) is especially relevant in FinTech because new employees watch how senior teammates handle incidents, fraud alerts, and customer escalations. If the first week teaches “cut corners and nothing happens,” the organization is training the wrong behavior. If it teaches “raise alarms early and the team helps you,” the organization trains safer behavior. Ask yourself after a busy sprint: did people get rewarded for careful checks, or did the system reward speed even when speed created rework?

Practical takeaway / reflection prompt: Look at one current process in your FinTech workplace (like KYC review or incident response). Identify what values and attitudes the process rewards in real life - not just on paper.

---

Perception Errors

Perception is how people take in information, interpret it, and act on it. In fast-moving FinTech, perception errors become operational risks because decisions happen quickly and under stress. The perception process usually looks like this: people select what they notice, organize it into a meaning, and interpret it. From there, they respond. When the team responds to the wrong meaning, even correct tools can produce wrong outcomes. This is why training in FinTech isn’t only about policy and systems - it’s also about how humans interpret signals like transaction patterns, customer messages, or system alerts.

Several factors influence perception. Experience shapes what people expect to see. Emotions shape what feels “important.” Time pressure shrinks attention and increases shortcuts. Team roles also matter: a fraud analyst and a customer support agent may view the same incident differently because their goals and information differ. In a real launch, the fraud team might see a pattern of transactions that “looks risky,” while customer support may see angry users who “just need help.” Both are partly right - perception is not purely objective.

Perceptual errors are predictable. The halo effect happens when one positive trait spills over into overall judgment. Example: if a team member is known for fast delivery, others may assume their risk analysis is also strong, even when their review is thin. The opposite can happen too - if someone once made a mistake, the team may assume they’re unreliable in future tasks. Stereotyping is another error: judging someone based on a group label rather than the person’s actual behavior. In FinTech, stereotypes show up when people assume “certain roles” always handle risk well, or “certain departments” always delay. Selective perception is when people notice information that matches their beliefs and ignore information that challenges them. During fraud spikes, selective perception can lead to “confirmation thinking,” where teams repeatedly look for the explanation they already prefer.

A worked way to understand these errors is to connect perception errors to concrete FinTech moments. Consider transaction monitoring. The monitoring system flags activities using rules and models. Humans still must interpret and decide what to do next. If a reviewer has selective perception - only noticing signals that match a prior case type - they may miss new fraud patterns. If the reviewer is influenced by the halo effect of a prior correct decision from the same model or the same analyst, they may treat the next alert as “probably fine.” If stereotyping is present - like assuming a specific merchant category cannot be involved - then the review can become biased even when evidence exists.

FinTech Case Study / Example (Perception Errors: Fraud Alert Review) A mobile payments company updates its fraud scoring model. The new model increases flags for certain user behavior patterns. The operations team notices that some flags are false positives and starts to “expect” noise. Over the next week, reviewers develop selective perception: they skim early evidence, focus on the patterns they believe are common false positives, and only dig deeper when the alert matches their old examples. Then a real fraud cluster appears with a different profile. Because reviewers were trained by experience to ignore certain signals, the team takes longer to detect the new pattern. The fix wasn’t only “train more.” It was also structured review prompts: checklists that force reviewers to examine specific evidence categories every time, so perception errors have less room to steer the decision.

Values and learning already discussed influence perception. If someone strongly values speed, they may treat uncertainty as “probably harmless” and move on. If someone learned in the past that escalations are punished, they might interpret alerts as “not worth it.” Perception errors are therefore not just individual mistakes; they can be shaped by the environment. That’s important because OB is not blaming people - it’s helping you see how the system pushes certain interpretations.

Practical takeaway / reflection prompt: Pick one decision point where humans judge data (refund approvals, KYC exceptions, fraud reviews). Write down the three pieces of evidence that must be checked every time. These act like “perception anchors” against halo effect, stereotyping, and selective perception.

---

Motivation Shape Performance in Fast-moving FinTech Teams

Motivation is what pushes people to start, continue, and put effort into work. In FinTech, motivation matters because many tasks are not exciting in the moment: compliance checks, audits, reconciliation, alert triage, documentation, and incident follow-ups. If motivation is weak, people shortcut. If motivation is misdirected, people focus on the wrong target. The result can be missed risks, poor customer handling, or slow recovery after system failures.

Several motivation theories explain how to think about effort in a structured way. Maslow’s Hierarchy of Needs starts with basic needs (like safety) and moves upward to belonging, esteem, and self-actualization. In a FinTech workplace, “safety” doesn’t only mean physical safety. It also means job security and psychological safety - feeling that you won’t be punished for raising an issue early. If employees fear blame during incidents, they may hide errors instead of escalating them. ERG Theory (Existence, Relatedness, Growth) is a simpler update. Existence covers basic needs, Relatedness covers relationships and belonging, and Growth covers development and challenge. Many FinTech teams struggle most with Growth motivation during repetitive compliance work, so they need ways to create learning and improvement opportunities.

McGregor’s Theory X and Theory Y focuses on assumptions managers make about people. Theory X assumes people dislike work and need control. Theory Y assumes people can be self-directed and seek responsibility. You can see the difference in how work is managed. If a team only uses strict monitoring and approvals, people may respond with minimal compliance. If a team gives ownership and clear boundaries, people are more likely to take initiative. Herzberg’s Two-Factor Theory separates hygiene factors (like pay, policies, work conditions) from motivators (achievement, recognition, the work itself, responsibility). In FinTech, hygiene issues can cause dissatisfaction quickly - unclear policies, unfair schedules, or poor tooling. But even with good hygiene, performance still needs motivators. People must feel their contribution matters in customer trust, risk reduction, and reliability.

McClelland’s Needs focuses on three needs: achievement (wanting to accomplish), affiliation (wanting relationships), and power (wanting influence). FinTech teams often attract people with achievement needs, especially in product and engineering. But risk teams also need affiliation and power in a healthy way: people should feel connected and should have authority to stop unsafe releases or escalate incidents. Goal-setting theory adds another practical angle: specific and challenging goals improve performance when people understand how to reach them. In FinTech, goals like “reduce chargeback rate” work better when they are measurable and paired with actionable steps, not just vague targets.

Two more theories are very useful for workplace decisions. Equity Theory is about fairness. People compare their inputs (time, skill, effort) and outcomes (pay, recognition, opportunities) with others. If they feel the comparison is unfair, motivation drops even if the work is technically good. In FinTech, equity issues can appear in shift work for support, overtime during incidents, or who gets promoted after a major product win. Vroom’s Expectancy Theory is about effort-to-performance-to-outcome links. People ask: “If I work harder, will I perform better?” and “Will better performance lead to rewards I value?” If the system rewards only speed, people may not invest in careful checks. If the system rewards quality reviews and safe escalations, people will do that.

All these theories point to one management action: motivation is not one switch. It’s a set of conditions. In fast-moving FinTech teams, the conditions shift weekly - new fraud rules, new regulatory guidance, new customer expectations, new releases. That’s why managers must keep re-checking what the organization rewards in practice. A team may say it values compliance, but if people are punished for raising issues late, behavior will follow fear, not policy.

FinTech Case Study / Example (Motivation: Equity and Expectancy in Customer Support) A neobank handles complaints through a ticketing system with strict turnaround targets. The company publicly says “we value customer trust,” but internally, the team is measured mostly on speed. Over time, support agents begin to close tickets early with generic responses. They feel that if they spend time investigating, they won’t reduce their workload score and may even get flagged for “slow handling.” This is Expectancy Theory breaking: effort doesn’t lead to better outcomes (in the metrics that matter). Equity also breaks if only certain agents are allowed to take complex cases while others are expected to handle simple tickets under time pressure. The fix is not just “tell agents to be better.” The organization changes the reward signals: it tracks quality indicators alongside turnaround time, and it rotates complex case ownership so fairness improves. Motivation rises because effort-to-outcome becomes real and fair.

Worked check for motivation: choose one team metric and one team reward (a recognition system, promotion criteria, or performance review focus). Ask yourself whether the metric truly rewards what you want. If your desired behavior is careful risk handling, then your metrics must include quality checks and safe escalation, not only “number of tickets closed” or “release count.” When metrics match desired behavior, motivation becomes easier and more stable.

Practical takeaway / reflection prompt: Pick one motivational theory (Equity or Expectancy are easiest). Use it to explain one real workplace issue you’ve seen - then write one process change that would improve the motivational link (fairness, clarity, or effort-to-outcome).

End of chapter one. 4 more chapters in the full book.