Skip to main content
Image coming soon

Influence in MiFID II Technical Decisions

$199.00
Adding to cart… The item has been added

A tailored course, built for your situation

Influence in MiFID II Technical Decisions

Become the engineer whose input shapes compliance-critical system architecture

$199 one-time
24-hour access provisioning 30-day money-back guarantee Hand-built implementation playbook
12 modules. 12 chapters per module. 144 chapters total.
12 modules, each with 12 chapters (144 chapters total), text-based, plus downloadable templates and a hand-built implementation playbook delivered alongside course access.
Being technically right isn’t enough if your recommendations get overruled or ignored in cross-team decisions

The situation this course is for

Strong engineers often have the best solution, but without influence, their input gets drowned out by louder voices or higher titles. The difference between being heard and being ignored comes down to how well technical reasoning is framed within regulatory context and business impact.

Who this is for

Senior individual contributor in financial technology who must align complex engineering work with strict regulatory frameworks

Who this is not for

Junior developers, managers without hands-on implementation roles, or compliance specialists who don’t write or review code

What you walk away with

  • Confidence in shaping technical direction during MiFID II compliance discussions
  • Credibility to lead vendor evaluation tracks based on architectural fit
  • Clarity in translating code-level choices to regulatory outcomes
  • Recognition as the go-to engineer when audit timelines tighten
  • Ability to frame implementation trade-offs in terms that resonate with compliance and risk stakeholders

The 12 modules (with all 144 chapters)

Module 1. How Influence Actually Works in Regulated Engineering
Understand the unwritten pathways through which technical decisions get made in MiFID II environments and where engineers can lean in effectively.
12 chapters in this module
  1. The myth of formal authority
  2. When peer review shapes outcomes
  3. Mapping decision influencers
  4. Engineer as anchor point
  5. Compliance by design mindset
  6. Signals of technical trust
  7. Reading organisational cues
  8. Pre-framing key choices
  9. Anticipating review points
  10. Building silent consensus
  11. Timing for maximum pickup
  12. From contributor to reference
Module 2. MiFID II Rules That Drive Real System Design
Focus on the specific articles and reporting requirements that actually constrain architecture choices in trading, surveillance, and data retention.
12 chapters in this module
  1. RTS 23 clock accuracy rules
  2. Reporting latency thresholds
  3. Audit trail completeness
  4. Order routing disclosures
  5. Best execution logging
  6. Data retention mandates
  7. Timestamp synchronisation
  8. Trade reconstruction paths
  9. Client classification logs
  10. Order lifecycle tracking
  11. Pre trade transparency rules
  12. Post trade reporting windows
Module 3. Translating Regulation into Code Constraints
Turn MiFID II obligations into explicit, testable system requirements that stand up to internal and external scrutiny.
12 chapters in this module
  1. From article to acceptance criteria
  2. Regulation as spec input
  3. Testable compliance checks
  4. Embedding auditability
  5. Logging with intent
  6. Designing for replay
  7. Schema evolution under scrutiny
  8. Versioning for compliance
  9. Data lineage by default
  10. Schema validation gates
  11. Immutable log structures
  12. Automated gap detection
Module 4. Designing Systems That Withstand Review
Structure your implementations so they pass audit the first time and become reference examples for others.
12 chapters in this module
  1. Audit-first design
  2. Self-documenting systems
  3. Evidence by default
  4. Minimal explanation overhead
  5. Standardised data flows
  6. Compliance-aware APIs
  7. Schema stability patterns
  8. Change control framing
  9. Peer validation cycles
  10. Design review readiness
  11. Version control narratives
  12. Deployment with trace
Module 5. Framing Technical Trade-offs for Influence
Learn how to present architectural options so compliance and risk stakeholders adopt your recommendation as their own.
12 chapters in this module
  1. The language of risk framing
  2. Positioning trade-offs fairly
  3. Highlighting hidden costs
  4. Making compliance tangible
  5. Balancing speed and control
  6. Consequences of inaction
  7. Presenting multiple paths
  8. Default option design
  9. Simplifying complexity
  10. Narrative over data dump
  11. Confidence without certainty
  12. Closing with momentum
Module 6. Building Technical Credibility Across Functions
Establish yourself as the reliable source others turn to when MiFID II questions arise outside your immediate team.
12 chapters in this module
  1. Earning cross-team referrals
  2. Consistency builds trust
  3. Documentation as currency
  4. Answering beyond scope
  5. Teaching without lecturing
  6. Reliability over speed
  7. Owning the edge cases
  8. Sharing patterns widely
  9. Creating re-usable assets
  10. Being the known quantity
  11. Reducing others' risk
  12. Becoming the shortcut
Module 7. Shaping Vendor Selection from Within
Guide procurement and architecture decisions by framing third-party tools in terms of long-term compliance sustainability.
12 chapters in this module
  1. Evaluating audit trail depth
  2. Assessing timestamp fidelity
  3. Reviewing data retention defaults
  4. API compliance readiness
  5. Schema change resilience
  6. Penetration testing posture
  7. Support response expectations
  8. Documentation quality check
  9. Upgrade path clarity
  10. Licensing compliance fit
  11. Interoperability thresholds
  12. Exit strategy evaluation
Module 8. Leading Without Formal Authority
Exert influence in technical governance forums where no one reports to you, but everyone looks to you for clarity.
12 chapters in this module
  1. Speaking last for impact
  2. Validating before redirecting
  3. Building on others' ideas
  4. Creating shared ownership
  5. Neutralising hierarchy
  6. Using precise language
  7. Avoiding expert tone
  8. Asking strategic questions
  9. Summarising group intent
  10. Closing open threads
  11. Documenting decisions fairly
  12. Owning follow-up silently
Module 9. Creating Artefacts That Compound Influence
Develop implementation templates, checklists, and playbooks that get adopted beyond your team and turn your work into lasting reference.
12 chapters in this module
  1. Checklist design fundamentals
  2. Template adoption triggers
  3. Playbook usability
  4. Version control approach
  5. Change notification method
  6. Feedback integration
  7. Cross-team onboarding
  8. Searchability and access
  9. Ownership transitions
  10. Updating without drift
  11. Linking to standards
  12. Attribution without ego
Module 10. Communicating with Audit and Compliance Teams
Frame technical work in a way that reduces back-and-forth and positions you as an enabler, not a hurdle.
12 chapters in this module
  1. Aligning timelines proactively
  2. Using compliance terminology
  3. Anticipating evidence requests
  4. Structuring responses
  5. Explaining trade-offs clearly
  6. Highlighting risk reduction
  7. Avoiding technical defensiveness
  8. Owning gaps constructively
  9. Providing context generously
  10. Building review efficiency
  11. Reducing clarification loops
  12. Creating self-service paths
Module 11. Sustaining Influence Across Regulatory Changes
Future-proof your role by designing systems and relationships that adapt to new interpretations and reporting demands.
12 chapters in this module
  1. Monitoring regulatory updates
  2. Change impact filtering
  3. Engagement escalation paths
  4. Internal feedback loops
  5. Stakeholder mapping update
  6. Version comparison tools
  7. Change communication rhythm
  8. Adaptation triggers
  9. System modularity
  10. Regulatory horizon scanning
  11. Cross-functional alerts
  12. Ownership clarity
Module 12. Becoming the Default Reference
Position yourself as the first call when MiFID II questions arise, across engineering, compliance, and internal audit.
12 chapters in this module
  1. Building recognition gradually
  2. Consistency over charisma
  3. Teaching at scale
  4. Creating re-usable guidance
  5. Documenting decisions publicly
  6. Sharing lessons widely
  7. Reducing repeat questions
  8. Mentoring peers
  9. Strengthening networks
  10. Owning unowned problems
  11. Improving on legacy
  12. Leaving evidence trails

How this maps to your situation

  • During architecture review for new trading system
  • When responding to internal audit findings
  • Prior to vendor selection for surveillance tool
  • After a regulatory update changes reporting scope

Before vs. after

Before
Technically sound but overlooked in cross-functional decisions
After
Consistently sought out for input on MiFID II system design and compliance strategy

What's included with your purchase

  • 12 modules with 12 chapters each (144 chapters)
  • Downloadable templates and worked examples for every module
  • Hand-built implementation playbook delivered alongside course access
  • 30-day money-back guarantee

Delivery and format

  • Course and learning environment access provisioned within 24 hours of purchase
  • Hand-built implementation playbook delivered alongside course access

Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.

Time investment: Approximately 3 hours per week over 12 weeks, with flexible pacing.

If nothing changes
Without sharpening influence, strong technical work remains localised and under-recognised, limiting impact on broader compliance outcomes and career growth.

How this compares to the alternatives

Unlike generic compliance courses, this program is tailored to engineers who must translate MiFID II rules into system design decisions and gain influence without formal authority.

Frequently asked

Who is this course for?
Senior individual contributor engineers working on systems subject to MiFID II compliance who want to increase their influence in technical and cross-functional decisions.
How is the course structured?
12 modules, each containing 12 chapters (144 chapters total).
What if I’m not directly in compliance?
This course is designed for engineers like you who shape compliant systems from the inside, not for compliance officers or auditors.
$199 one-time. Approximately 3 hours per week over 12 weeks, with flexible pacing..

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.

30-day money-back guarantee· 144 chapters· Hand-built playbook included· Account access within 24 hours