From Fintech to Foundations
Why Project Management Skills Travel further Than What We Think
Over two decades managing projects in fintech and ICT, I have worked in environments defined by digital transformation, rapid iteration, regulatory pressure, and fast-changing technology. So, when I recently delivered a project management training session to construction professionals, focused on schedule management and MS Project, I expected to do a fair amount of translation. Construction runs on physical sequencing and decades-old methods; fintech runs on sprints and shifting requirements. Instead, the session became one of the clearest demonstrations of a truth I’ve always believed deeply; that project management is a discipline of thinking and controlling variables, and it transfers with remarkable ease across sectors that look nothing alike on the surface.
A Receptive Audience
The participants were not blank slates. A few of them had been sequencing tasks and building timelines long before hearing the term “critical path.” What they lacked was a formal framework to make that intuition visible and controllable at scale. That gap is exactly where structured training earns its value, and the group’s receptiveness confirmed it immediately.
Agile vs. Traditional
One highlight was the discussion of agile versus traditional project management. Rather than presenting agile as something construction “should” adopt, we framed both as tools suited to different types of uncertainty. Traditional approaches fit fixed, physical dependencies; agile fits evolving requirements and frequent iteration, providing stage gates for constant stakeholder feedback throughout the process. Participants left with a clear understanding of the value of both approaches and a better sense of when hybrid would best apply. Example; an iterative design planning ahead of a locked traditional execution schedule.
The WBS as a Universal Language
The single biggest “lightbulb moment” for many was the Work Breakdown Structure (WBS). Participants already broke projects into phases, but few had formally decomposed those phases into a hierarchical, deliverable-based structure. This session showed them why breaking chunks of work down to the most granular point where time and cost can be derived, is crucial. Once our hands-on sessions that allowed us to build-out a WBS together using a live scenario progressed, its value as the backbone of accurate estimating and resource assignment became self-evident to all participants. A concept that maps just as cleanly onto a mid-rise building as it does onto a core-banking rollout.
Tasks, Dependencies, and Linking
From the WBS we moved into MS Project itself: durations, predecessors and successors, and the four dependency types: finish-to-start, start-to-start, finish-to-finish, and start-to-finish. Watching the schedule recalculate live as a single link changed was a genuine revelation, and it gave participants language to explain scheduling pressure to clients with real authority rather than instinct alone. This session underscored the fact that MS Project is a scheduling engine and not a mere task tracker. Key takeaways from this part of the course were anchored around the planning, task management and the entire tracking lifecycle. Trainees quickly appreciated that a project schedule is not just a list of tasks; it represents the logical flow of work, including the sequence in which tasks must be completed, how long they take, and how they depend on one another. The three primary elements of a basic schedule: tasks, durations, and dependencies really stood out for them.
Resources and Cost Together
Perhaps the most impactful takeaway related to resourcing; primarily the areas of resource overallocations and options for auto levelling. Additionally, seeing resource assignments, rates, and hours tied directly to schedule tasks and producing real-time cost tracking alongside progress was eye-opening. Many had tracked budgets and schedules separately. Seeing both controlled together, the way I do routinely in fintech projects, shifted the conversation from “are we on time?” to “are we on time and on budget by interrogating the Gantt Chart.
The Broader Lesson
Project management is a portable operating system, not an industry-specific skill. The vocabulary shifts; sprints become phases, user stories become work packages, but the discipline of decomposition, sequencing, dependency management, and cost control stays constant. For this group, the training sharpened instincts they already had. For me, it was a reminder that after twenty-plus years leading projects as project management practitioner, the most valuable thing I carry into any room is not domain, sector or industry expertise, it’s the discipline of project management itself.