A tailored course, built for your situation
Influence in MiFID II Technical Decisions
Become the engineer whose input shapes compliance-critical system architecture
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)
- The myth of formal authority
- When peer review shapes outcomes
- Mapping decision influencers
- Engineer as anchor point
- Compliance by design mindset
- Signals of technical trust
- Reading organisational cues
- Pre-framing key choices
- Anticipating review points
- Building silent consensus
- Timing for maximum pickup
- From contributor to reference
- RTS 23 clock accuracy rules
- Reporting latency thresholds
- Audit trail completeness
- Order routing disclosures
- Best execution logging
- Data retention mandates
- Timestamp synchronisation
- Trade reconstruction paths
- Client classification logs
- Order lifecycle tracking
- Pre trade transparency rules
- Post trade reporting windows
- From article to acceptance criteria
- Regulation as spec input
- Testable compliance checks
- Embedding auditability
- Logging with intent
- Designing for replay
- Schema evolution under scrutiny
- Versioning for compliance
- Data lineage by default
- Schema validation gates
- Immutable log structures
- Automated gap detection
- Audit-first design
- Self-documenting systems
- Evidence by default
- Minimal explanation overhead
- Standardised data flows
- Compliance-aware APIs
- Schema stability patterns
- Change control framing
- Peer validation cycles
- Design review readiness
- Version control narratives
- Deployment with trace
- The language of risk framing
- Positioning trade-offs fairly
- Highlighting hidden costs
- Making compliance tangible
- Balancing speed and control
- Consequences of inaction
- Presenting multiple paths
- Default option design
- Simplifying complexity
- Narrative over data dump
- Confidence without certainty
- Closing with momentum
- Earning cross-team referrals
- Consistency builds trust
- Documentation as currency
- Answering beyond scope
- Teaching without lecturing
- Reliability over speed
- Owning the edge cases
- Sharing patterns widely
- Creating re-usable assets
- Being the known quantity
- Reducing others' risk
- Becoming the shortcut
- Evaluating audit trail depth
- Assessing timestamp fidelity
- Reviewing data retention defaults
- API compliance readiness
- Schema change resilience
- Penetration testing posture
- Support response expectations
- Documentation quality check
- Upgrade path clarity
- Licensing compliance fit
- Interoperability thresholds
- Exit strategy evaluation
- Speaking last for impact
- Validating before redirecting
- Building on others' ideas
- Creating shared ownership
- Neutralising hierarchy
- Using precise language
- Avoiding expert tone
- Asking strategic questions
- Summarising group intent
- Closing open threads
- Documenting decisions fairly
- Owning follow-up silently
- Checklist design fundamentals
- Template adoption triggers
- Playbook usability
- Version control approach
- Change notification method
- Feedback integration
- Cross-team onboarding
- Searchability and access
- Ownership transitions
- Updating without drift
- Linking to standards
- Attribution without ego
- Aligning timelines proactively
- Using compliance terminology
- Anticipating evidence requests
- Structuring responses
- Explaining trade-offs clearly
- Highlighting risk reduction
- Avoiding technical defensiveness
- Owning gaps constructively
- Providing context generously
- Building review efficiency
- Reducing clarification loops
- Creating self-service paths
- Monitoring regulatory updates
- Change impact filtering
- Engagement escalation paths
- Internal feedback loops
- Stakeholder mapping update
- Version comparison tools
- Change communication rhythm
- Adaptation triggers
- System modularity
- Regulatory horizon scanning
- Cross-functional alerts
- Ownership clarity
- Building recognition gradually
- Consistency over charisma
- Teaching at scale
- Creating re-usable guidance
- Documenting decisions publicly
- Sharing lessons widely
- Reducing repeat questions
- Mentoring peers
- Strengthening networks
- Owning unowned problems
- Improving on legacy
- 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
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.
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
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.