Business Analyst

Role Purpose

The Business Analyst is the connective tissue between project SOWs, business stakeholders, cross-functional teams, multiple business units, and end-user personas at JLOOP Enterprise. This role helps Producers deeply understand business scope, application requirements, client needs, and user expectations, then translates that understanding into clear, actionable actionable documentation of deliverables for execution teams.

This position requires strong analytical acumen, business process fluency, and communication discipline in an enterprise, contract-driven IT environment. The Business Analyst ensures outcomes, value, and functionality align with organizational objectives, contractual obligations, and measurable user impact.

Core Accountabilities

1. Business Requirements Gathering & Analysis

• Lead the process of gathering, analyzing, and documenting comprehensive business requirements for customer contract scope.
• Engage diverse stakeholders including HR representatives, technical teams, end users, and external partners to clarify business needs, pain points, and desired outcomes.
• Translate complex requirements into clear, actionable documentation of deliverables for project teams.

The BA turns business complexity into execution-ready clarity.

2. User Persona Development & User Story Creation

• Develop detailed user personas and user stories for internal and external stakeholders.
• Ensure scenarios cover different roles, workflows, edge cases, and decision points.
• Work cross-functionally to validate and iterate on personas and stories in alignment with project objectives and business value.

The BA ensures the team builds for real users, not assumptions.

3. Legacy Systems Analysis & Process Mapping

• Conduct thorough analysis of existing systems, process flows, architecture, and integrations across the use case.
• Identify gaps, inefficiencies, and modernization opportunities before they become delivery risk.
• Document current-state and future-state process maps for clarity, alignment, and traceability.

The BA makes transformation decisions evidence-based and defensible.

4. Stakeholder Communication & Collaboration

• Serve as the primary analyst voice for defined SOWs across business and technical conversations.
• Facilitate and attend meetings with key persona groups to gather insight that supports clear definitions of done and measurable deliverables.
• Maintain requirement traceability and decision records so teams can move quickly without losing alignment.

The BA keeps stakeholders aligned to one shared understanding of scope.

5. Outcome Measurement & Value Realization

• Define key performance metrics and desired business outcomes tied to the SOW.
• Produce analysis findings and recommendation reports that help Producers and stakeholders maintain scope alignment.
• Ensure user, business, and contractual objectives are measurable and delivered.

The BA links requirements to real, trackable value.

Preferred Qualifications

• Degree in Business Analytics, Project Management, or a related field
• Professional certifications such as CBAP (Certified Business Analysis Professional) or PMI-PBA (Professional in Business Analysis)
• Experience working on high-pedigree technology platforms or proficiency testing applications
• Prior experience with contract management in the science lab sector
• Knowledge of clinical, laboratory, or regulated business domains and environments
• Seasoned experience with modern requirements management and collaboration tools

Ideal Candidate Traits

• Structured thinker who can move from ambiguity to clear requirements quickly.
• Strong facilitator who earns trust across technical and non-technical stakeholders.
• Detail-oriented and rigorous, with high standards for requirement quality and traceability.
• Commercially aware and contract-literate, able to separate must-haves from nice-to-haves.
• Comfortable challenging assumptions while staying collaborative, objective, and outcome-focused.

Success Indicators

• Requirements are complete, testable, and approved without repeated rework cycles.
• User stories, personas, and process maps are current and actively used by delivery teams.
• Scope ambiguity decreases over time and change requests are intentional, not reactive.
• Producers and stakeholders can quickly explain what is being built, why, and how success will be measured.
• Decisions and assumptions are documented with clear traceability from business need to implementation.
• Delivered outcomes align to contractual obligations and agreed business value metrics.