Management Functions In Fintech

Title Page

Management Functions in FinTech: A Complete Study Guide

Chapter 1: FinTech OB (Behavior, Perception, Motivation)

Organizational Behavior for fast-moving FinTech teams

---

Table of Contents

1. Learn How Individual Behavior

2. Perception Errors

3. Motivation Shape Performance in Fast-moving FinTech Teams

---

Learn How Individual Behavior

In FinTech, performance doesn’t only come from “better tools.” It comes from how people think, react, and keep going under pressure. When a payments app launches a new feature, the work is not only code and compliance - it's also the behavior of product managers, risk analysts, support agents, and engineers who must make quick decisions with partial information. Organizational Behavior (OB) studies how people behave in groups and inside organizations, and it matters in FinTech because the environment is fast, data-heavy, and high-stakes. A single misunderstanding can turn into a customer complaint, a fraud risk, or a delayed release.

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)....