Practical Ways for FinTech Professionals to Master New Business Domains

Overall Framework

When a fintech engineer is transferred to a new team, the goal is to acquire domain knowledge quickly. The author recommends the COLA framework (People, Business, Technology, Culture) from chapter 17 of *Programmer’s Underlying Thinking* and applies the principle of deliberate practice to build a mental model of the new domain.

Key Dimensions

People – Identify roles, build relationships, and obtain information from the right stakeholders.

Synchronous learning – Gather information from each source across multiple dimensions and integrate it into a unified “business panorama map”.

Culture – Observe both explicit rules and implicit habits; adopt a “listen more, speak less” stance.

The panorama map visualises product characteristics, target customers, delivery channels, responsibilities, personnel, and system modules.

Step‑by‑Step Process

1. Domain Knowledge & Concept Model

Collect data from the internet, specialised books, internal training material, and product documentation. Map data‑model fields to existing knowledge. If the system contains complex business processes, model them with BPMN. Experience the product directly (e.g., use the app or shadow a customer) while simultaneously populating the panorama map.

2. Industry Awareness

Understand the broader industry context, especially regulatory requirements in banking. Download and read the relevant regulations, then apply a PESTEL analysis. AI‑assisted tools can accelerate the extraction of key industry signals.

3. Business Analysis

Summarise the business’s historical evolution, internal strategies, and market trends. Extract a handful of keywords that capture the essence of the business.

4. System Analysis

List architectural components, technical specifications, and runtime metrics (e.g., traffic per channel). Review source code to identify system‑specific technical characteristics that correspond to the business keywords.

5. Current Pain Points

Interview representatives from different roles to uncover issues:

Developers – efficiency, project‑management, technical debt.

Operations – system stability.

Business staff – delivery speed, data‑analysis needs.

Leadership – strategic expectations and platform positioning.

Analyse these pain points to shape future development directions.

6. Team Culture

Observe the team’s mission, vision, and values, as well as implicit norms such as project‑management style, requirement‑handling practices, and meeting conventions. Record observations without imposing changes.

Deep Mastery

After the surface panorama is complete, shift focus from application‑level details to the domain layer. Build a transferable concept model that abstracts the core business mechanisms (e.g., pricing engine, real‑time interest calculation, position management) which are common across similar domains such as e‑commerce. Core technology is defined as the business‑specific mechanisms rather than generic frameworks.

Next Steps

With the panorama map established, refine sub‑domains, deepen the concept model, and aim to deliver value recognised by leadership.