Business Analyst – Process Design & Documentation

Location: Boston, MA or New York, NY

Most Important Skillsets

• 5+ years of Business Analyst experience within asset management, insurance investment, banking, or consulting supporting these industries
• Strong process mapping and documentation experience
• Experience with swimlane and cross-functional process flows
• Experience writing operating procedures, desk procedures, and playbooks
• Proficiency with Visio, Lucidchart, or equivalent process-mapping tools
• Strong proficiency with Word, Excel, and PowerPoint
• Familiarity with AI tools such as ChatGPT, Claude, or Gemini

This is not a general BA role . The ideal candidate needs to be strong in process design, process mapping, operational documentation, requirements gathering, and stakeholder engagement within a financial services environment.

Rate: Experience base W2 Role Only

About the Role

LMI is launching a rated note fund that will be serviced by a third-party fund administrator. Key project milestones include:

• Operational readiness: November 1
• Legal close: December 15
• Go-live: January 1

The Business Transformation team within Strategy & Execution (S&E) owns the process documentation required for the launch.

This role will provide Business Analysis support focused primarily on process design and documentation . The analyst will work with operations owners across six workstreams to map new and modified processes, draft the corresponding procedures and playbooks, and maintain the deliverable register as decisions are finalized.

This is a documentation-led role rather than an advisory role . The documentation created will serve as the operating record that the operations teams will use to run the fund once it goes live.

The role requires close collaboration with teams across loan operations, fund operations, finance, data, and technology . Success will depend on the ability to work directly with subject matter experts, extract detailed information from them, and translate that information into clear, usable documentation.

Key Responsibilities

Process Mapping & Documentation

• Partner with workstream owners to map new and modified processes end-to-end, including the division of responsibilities between LMI and the third-party fund administrator.
• Document control points, handoffs, exception paths, and system touchpoints.
• Identify process steps where ownership is unclear and help drive resolution.
• Draft operating procedures, desk procedures, and playbooks using established templates.
• Walk documentation through review and validation with the appropriate operations owner.
• Maintain consistency in structure, terminology, and formatting across all six workstreams:
• Cash Management
• Fund Administration
• Monthly & Quarterly Reporting
• Compliance & Waterfall
• Rating Agency
• Loan Servicing & Reconciliation
• Maintain version control so the current state of each document is always clear.

Requirements, Decisions & Tracking

• Maintain the operational deliverable register, including status, ownership, and open items across workstreams.
• Capture requirements, decisions, and open questions from working sessions.
• Translate discussions into clear written follow-ups and actionable next steps.
• Support development of RACI matrices and service-level definitions with SMEs and workstream owners.
• Prepare materials for working group and program reviews.

Workshops & Stakeholder Support

• Prepare for, support, and document working sessions with operations, finance, data, and technology teams.
• Follow up on open items between meetings and proactively escalate risks to the November 1 operational readiness date .
• Help document data requirements and lineage supporting compliance and waterfall testing, rating agency reporting, and periodic reporting.

Standard of Completion

Two standards apply to all deliverables:

1. Every process flow and procedure must be developed and validated with the LMI operations professional who will ultimately own and perform the process.
2. The documentation must be consistent in structure and terminology so the operations teams can maintain it independently after go-live without significant rework.

Important: A process document is not considered complete until it has been reviewed and validated with the individual responsible for owning the process.

**Required Qua…