Senior Business Analyst ID95136

Pereira, Colombia

WHY JOIN US

If you're looking for a place to grow, make an impact, and work with people who care, we'd love to meet you

ABOUT THE ROLE

We are looking for a Business Analyst to assess existing reporting and define a future-state reporting strategy and governance model across a broad stakeholder community.

MUST HAVES

• Strong business analysis and requirements-management experience of at least 4 years.
• Demonstrated ability to conduct stakeholder interviews and facilitate requirements workshops.
• Experience assessing and rationalizing an existing reporting or analytics portfolio.
• Strong ability to translate complex business needs into structured business and functional requirements.
• Experience developing process maps, requirements documentation, reporting inventories, and roadmaps.
• Strong analytical skills with an ability to identify duplication, gaps, inconsistencies, and opportunities for simplification.
• Ability to operate across business, technology, data, and risk stakeholders.
• Excellent written and verbal communication skills, including the ability to communicate effectively with senior stakeholders.
• Strong organizational skills and the ability to drive requirements through ambiguity and competing stakeholder priorities.

NICE TO HAVES

• Experience with management reporting, operational risk, technology risk, cybersecurity, vulnerability management, or other data-intensive operational environments.
• Experience with BI and other reporting platforms and familiarity with data governance concepts.
• Understanding of metric definitions, controls, data quality, lineage, and reporting governance.
• Experience establishing sustainable reporting operating models rather than solely delivering individual reports.

WHAT YOU WILL DO

• Develop a comprehensive inventory of existing reports, dashboards, metrics, and related reporting artifacts.
• Research historical reporting and prior requirements to understand the original business need, intended audience, and use cases.
• Assess existing reporting for relevance, duplication, usability, consistency, and continued business value.
• Identify reporting gaps as well as reports that may no longer serve a meaningful business purpose.
• Develop recommendations to retain, enhance, consolidate, replace, or decommission existing reporting.
• Identify the stakeholder groups and personas that consume, produce, or rely upon reporting.
• Conduct structured interviews and working sessions to understand business objectives, reporting needs, pain points, decision-making requirements, and desired outcomes.
• Translate stakeholder needs into well-defined business and functional requirements.
• Reconcile competing or overlapping requirements across stakeholder groups and establish a consolidated view of reporting demand.
• Maintain traceability between business needs, requirements, reports, metrics, and intended outcomes.
• Develop a target-state reporting portfolio based on stakeholder requirements and current-state findings.
• Define which reports should be created to address unmet business needs.
• Define which reports should be enhanced where existing reporting partially meets requirements.
• Define which reports should be consolidated where multiple reports address similar requirements.
• Define which reports should be retained where reporting remains effective and relevant.
• Define which reports should be decommissioned where reporting is obsolete, duplicative, or no longer creates sufficient value.
• Prioritize requirements based on business value, risk, stakeholder need, dependencies, and implementation considerations.
• Develop a roadmap that sequences reporting changes and enables an orderly transition from the current to future state.
• Establish clear ownership and accountability for reports, metrics, data sources, and business requirements.
• Define standards for requirements documentation, report definitions, business logic, data lineage and supporting metadata, where applicable.
• Establish a sustainable process for managing changes to reports and reporting requirements.
• Define periodic review cycles to reassess usage, relevance, accuracy, stakeholder needs, and opportunities for improvement.
• Establish criteria and governance for report retirement so that the reporting portfolio does not continually grow without rationalization.
• Maintain a reporting catalog that provides transparency into available reporting, ownership, purpose, audience, and status.
• Regularly engage stakeholders to determine whether reporting continues to support business and management decision-making.<